PR Drain
Pull requests converging on master, one at a time.
Every open pull request as the integration lane assessed it: what it waits for, what would move it, what it depends on and overlaps, and the issue it carries.
- Issues ready86plan.status /counts/by_status/READY
- Issues active1plan.status /counts/by_status/ACTIVE
- Issues blocked159plan.status /counts/by_status/BLOCKED
- Issues done161plan.status /counts/by_status/DONE
Issue
One issue of the plan, as the plan records it.
I2786 · test-evidence · p0 · wave 0
The published UI reads the evidence CI recorded, and a publication that would show tests as not run is refused
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.
- Depends on
- none
- Blocked by
- none
- Unblocks
- none
- Serves
- none
- Scope
.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.shand 2 more- Evidence
- 0 of 1
- Started
- not yet
- Verified
- not yet
- Completed
- not yet
plan.issues0 msAPI/api/v1/plan/issuesMCPmajordomus_plan_issuestechnical view
Pull-request drain
The integration lane asks the forge for every open pull request; this takes a while and arrives after the screen.