A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:01:48Z by majordomus 0.29.0. Nothing on this page is read again. See it live
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.
I2303 · test-evidence · p0 · wave 0
A release publishes its metadata to the site before its record lands, and the site never goes back a release
Make majordomus.dev serve a release's releases/latest.json and releases/<tag>.json from the release run itself, minutes after its archives are published, instead of after its record's pull request has passed its ci, without the site ever going back a release.
- Depends on
- none
- Blocked by
- none
- Unblocks
- none
- Serves
- none
- Scope
scripts/site-deploy.github/workflows/release.ymldocs/DISTRIBUTION.md.ai/repo/adrs/0131-a-release-publishes-its-metadata-before-its-record-lands.md.ai/repo/project/issues/I2303.yamltest/cases/1041_a_release_publishes_its_metadata.shand 6 more- Evidence
- 2 of 2
- Started
- 2026-10-14 08:00:25Z
- Verified
- not yet
- Completed
- 2026-10-14 08:00:34Z
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.