@akagilnc/pi-workflow-roles 0.1.2460 → 0.1.2464

package/package.json

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

package/resources/engines/cursor.md

@@ -7,26 +7,40 @@ Before invoking the engine, read `../engine-dispatch.md`, resolving that path
 relative to this note. This note only covers this engine's CLI technical
 parameters.
 
-## Invocation examples (local Cursor Agent CLI)
+## Entrypoint (verified 2026-08-28)
 
-The machine entrypoint is `agent` (also exposed as `cursor-agent`). Run from the
-role project root. Non-interactive print mode:
+The machine entrypoint is **`cursor-agent`**. Do NOT use the bare `agent`
+name on this host: PATH resolves `agent` to the Grok CLI (`~/.grok/bin/agent`
+→ grok 1.0.5, a different product billed to grok.com Build) — its flags
+differ and it fails labor invocations (`--force` unknown; billing 402 when
+the Grok Build balance is exhausted).
 
-```bash
-agent -p --force --output-format text "YOUR_LABOR_PROMPT"
-```
+## Invocation (local Cursor Agent CLI)
 
-Choose a model explicitly when the seat needs a known Cursor model id:
+Run from the role project root. Non-interactive print mode; `-f/--force`
+allows command execution headlessly; `-p` prints responses for scripts:
 
 ```bash
-agent -p --force --model grok-4.5 --output-format text "YOUR_LABOR_PROMPT"
+cursor-agent -p -f --output-format text --model <MODEL_ID> "YOUR_LABOR_PROMPT"
 ```
 
-Stream JSON events for long labor:
+- Model ids come from `cursor-agent models`. Effort tiers are encoded in the
+  id itself (e.g. `cursor-grok-4.6-low`, `cursor-grok-4.6-medium`,
+  `cursor-grok-4.6-high`, plus `-fast` variants); some models also accept a
+  bracket override form (`'claude-opus-4-8[context=1m,effort=high]'` — see
+  `cursor-agent --help`).
+- Owner pool directive 2026-08-28: default labor model = `cursor-grok-4.6-low`.
+- Stream JSON events for long labor: `--output-format stream-json`.
+
+Prefer `cursor-agent --help` on the host over any remembered flag set. Do not
+wrap this engine behind `ak-role` flags.
+
+## Smoke test (run before first labor leg of a session)
 
 ```bash
-agent -p --force --output-format stream-json "YOUR_LABOR_PROMPT"
+cursor-agent -p -f --output-format text --model cursor-grok-4.6-low "Reply with exactly one word: OK"
 ```
 
-Prefer `agent --help` on the host over any remembered flag set. Do not wrap this
-engine behind `ak-role` flags.
+Expected: stdout ends with exactly `OK`, exit code 0. Verified 2026-08-28 on
+this host (Cursor subscription login). If it asks about directory trust, the
+`-f` flag (or `--trust`) is missing.

package/resources/engines/hermes.md

@@ -65,9 +65,8 @@ hermes -z "YOUR_LABOR_PROMPT" --in /path/to/project --no-restore-cwd \
   simultaneously, losing legs saw sustained HTTP 429 across 9-29 detour
   attempts while the 1-2 winners completed normally (Ming_LLM books runs
   01a046ec-*/01a046f4-*, 14:55-15:04 window).
-- Keep at most ONE in-flight hermes labor call per account; queue the rest.
-- On 429: back off once (~60s) and retry once; if still 429, stop and record
-  the typed engine failure in the receipt — do not hammer retries.
+  No concurrency ceiling has been measured beyond this observation; policy on
+  concurrency and retries is the dispatcher's call, not this note's.
 
 ## Smoke test (run before first labor leg of a session)