@jaybeeuu/agent-cortex 2.4.1 → 2.4.2

package/CHANGELOG.md

@@ -1,5 +1,38 @@
 # Changelog
 
+## 2.4.2
+
+### Patch Changes
+
+- 015ede5: Stop the Claude install from dropping `{{TOOL:read_agent}}` and `{{TOOL:wait_for_agents}}`
+  into dangling prose. Both tokens are null on the claude column (Claude reports a subagent's
+  result inline, so there is no separate read or wait step), so the installer replaced them with
+  an empty string and warned three times — leaving `Read the completed agent's output with  and
+parse…` and two similar broken sentences in the installed `ralph` and `design-an-interface`
+  skills. Those sentences are now harness-neutral, so both installs read correctly and the
+  installer emits no null-mapping warning. A regression guard fails the installer test if a
+  shipped skill names a tool the claude column cannot map.
+- 199cefe: Point the shipped pi settings at models that still exist. `tinyModel.model` was
+  `opencode/mimo-v2.5-free`, which the provider catalogue has dropped, so the
+  setting resolved to nothing and pi fell back to another free model. That fallback
+  returns `429 FreeUsageLimitError` once the free quota is spent, and the 429 JSON
+  became the entire output of the background call that runs auto-naming and
+  notifications — so a subagent run died at session start while the agent itself was
+  on a paid model. `tinyModel.model` is now `opencode-go/deepseek-v4.1-flash`.
+  `enabledModels` also drops three ids that do not resolve — `opencode-go/deepseek-v4-flash`,
+  `opencode/deepseek-v4-flash` and `opencode/mimo-v2.5-free` — which made pi print a
+  `No models match pattern` warning on every startup.
+- 6b6080b: Stop the test suite from leaking temp workspaces into `/tmp`. Each test file that
+  creates workspaces under the system temp dir now shares one temp root that a
+  file-level `after()` hook removes, so the removal happens whether the tests
+  passed, failed, or threw before reaching their own cleanup — previously a single
+  green run of `test/installer.test.mjs` left 21 workspaces behind (7.4 MB apparent,
+  13 MB on disk: each is a materialised plugin tree of skills, agents and hooks),
+  plus one from `test/cli.test.mjs`'s `install claude --output` case. Repeated runs
+  could fill a small tmpfs and make unrelated tests fail with ENOSPC. A regression
+  guard runs a deliberately failing test file and asserts the run leaves nothing
+  behind.
+
 ## 2.4.1
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jaybeeuu/agent-cortex",
-  "version": "2.4.1",
+  "version": "2.4.2",
   "description": "Personal PI package with custom agents, skills, and extensions",
   "keywords": [
     "pi-package"

package/skills/engineering/design-an-interface/SKILL.md

@@ -55,7 +55,7 @@ description: "Generate multiple radically different interface designs for a modu
    4. Trade-offs of this approach
    ```
 
-   Collect each agent's output with {{TOOL:read_agent}} when it finishes.
+   Collect each agent's output as it finishes.
 
 3. **Present designs.** Show each design sequentially — signature, usage examples, what it hides — so the user absorbs each approach before any comparison happens.
 

package/skills/workflow/ralph/SKILL.md

@@ -41,7 +41,7 @@ State model: task state lives in beads (ready/in_progress via `bd`); the only lo
    - **Bead that already has its children** (a decomposed feature, an expanded task parent): skip it — it is not dispatchable itself, and its `stage:*` chore is dispatched on its own.
    `execution:hitl` beads are not in this query and are not ralph's to touch: record them for the Pending Human Action summary. That includes every feature still at its default `execution:hitl` label.
 7. Dispatch each unit from its parent's worktree, up to 5 in flight: a stage chore via the event loop, a childless feature via a decomposition worker (_Feature decomposition_), a chore-less task via an expansion worker (_Expansion guard_). Create branches and worktrees first (REFERENCE.md, _Feature Branches and Worktrees_).
-8. Hand over to your harness's completion-detection mechanism: PI keeps a {{TOOL:wait_for_agents}} call outstanding over every in-flight agent ID, and Claude re-invokes you as each worker completes. If no **agent work** was dispatched — `state.json`'s `inflight` holds no entries, so no stage, decomposition or expansion worker is running — and `skills/workflow/ralph/scripts/pending-gates.mjs` reports a non-empty `pendingHumanAction` (an unblocked `lifecycle:feature-pr` gate, or an epic tagged `awaiting-epic-pr-merge`), go straight to HITL Pause (REFERENCE.md). A decomposition- or expansion-only init is in flight, not idle: keep the completion mechanism running and continue at the event loop.
+8. Hand over to your harness's completion-detection mechanism: PI keeps a blocking wait outstanding over every in-flight agent ID, and Claude re-invokes you as each worker completes. If no **agent work** was dispatched — `state.json`'s `inflight` holds no entries, so no stage, decomposition or expansion worker is running — and `skills/workflow/ralph/scripts/pending-gates.mjs` reports a non-empty `pendingHumanAction` (an unblocked `lifecycle:feature-pr` gate, or an epic tagged `awaiting-epic-pr-merge`), go straight to HITL Pause (REFERENCE.md). A decomposition- or expansion-only init is in flight, not idle: keep the completion mechanism running and continue at the event loop.
 
 ### 2. Expansion guard (stage chores are pre-created)
 
@@ -60,7 +60,7 @@ A feature carries `execution:hitl` by default, so this only runs when a human ha
 On each completion notification (a background agent finished):
 
 1. Poll that parent's log for new lines — `tail -n +<nextLine> .agent-cortex/ralph/ralph-<parent-id>.log` (logs are keyed by parent bead ID, so every stage of a feature shares one file) — and post only new key events (stage transitions, test/lint results), never empty updates.
-2. Read the completed agent's output with {{TOOL:read_agent}} and parse its `---REPORT---` block for `BEAD_ID`, `STAGE_COMPLETED`, and the outcome. A **decomposition** (`kind: "decompose"`) or **expansion** (`kind: "expand"`) worker has no REPORT and no leaf bead to confirm. An **expansion worker** owns no bead — confirm the parent now has `stage:*` chores (`bd children <parent-id> --json | grep -c '"stage:'`) and skip to step 5 to dispatch its ready `stage:code` chore. A **decomposition worker** — confirm the feature now has children (`bd children <feature-id> --json` returns a non-empty list), record that nothing is dispatchable for it until a human closes the planning bead, and skip to step 5; never re-decompose. If either confirmation comes back empty, the worker failed: surface its output, record the parent for the shutdown summary, and do not re-dispatch.
+2. Read the completed agent's output and parse its `---REPORT---` block for `BEAD_ID`, `STAGE_COMPLETED`, and the outcome. A **decomposition** (`kind: "decompose"`) or **expansion** (`kind: "expand"`) worker has no REPORT and no leaf bead to confirm. An **expansion worker** owns no bead — confirm the parent now has `stage:*` chores (`bd children <parent-id> --json | grep -c '"stage:'`) and skip to step 5 to dispatch its ready `stage:code` chore. A **decomposition worker** — confirm the feature now has children (`bd children <feature-id> --json` returns a non-empty list), record that nothing is dispatchable for it until a human closes the planning bead, and skip to step 5; never re-decompose. If either confirmation comes back empty, the worker failed: surface its output, record the parent for the shutdown summary, and do not re-dispatch.
 3. Confirm the stage worker closed its chore bead: `bd show <bead-id>` should read `closed` with the outcome in its close reason. If it is still open the worker died mid-stage — read its notes and re-dispatch; never close it yourself.
 4. Route the parent per the dispatch table — nothing is created here: the pre-created chain already encodes the order, and the worker owns any remediation it needs.