@sjawhar/pi-legion 8.11.0 → 8.13.0

package/dist/legion.js

@@ -15244,7 +15244,7 @@ function onEnvoyRoleRegained(listener) {
 // package.json
 var package_default = {
   name: "@sjawhar/pi-legion",
-  version: "8.11.0",
+  version: "8.13.0",
   license: "Apache-2.0",
   type: "module",
   omp: {

package/dist/skills/legion-controller/SKILL.md

@@ -1,14 +1,14 @@
 ---
 name: legion-controller
-description: Use when handling Legion controller wakes for root-issue triage, keeping the admission slots full from `todo` issues, the daily report, architect escalation, or human interaction.
+description: Use when handling Legion controller wakes for weekly-plan ranking, backlog stewardship, root-issue triage, keeping the admission slots full from `todo` issues, the daily report, architect escalation, or human interaction.
 ---
 
 # Legion Controller
 
 The controller is the one persistent, wake-driven session for a Legion project. It keeps the
-project's admission slots full with the highest-priority work, and makes triage, escalation, and
-human-interaction judgments; it never does phase-worker work or routes raw events into an
-architect.
+project's admission slots full with the highest-priority work, keeps the weekly plan's order and
+owners current in Dispatch, and makes triage, escalation, and human-interaction judgments; it never
+does phase-worker work or routes raw events into an architect.
 
 ## Start and claim the controller role
 
@@ -25,6 +25,16 @@ alone: `op: "read_state"` returns the daemon's whole state (`issues.<KEY>.phase`
 `status` (`todo`, `backlog` or `icebox`) moves an issue. It never reads GitHub, and it runs no
 `legion` from bash.
 
+## Backlog stewardship
+
+The controller is the project's order keeper. It retains its startup role,
+`legion-<project>-controller`; `backlog-order` is retired. Send READY packets, scope questions,
+and routing requests to `notifications.role.legion-<project>-controller`, then follow
+[Backlog stewardship](skill://legion-controller/references/backlog-stewardship.md) for daily
+weekly-plan reconciliation, Sami's rulings, ownership routing, and stopped-session recovery.
+These duties change Dispatch's priority and board-rank data; they do not change the admission order
+in [Keeping the slots full](#keeping-the-slots-full-go-daemon).
+
 For an interactive takeover from a hand-started OMP session, start OMP with
 `LEGION_CONTROLLER_SECRET` (or `LEGION_CONTROLLER_SECRET_FILE`, a path to a file holding it),
 `LEGION_DAEMON_URL`, `LEGION_PROJECT` (the daemon's project) and `LEGION_STATE_DIR` in its
@@ -324,11 +334,15 @@ priority first, then board rank ([Keeping the slots full](#keeping-the-slots-ful
 
 - **Direct user message always first.** If this turn includes a direct user message, answer
   it before handling every other wake.
+- **Sami's rulings.** A direct Dispatch message from Sami is a ruling: after answering it, run
+  the full [Backlog stewardship](#backlog-stewardship) reconciliation and record the current rule
+  in the weekly plan.
 - **One wake = one turn.** Handle exactly the wake's implication, then end the turn. Never
   poll, idle-loop, or wait for another event. Two additions, after any direct user message: every
   turn first rechecks the [trees waiting on a root
   claim](#trees-waiting-on-a-root-claim-go-daemon), and your first turn of each UTC day, whatever
-  woke you, also posts the day's report ([Daily report](#daily-report-go-daemon)).
+  woke you, also runs the [Backlog stewardship](#backlog-stewardship) reconciliation and posts the
+  day's report ([Daily report](#daily-report-go-daemon)).
 - **Wakes are advisory.** Before any side effect, verify the current daemon state and the
   relevant Dispatch issue. A stale or duplicate wake may cost a read, never a wrong action.
 - **Controller state is disposable.** Do not reconstruct or preserve local controller

package/dist/skills/legion-controller/references/backlog-stewardship.md

@@ -0,0 +1,60 @@
+# Backlog stewardship
+
+The controller keeps the Dispatch backlog's facts aligned with the deployment's current weekly
+plan. The plan is the source of the work order and its one-owner map; Dispatch priority and board
+rank are the executable form of that order. The deployment instructions name the weekly-planning
+issue and its `plan-week-*` artifact.
+
+## Controller routing address
+
+The controller keeps its startup role, `legion-<project>-controller`; it never claims
+`backlog-order`, which is retired. Send READY packets, scope questions, and routing requests to
+`notifications.role.legion-<project>-controller`. Do not add another role claim or manual
+subscription: changing roles ends the controller's wake delivery.
+
+## Reconcile the weekly plan
+
+Run this pass on the first turn of every UTC day and after every ruling from Sami:
+
+1. Read the weekly-planning issue and select its newest `plan-week-*` artifact by its latest
+   `artifact.version` event. Read that artifact before changing any issue.
+2. For every current plan line in this deployment's project, make Dispatch's sort order exactly
+   match the line order: set the coarse priority and board rank together so the admission rule
+   (highest priority, then board rank) produces the plan's order. Keep each line's own stated
+   sequence. Do not invent a second order from a title, a stale route, or an instruction.
+   Reorder through Dispatch's board-rank API described in
+   `skill://dispatch/references/issues.md#board-rank-priority-and-assignee-on-a-read`.
+3. Reconcile the plan's one-owner map. For each listed owner, verify the named session is live.
+   For unowned work, find a suitable live owner with `envoy_sessions` filtered by `title` or `dir`,
+   route the issue to that exact session, and tell it what it owns. Do not change the human
+   `Assignee:` field: it controls who receives asks, not the working session.
+4. Rewrite the plan row with `dispatch doc-edit` guarded by the document token from the current
+   `dispatch doc-read`. The artifact states the current rule; replace superseded text instead of
+   keeping a change log in it. A comment or message does not update the one-owner map.
+
+A ruling from Sami is a direct Dispatch message to this controller. Answer it first, carry out its
+scope or priority decision, then record the resulting current rule in the affected weekly-plan row
+(or its ruling section when it has no one line). Link the message when Dispatch gave it a reference.
+A ruling triggers the full reconciliation pass even when it appears to affect only one issue.
+
+## Answering controller deliveries
+
+Read every delivery to `notifications.role.legion-<project>-controller` against live Dispatch and
+daemon state. Answer scope questions from the weekly plan and deployment instructions. Route a
+request to the verified owner when it is not the controller's decision.
+
+Until the deployment's daemon arms READY pull requests, answer each READY packet with its current
+queue or hold outcome and route it to the live owner named by the deployment's rules. Never merge
+or use a GitHub credential from the controller. Once the daemon arms READY pull requests, the
+controller confirms the Dispatch record and leaves the arm to the daemon.
+
+## Recovering stopped-session work
+
+Treat a session route as stopped only after the owner audit's two `no_holder` reads at least ten
+minutes apart. Do not poll to create the second read; use the next normal controller wake. Confirm
+that no live owner is available with `envoy_sessions` before changing the issue.
+
+For work that the plan or its handoff says moves to Legion when its session stops, preserve its
+existing labels, add `legion`, then use `legion status <KEY> todo`. The label comes first: it is what
+lets the daemon admit the root. Do not apply that recovery to an issue already in an active Legion
+tree; its architect and daemon own its lifecycle. Update the weekly-plan owner row after the move.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sjawhar/pi-legion",
-  "version": "8.11.0",
+  "version": "8.13.0",
   "license": "Apache-2.0",
   "type": "module",
   "omp": {