Two separate issues fixed together:
1. gitea-merge-queue.yml REQUIRED_CONTEXTS: CI workflow posts
"CI / Test / test (pull_request)" — the workflow triggers on
pull_request events so Gitea uses "(pull_request)" suffix (not
"(push)" as was previously documented).
2. ci.yml and release.yml path filters: the post-suspension sweep
renamed .github/workflows/ → .gitea/workflows/ but the path
filters inside both files still referenced .github/workflows/.
Corrected to .gitea/workflows/ so the CI actually runs on
subsequent PRs touching workflow files.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The workflow override set REQUIRED_CONTEXTS=CI / test (pull_request),
but Gitea's status API reports contexts as "CI / Test / test (push)"
for cron-triggered/scheduled runs. This mismatch caused the queue script
to always see the context as "missing" and never attempt a merge.
Fix: update REQUIRED_CONTEXTS to the live API-reported context name
"CI / Test / test (push)" and restore the SOP checklist gate context
(dropped when the workflow overrode the script defaults).
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>