@sjawhar/pi-legion 18.50.0 → 18.50.2
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 +2 -2
- package/dist/skills/legion-architect/references/merge-notices.md +6 -0
- package/dist/skills/legion-controller/SKILL.md +4 -4
- package/dist/skills/legion-controller/references/backlog-stewardship.md +8 -8
- package/dist/skills/legion-worker/references/withheld-capability.md +2 -2
- package/package.json +1 -1
package/dist/legion.js
CHANGED
|
@@ -8062,7 +8062,7 @@ function imagesArgument(z, owner) {
|
|
|
8062
8062
|
var ASK_URGENCIES = ["low", "med", "high", "blocking"];
|
|
8063
8063
|
var DISPATCH_BLOCK_UNITS = 32000;
|
|
8064
8064
|
var DISPATCH_ITEM_BLOCKS = 32768;
|
|
8065
|
-
var BODY_BLOCK_RULE = `Each block (a paragraph, list, quote, table or code block) holds at most ${DISPATCH_BLOCK_UNITS} ` + `characters and a body at most ${DISPATCH_ITEM_BLOCKS} blocks; Dispatch refuses a longer one and ` + "names it, and `dispatch limits` prints the bounds.";
|
|
8065
|
+
var BODY_BLOCK_RULE = `Each block (a paragraph, list, quote, table or code block) holds at most ${DISPATCH_BLOCK_UNITS} ` + `characters and a body at most ${DISPATCH_ITEM_BLOCKS} blocks; Dispatch refuses a longer one and ` + "names it, and `dispatch limits` prints the bounds. A body holding a decision block (`:::ask`) " + "is refused however short it is, since nobody can answer a question put in a comment or a " + "message: ask the question in the issue's own document, as a decision block there, or open an " + "ask with `dispatch ask`.";
|
|
8066
8066
|
var ASK_BOUND_RULE = "Dispatch bounds an ask's question and its options together, refuses a longer one and names " + "the bound, and `dispatch limits` prints it. An ask is short and asks one thing; its reasoning " + "goes in the document, not in the question.";
|
|
8067
8067
|
var DISPATCH_HANDOFF_BODY_MAX = 262144;
|
|
8068
8068
|
var HANDOFF_PHASE_PATTERN = /^[a-z][a-z0-9-]{0,31}$/;
|
|
@@ -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.
|
|
14340
|
+
version: "18.50.2",
|
|
14341
14341
|
license: "Apache-2.0",
|
|
14342
14342
|
type: "module",
|
|
14343
14343
|
omp: {
|
|
@@ -81,6 +81,12 @@ carries them — `close_root` answers `CLOSE_REASON_TOO_LONG` and `handoff_compl
|
|
|
81
81
|
`READY_PACKET_TOO_LONG`, each naming the bound and how far over the text is — so this notice is a
|
|
82
82
|
refusal those checks did not predict.
|
|
83
83
|
|
|
84
|
+
Those two calls also answer `CLOSE_REASON_DECISION_BLOCK` and `READY_PACKET_DECISION_BLOCK` for a
|
|
85
|
+
text holding a decision block (`:::ask{…}`). Such a text is refused however short it is, because
|
|
86
|
+
a question put in a message is one nobody can answer where it stands. The question belongs in the
|
|
87
|
+
issue's own document, as a decision block there, or in an ask opened with `dispatch ask`; the
|
|
88
|
+
close reason or the packet then goes again with the decision stated.
|
|
89
|
+
|
|
84
90
|
On a status write the daemon writes the status all the same, retrying it on the row's backoff
|
|
85
91
|
until Dispatch takes it, so the status is set unless Dispatch refused the status itself — the
|
|
86
92
|
reason says which. With the status set, only the reason beside it is on no issue: the issue's
|
|
@@ -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
|
|
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
|
-
|
|
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
|
|
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
|
|
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
|
|
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
|
|
45
|
-
its scope or priority
|
|
46
|
-
row (or its
|
|
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
|
|
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
|
|
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
|
|
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
|
-
|
|
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`,
|
|
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
|
|
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
|