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.

I2674 · development-runtime · p1 · wave 1

A node is provisioned as an S3 cache provider, idempotently, with no secret in the repository

blockedPull requests that name it Close

Provision a MinIO service on a chosen node: native or declared service, persistent storage on a bounded path, a private bucket with expiry, a least-privilege client identity, and a bounded bind.

Depends on: I2670
Blocked by: I2670
Unblocks: I2676
Serves: none
Scope: apps/majordomus-cli/src/capability/builtin/apps/majordomus-cli/src/mesh/build_cache/docs/BUILD_CACHE.md
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