@sjawhar/pi-legion 18.50.1 → 18.50.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/legion.js CHANGED
@@ -14337,7 +14337,7 @@ import { logger as logger3 } from "@oh-my-pi/pi-utils";
14337
14337
  // package.json
14338
14338
  var package_default = {
14339
14339
  name: "@sjawhar/pi-legion",
14340
- version: "18.50.1",
14340
+ version: "18.50.3",
14341
14341
  license: "Apache-2.0",
14342
14342
  type: "module",
14343
14343
  omp: {
@@ -15803,12 +15803,13 @@ var operation = (op, shape) => strictObject({ op: literal(op), ...shape }, {
15803
15803
  error: (issue) => issue.code === "unrecognized_keys" ? issue.keys.map((key) => `${op} does not accept field "${key}"`).join("; ") : undefined
15804
15804
  });
15805
15805
  var PhaseOpArguments = discriminatedUnion("op", [
15806
- operation("read_record", { issue: requiredString("read_record", "issue") }),
15806
+ operation("read_record", { issue: string2().optional() }),
15807
15807
  operation("read_release_records", {
15808
15808
  since: windowStart
15809
15809
  }),
15810
15810
  operation("handoff_complete", {
15811
15811
  summary: requiredString("handoff_complete", "summary"),
15812
+ issue: string2().optional(),
15812
15813
  verdict: _enum(["pass", "pending", "fail"], {
15813
15814
  error: "handoff_complete's verdict is pass, pending or fail"
15814
15815
  }).optional(),
@@ -15851,7 +15852,7 @@ function phaseOpParameters(zod) {
15851
15852
  return byField;
15852
15853
  }
15853
15854
  var PHASE_OP_SENTENCES = {
15854
- readRecord: "read_record returns the record of `issue` from the daemon's state. ",
15855
+ readRecord: "read_record returns the record of `issue` from the daemon's state, your own issue when you leave `issue` out. ",
15855
15856
  readReleaseRecords: "read_release_records returns this deployment's idle-release records from `since` (an RFC 3339 time) on, read with this session's own claim: " + "every release, resume and hold the daemon recorded, and over them the counts of releases, of the releases among them that suspended no " + "role, of resumes by wake kind and of holds by reason, the pod-hours released, the share of releases woken again within ten minutes, and " + "the median, 90th percentile and maximum seconds from a wake to the woken role's first turn. A release that suspended no role is woken by " + "nothing, so the pod-hours released and the woken share count the releases that suspended a role alone. ",
15856
15857
  requestBackwardMove: "request_backward_move returns an issue to an earlier phase (`to`, `reason`): a phase worker moves its own issue; " + "the tree's architect moves an issue in accepting, named by `issue`, back to implementing or testing, which counts a review round. "
15857
15858
  };
@@ -15889,12 +15890,19 @@ async function executePhaseOp(runtime, input) {
15889
15890
  }
15890
15891
  const args = parsed.data;
15891
15892
  switch (args.op) {
15892
- case "read_record":
15893
- return { record: recordFrom(await daemon.state(), args.issue) };
15893
+ case "read_record": {
15894
+ const issue = args.issue !== undefined && args.issue.trim() !== "" ? args.issue : claim.issue;
15895
+ return { record: recordFrom(await daemon.state(), issue) };
15896
+ }
15894
15897
  case "read_release_records":
15895
15898
  return releaseRecords(runtime, args.since);
15896
- case "handoff_complete":
15899
+ case "handoff_complete": {
15900
+ const named = args.issue?.trim() ?? "";
15901
+ if (named !== "" && named !== claim.issue) {
15902
+ throw new Error(`handoff_complete reports this session's own issue ${claim.issue}; leave issue out, or name ${claim.issue}, not ${named}`);
15903
+ }
15897
15904
  return retryWhileDaemonRestarts("handoff_complete", () => completeHandoff(runtime, args), runtime.restart);
15905
+ }
15898
15906
  case "request_backward_move": {
15899
15907
  let issue;
15900
15908
  if (claim.role === "architect") {
@@ -16157,7 +16165,7 @@ function createLegionTool(deps) {
16157
16165
  label: "legion",
16158
16166
  description: legionToolDescription({
16159
16167
  envoyPublish: "envoy_publish",
16160
- before: PHASE_OP_SENTENCES.readReleaseRecords,
16168
+ before: PHASE_OP_SENTENCES.readRecord + PHASE_OP_SENTENCES.readReleaseRecords,
16161
16169
  after: PHASE_OP_SENTENCES.requestBackwardMove + "sign_off is the architect's acceptance of an issue in accepting, moving it to retro; the daemon refuses it in every " + "other phase (SIGNOFF_OUTSIDE_ACCEPTING) and while an issue beneath it is still in the workflow " + "(SIGNOFF_CHILD_IN_WORKFLOW, naming each one), since a parent's head proves its children's merged work: take each one " + "to done, or out of the workflow with park_child, and sign off again. close_root is refused the same way and with the " + "same code while an issue beneath the root is still in the workflow, since closing it would stop that work mid-turn. " + "release_children and rerun_child are refused for a child whose ancestor is in retro, merging or awaiting_merge " + "(CHILD_UNDER_ACCEPTED_PARENT, naming the ancestor), since that ancestor's approved head cannot carry work released " + "under it now: wait for the ancestor to close, then release it. " + "The controller's read_state returns the daemon's whole state and set_status moves an issue to todo, backlog or icebox. " + "fresh_session (issue, role) has one claim leave the session it runs in behind and start again in a new one: the daemon " + "stops the agent if it runs, forgets the session, and starts the claim, which loses everything that session held. A " + "phase worker that comes back owing no task is started through its issue's current phase, so it has that phase's work. " + "The answer is empty when the claim came back and nothing else is to be said, and names why nothing restarted the " + "phase (phaseNotRestarted) when the claim came back owing no task and the workflow refused that restart: the claim is " + "running, and no work was handed to it. " + "The daemon refuses it for a claim it records as working, which may be in a turn " + "(CLAIM_IN_A_TURN), for a claim left working over a process the daemon's last report " + "of it found gone, where no turn is running (CLAIM_IN_A_TURN as well), for a claim a " + "suspension is held over, in whatever state the hold found it (CLAIM_IN_A_TURN where " + "the claim is working, CLAIM_UNSETTLED where it is not), for a claim between states \u2014 " + "one queued, one whose launch is in flight, and one left working under a relaunch the " + "wake pacing parked (CLAIM_UNSETTLED) \u2014 and for role controller. " + "compact (issue, role) shortens one claim's session instead: the daemon has Oh My Pi write a text summary of the " + "session so far, and the claim keeps its session, its workspace and everything it knows of its issue and is sent " + "whatever task it owes again. Try compact before fresh_session for a claim that stays stuck. The answer says " + "whether the session was compacted and, when it was not, why; the claim is back either way. The daemon refuses " + "it for a claim that is suspended, failed or retired (CLAIM_NOT_RUNNING: fresh_session " + "reaches that one), for a claim it records as working, which may be in a turn " + "(CLAIM_IN_A_TURN), for a claim left working over a process the daemon's last report " + "of it found gone, where no turn is running (CLAIM_IN_A_TURN), for a claim a " + "suspension is held over (CLAIM_IN_A_TURN where the claim is working, CLAIM_UNSETTLED " + "where it is not), for a claim between states \u2014 one queued, one whose launch is in " + "flight, one whose agent has registered and is not ready yet, which fresh_session " + "reaches, and one left working under a relaunch the wake pacing parked " + "(CLAIM_UNSETTLED) \u2014 for a claim whose role runs on Claude Code (CLAIM_NOT_ON_OMP) " + "and for role controller. " + "Each refusal says what the claim does now and which operation reaches each state. It " + "names no moment to come back at: ask again later, and read the claim's state in " + "read_state. "
16162
16170
  }),
16163
16171
  defaultInactive: true,
@@ -14,7 +14,7 @@ except a clear defect a role reports ([Issues handed to Legion](#issues-handed-t
14
14
 
15
15
  - Handle no wake until the extension has registered this session with the daemon as the project's controller, at session startup or, in a controller an operator started, from its first command once Oh My Pi has started, because without that registration the daemon does not know you as its controller.
16
16
  - Answer a person's direct message first, in the conversation. A plain user turn that is neither the start message nor a task sent with `legion claims deliver` is a person writing from Dispatch's Agents page.
17
- - A direct Dispatch message that decides scope, priority or an owner is a ruling: after you answer it, run the weekly-plan reconciliation (`skill://legion-controller/references/backlog-stewardship.md`), because the plan must record the rule.
17
+ - A direct Dispatch message that settles scope, priority or an owner is a directive: after you answer it, run the weekly-plan reconciliation (`skill://legion-controller/references/backlog-stewardship.md`), because the plan must record the rule.
18
18
  - Handle one wake per turn, then end the turn. Never poll or wait for an event, because the daemon wakes you again (`tick` at least every `controller_wake_interval_seconds`).
19
19
  - Before any side effect, read `read_state` and the Dispatch issue, because a wake can be stale or sent twice.
20
20
  - Read a session's state from the Envoy registry, never from its absence from a list (`skill://envoy`). Start no replacement for an `unresponsive` session, take nothing from it, and never report it as gone, because it is working and keeps its claims.
@@ -98,7 +98,7 @@ Before you publish to more than one role topic, read whether a wave of wakes is
98
98
  The daemon works only issues carrying the Dispatch label `legion` (any case). Work reaches Legion
99
99
  by a person's decision: they set the label from the issue header, or ask you to (a direct
100
100
  message, a Slack request that asks Legion to do the work, their answer to a finding ask, or a
101
- ruling the weekly plan records with its link). The one exception is a clear defect a role hands
101
+ directive the weekly plan records with its link). The one exception is a clear defect a role hands
102
102
  you whose code no running tree owns: you file it with the label, because its fix is how to do work
103
103
  a person already wants, and humans decide what, agents decide how (the operator's answer on one
104
104
  such case: a clear defect is fixed, not asked about). A defect whose code a running
@@ -132,7 +132,7 @@ which branch to open the pull request against; nothing else carries that.
132
132
 
133
133
  A free slot is no reason to take an issue: a labelled root in `todo` takes the next slot through
134
134
  `admission.waiting` without you, and a parked issue (status `backlog` or `icebox`) means "do not
135
- run now". Move an issue out of `backlog` or `icebox` only on a request or a plan ruling that names
135
+ run now". Move an issue out of `backlog` or `icebox` only on a request or a plan directive that names
136
136
  it, and cite that request. A slot is one issue the daemon has started, a root or a child, not one
137
137
  tree: a tree of four started issues holds four slots. An issue takes its slot when the daemon
138
138
  starts it and keeps it
@@ -156,7 +156,7 @@ move to `todo` you make is one of these:
156
156
  gone, or because a person asks;
157
157
  - a tree you parked for a hold (`Parked by Legion while it waits on:`), once a person's decision
158
158
  gives it a next step (`skill://legion-controller/references/parked-decisions.md`);
159
- - stopped-session work that a person's ruling in the weekly plan moves to Legion.
159
+ - stopped-session work that a person's directive in the weekly plan moves to Legion.
160
160
 
161
161
  ## Findings, and the issues you file
162
162
 
@@ -13,7 +13,7 @@ reach you on `notifications.role.legion-<project>-controller`.
13
13
 
14
14
  ## Reconcile the weekly plan
15
15
 
16
- Run this pass on the first turn of every UTC day and after every ruling from a person:
16
+ Run this pass on the first turn of every UTC day and after every directive from a person:
17
17
 
18
18
  1. Read the weekly-planning issue and select its newest `plan-week-*` artifact by its latest
19
19
  `artifact.version` event. Read that artifact before changing any issue.
@@ -41,11 +41,11 @@ Run this pass on the first turn of every UTC day and after every ruling from a p
41
41
  instead of keeping a change log in it, because the artifact states the current rule. A comment
42
42
  or message does not update the one-owner map.
43
43
 
44
- A ruling from a person is a direct Dispatch message to this controller. Answer it first, carry out
45
- its scope or priority decision, then record the resulting current rule in the affected weekly-plan
46
- row (or its ruling section when it has no one line). Link the message when Dispatch gave it a
44
+ A directive from a person is a direct Dispatch message to this controller. Answer it first, carry out
45
+ its directive on scope or priority, then record the resulting current rule in the affected weekly-plan
46
+ row (or its directives section when it has no one line). Link the message when Dispatch gave it a
47
47
  reference.
48
- A ruling triggers the full reconciliation pass even when it appears to affect only one issue.
48
+ A directive triggers the full reconciliation pass even when it appears to affect only one issue.
49
49
 
50
50
  ## Answering controller deliveries
51
51
 
@@ -86,9 +86,9 @@ send it waits for it. Recover the work only from an owner that reads `gone`, or
86
86
  `unresponsive` with a `last_seen` more than 20 minutes old, which is as long as an issue claim is
87
87
  protected.
88
88
 
89
- For work that a ruling of a person's, recorded in the plan with its link (the ruling section
89
+ For work that a person's directive, recorded in the plan with its link (the directives section
90
90
  above), says moves to Legion when its session stops, preserve its existing labels, add `legion`,
91
- then set it `todo` with the `legion` tool's `set_status`. A plan row you wrote with no such ruling
91
+ then set it `todo` with the `legion` tool's `set_status`. A plan row you wrote with no such directive
92
92
  behind it moves nothing. The label comes first: it is what
93
93
  lets the daemon admit the root. Do not apply that recovery to an issue already in a live Legion
94
94
  tree (a root in `admission.trees`, or an issue whose `tree` is one); its architect and daemon own its lifecycle. Update the weekly-plan owner row after the move.
@@ -99,5 +99,5 @@ A person's `legion` label outranks a plan's deferral. The daemon queues the root
99
99
  person's label on an unrecorded root in `triage` is the root's `todo`, written by the daemon. A
100
100
  labelled root the weekly plan says to defer is parked by you at your next backlog pass, not
101
101
  before: `set_status` it to `backlog`, or to `icebox` for a longer deferral, and cite the plan's
102
- ruling in a comment on the issue. The cost is the architect's work between the daemon's `todo`
102
+ directive in a comment on the issue. The cost is the architect's work between the daemon's `todo`
103
103
  and your park.
@@ -5,10 +5,10 @@ unpack, extract or install anything the worker image does not carry. Every path
5
5
  cybermonklabs/legion.
6
6
 
7
7
  The withheld row reads `installs or configures its own dependencies in the pod: Legion owns its
8
- dependencies` (`packages/daemon/internal/capabilities/capabilities.go`, ruling
8
+ dependencies` (`packages/daemon/internal/capabilities/capabilities.go`, decision
9
9
  dispatch://LEGION-200). Read as a sentence on its own, that wording would also forbid `uvx`,
10
10
  `bunx --package` and `go run`, each of which fetches a package and writes a cache. It does not, and
11
- three artefacts in this repository are what draw the line — not a claim about what the ruling meant:
11
+ three artefacts in this repository are what draw the line — not a claim about what the decision meant:
12
12
 
13
13
  - **What the image ships for a role to use.** `packages/daemon/docker/worker.Dockerfile` installs
14
14
  `uv` and `uvx`, `bun` with its `bunx` link, and the Go toolchain, and the `toolchain` capability
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sjawhar/pi-legion",
3
- "version": "18.50.1",
3
+ "version": "18.50.3",
4
4
  "license": "Apache-2.0",
5
5
  "type": "module",
6
6
  "omp": {