@sjawhar/pi-envoy 16.38.0 → 16.38.1
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/README.md
CHANGED
|
@@ -278,7 +278,7 @@ messages; with Envoy on and no NATS server, or with its NATS seed refused (a see
|
|
|
278
278
|
other servers, a failing `natsSeed` command, a seed variable that cannot be read), it keeps the
|
|
279
279
|
tools and `/whoami`, takes no inbound messages, connects to no NATS server, and refuses
|
|
280
280
|
`envoy_subscribe` and the Legion role claim with `inbound messages are off for this session: <why>`,
|
|
281
|
-
the claim before any listener call, so a Legion process
|
|
281
|
+
the claim before any listener call, so a Legion process stops rather than hold a role
|
|
282
282
|
whose tasks reach nobody. When a
|
|
283
283
|
section is off for a reason worth saying, the session says so once at its start:
|
|
284
284
|
`envoy: no envoy.json at <path>: Dispatch and Envoy are off`, the lost `DISPATCH_URL` when
|
package/dist/envoy.js
CHANGED
|
@@ -42680,7 +42680,7 @@ var import_nats2 = __toESM(require_mod4(), 1);
|
|
|
42680
42680
|
|
|
42681
42681
|
// package.json
|
|
42682
42682
|
var name = "@sjawhar/pi-envoy";
|
|
42683
|
-
var version2 = "16.38.
|
|
42683
|
+
var version2 = "16.38.1";
|
|
42684
42684
|
var package_default = {
|
|
42685
42685
|
name,
|
|
42686
42686
|
version: version2,
|
|
@@ -80,4 +80,4 @@ Every topic starts with `notifications.`.
|
|
|
80
80
|
- A message that must reach more than 4 role topics is the project controller's to send, not yours. Each publish wakes a session, and a woken session reads its whole context again, which the provider charges as uncached input: a mean of 576,083 tokens a wake, a median of 493,636 and a ninetieth percentile of 1,327,888. The controller is also the one session that can read whether a wave of wakes is already running, and a fan-out sent into a daemon restart or a pod roll is what puts an Anthropic organization over its per-minute uncached-input cap. Send the controller the topics and the text, and it sends them at its own rate (`skill://legion-controller`).
|
|
81
81
|
- For a team, the group subscribes to `notifications.team.<name>.>`, and any member publishes to `notifications.team.<name>.all`. Envoy treats any other `notifications.` topic that no source in the table uses the same way. It reaches every session subscribed when it is published, yours too when you subscribe. The listener also asks each other session that holds its own NATS connection and registered the topic (every session that follows it with `envoy_subscribe`) to confirm the message; your own session is never asked. A publish returns an error naming each such session that did not confirm within about 4 seconds, and you see it after about 8 seconds, because the client tries once more. A session named with `receipt_timeout` still gets the message: the listener kept a copy in that session's inbox, which the session reads back once its connection returns. An `unresponsive` session is sent the message the same way, asked for no receipt and named under `unresponsive` in the answer, which is no failure. A session that stopped without unregistering stays in the registry until the reaper finds it `gone`, and is named until then; a named session is not a failed delivery to the others. A team topic is not kept for a session that subscribes later. A topic outside `notifications.` is refused.
|
|
82
82
|
- How a role claim survives a resume, a fork or a dead process: `skill://envoy/references/roles.md`.
|
|
83
|
-
- In a Legion pane, the plugin claims your role at session
|
|
83
|
+
- In a Legion pane, the plugin claims your role for you, at your session's first turn; read `skill://envoy/references/legion.md` before you claim, release or publish to a role, or answer a role delivery failure there.
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
Read this in a Legion pane before you touch a role claim, or when a Legion role message fails.
|
|
4
4
|
|
|
5
|
-
- The Legion plugin claims your assigned role
|
|
5
|
+
- The Legion plugin claims your assigned role for you, through a daemon-minted role token: it registers your session and reports it ready at session start, and takes the role at your first turn, or at a bound (30 s by default) when no turn comes first. Never call `envoy_role_set` and never subscribe to your role topic yourself, because the claim is already made (`packages/pi-shared/src/legion-claim-core.ts`).
|
|
6
6
|
- Never build a role token from an issue number or title: only the daemon maps tokens to issues.
|
|
7
7
|
- A Legion claim is last-claim-wins. It survives parking and worker re-creation, and stays through the issue's linger after close (the deployment's `linger_hours`).
|
|
8
8
|
- `no_holder`, `holder_lapsed`, `delivery_failed` and `receipt_timeout` on a Legion role are the daemon's liveness signals. Never add a second subscriber or retry by hand: the daemon revives or recreates the worker and re-delivers, or relaunches the root process, which gets a `catch-up` notice of its tree and reads each issue's handoffs on its Dispatch issue (`dispatch handoff-read`).
|