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
I2786
The published UI reads the evidence CI recorded, and a publication that would show tests as not run is refused
Where it stands
devtask.issue- Readiness
- ready no dependency and no gate holds it; nobody has started it
- Status
- READY
- Can start
- startable
- Milestone
- Milestone status
- ACTIVE
- Wave
0- Waiting on
- none
- Holds back
- none
- Behind it in all
0- Evidence
0of1
Moves
plan.transitionWhat it is
- Objective
- Give the Pages workflow's UI snapshot job the ledger the validation of the published commit, or of its nearest validated ancestor, recorded (scripts/pages evidence --ledger-out), before the UI is read; then refuse to publish when evidence.report still counts more not-run claims than .ai/repo/evidence/published-not-run.txt declares (scripts/pages published-evidence); with the rule, a case and the documentation.
- Why
- On 2026-10-16 the owner saw https://majordomus.dev/ui/kiosk/ show 154 test claims as not run. The validation of the same commit had recorded 606 executions in its evidence artifact; the snapshot read the tracked ledger, which holds fourteen local runs because the recording branch (ADR 0080, I1954) is not built. Over that artifact the report reads 235 proven and 0 not run.
- Now
- The ui-snapshot job reads the tracked ledger alone, and nothing counts what a publication shows as not run.
- Wanted
- The ui-snapshot job puts the run's ledger in place and refuses a publication whose not-run count exceeds the declared baseline of 0.
- Done when
- unknown: the record declares no `completion`
- Risk
- unknown: the record declares no `risk`
Acceptance
- scripts/pages evidence --ledger-out puts the run's ledger in place only for an artifact of the published history
- scripts/pages published-evidence exits 10 over the baseline, 0 within it, 12 when the report or the baseline cannot be read
- The published kiosk shows no claim as not run that CI ran
- Validation
majordomus plan validatebash test/run.sh 3178_the_published_ui_reads_the_evidence_ci_recordedbash test/run.sh 357_ci_records_evidence- Evidence required
case_3178- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
.github/workflows/pages.ymlscripts/pages.ai/repo/evidence/published-not-run.txt.ai/repo/rules/project/published-evidence-is-what-ci-recorded.v1.md.ai/repo/adrs/0087-evidence-is-indexed-by-subject-and-judged-at-the-presented-revision.mdtest/cases/3178_the_published_ui_reads_the_evidence_ci_recorded.shdocs/EVIDENCE.mddocs/MAJORDOMUS_UI.md- Not
- unknown: the record declares no `non_scope`
- Depends on
- none
- 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-10-17
- Updated
- 2026-10-17
- 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.