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.

I0103 · M001 · p1 · wave 2

Implement the decision and prove it holds

donePull requests that name itClose

Make the chosen behaviour real in the question store and the blocker gate, and turn the characterisation case from I0101 into a case that fails when the behaviour is removed.

Depends on
I0102
Blocked by
none
Unblocks
I0104
Serves
none
Scope
lib/question.shlib/check.shtest/cases
Evidence
1 of 1
Started
2026-09-04 07:05:35Z
Verified
2026-09-04 07:32:11Z
Completed
2026-09-04 07:32:14Z

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.