@sjawhar/pi-legion 10.19.11 → 10.20.0

package/dist/legion.js

@@ -14349,6 +14349,7 @@ var SESSION_ID_PATTERN = "[^/?#\\s\\p{Z}\\p{Cc}<>\"'`\\[\\]|]+";
 var sessionIdOnly = new RegExp(`^${SESSION_ID_PATTERN}$`, "u");
 // ../contracts/src/dispatch-tools.ts
 var ISSUE_REFERENCE = "An issue is a native KEY or external owner/repo#n reference. An external reference addresses an existing Dispatch issue, including one linked to that GitHub pull request; only dispatch issue with --external creates a native issue.";
+var BOARD_NEIGHBOUR_REFUSAL = "The server refuses a key that does not exist, one in another project, this issue itself, an empty value, and a pair the board does not hold in that order.";
 var OWNER_REFERENCE = "Exactly one of issue and project is required. An issue is a native KEY or external owner/repo#n reference; a project is a project key such as CORE and addresses an unlinked project document named by artifact.";
 var ASK_QUESTION_CONTRACT = "The question carries the problem the reader recognises and why it matters now, what constrains " + "the answer, and the recommendation with its reason. It asks how to solve the problem or which " + "outcome is wanted; never enumerate choices in the question.";
 var ASK_OPTIONS_CONTRACT = "Options carry the genuinely different approaches. Each option has a label, and its description " + "says what that approach costs.";
@@ -14388,7 +14389,7 @@ var commentValidation = {
   },
   message: `${commentOwner.message} turn requires reply_to_ask.`
 };
-var ISSUE_UPDATE_FIELDS_RULE = "Issue update requires at least one field besides issue: status, title, labels, priority, external_links, route, parent, blocked_by, components, or repo.";
+var ISSUE_UPDATE_FIELDS_RULE = "Issue update requires at least one field besides issue: status, title, labels, priority, external_links, route, parent, blocked_by, components, repo, before, or after.";
 var ISSUE_UPDATE_DONE_RULE = "status done requires reason, a non-empty note saying why the issue is closing, posted on the issue before it closes because a closed issue refuses messages, comments, and artifacts";
 var ISSUE_UPDATE_REASON_RULE = "reason goes only with status done";
 var ISSUE_UPDATE_RULE = `${ISSUE_UPDATE_FIELDS_RULE} ${ISSUE_UPDATE_DONE_RULE}; ${ISSUE_UPDATE_REASON_RULE}.`;
@@ -14402,7 +14403,7 @@ function issueUpdateProblem(value) {
     const status = typeof input.status === "string" ? `status ${input.status}` : "an update without status done";
     return `${ISSUE_UPDATE_REASON_RULE}: it is the note posted on the issue as it closes, and ${status} closes nothing. Drop reason, or set status done to close the issue.`;
   }
-  const changesAField = typeof input.status === "string" || typeof input.title === "string" || Array.isArray(input.labels) || typeof input.priority === "number" || input.priority === null || Array.isArray(input.external_links) || typeof input.route === "string" || typeof input.parent === "string" || Array.isArray(input.blocked_by) || typeof input.components === "object" && input.components !== null || typeof input.repo === "string";
+  const changesAField = typeof input.status === "string" || typeof input.title === "string" || Array.isArray(input.labels) || typeof input.priority === "number" || input.priority === null || Array.isArray(input.external_links) || typeof input.route === "string" || typeof input.parent === "string" || Array.isArray(input.blocked_by) || typeof input.components === "object" && input.components !== null || typeof input.repo === "string" || typeof input.before === "string" || typeof input.after === "string";
   return changesAField ? undefined : ISSUE_UPDATE_FIELDS_RULE;
 }
 var messageValidation = {
@@ -14487,10 +14488,10 @@ var dispatchToolSpecs = [
     name: "dispatch_issue_update",
     example: {
       issue: "DSP-1",
-      status: "done",
-      reason: "Shipped in owner/repo#7; verified on the production dashboard."
+      priority: 1,
+      before: "DSP-2"
     },
-    description: "Update an existing issue: move its lifecycle status, retitle it, replace its labels, set " + "its priority, link a URL (the pull request that delivers it, a run, a document), set its " + "route, set or clear its parent, replace the issues it is blocked by, attach it to " + "architecture components, or set the repository it targets. Status is one of " + `${ISSUE_STATUSES.join(", ")}; outside Legion, move it yourself as the work advances; inside ` + "Legion the daemon moves it. A non-empty external_links is " + "merged into the issue's existing links by URL, so linking the pull request you just opened " + "keeps every earlier link; an empty external_links removes every link instead. components " + "replaces the issue's own attachment. Closing an issue " + "(status done) requires reason, the note that says why: it is posted on the issue as a " + "message, then the issue closes, because a closed issue refuses messages, comments, and " + "artifacts; reason goes only with status done. A closed issue takes only rank, components, " + "a reopening status (any status but done), and an external_links write that adds no new " + "link (so a link can move to the issue that replaced it); everything else, priority " + "included, waits for the reopen. " + "priority is yours to set and a human overrides it; rank, the board's own order, is not " + "settable here. At least one " + `field besides issue is required. ${ISSUE_REFERENCE}`,
+    description: "Update an existing issue: move its lifecycle status, retitle it, replace its labels, set " + "its priority, link a URL (the pull request that delivers it, a run, a document), set its " + "route, set or clear its parent, replace the issues it is blocked by, attach it to " + "architecture components, set the repository it targets, or move it on its project's " + "board. Status is one of " + `${ISSUE_STATUSES.join(", ")}; outside Legion, move it yourself as the work advances; inside ` + "Legion the daemon moves it. A non-empty external_links is " + "merged into the issue's existing links by URL, so linking the pull request you just opened " + "keeps every earlier link; an empty external_links removes every link instead. components " + "replaces the issue's own attachment. Closing an issue " + "(status done) requires reason, the note that says why: it is posted on the issue as a " + "message, then the issue closes, because a closed issue refuses messages, comments, and " + "artifacts; reason goes only with status done. A closed issue takes only a board move " + "(before, after), components, " + "a reopening status (any status but done), and an external_links write that adds no new " + "link (so a link can move to the issue that replaced it); everything else, priority " + "included, waits for the reopen. " + "priority is yours to set and a human overrides it. before and after move the issue on " + "its project's board: before puts it above that issue, after below, and both together " + "land it between them. A project's board order is one agent's to keep; in a Legion " + "deployment that is the controller. At least one " + `field besides issue is required. ${ISSUE_REFERENCE}`,
     arguments: (z2) => ({
       issue: z2.string().describe(ISSUE_REFERENCE),
       status: z2.enum(ISSUE_STATUSES).describe("New lifecycle status.").optional(),
@@ -14503,7 +14504,9 @@ var dispatchToolSpecs = [
       parent: z2.string().describe("Parent issue key in the same project; an empty string clears the parent.").optional(),
       blocked_by: z2.array(z2.string({ min: 1 }), { max: MAX_ISSUE_BLOCKERS }).describe("Replacement list of issue keys in the same project this issue waits on; [] clears it. Dispatch refuses a dependency cycle.").optional(),
       components: componentsArgument(z2).optional(),
-      repo: z2.string().describe("The repository the issue targets, owner/name, mapped to the issue's project in Settings; an empty string clears it, so the issue inherits its parent's or the project's default again.").optional()
+      repo: z2.string().describe("The repository the issue targets, owner/name, mapped to the issue's project in Settings; an empty string clears it, so the issue inherits its parent's or the project's default again.").optional(),
+      before: z2.string().describe(`Move the issue above this issue on its project's board: an issue key in the same project. With after, the issue lands between the two. ${BOARD_NEIGHBOUR_REFUSAL}`).optional(),
+      after: z2.string().describe(`Move the issue below this issue on its project's board: an issue key in the same project. With before, the issue lands between the two. ${BOARD_NEIGHBOUR_REFUSAL}`).optional()
     }),
     validation: {
       check: (value) => issueUpdateProblem(value) === undefined,
@@ -16932,7 +16935,7 @@ async function bootLegionClaim(host2) {
 // package.json
 var package_default = {
   name: "@sjawhar/pi-legion",
-  version: "10.19.11",
+  version: "10.20.0",
   license: "Apache-2.0",
   type: "module",
   omp: {

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

@@ -59,7 +59,7 @@ 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.
+weekly-plan reconciliation, a person's rulings, ownership routing, and stopped-session recovery.
 These duties change Dispatch's priority and board-rank data and route plan work to a live session;
 they start nothing on Legion and hand it no issue ([Free slots](#free-slots-go-daemon)).
 
@@ -365,9 +365,9 @@ themselves: an issue reaches Legion only when a person hands it over
 
 - **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.
+- **A person's rulings.** A direct Dispatch message to this controller from a person 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

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

@@ -1,9 +1,9 @@
 # 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.
+plan. The plan is the source of the work order and its one-owner map; Dispatch board rank is the
+executable form of that order. The deployment instructions name the weekly-planning issue and its
+`plan-week-*` artifact.
 
 ## Controller routing address
 
@@ -14,16 +14,17 @@ 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:
+Run this pass on the first turn of every UTC day and after every ruling from a person:
 
 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`.
+2. For every current plan line in this deployment's project, make the project's board order match
+   the line order exactly: Legion admits waiting roots by board rank alone — unlike the ready order
+   an agent takes its own next issue by, which is priority, then board rank — so board rank is what
+   carries the plan's order. Set the coarse priority too, as the signal people and filters read; it
+   changes no order. Keep each line's own stated sequence. Do not invent a second order from a
+   title, a stale route, or an instruction. Reorder with
+   `dispatch issue-update --issue <KEY> --before <OTHER>` or `--after <OTHER>`.
 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. Routing hands the work to that
@@ -33,9 +34,10 @@ Run this pass on the first turn of every UTC day and after every ruling from Sam
    `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 from a person 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

package/package.json

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