magpie-release-vote-tally

<!-- 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) <version> → release version string (e.g. 2.11.0) <rcN> → release candidate number (e.g. rc1) <version>-<rcN> → fully-qualified RC identifier (e.g. 2.11.0-rc1) <vote-list> → configured vote mailing list (e.g. dev@airflow.apache.org) <release-approver-roster> → path to the approver roster file (default <project-config>/pmc-roster.md for ASF) Substitute these with concrete values from the adopting project's <project-config>/release-management-config.md before running any command below. --> # release-vote-tally This skill tallies the votes (or equivalent approval signals) for an Apache-convention RC and drafts the `[RESULT] [VOTE]` email. It is Step 9 of the [release-management lifecycle](../../docs/release-management/process.md). The skill **never sends mail** and **never flips the planning-issue label** without explicit RM confirmation. Both the tally table and the `[RESULT] [VOTE]` draft are paste-ready artefacts; the RM reviews them, sends the email themselves, and applies the next label (`vote-passed`...