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.
I2745 · truthful-plan-surfaces · p0 · wave 0
The landing page states no present it does not read
Replace every sentence in site/data/marketing.toml, manifesto.toml and homepage.toml that describes the current state of the product with a rendered datum from site/data/generated (release, plan figures, delivery, recent landings) or remove it, fix the link text that promises waves the roadmap does not show, and extend scripts/ci/homepage-check to refuse present-state vocabulary (today, not yet, nothing ... yet, no command ... today, is shipped) in those files.
- Depends on
- none
- Blocked by
- none
- Unblocks
- none
- Serves
- none
- Scope
site/data/marketing.tomlsite/data/manifesto.tomlsite/data/homepage.tomlsite/templates/index.htmlscripts/ci/homepage-checktest/cases/333_homepage_narrative.shand 1 more- Evidence
- 1 of 1
- Started
- 2026-10-16 09:56:46Z
- Verified
- 2026-10-16 10:26:57Z
- 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.