@sjawhar/pi-envoy 13.13.1 → 14.0.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
|
@@ -382,8 +382,8 @@ gated write only when it consumes one, so a write sent any other way is refused
|
|
|
382
382
|
it when the ledger cannot take that line, and then posts it with a `dispatch: warning:` line.
|
|
383
383
|
Either way pi-envoy records an `advisor-gate` entry with outcome `unmarked`. A record that cannot
|
|
384
384
|
be read, or that names a store that is gone, is a refusal. A session no live record names needs
|
|
385
|
-
no marker: a terminal, CI, Claude Code,
|
|
386
|
-
|
|
385
|
+
no marker: a terminal, CI, Claude Code, a pod without pi-envoy, a session with no Dispatch and
|
|
386
|
+
one with `askgate.enabled: false`.
|
|
387
387
|
- **The cause note.** When a `bash` call outside the literal form holds a `dispatch` word and a
|
|
388
388
|
gated subcommand, and its result holds the CLI's refusal (or warn-mode warning) of a write with
|
|
389
389
|
no marker, the gate appends an `AskGate note:` to that result. It names the first cause it found
|
package/dist/dispatch.js
CHANGED
|
@@ -21023,8 +21023,7 @@ function neutralConfig(env) {
|
|
|
21023
21023
|
}
|
|
21024
21024
|
var HARNESS_DIRECTORY_VARIABLE = {
|
|
21025
21025
|
omp: "PI_CODING_AGENT_DIR",
|
|
21026
|
-
claude: "CLAUDE_CONFIG_DIR"
|
|
21027
|
-
opencode: "OPENCODE_CONFIG_DIR"
|
|
21026
|
+
claude: "CLAUDE_CONFIG_DIR"
|
|
21028
21027
|
};
|
|
21029
21028
|
var PLUGIN_HARNESSES = Object.keys(HARNESS_DIRECTORY_VARIABLE);
|
|
21030
21029
|
function namedDirectory(harness, env) {
|
|
@@ -21876,7 +21875,7 @@ function sourceSession(sessionID) {
|
|
|
21876
21875
|
var OK = 0;
|
|
21877
21876
|
var REFUSED = 1;
|
|
21878
21877
|
var USAGE = 2;
|
|
21879
|
-
var HOSTS = ["omp", "claude"
|
|
21878
|
+
var HOSTS = ["omp", "claude"];
|
|
21880
21879
|
var CLAUDE_OUTPUT_MAX = 25000;
|
|
21881
21880
|
var SAME_MESSAGE = "AskGate reviews the calls of a message before any of them runs, so it did not review that change.";
|
|
21882
21881
|
var STATE_WRITE_FAILED = "dispatch: Dispatch took the call, but this session's state";
|
|
@@ -21958,7 +21957,7 @@ async function runDispatchCli(argv, rawEnv, io) {
|
|
|
21958
21957
|
const hostName = env.DISPATCH_HOST ?? (env.CLAUDE_CODE_CHILD_SESSION === "1" ? "claude" : undefined);
|
|
21959
21958
|
const host = HOSTS.find((name) => name === hostName);
|
|
21960
21959
|
if (host === undefined) {
|
|
21961
|
-
return refuse(hostName === undefined ? "dispatch: DISPATCH_HOST is not set. The host plugin sets it in an agent's shell. From an agent's session, send the command as a bash call. To run dispatch by hand, set DISPATCH_HOST, and set DISPATCH_SESSION_ID to the id of your own session." : `dispatch: DISPATCH_HOST is ${JSON.stringify(hostName)}, not omp
|
|
21960
|
+
return refuse(hostName === undefined ? "dispatch: DISPATCH_HOST is not set. The host plugin sets it in an agent's shell. From an agent's session, send the command as a bash call. To run dispatch by hand, set DISPATCH_HOST, and set DISPATCH_SESSION_ID to the id of your own session." : `dispatch: DISPATCH_HOST is ${JSON.stringify(hostName)}, not omp or claude.`, USAGE, parsed.tool);
|
|
21962
21961
|
}
|
|
21963
21962
|
const sessionVariable = host === "claude" ? "CLAUDE_CODE_SESSION_ID" : "DISPATCH_SESSION_ID";
|
|
21964
21963
|
const sessionId = env[sessionVariable];
|
package/dist/envoy.js
CHANGED
|
@@ -33602,8 +33602,7 @@ function neutralConfig(env) {
|
|
|
33602
33602
|
}
|
|
33603
33603
|
var HARNESS_DIRECTORY_VARIABLE = {
|
|
33604
33604
|
omp: "PI_CODING_AGENT_DIR",
|
|
33605
|
-
claude: "CLAUDE_CONFIG_DIR"
|
|
33606
|
-
opencode: "OPENCODE_CONFIG_DIR"
|
|
33605
|
+
claude: "CLAUDE_CONFIG_DIR"
|
|
33607
33606
|
};
|
|
33608
33607
|
var PLUGIN_HARNESSES = Object.keys(HARNESS_DIRECTORY_VARIABLE);
|
|
33609
33608
|
function namedDirectory(harness, env) {
|
|
@@ -36923,7 +36922,7 @@ var envoyToolSpecs = [
|
|
|
36923
36922
|
},
|
|
36924
36923
|
{
|
|
36925
36924
|
name: "envoy_publish",
|
|
36926
|
-
description: `Publish an Envoy message to a notifications. topic. A role or built-in topic is delivered as its guide says; a role message errs when its holder did not confirm it within the listener's window. Any other notifications. topic you name (a team topic such as notifications.team.deploy-squad.all) reaches every session subscribed to it when you publish, and is not kept for a session that subscribes later. The listener confirms it with each other session that holds its own NATS connection and registered the topic, and errs naming each session that did not confirm; a session that stopped without unregistering stays registered for up to 5 minutes and is named in that time, and a named session is not a failed delivery to the other sessions. A session that holds its own NATS connection receives it directly, yours included; a session the listener delivers to over a serve port
|
|
36925
|
+
description: `Publish an Envoy message to a notifications. topic. A role or built-in topic is delivered as its guide says; a role message errs when its holder did not confirm it within the listener's window. Any other notifications. topic you name (a team topic such as notifications.team.deploy-squad.all) reaches every session subscribed to it when you publish, and is not kept for a session that subscribes later. The listener confirms it with each other session that holds its own NATS connection and registered the topic, and errs naming each session that did not confirm; a session that stopped without unregistering stays registered for up to 5 minutes and is named in that time, and a named session is not a failed delivery to the other sessions. A session that holds its own NATS connection receives it directly, yours included; a session the listener delivers to over a serve port is not confirmed and receives it through its machine's listener when that listener subscribes to every topic (ENVOY_SUBSCRIBE_ALL_TOPICS=1; the shared hub's listener does not). ${DELIVERY_CONTRACT}`,
|
|
36927
36926
|
arguments: (schema) => ({ topic: schema.string(), ...messageArguments(schema) }),
|
|
36928
36927
|
operation: EnvoyToolOperation.publish
|
|
36929
36928
|
},
|
|
@@ -37276,7 +37275,7 @@ var import_nats2 = __toESM(require_mod4(), 1);
|
|
|
37276
37275
|
|
|
37277
37276
|
// package.json
|
|
37278
37277
|
var name = "@sjawhar/pi-envoy";
|
|
37279
|
-
var version2 = "
|
|
37278
|
+
var version2 = "14.0.1";
|
|
37280
37279
|
var package_default = {
|
|
37281
37280
|
name,
|
|
37282
37281
|
version: version2,
|
|
@@ -41,7 +41,7 @@ Which machines, files or people, the numbers, then "A happens to X, or B to Y?"
|
|
|
41
41
|
|
|
42
42
|
## Issue status is yours to move
|
|
43
43
|
|
|
44
|
-
Outside Legion, claim your issue (`dispatch claim`) and move it and your children: `in_progress` at implementation, `testing` on a production-like surface, `needs_review` while its PR waits, `done` with `--reason` once driven in production. An issue with the `legion` label, or under one: never write its status or route it, and claim it only as a
|
|
44
|
+
Outside Legion, claim your issue (`dispatch claim`) and move it and your children: `in_progress` at implementation, `testing` on a production-like surface, `needs_review` while its PR waits, `done` with `--reason` once driven in production. An issue with the `legion` label, or under one: never write its status with `dispatch` or route it, and claim it only as a role of its tree, even when its claim reads `· not running`. An outside claim can take the tree out of the workflow. A status write is set back or stands.
|
|
45
45
|
|
|
46
46
|
A claim, or `dispatch issue-update --route session:<your id>` (`--route ''` on release), brings a person's answers, comments and messages; for agents' activity, `envoy_subscribe notifications.dispatch.issue.<KEY>.>`, which shows no event Dispatch marks quiet.
|
|
47
47
|
|
|
@@ -19,7 +19,7 @@ Part | Content
|
|
|
19
19
|
`Problem` | What goes wrong, for whom, with counts
|
|
20
20
|
`Goals and non-goals` | What is in and out of scope
|
|
21
21
|
`Requirements` | `**R1.**` on, each naming its source (`From:`)
|
|
22
|
-
`Design` | How it meets them; a value for each limit, size and time
|
|
22
|
+
`Design` | How it meets them; a value and its reason for each limit, size and time
|
|
23
23
|
`Decisions` | Your own choices
|
|
24
24
|
`Acceptance` | `**A1.**` on, each naming the requirements it tests
|
|
25
25
|
|
|
@@ -58,7 +58,7 @@ envoy:
|
|
|
58
58
|
It depends on where a session takes its deliveries, not on whether the topic is built in or your own.
|
|
59
59
|
|
|
60
60
|
- A session that holds its own NATS connection (every Oh My Pi session, and a Claude Code one) receives every message published on a subject it subscribes to, whoever sent it: its own publish included, and a subagent's publish to a topic the parent subscribes to. This holds for a topic the stream keeps and for a live team topic alike while it is connected. After an outage, once its connection or subscription is back, the session recovers from the stream what was published meanwhile on its own inbox and on each kept topic it follows, up to 72 hours back, and is shown each message once, marked as published while its connection was down. That includes a team topic it registered with the listener (every topic it follows with `envoy_subscribe`): the listener forwards each team topic message to the inbox of every session registered on it but the sender, and the stream keeps that copy. A team topic it subscribes to without registering it is gone for the outage.
|
|
61
|
-
- A session the listener delivers to by push, over a serve port
|
|
61
|
+
- A session the listener delivers to by push, over a serve port, does not receive its own publish, and receives a team topic only through the listener that owns it when that listener runs with `ENVOY_SUBSCRIBE_ALL_TOPICS=1` (the shared hub's listener does not).
|
|
62
62
|
- A role is not a subject its holder subscribes to: the listener finds the live holder and forwards the message to it, and drops the message when that holder is the message's source session.
|
|
63
63
|
|
|
64
64
|
## Listener API errors
|