Delivery wait

Run scripts/delivery_wait.py as a silent foreground child whenever a workflow must await external GitHub state. The harness passively waits for the command to finish; it must not simulate waiting with model heartbeats.

The caller supplies the repository, expected identity, absolute deadline, and an optional state path. The command reconciles any saved state with fresh GitHub state, waits while nothing relevant changes, and exits with one result. Use --json from workflow skills; human output is for direct terminal use. Skills default state files beneath gitignored .agent/waits/; another harness may supply any private state path through --state.

Invocation

wait <kind> --repo <owner/repo> --deadline <ISO 8601> [--interval <seconds>] [--state <path>] [--json] runs a foreground wait; inspect <kind> takes the same identity flags without --deadline, --interval, or --state. Each kind requires its own identity flags:

• checks-terminal: --pr <number>, --head <sha>, and one --check <name> per expected check context. Repeat --check for every context the caller needs; a run with no --check exits with an operational error instead of waiting.
• pr-merged: --pr <number> and --head <sha>.
• workflow-terminal: --run-id <id> and --head <sha>.
• tag-target: --tag <name> and --head <sha>.
• release-assets: --tag <name>, --head <sha>, and one --asset <name> per required asset.
• wake-at (wait only): --deadline alone.

There is no --checkpoint flag. The state path is --state, and the command derives a default path from the kind and identity when it is omitted.

Use inspect for a single authoritative delivery snapshot and wait for a foreground transition wait. Supported predicates are exact-head checks, pull-request merge, workflow completion, tag target, release assets, and an absolute wake time. A changed expected head or ref invalidates the wait instead of being followed silently. GitHub remains authoritative; checkpoints contain normalized identities and observations, no credentials, raw comment bodies, or raw API payloads.

The helper uses authenticated gh transport. GraphQL is primary. A REST fallback is used only when GraphQL is rate-limited and REST preserves the same fact, or when GitHub exposes the fact only through REST.