Skip to content

Read at

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.

I1029 · capability-graph · p1 · wave 6

The gate refuses what would silently break the interface

blockedPull requests that name itClose

Put the drift check, the enforcement rules, the parity test, the browser checks and the public-data scan into the existing verification workflow, so that a change leaving any derived surface stale or unsafe cannot merge.

Depends on
I1021I1022I1023
Blocked by
I1021I1022I1023
Unblocks
I1030
Serves
none
Scope
.github/workflows/validate.yml
Evidence
0 of 2
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.