ci-convergencelisted
Install: claude install-skill SenjuWoo/Ultimate-AI-Starter-Bundle
# CI convergence
The authoritative unit is the **pushed SHA** and every required check attached
to that exact SHA. Local green is necessary, never sufficient; never substitute
the latest run for the required checks of the pushed SHA.
## One lifecycle
Local change -> full local gate -> commit -> push to main -> exact-SHA CI -> pass
-> build/tag/publish that SHA (automated where a release workflow exists) ->
download and verify shipped bytes. Put changelog/version in the commit that is
the release; query security after every push and before publication.
`release-checklist` owns packaging/publication mechanics; this skill owns convergence.
Run `powershell -NoProfile -ExecutionPolicy Bypass -File TOOLS/Wait-External.ps1 -GitHubRun auto -Repo OWNER/REPO -Sha FULL_SHA`.
It reads workflows, check-runs, commit statuses and the checks rulesets or
classic protection require; polling and logs are bounded.
| Verdict | Exit | Action |
|---|---|---|
| pass | 0 | Every required check reached a terminal successful state; release only that green SHA. |
| fail | 1 | Inspect the failing job/status; fix the cause, push a NEW SHA, re-converge. |
| pending | 8 | Wait to timeout, then report the URL; never tag. |
| none | 2 | NO CI RAN. Do not release. Push or dispatch the supported CI. |
| unknown | 3 | Report command, bounded stderr and what settles it; never tag. |
A gh error is not a red check: missing gh, auth, bad IDs, rate limits, network
and unreadable polic