@akagilnc/pi-workflow-roles 0.1.2130 → 0.1.2135

package/package.json

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

package/resources/engines/grok-4.6.md

@@ -24,10 +24,20 @@ grok --prompt-file /path/to/labor-prompt.md -m grok-4.6 --always-approve --outpu
 - Official docs list `-p/--single` as the canonical headless prompt input;
   `--prompt-file` exists in the installed CLI (`--help`) and is smoke-verified
   on this host — prefer it for long prompts, fall back to `-p` if absent.
-- `--output-format plain` keeps stdout clean for capture.
-- Reasoning effort follows the host CLI defaults; grok effort tiers are
-  low/med/high when a flag is exposed by the installed CLI version — check
-  `grok --help` and follow the actual interface. Do not invent flags.
+- `--output-format plain` keeps stdout clean for capture — but it stays
+  silent until the run finishes. **For labor longer than ~2 minutes use
+  `--output-format streaming-json` instead**: it emits NDJSON events
+  (thought/text deltas) continuously from the first second, which keeps the
+  package idle watchdog fed (verified live 2026-08-21; a plain-format judge
+  run was killed by the 183s idle timeout). Reconstruct the final answer by concatenating each NDJSON
+  object's `data` where `type == "text"`, in stream order; `type == "end"`
+  (stopReason end_turn) marks completion. Do not treat `thought` events as
+  the answer (live-verified stream shape 2026-08-21).
+- **Always pass `--reasoning-effort <low|medium|high>`** matching the effort
+  tier ordered in the labor mandate (verified live 2026-08-21: flag exists,
+  alias `--effort`; a low-tier run completed correctly). If the mandate names
+  no tier, use the seat's ordered thinking tier; never omit the flag — the
+  CLI default is not guaranteed to match the ordered tier.
 
 ## Failure handling