fix(ci): rename sop-checklist-gate→sop-checklist to match BP context

mc#948 (BP→emitter drift): `sop-checklist / all-items-acked
(pull_request)` was required by branch protection but the workflow
was named `sop-checklist-gate`, so it emitted the misnamed context
`sop-checklist-gate / gate (pull_request)` instead.

Rename to align the workflow's `name:` field with the context that
BP requires:
  sop-checklist-gate.yml → sop-checklist.yml
  sop-checklist-gate.py  → sop-checklist.py
  test_sop_checklist_gate.py → test_sop_checklist.py

New context emitted: `sop-checklist / all-items-acked (pull_request)`.

Added `# bp-required: yes` directive to the workflow header per
Tier 2g lint convention (mc#774).

All 52 script tests pass.

Closes #948.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

.gitea/scripts/review-check.sh

@@ -145,7 +145,7 @@ if [ -z "$PR_AUTHOR" ] || [ -z "$PR_HEAD_SHA" ]; then
 fi
 
 # --- RFC#324 §N/A follow-up: check N/A declarations status ---
-# sop-checklist-gate.py posts `sop-checklist / na-declarations (pull_request)`
+# sop-checklist.py posts `sop-checklist / na-declarations (pull_request)`
 # status when a peer posts /sop-n/a <gate>. If our gate is declared N/A,
 # the requirement for a Gitea APPROVE review is waived.
 NA_STATUSES_TMP=$(mktemp)

.gitea/scripts/sop-checklist.py

@@ -1,11 +1,11 @@
 #!/usr/bin/env python3
-# sop-checklist-gate — evaluate whether a PR has peer-acked each
+# sop-checklist — evaluate whether a PR has peer-acked each
 # SOP-checklist item. Posts a commit-status that branch protection
 # can require.
 #
 # RFC#351 Step 2 of 6 (implementation MVP).
 #
-# Invoked by .gitea/workflows/sop-checklist-gate.yml on:
+# Invoked by .gitea/workflows/sop-checklist.yml on:
 #   - pull_request_target: [opened, edited, synchronize, reopened]
 #   - issue_comment:       [created, edited, deleted]
 #

.gitea/scripts/tests/test_sop_checklist.py

@@ -1,8 +1,8 @@
 #!/usr/bin/env python3
-# Unit tests for sop-checklist-gate.py
+# Unit tests for sop-checklist.py
 #
-# Run:  python3 .gitea/scripts/tests/test_sop_checklist_gate.py
-#   or:  pytest .gitea/scripts/tests/test_sop_checklist_gate.py
+# Run:  python3 .gitea/scripts/tests/test_sop_checklist.py
+#   or:  pytest .gitea/scripts/tests/test_sop_checklist.py
 #
 # RFC#351 Step 2 of 6 — implementation MVP. Tests cover:
 #   - slug normalization (the 4 example variants in the script header)
@@ -33,7 +33,7 @@ sys.path.insert(0, PARENT)
 import importlib.util  # noqa: E402
 
 _spec = importlib.util.spec_from_file_location(
-    "sop_checklist_gate", os.path.join(PARENT, "sop-checklist-gate.py")
+    "sop_checklist", os.path.join(PARENT, "sop-checklist.py")
 )
 sop = importlib.util.module_from_spec(_spec)
 _spec.loader.exec_module(sop)  # type: ignore[union-attr]

.gitea/sop-checklist-config.yaml

@@ -111,7 +111,7 @@ items:
 # N/A gate declarations (RFC#324 §N/A follow-up).
 # PRs where a gate genuinely does not apply (e.g., pure-infra with no
 # qa surface, or docs-only) can be declared N/A by a non-author peer
-# who is in one of the gate's required_teams. The sop-checklist-gate
+# who is in one of the gate's required_teams. The sop-checklist
 # posts a `sop-checklist / na-declarations (pull_request)` status that
 # review-check.sh reads to skip the Gitea-APPROVE requirement.
 #

.gitea/workflows/review-refire-comments.yml

@@ -2,7 +2,7 @@
 #
 # Gitea 1.22 queues one run per workflow subscribed to `issue_comment` before
 # evaluating job-level `if:`. SOP-heavy PRs therefore created queue storms when
-# qa-review, security-review, sop-checklist-gate, and sop-tier-refire all
+# qa-review, security-review, sop-checklist, and sop-tier-refire all
 # listened to comments. This workflow is the single non-SOP comment subscriber:
 # ordinary comments no-op quickly; slash commands post the required status
 # contexts to the PR head SHA.

.gitea/workflows/sop-checklist.yml

@@ -1,4 +1,4 @@
-# sop-checklist-gate — peer-ack merge gate for SOP-checklist items.
+# sop-checklist — peer-ack merge gate for SOP-checklist items.
 #
 # RFC#351 Step 2 of 6 (implementation MVP).
 #
@@ -65,7 +65,9 @@
 # membership, compute, post status). Re-running on any event is safe —
 # the new status overwrites the previous one for the same context.
 
-name: sop-checklist-gate
+name: sop-checklist
+
+# bp-required: yes  ← emits sop-checklist / all-items-acked (pull_request)
 
 on:
   pull_request_target:
@@ -83,7 +85,7 @@ permissions:
   statuses: write
 
 jobs:
-  gate:
+  all-items-acked:
     # Run on pull_request_target events always. On issue_comment events,
     # only when the comment is on a PR (issue_comment fires for issues
     # too) and the body contains one of the slash-commands.
@@ -106,7 +108,7 @@ jobs:
           # qa-review.yml so the script source is always trusted.
           ref: ${{ github.event.repository.default_branch }}
 
-      - name: Run sop-checklist-gate
+      - name: Run sop-checklist
         env:
           GITEA_TOKEN: ${{ secrets.SOP_CHECKLIST_GATE_TOKEN || secrets.GITHUB_TOKEN }}
           PR_NUMBER: ${{ github.event.pull_request.number || github.event.issue.number }}
@@ -114,7 +116,7 @@ jobs:
           REPO_NAME: ${{ github.event.repository.name }}
         run: |
           set -euo pipefail
-          python3 .gitea/scripts/sop-checklist-gate.py \
+          python3 .gitea/scripts/sop-checklist.py \
             --owner "$OWNER" \
             --repo "$REPO_NAME" \
             --pr "$PR_NUMBER" \