deploy-watch

deploy-watch proves a merged change reached staging and works there, using only the CI deploy and the staging app's own URL. It stops at "ready for owner": production promotion, feature-flag rollout, and server access belong to someone else.

Inputs

• PR — number or URL; read gh pr view <pr> --json number,state,baseRefName,mergeCommit,mergedAt,closingIssuesReferences. Not merged → stop and suggest /factory.
• Staging branch — default staging, confirmed by git ls-remote. Accept a staging-base PR, or an authorized delivery-local PR when refreshed staging contains its merge SHA. Quote the ancestry check; other bases or absent ancestry stop. Production branches are forbidden.
• Deploy workflow — read its staging push trigger, deployment job, checkout revision and staging destination. A test-only workflow is not a deploy. Zero or ambiguous candidates → inspect handoff in step 6, then stop the deploy gate with missing routing evidence.
• Staging URL — from workspace instructions, the workflow environment URL, or the user; needed only for smoke. Missing → deploy-only result, smoke not run.
• Smoke checklist — the spec's integration-contract smoke gate when one exists; otherwise issue body criteria/checklist, or its newest standalone acceptance-criteria comment (legacy records remain readable), turned into 1–5 browser checks. Add checks for reproduced escape classes in the area, excluding not-a-regression; show missing criteria as smoke blocked. Show the checklist before running it.
• Smoke approval — explicit user approval this session plus user-provided SSH access, as the global staging rule requires; this skill uses neither SSH nor server commands. Missing either → watch GitHub only, smoke not run.
• Delivered issues — explicit tracker identifiers supplied by factory, otherwise canonical non-closing issue references and newest delivery records naming this PR. Inspect event-owned handoff through staging-handoff.md; ambiguity leaves handoff pending.

Rules