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.

I0814 · M003 · p1 · wave 5

Give the worker a bounded slice of knowledge, not the knowledge base

donePull requests that name itClose

Add a knowledge section to `majordomus context`, selected deterministically from what the active task and issue already reference, capped by a profile toggle and an item limit, dropped before any immutable fact when the budget is short, and named under EXCLUDED whenever it is dropped or switched off.

Depends on
I0811
Blocked by
none
Unblocks
I0815
Serves
none
Scope
lib/context.shshare/skeletonshare/allow/profile.txt.majordomus/profilesdocstest/cases
Evidence
1 of 1
Started
2026-10-16 08:10:20Z
Verified
2026-10-16 08:10:24Z
Completed
2026-10-16 08:10:32Z

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.