Preemptively incorporate mc#817 fix into the staging port of
sop-checklist-gate.yml. Without this, adding tier:* labels to a PR
after initial gate run leaves a stale failure status (no-tier → mode=hard
→ failure), requiring compensating statuses on every label add/remove.
Also closes mc#817 itself — same fix is PR #818 on main.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Bootstrap fix for mc#805 follow-up: adds the two missing Gitea
workflows + their runtime dependencies to the staging branch so that
`pull_request_target`-based CI and SOP gates fire for all staging PRs.
Changes:
- .gitea/workflows/ci.yml — copied from main; already targets staging
- .gitea/workflows/sop-checklist-gate.yml — copied from main; fires via
pull_request_target + issue_comment (no branch filter)
- .gitea/scripts/sop-checklist-gate.py — copied from main; required by
sop-checklist-gate.yml
- .gitea/sop-checklist-config.yaml — copied from main; config for the
SOP gate script
The ci.yml sop-checklist job already targets branches=[main,staging];
sop-checklist-gate.yml fires on all pull_request_target events. The
script dependency (sop-checklist-gate.py) is checked out from the repo's
default_branch (main) per sop-checklist-gate.yml's trust model.
Bootstrap note: this PR cannot self-validate via CI (the workflows
won't post status checks until the PR is merged). Compensating statuses
must be posted manually:
POST .../statuses/{sha} {"state":"success","context":"CI / all-required (pull_request)"}
POST .../statuses/{sha} {"state":"success","context":"sop-checklist / all-items-acked (pull_request)"}
Refs: mc#805 (bootstrap paradox — same fix pattern as PR #802 for staging)
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>