pm-verify-release-v1

# pm-verify-release-v1, deployed build vs spec → acceptance evidence → feedback pack Input is a shipped scope: the cycle's handoff package directory and the tier it is deployed on. Output is a scenario-by-scenario verdict table with receipts, an acceptance report prepared **for** the owner, and a feedback pack that makes the next cycle smarter. **Completion is not acceptance.** This verb produces evidence. A named human owns the acceptance decision. This skill **never marks anything accepted, never flips a gate, and never softens a verdict to make a release look accepted.** **Posture: read-only everywhere.** Behavioural probes look; analytics probes query; nothing is written to any tier, flag, dashboard or repository. Where an engineering toolchain is configured, its run records are **inputs only**, never authored, never edited, never re-minted. ## Preflight (run first) ```bash PKG_ROOT="${CLAUDE_PLUGIN_ROOT:-${PKG_ROOT:-}}" [ -n "$PKG_ROOT" ] && [ -r "$PKG_ROOT/.claude-plugin/plugin.json" ] || { echo "STOP: set PKG_ROOT to this package's root directory, the one holding .claude-plugin/plugin.json, then re-run."; exit 2; } bash "$PKG_ROOT/scripts/preflight.sh" pm-verify-release-v1 [--stack <keys>] ``` A miss on a required capability blocks the run and prints its exact one-time fix. Conditional keys are passed once the scenario scope is assembled: `analytics-verification` (any analytics-touch scenario in scope) · `eng-handoff` (the downstream registry, for deployed coordi...