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.

I0915 · fly-deployment · p0 · wave 5

Deployment joins the diagnostics that already exist

cancelledPull requests that name itClose

Add the deployment checks to the health and doctor architecture the repository already has, so that the answer to whether a deployment can succeed comes from the same diagnostic surface as every other verdict.

Depends on
I0914
Blocked by
I0914
Unblocks
I0925
Serves
none
Scope
apps/majordomus-cli/src/deploy/doctor.rs
Evidence
0 of 3
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.