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.

I1988 · adopter-upgrades · p2 · wave 1

A use case's setup scripts live where the adopter declares, and its scenarios may run the adopter's own commands

readyPull requests that name itClose

Declare the use-case setup directory in the manifest instead of hard-coding this repository's test/fixtures/commands/setup, and allow a scenario step to run commands the adopter declares, judged by the same effect classes as I1981.

Depends on
I1981
Blocked by
none
Unblocks
none
Serves
none
Scope
lib/usecase.shshare/schemasshare/skeletondocstest/cases
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.