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.

I2721 · safe-self-update · p0 · wave 1

An enrolled mesh node follows the stable pointer by itself

blockedPull requests that name it Close

Make every node the mesh declaration enrolls keep its installation at the version releases/latest.json names, checking at server start, every 15 minutes with jitter and when the mesh announces a release, and applying through self update.

Depends on: I2720
Blocked by: I2720
Unblocks: none
Serves: none
Scope: apps/majordomus-cli/src/meshapps/majordomus-cli/src/commands/serve.rsapps/majordomus-cli/src/release.ai/repo/mesh/majordomus.yamlshare/schemasdocs/MESH.mdand 2 more
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.

Open the drain on its own page