Skip to content
Cockpit0.29.0
A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I0012

Make CI refuse an invalid model or a stale projection

Where it stands

devtask.issue
Readiness
complete completion is recorded and every required evidence token is present
Status
DONE
Can start
not now
Milestone
Milestone status
DONE
Wave
7
Waiting on
none
Holds back
Behind it in all
1
Evidence
1 of 1
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I0012

majordomus plan verify I0012

majordomus plan done I0012

What it is

Objective
Add the model validation and the projection freshness check to the blocking CI job, with no advisory pass.
Why
A validator that runs only when somebody remembers is not enforcement.
Now
CI ran the suite, doctor, watch and the site data sync check.
Wanted
CI also runs plan validate and the offline GitHub projection check, and fails on either.
Done when
unknown: the record declares no `completion`
Risk
Low

Acceptance

  • plan validate runs in the blocking job and its exit code is not swallowed
  • The GitHub projection is checked offline against the canonical model
  • No new step requires network access to succeed
Validation
bash test/run.sh 26_ci_wiring
Evidence required
ci_test
Evidence present
ci_test

Scope

Touches
.github/workflows
Not
Any CI step that needs a GitHub token to pass
Depends on
Priority
p1
Profile
implementation
Parallel safe
true
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-09-04
Updated
2026-09-04T05:15:04Z
Started
2026-09-04T05:15:01Z
Verified
2026-09-04T05:15:02Z
Completed
2026-09-04T05:15:04Z

Synchronisation

Adapter
scripts/github-sync
Repository
unknown: the derived plan's header carries no repository
External issue
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.