@sjawhar/pi-legion-envoy 0.9.0 → 0.10.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.
Files changed (4) hide show
  1. package/README.md +17 -15
  2. package/dist/envoy.js +989 -885
  3. package/dist/legion.js +33392 -0
  4. package/package.json +5 -3
package/README.md CHANGED
@@ -45,8 +45,8 @@ set -g set-clipboard on
45
45
  This package declares two OMP extension entries in `package.json`: `extensions/envoy.ts`
46
46
  (Envoy messaging, subscriptions, and steering delivery) and `extensions/legion.ts` (the
47
47
  Legion lifecycle: root bootstrap, worker spawning, budgets, and daemon capabilities).
48
- Loading the package directory with OMP's `--extension` flag — as the Legion daemon does
49
- when it launches trees and workers — loads both.
48
+ `extensions/legion.ts` is inert without `LEGION_TREE`, `LEGION_ROLE`, or `LEGION_CONTROLLER`
49
+ set in the environment, so loading both alongside each other is safe for every session.
50
50
 
51
51
  For local development of the messaging extension alone, link the entry into OMP:
52
52
 
@@ -56,23 +56,25 @@ ln -sfn "$PWD/packages/pi-envoy/extensions/envoy.ts" \
56
56
  ```
57
57
 
58
58
  The repository root `package.json` likewise loads only `extensions/envoy.ts` for dev
59
- sessions inside this repo: the Legion extension is meant to be loaded by the daemon with
60
- its environment prepared, not by ambient dev sessions.
59
+ sessions inside this repo, since `legion.ts` needs nothing from a repo checkout beyond
60
+ what the installed package already ships.
61
61
 
62
62
  ## Published package
63
63
 
64
64
  Released installs come from npm as `@sjawhar/pi-legion-envoy`. The tarball is
65
- self-contained: it ships only `dist/envoy.js` — bundling every dependency except the
66
- OMP host package — and the repo `skills/` tree staged beside it at `dist/skills` so
67
- `resources_discover` serves the Legion skills from the installed package. The published
68
- manifest exposes only `dist/envoy.js` — matching the repository root — while the
69
- committed manifest keeps the TypeScript entries for repo checkouts; `extensions/legion.ts`
70
- is daemon infrastructure and is not packed at all.
71
-
72
- `.github/workflows/release-pi-envoy.yaml` performs that manifest rewrite around
73
- `bun pm pack` and restores the committed file before tagging. Packing with the committed
74
- source manifest is refused by `scripts/prepack.sh`, because such a tarball would point
75
- OMP at extension files it does not contain.
65
+ self-contained: it ships `dist/envoy.js` and `dist/legion.js` — bundling every
66
+ dependency except the OMP host package — and the repo `skills/` tree staged beside it
67
+ at `dist/skills` so `resources_discover` serves the Legion skills from the installed
68
+ package. The published manifest exposes both `dist/envoy.js` and `dist/legion.js`, while
69
+ the committed manifest keeps the TypeScript entries for repo checkouts. The Legion
70
+ daemon spawns every session against this one installed package instead of also loading
71
+ a repo checkout with OMP's `--extension` flag, so a daemon session ends up with exactly
72
+ one instance of each extension.
73
+
74
+ `.github/workflows/release.yaml` performs that manifest rewrite around `bun pm pack`
75
+ and restores the committed file before tagging. Packing with the committed source
76
+ manifest is refused by `scripts/prepack.sh`, because such a tarball would point OMP at
77
+ extension files it does not contain.
76
78
 
77
79
  ## Dispatch
78
80