@akagilnc/pi-workflow-roles 0.1.3527 → 0.1.3531

package/dist/grok/production-host.js

@@ -14147,7 +14147,6 @@ function controlledGrokChildEnv(base, grokHome) {
   return {
     ...base,
     ...PRIVATE_COMPAT_ENV,
-    HOME: grokHome,
     GROK_HOME: grokHome,
     GROK_MEMORY: "0",
     GROK_SUBAGENTS: "0"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@akagilnc/pi-workflow-roles",
-  "version": "0.1.3527",
+  "version": "0.1.3531",
   "description": "Soul-bound workflow roles for Pi",
   "type": "module",
   "license": "Apache-2.0",

package/resources/engines/codex.md

@@ -32,14 +32,9 @@ codex exec --skip-git-repo-check --ephemeral -C "$PROJECT_ROOT" "YOUR_LABOR_PROM
 
 Default (non-`--json`) mode prints the session banner and progress on stderr
 (measured on this host). Collect the labor body from stdout so that stderr log
-noise is not mixed into the returned body. Use `--json` only when the seat itself
-needs machine-readable event rows (those rows land on stdout as JSONL; measured
-event types include `thread.started`, `turn.started`, `item.completed`, `error`,
-`turn.failed`):
-
-```bash
-codex exec --skip-git-repo-check --ephemeral --json "YOUR_LABOR_PROMPT"
-```
+noise is not mixed into the returned body. Never use `--json` for labor: its
+JSONL event rows go back into the seat's context as noise (see `opus.md` for the
+measured ratio).
 
 Prefer `codex exec --help` on the host over any remembered flag set. Do not wrap
 this engine behind `ak-role` flags.

package/resources/engines/opencode.md

@@ -20,7 +20,8 @@ opencode run -m opencode-go/glm-5.2 "YOUR_LABOR_PROMPT"
   `opencode models` first** — provider prefixes migrate (verified 2026-08-21:
   GLM lives under `opencode-go/`, e.g. `opencode-go/glm-5.2`; the older
   `zai/glm-5.2` id errors with "Unexpected server error").
-- `--format json` gives structured output; `--auto` auto-approves non-denied
-  permissions for unattended runs (both per official docs).
+- Plain text output only (never `--format json` for labor — the returned body
+  goes back into the seat's context); `--auto` auto-approves non-denied
+  permissions for unattended runs (per official docs).
 - Output goes to stdout; long prompts may be passed via shell heredoc or a
   file read into the argument — follow the installed CLI's actual interface.

package/resources/engines/zcode.md

@@ -18,8 +18,8 @@ zcode --prompt 'YOUR_LABOR_PROMPT' --cwd /path/to/worktree
 
 `--prompt` defaults to permission mode `yolo` (no TTY permission stalls).
 Useful extras measured from `zcode --help`: `--attach <path>` (repeatable),
-`--mode build|edit|plan|yolo`, `--resume <sess_...>`, `--json` where
-supported. Prefer `zcode --help` on the host over any remembered flag set.
+`--mode build|edit|plan|yolo`, `--resume <sess_...>`. Never `--json` for
+labor (the returned body goes back into the seat's context as plain text). Prefer `zcode --help` on the host over any remembered flag set.
 
 ## Realm and model traps (host-verified 2026-08-29, all three hit in sequence)
 

package/src/grok/production-host.ts

@@ -143,7 +143,7 @@ function childEnv(controlledHome: string, packageRoot: string): NodeJS.ProcessEn
 }
 
 /**
- * Single production isolation binding: auth root, GROK_HOME/HOME, and binary
+ * Single production isolation binding: auth root, GROK_HOME, and binary
  * resolution. Production executeTurn passes controlledHome as S6 request.home
  * (seatbelt hang root proven separately by S6 seatbelt tests).
  */

package/src/grok/role-turn-host.ts

@@ -753,7 +753,6 @@ export function controlledGrokChildEnv(base: NodeJS.ProcessEnv, grokHome: string
   return {
     ...base,
     ...PRIVATE_COMPAT_ENV,
-    HOME: grokHome,
     GROK_HOME: grokHome,
     GROK_MEMORY: "0",
     GROK_SUBAGENTS: "0",