@sjawhar/opencode-legion-envoy 1.31.2 → 1.32.0

package/dist/src/server.js

@@ -14231,6 +14231,12 @@ var stateTreeLocator = discriminatedUnion("runtime", [
   stateTmuxLocator.extend({ ompSessionFile: nonEmptyString.optional() }),
   stateK8sLocator.extend({ ompSessionFile: nonEmptyString.optional() })
 ]);
+var stateExternalControllerLocator = strictObject({
+  runtime: literal("kubernetes"),
+  external: literal(true),
+  sessionId: nonEmptyString,
+  registeredAt: number2().int().nonnegative()
+});
 var stateIssue = strictObject({
   key: nonEmptyString,
   title: string2(),
@@ -14286,7 +14292,7 @@ var LegionDaemonApi = {
         queue: array(nonEmptyString)
       }),
       gates: record(string2(), stateGate),
-      controllerLocator: stateTreeLocator.optional(),
+      controllerLocator: union([stateTreeLocator, stateExternalControllerLocator]).optional(),
       roles: record(string2(), stateRole),
       controllerPendingNotices: number2().int().nonnegative(),
       pendingStatusWrites: array(nonEmptyString),
@@ -14301,6 +14307,10 @@ var LegionDaemonApi = {
     }),
     response: object({})
   },
+  ControllerSecret: {
+    request: strictObject({}),
+    response: object({ secret: nonEmptyString })
+  },
   ProcessStarted: {
     request: strictObject({
       tree: nonEmptyString,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sjawhar/opencode-legion-envoy",
-  "version": "1.31.2",
+  "version": "1.32.0",
   "type": "module",
   "main": "dist/src/server.js",
   "exports": {

package/skills/legion-controller/SKILL.md

@@ -64,6 +64,26 @@ command run `/legion-claim-controller` again.
 This handshake lets the daemon redeliver held controller work. It does not turn the controller
 into a state holder: daemon state and the Dispatch project remain authoritative.
 
+### Started by the operator (runtime: kubernetes)
+
+When the daemon runs inside a Kubernetes cluster it cannot open a terminal anywhere, so nobody
+launched your pane: the operator ran `legion controller start --config controller.yaml
+[--daemon-url <port-forward>]` on their own machine, and you are that foreground OMP session.
+The command fetched a fresh controller secret from the daemon with the operator's token, wrote it
+to a 0600 file under `LEGION_STATE_DIR` (`~/.local/state/legion/<project>-controller` by default)
+beside the `gh` shim and the `legion` launcher, and started you with `LEGION_CONTROLLER=1` and
+the same environment a tmux controller pane carries — so the extension claims the role and calls
+`/controller/ready` exactly as under tmux, and nothing changes in how you handle wakes. The
+daemon records you as `controllerLocator: {runtime: "kubernetes", external: true, sessionId,
+registeredAt}` and reads your liveness from the Envoy role registry (the holder of
+`legion-<project>-controller` and its `last_seen`), not from a pane: keep the session running.
+Exiting it leaves the project without a controller until the operator runs the command again —
+the daemon logs `controller not registered; run legion controller start` once per boot-timeout
+interval and launches nothing itself. `legion state`, `legion gh -- <args>`, and
+`legion status <KEY> <status>` work here over `LEGION_DAEMON_URL` (the port-forward). A second
+`legion controller start` replaces you: it mints a new secret, so your grants stop working and
+the role moves to the new session.
+
 ## Deployment instructions
 
 Deployment instructions, when present, are the operator's standing rules for this repository —