potiuk commented on PR #541: URL: https://github.com/apache/airflow-steward/pull/541#issuecomment-4814983358
Rebased this onto current `main` and folded in a spec-sync commit — heads-up on what changed. **Rebase:** one conflict, in `docs/labels-and-capabilities.md` (capability-to-skill map). `main` had added the `release-verify-rc` and `release-promote` rows; this PR adds `release-keys-sync`. Kept all three. **Spec-sync pre-check** (per the [#583](https://github.com/apache/airflow-steward/pull/583) `AGENTS.md` convention): #540 merged in the meantime (specs were at 5/10 shipped), so this PR's `release-keys-sync` makes it **6/10**. Folded into a second commit: - **`release-management-lifecycle.md`** — `release-keys-sync` moved proposed → shipped (now **6 shipped / 4 proposed**); added to the Skills inventory (Step 3, `mode: Drafting`, with the "never holds or reads the private key" boundary), the source note, and the validation block. - **`overview.md`** — release-management line now "6 of 10 skills shipped". - **`.last-sync`** — bumped to the current `main` tip. **Verified:** `spec-validate` (OK, no violations) and `skill-and-tool-validate` (exit 0 — the new capability-map row matches the skill's declared `capability:resolve`). Nice work on the ASF-strength-floor validation in the eval cases. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
