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

I0835

CI runs the structural performance checks

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
Milestone status
ACTIVE
Wave
5
Waiting on
Holds back
Behind it in all
1
Evidence
0 of 1
In the waySubjectDetail
issueI0822I0822 is not DONE
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 I0835

majordomus plan verify I0835

majordomus plan done I0835

What it is

Objective
Add the flatten-once case, the cache-equivalence case and bench --check with the CI profile to validate.yml, with the wall-clock thresholds conservative and the counters exact.
Why
A check that nobody runs is documentation.
Now
CI runs the suite, the generator check and shellcheck.
Wanted
The counters gate strictly; bench --check gates on gross regressions only; results are uploaded as an artifact.
Done when
unknown: the record declares no `completion`
Risk
GitHub runners are slower and noisier than a laptop; the CI profile has more warmup and wider thresholds, declared in the policy.

Acceptance

  • Case 26 proves the new steps are wired
  • A deliberately regressed baseline fails the workflow step locally
Validation
bash test/run.sh 26_ci_wiring
Evidence required
regression_refused
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
.github/workflows/validate.ymltest/cases/26_ci_wiring.sh
Not
Latency gates at millisecond precision
Depends on
Priority
p0
Profile
implementation
Parallel safe
false
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-09-05
Updated
2026-09-05
Started
unknown: the record declares no `started_at`
Verified
unknown: the record declares no `verified_at`
Completed
unknown: the record declares no `completed_at`

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.