@sjawhar/pi-envoy 11.2.0 → 11.4.0
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 +18 -1
- package/dist/dispatch.js +3830 -3758
- package/dist/envoy.js +6457 -4938
- package/dist/skills/dispatch/SKILL.md +4 -4
- package/dist/skills/dispatch-first/SKILL.md +2 -2
- package/dist/skills/dispatch-writing-specs/SKILL.md +5 -5
- package/dist/skills/envoy/SKILL.md +1 -1
- package/dist/skills/envoy/references/deliveries.md +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -16,7 +16,7 @@ a receipt-backed request with the original role topic to the holder's direct age
|
|
|
16
16
|
and it keeps open, listing them as kept, the subscriptions another plugin holds for that role.
|
|
17
17
|
The agent pump replies after accepting the envelope; without a receipt within two seconds the
|
|
18
18
|
listener emits a `delivery_failed` exception. Role messages are live only; they are not retained
|
|
19
|
-
for a later claimant.
|
|
19
|
+
for a later claimant, and a session does not recover one it missed.
|
|
20
20
|
|
|
21
21
|
`envoy_list()` shows the union of the local subscriptions and the listener's persisted interest
|
|
22
22
|
registry. Each reported interest identifies whether it is `live`, `registry`, or `both`, so
|
|
@@ -34,6 +34,23 @@ and `summary`) for recovery after an interrupt. `envoy_role_get` returns the cur
|
|
|
34
34
|
last-seen timestamp for a role. `envoy_subscribe` reports listener warnings in both its text and
|
|
35
35
|
details result, including subscriptions whose stream currently has no matching event.
|
|
36
36
|
|
|
37
|
+
A message published while the session's NATS connection or one of its subscriptions was down is
|
|
38
|
+
recovered from Envoy's notification stream, which keeps messages for 72 hours: the session asks
|
|
39
|
+
its listener (`POST /v1/replay`) for what the stream stored on its own agent subject and on each
|
|
40
|
+
topic it follows, after the place it last read to, and shows each missed message once, as a card
|
|
41
|
+
saying it was published while the connection was down. It asks after it reconnects, after a
|
|
42
|
+
subscription is reopened, when it starts or resumes, and on every heartbeat. A targeted Dispatch
|
|
43
|
+
delivery recovered this way (BTW, Aside, Steer, a person's Send) is shown as that card only and
|
|
44
|
+
runs nothing. Role messages and team or other ad-hoc topics are live only and are not recovered,
|
|
45
|
+
and neither is anything older than 72 hours, published before the session followed the topic, or
|
|
46
|
+
published before the session first ran this plugin. A message the session fails to show three
|
|
47
|
+
times is replaced by one card naming it and saying how to read it. The session file keeps what
|
|
48
|
+
it was shown and where it read to, so a restart skips nothing the stream still holds and shows
|
|
49
|
+
nothing again (up to 20,000 messages shown in 72 hours); a crash between showing a message and
|
|
50
|
+
recording it can show it twice, never lose it. Against a listener without the route, the session
|
|
51
|
+
warns once that missed messages are not recovered, and live delivery goes on as before. "Missed
|
|
52
|
+
messages" in `AGENTS.md` has the full rules.
|
|
53
|
+
|
|
37
54
|
## Session identity
|
|
38
55
|
|
|
39
56
|
Run `/whoami` to copy the active session ID to the clipboard. OMP copies through its host
|