Proposed GitHub required-check migration

Status: prepared for separate maintainer approval; no settings API writes, merge, or production action performed. This is the exact replacement for the historical 27 contexts in the baseline, under the approved design.

Remove each requirement below and require the one always-running Repository quality context. That aggregate waits for all seven parallel repository checks and rejects unsuccessful results. This is a removal/replacement map, not a claim that Repository quality executes all historical work: project-specific checks become optional in protection and must be reviewed before merge.

Also remove old Tool validation, Generator validation, Website validation, or historical proposed summary names only if they have subsequently been configured. They are not part of the baseline 27. Preserve unrelated security, review, environment and publication protections. Do not use a settings write to bypass unrelated requirements.

Coordinate the reviewed workflow merge and separately authorized settings change; this branch intentionally stops producing the legacy jobs and may wait for missing old checks until migration. Keep main’s functioning pair intact until transition. Inspect hosted check names, optional project failures, artifacts and main-push-only deployment gates before proceeding. Rollback restores the matching historical workflow graph and exact original required-context settings together. Neither local contract tests nor this document is approval to perform that operation.

Implementation verification

The project-workflow implementation at a22e0b5 passed task-level spec/quality reviews and a whole-branch review against the approved design. The existing isolated checkout was reused serially; unrelated local files were preserved.

Local verification passed 95 comprehensive root tests, including 94 contract-only tests and the separate model integration test; root/integration TypeScript; CLI build and 117 tests; formatting of 351 tracked inputs; Markdown lint of 78 tracked documents; code lint, spelling, documentation validation, Actionlint 1.7.12 and Zizmor 1.31.1 offline. Clean CI checkouts exclude the unrelated local notes that prevent broad local formatting/Markdown commands from passing.

The packed CLI passed all 11 behavior fixtures and locked default build/validation. The isolated template passed static quality, 44 canonical unit tests, build and validation, Chromium/WebKit checks, and all nine Lighthouse audits. The moved customization harness passed 39 unit tests and 26 Chromium checks with edited route/content/theme output. Inspected package artifacts and template source/build archive restoration were verified locally.

Local Rust is unavailable; native reproducibility and CMS execution require hosted validation. Firefox failed before assertions during macOS profile launch; Ubuntu Firefox remains enabled. New hosted runtime matrices, artifact service behavior and actual check contexts must be inspected after pushing this revision. Historical green workflow runs do not verify this architecture. No production effects, GitLab server execution or protection migration were performed.