Repository navigation
Re-add spec-alignment + capability-validation as required checks (#39 drifted) #511
Description
Summary
#39 asked to add spec-alignment and capability-validation as required checks and was closed completed (decision-log 28). The live ruleset traverse-governance-required-checks (id 18597008) still only requires:
cla / clabaseline / governance-baseline
Confirmed 2026-09-14 while reviewing how #487 merged. PR #487's capability-validation was green; it could have merged even if that job had failed. Post-merge push CV going red is a different (signature) issue; this ticket is only the ruleset drift.
This still conflicts with spec 001 SC-002.
Decided in the 2026-09-14 first-contributor-publish brainstorm (decision-log entry 113): honor decision 28 — require those two contexts. Do not add a required human review count (review-count stays 0).
Ask (owner action — rulesets are owner-controlled)
On traverse-governance-required-checks for main, add:
spec-alignmentcapability-validation
Leave cla / cla and baseline / governance-baseline in place.
Why now
Outside contributors are on the one-PR publish path (#485, #488, #489, #492). CLA + baseline alone is not enough once 1.0.0 is immutable.
Labels
no-spec-needed · needs-enrico
Activity
enricopiovesan commentedon Nov 4, 2026
Ruleset
traverse-governance-required-checks(18597008) now requiresbaseline / governance-baseline,cla / cla,spec-alignment, andcapability-validationon the default branch, per decision-log 28/113 (owner-approved 2026-11-04). Required review count unchanged at 0. Verified via the branch rules API. Main's push CI was green on the last three pushes before the change.