magpie-release-keys-sync

<!-- SPDX-License-Identifier: Apache-2.0 https://www.apache.org/licenses/LICENSE-2.0 --> <!-- Placeholder convention (see ../../AGENTS.md#placeholder-convention-used-in-skill-files): <project-config> → adopter's project-config directory path <upstream> → adopter's public source repo (e.g. apache/airflow) <project-dist-name> → project's dist name (e.g. airflow) <rm-uid> → Release Manager's UID string (e.g. "A. Smith <asmith@apache.org>") <fingerprint> → the RM's GPG key fingerprint (40 hex chars, no spaces) <keys-file-url> → configured keys_file_url value <keyserver> → configured keyserver value (e.g. keys.openpgp.org) <svn-keys-dir-url> → parent SVN directory URL containing the KEYS file (derived by stripping "/KEYS" from keys_file_url) Substitute these with concrete values from the adopting project's <project-config>/release-management-config.md before running any command below. --> # release-keys-sync This skill ensures the Release Manager's public GPG key appears in the project's KEYS file before RC artefacts are signed. It is Step 3 of the [release-management lifecycle](../../docs/release-management/process.md). The skill **never holds, reads, or proxies the RM's private key**, and **never commits to the SVN (or equivalent) repository**. Every command is a paste-ready recipe the RM runs under their own credentials....