@sjawhar/pi-legion-envoy 0.7.0 → 0.8.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 CHANGED
@@ -16,6 +16,18 @@ claimant.
16
16
  registry. Each reported interest identifies whether it is `live`, `registry`, or `both`, so
17
17
  temporary registration drift does not hide the extension's actual delivery state.
18
18
 
19
+ ## Inbound delivery
20
+
21
+ Pi renders every Envoy envelope through the shared `@legion/envoy-client/delivery` renderer. The
22
+ result is one TOON block with recognized routing and delivery fields such as `to`, `from`, `at`,
23
+ `id`, and `summary`; a structured `payload` appears once as `message`. Invalid JSON is represented
24
+ as a safe `unrecognised` value rather than exposed as raw bytes.
25
+
26
+ `envoy_inbox` returns the 50 most recent delivered envelopes as metadata (`event_id`, `at`, `from`,
27
+ and `summary`) for recovery after an interrupt. `envoy_role_get` returns the current holder and
28
+ last-seen timestamp for a role. `envoy_subscribe` reports listener warnings in both its text and
29
+ details result, including subscriptions whose stream currently has no matching event.
30
+
19
31
  ## Session identity
20
32
 
21
33
  Run `/whoami` to copy the active session ID to the clipboard. OMP copies through its host