Blocker: strict-23 rollout requires missing check integrations

[Prekzursil]

Blocker Summary

Strict-23 rollout is blocked in WebCoder under the no-bypass policy because required canonical contexts are not currently emitted on the latest evaluated commit.

• Evaluated ref type: pr
• Evaluated ref SHA: cf0b7569a1fa84b69f5b5a17764c5c4c404eeee4
• Contexts present: 7
• Missing canonical contexts: 18

Missing Canonical Contexts

• applitools-core
• pr-agent
• deep-agent
• audit-pr-evidence
• backend
• backend-postgres
• coverage
• codecov-analytics
• CodeRabbit
• dependency-review
• compose-smoke
• frontend
• label
• codacy-equivalent-zero
• sonar-branch-zero
• Seer Code Review
• Vercel
• Vercel Preview Comments

Evidence Commands

Run the following to reproduce:

gh api repos/Prekzursil/WebCoder/commits/cf0b7569a1fa84b69f5b5a17764c5c4c404eeee4/check-runs?per_page=100
gh api repos/Prekzursil/WebCoder/commits/cf0b7569a1fa84b69f5b5a17764c5c4c404eeee4/status
gh api repos/Prekzursil/WebCoder/branches/main/protection

Required External Setup (No Placeholder Checks)

• Install and enable required external providers/apps for this repo: Applitools, CodeRabbit, Seer Code Review, Vercel + Vercel Preview Comments, SonarCloud (where missing).
• Configure Codecov project linkage/auth (OIDC path with explicit slug Prekzursil/WebCoder).
• Configure Codacy coverage/status integration where missing.
• Keep strict hard-fail semantics and do not introduce bypass/placeholder-success contexts.

Stop Rule

Until the missing contexts are genuinely emitted and green on a PR head SHA, main-branch strict-23 branch-protection cutover must remain paused.