Red Team and specialist findings on #3495, all fixed in the diff:
- green gates on every check on the head, as gstack-ci-gate does, so
land-and-deploy Step 2 and Step 3 can no longer disagree while a
non-required check pends; required checks still gate before they appear
- --timeout MINUTES (default 60, 0 = none) ends a watch that met nothing as
PR_WAIT_BLOCKED naming the still-pending checks; restores Step 3's cap
- a bot owns logins that start with its name (greptile-apps[bot]), not any
login containing it; a failed gating-bot check is a failed check, never a
completed review
- ready: green alone when no gating bot is configured (pr_wait_gating_bots
none no longer polls forever); held while merge state is UNKNOWN
- BEHIND and DIRTY announced once per head, with the short head in the line
- the bin installs no signal handlers: the synchronous loop never ran them
and they made the process ignore SIGTERM/SIGINT; default disposition kills
it at once and the next watcher takes over the dead pid's lock
- a gh spawn timeout (ETIMEDOUT) is retried like any transient failure
- a local fault (unwritable state root) is PR_WAIT_REFUSED exit 2, so exit 1
always carries a PR_WAIT_BLOCKED line
- control characters in GitHub text never start a second event line
Tests: 21 new cases including a real SIGTERM against the bin, gstack-config
set-time validation and default parity, and the 14 state-matrix cells the
state-machines specialist listed (gstack-state-matrix check: ok, 33/33).
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
