chore: retrigger CI

Issue: molecule-core#1148 [ci-drift] (F3b finding).

The polling sentinel in `all-required` was missing `CI / Canvas Deploy
Reminder` from its `required:` list. Without this, a force-merge that
skipped the canvas-deploy-reminder check (e.g. the check was still
pending or failed) would not be flagged by the §SOP-6 force-merge audit.

The polling approach handles this correctly: the sentinel waits for all
required contexts to emit 'success' (or timeout), unlike the needs:-based
approach which could deadlock when canvas-deploy-reminder is skipped on
CI-only PRs (it needs canvas-build which is also skipped).

Also updated `audit-force-merge.yml REQUIRED_CHECKS` to include
`CI / Canvas Deploy Reminder (pull_request)`, ensuring the §SOP-6
audit evaluates this check at merge time.

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

.gitea/workflows/audit-force-merge.yml

@@ -54,5 +54,6 @@ jobs:
           # read-only by design (least-privilege).
           REQUIRED_CHECKS: |
             CI / all-required (pull_request)
+            CI / Canvas Deploy Reminder (pull_request)
             sop-checklist / all-items-acked (pull_request)
         run: bash .gitea/scripts/audit-force-merge.sh

.gitea/workflows/ci.yml

@@ -552,10 +552,11 @@ jobs:
     # required commit-status contexts for this SHA and fails if any fail, skip,
     # or never emit.
     #
-    # canvas-deploy-reminder is intentionally NOT included in all-required.needs.
-    # It is an informational main-push reminder, not a PR quality gate. Keeping
-    # it in this dependency list lets a skipped reminder skip the required
-    # sentinel before the `always()` guard can emit a branch-protection status.
+    # canvas-deploy-reminder is included in the polling list below. Unlike the
+    # needs:-based approach (which could deadlock when canvas-deploy-reminder is
+    # skipped on CI-only PRs since it needs canvas-build), the polling sentinel
+    # safely handles skipped/never-emitted status: it reports failure for any
+    # required context that is not 'success' within the timeout window.
     #
     continue-on-error: false
     runs-on: ubuntu-latest
@@ -587,6 +588,7 @@ jobs:
               f"CI / Detect changes ({event})",
               f"CI / Platform (Go) ({event})",
               f"CI / Canvas (Next.js) ({event})",
+              f"CI / Canvas Deploy Reminder ({event})",
               f"CI / Shellcheck (E2E scripts) ({event})",
               f"CI / Python Lint & Test ({event})",
           ]