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.

I1981 · adopter-upgrades · p0 · wave 0

A command's effect class is declared per subcommand and flag, and live scenarios judge the whole argv

donePull requests that name itClose

Declare read-only or state-mutating per subcommand and per flag in share/commands.yaml where a command has both, and make live use-case validation and runs judge the full argument vector against that declaration.

Depends on
none
Blocked by
none
Unblocks
I1988
Serves
none
Scope
share/commands.yamllib/usecase.shlib/commands.shdocs/CLI.mdtest/cases/359_live_scenarios.shtest/fixtures/commands
Evidence
4 of 2
Started
2026-10-11 05:05:14Z
Verified
2026-10-11 05:05:29Z
Completed
2026-10-14 07:39:39Z

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.