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

I1961

A deploy verifies the evidence routes it publishes

Where it stands

devtask.issue
Readiness
blocked 2 of its dependencies are not DONE
Status
BLOCKED
Can start
not now
Milestone
test-evidence
Milestone status
ACTIVE
Wave
5
Waiting on
I1959I1958
Holds back
none
Behind it in all
0
Evidence
0 of 1
In the waySubjectDetail
issueI1959I1959 is not DONE
issueI1958I1958 is not DONE

Moves

plan.transition
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 I1961

majordomus plan verify I1961

majordomus plan done I1961

What it is

Objective
Make pages-check probe the evidence routes a deploy published, deriving the probes from the published evidence-subjects.json rather than from a hand-written list.
Why
A route the build generated and the deploy lost is a badge that links nowhere. ADR 0087 names the deploy check as one mechanism against a badge verified for a revision it did not test.
Now
scripts/ci/pages-check verifies the published site and knows nothing of evidence routes.
Wanted
pages-check reads the published subject index and probes the evidence index, the first subject of each kind, coverage and runs, and refuses published evidence that does not name the deployed commit.
Done when
unknown: the record declares no `completion`
Risk
It also waits on PR #593.

Acceptance

  • The probes are derived from the published subject index, and a route missing from the deploy fails the check naming it
  • Published evidence that does not name the deployed commit is refused
Validation
bash test/run.sh 521_deploy_verifies_evidence_routes
Evidence required
deploy_verifies_evidence_routes
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
scripts/ci/pages-checkscripts/pages.github/workflows/pages.ymltest/casesdocs/CLAIMS.yamldocs/claims/deploy-verifies-evidence-routes.md.ai/repo/features/ci.md
Not
A hand-declared list of routes to verify
Depends on
I1959I1958
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-26
Updated
2026-09-26
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.