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.

I2677 · development-runtime · p2 · wave 2

The build cache is documented, governed by a rule and described on the site and the Pages

blockedPull requests that name it Close

Say once, derived, what the cache is, how a node offers and uses it and how to see it, on the handbook, the site and the landing's account of how the cluster compiles.

Depends on: I2672
Blocked by: I2672
Unblocks: none
Serves: none
Scope: docs/BUILD_CACHE.md.ai/repo/rules/project/site/
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.

Open the drain on its own page