@codyswann/lisa 4.27.6 → 4.27.8

package/plugins/lisa-copilot/skills/lisa-intake/SKILL.md

@@ -145,33 +145,38 @@ Record **exactly one** outcome per invocation through the run-record CLI, naming
 specific, actionable, e.g. `Scanned 12 ready items; nothing to propose.` for `nothing-needed`):
 
 ```bash
-node "${CLAUDE_PLUGIN_ROOT}/scripts/automation-run-record.mjs" \
+node "${CLAUDE_PLUGIN_ROOT:-node_modules/@codyswann/lisa/plugins/lisa}/scripts/automation-run-record.mjs" \
   --loop-id intake-tickets --outcome candidate-proposed \
   --summary "Routed PRD #1810 to Blocked with clarifying questions; the run succeeded." \
   --runbook .lisa/automations/intake-tickets.runbook.md [--ref <item-url>]...
 ```
 
 **A dry build lane must say what it looked in.** A `nothing-needed` run on `intake-tickets`
-additionally passes `--denominator` — the JSON from `buildIntakeDenominator()` in
-`scripts/intake-prework-denominator.mjs` — and the recorder **refuses the row without it**. This is
-not decoration: 31 consecutive cycles reported a dry lane against a queue holding 61 unswept
-pre-work rows, and every one of those records was honest. A missing row is noisy on inspection; a
-wrong denominator is silent forever and looks exactly like a healthy dry queue. Stating the swept
-set is what turns the silent wrong answer into an inspectable one (#2657).
+additionally passes `--denominator` — the JSON from `buildIntakeDenominator()` in the plugin
+scripts directory's `intake-prework-denominator.mjs`, resolved exactly like the recorder below —
+and the recorder **refuses the row without it**. This is not decoration: 31 consecutive cycles
+reported a dry lane against a queue holding 61 unswept pre-work rows, and every one of those
+records was honest. A missing row is noisy on inspection; a wrong denominator is silent forever
+and looks exactly like a healthy dry queue. Stating the swept set is what turns the silent wrong
+answer into an inspectable one (#2657).
 
 ```bash
-node "${CLAUDE_PLUGIN_ROOT}/scripts/automation-run-record.mjs" \
+node "${CLAUDE_PLUGIN_ROOT:-node_modules/@codyswann/lisa/plugins/lisa}/scripts/automation-run-record.mjs" \
   --loop-id intake-tickets --outcome nothing-needed \
   --summary "Nothing ready to build on team ENG. Looked in every lane holding work that has not started — Backlog (20), Todo (17), Ready (2), Blocked (61) — 100 items checked out of 343 still open." \
   --denominator "$DENOMINATOR_JSON" \
   --runbook .lisa/automations/intake-tickets.runbook.md
 ```
 
-If `${CLAUDE_PLUGIN_ROOT}` is unset, resolve the plugin scripts directory directly — the built copy
-`plugins/lisa/scripts/automation-run-record.mjs` or the source
-`plugins/src/base/scripts/automation-run-record.mjs`. If recording still fails, **degrade, never
-abort** (per `automation-runbook-contract`): note the recording failure in the run output and finish
-the cycle — a recording failure is a degradation to report, never a reason to block the loop.
+The `:-` default in that command is load-bearing, not decoration. `CLAUDE_PLUGIN_ROOT` is **not
+exported into an agent's Bash tool environment**, so the bare `"${CLAUDE_PLUGIN_ROOT}/scripts/…"`
+form expands to an absolute `/scripts/…` and exits 1. The default names the installed package copy,
+which resolves from the **consumer repository root** — which is where the recorder is actually
+invoked. Never substitute a bare `plugins/lisa/scripts/…` or `plugins/src/base/scripts/…` path:
+those are relative to the **Lisa package root**, not the repository you are standing in, and exit 1
+from there. If recording still fails, **degrade, never abort** (per `automation-runbook-contract`):
+note the recording failure in the run output and finish the cycle — a recording failure is a
+degradation to report, never a reason to block the loop.
 
 **Retirement evaluation (every run).** Both loop-ids this skill backs are **structural to the
 factory — they do not retire.** Their runbooks say so plainly instead of leaving the Retirement

package/plugins/lisa-copilot/skills/lisa-learnings-audit/SKILL.md

@@ -368,18 +368,24 @@ loop's runbook (the `--summary` is the operator-readable one-liner in the
 contract's exemplar voice — plain, specific, actionable):
 
 ```bash
-node "${CLAUDE_PLUGIN_ROOT}/scripts/automation-run-record.mjs" \
+node "${CLAUDE_PLUGIN_ROOT:-node_modules/@codyswann/lisa/plugins/lisa}/scripts/automation-run-record.mjs" \
   --loop-id learnings-audit --outcome candidate-proposed \
   --summary "Proposed 2 promotions and 1 batch confirm; awaiting your flip to ready." \
   --runbook .lisa/automations/learnings-audit.runbook.md [--ref <ticket-url>]...
 ```
 
-If `${CLAUDE_PLUGIN_ROOT}` is unset, resolve the plugin scripts directory
-directly — the built copy `plugins/lisa/scripts/automation-run-record.mjs` or
-the source `plugins/src/base/scripts/automation-run-record.mjs`. If recording
-still fails, **degrade, never abort** (per `automation-runbook-contract`): note
-the recording failure in the run output and finish the run — a recording
-failure is a degradation to report, never a reason to block the loop.
+The `:-` default in that command is load-bearing, not decoration.
+`CLAUDE_PLUGIN_ROOT` is **not exported into an agent's Bash tool
+environment**, so the bare `"${CLAUDE_PLUGIN_ROOT}/scripts/…"` form expands
+to an absolute `/scripts/…` and exits 1. The default names the installed
+package copy, which resolves from the **consumer repository root** — which
+is where the recorder is actually invoked. Never substitute a bare
+`plugins/lisa/scripts/…` or `plugins/src/base/scripts/…` path: those are
+relative to the **Lisa package root**, not the repository you are standing
+in, and exit 1 from there. If recording still fails, **degrade, never
+abort** (per `automation-runbook-contract`): note the recording failure in
+the run output and finish the run — a recording failure is a degradation to
+report, never a reason to block the loop.
 
 ## Retirement condition
 

package/plugins/lisa-copilot/skills/lisa-linear-build-intake/SKILL.md

@@ -140,13 +140,15 @@ Build the denominator with the shared helper, which owns the type vocabulary so
 
 ```bash
 node -e '
-import("'"${CLAUDE_PLUGIN_ROOT:-plugins/src/base}"'/scripts/intake-prework-denominator.mjs").then(m => {
+import("'"${CLAUDE_PLUGIN_ROOT:-./node_modules/@codyswann/lisa/plugins/lisa}"'/scripts/intake-prework-denominator.mjs").then(m => {
   const d = m.buildIntakeDenominator({ lanes: JSON.parse(process.argv[1]), totalOpen: Number(process.argv[2]) });
   console.log(JSON.stringify(d));
   console.log(m.summarizeDryLane(d, { queue: process.argv[3] }));
 });' "$LANES_JSON" "$TOTAL_OPEN" "team $TEAM_KEY"
 ```
 
+The `./` on that default is load-bearing and is not the same as the recorder's. `import()` reads a bare `node_modules/…` as a **package specifier** named `node_modules` and fails with `ERR_MODULE_NOT_FOUND: Cannot find package 'node_modules'`; only `./`, `../`, `/` or a `file:` URL is a path. A `node <path>` command line has no such rule, which is why the run-recorder default alongside this one carries no `./`.
+
 `$LANES_JSON` is `[{"name":"<state>","type":"<state.type>","position":<state.position>,"count":<open rows>}, …]` for **every** state on the team, pre-work and not — the helper does the selecting.
 
 **Candidate order.** Work `$READY` first (it is the human-flipped signal), then the remaining pre-work lanes oldest-first. Every candidate outside `$READY` must clear Phase 2.5 before it is treated as a candidate at all.

package/plugins/lisa-copilot/skills/lisa-monitor/SKILL.md

@@ -171,17 +171,21 @@ plain, specific, actionable, e.g. `Health green; audit clean — nothing to prop
 unreachable during the decline check — restore credentials; nothing was filed this run.`):
 
 ```bash
-node "${CLAUDE_PLUGIN_ROOT}/scripts/automation-run-record.mjs" \
+node "${CLAUDE_PLUGIN_ROOT:-node_modules/@codyswann/lisa/plugins/lisa}/scripts/automation-run-record.mjs" \
   --loop-id monitor --outcome candidate-proposed \
   --summary "Filed #1810 for the p99 latency spike; awaiting your flip to ready." \
   --runbook .lisa/automations/monitor.runbook.md [--ref <ticket-url>]...
 ```
 
-If `${CLAUDE_PLUGIN_ROOT}` is unset, resolve the plugin scripts directory directly — the built copy
-`plugins/lisa/scripts/automation-run-record.mjs` or the source
-`plugins/src/base/scripts/automation-run-record.mjs`. If recording still fails, **degrade, never
-abort** (per `automation-runbook-contract`): note the recording failure in the run output and finish
-the cycle — a recording failure is a degradation to report, never a reason to block the loop.
+The `:-` default in that command is load-bearing, not decoration. `CLAUDE_PLUGIN_ROOT` is **not
+exported into an agent's Bash tool environment**, so the bare `"${CLAUDE_PLUGIN_ROOT}/scripts/…"`
+form expands to an absolute `/scripts/…` and exits 1. The default names the installed package copy,
+which resolves from the **consumer repository root** — which is where the recorder is actually
+invoked. Never substitute a bare `plugins/lisa/scripts/…` or `plugins/src/base/scripts/…` path:
+those are relative to the **Lisa package root**, not the repository you are standing in, and exit 1
+from there. If recording still fails, **degrade, never abort** (per `automation-runbook-contract`):
+note the recording failure in the run output and finish the cycle — a recording failure is a
+degradation to report, never a reason to block the loop.
 
 **Retirement evaluation (every run).** Evaluate this loop's runbook **Retirement condition** on
 every standalone run, exactly as the `automation-runbook-contract` rule's Retirement section defines

package/plugins/lisa-copilot/skills/lisa-project-ideation/SKILL.md

@@ -321,17 +321,21 @@ propose.` for `nothing-needed`; and for a `recovery-required` from an unreadable
 `Tracker unreachable during the decline check — restore credentials; nothing was filed this run.`):
 
 ```bash
-node "${CLAUDE_PLUGIN_ROOT}/scripts/automation-run-record.mjs" \
+node "${CLAUDE_PLUGIN_ROOT:-node_modules/@codyswann/lisa/plugins/lisa}/scripts/automation-run-record.mjs" \
   --loop-id exploratory-prds --outcome candidate-proposed \
   --summary "Created PRD #1810 for offline export; awaiting your flip to ready." \
   --runbook .lisa/automations/exploratory-prds.runbook.md [--ref <prd-url>]...
 ```
 
-If `${CLAUDE_PLUGIN_ROOT}` is unset, resolve the plugin scripts directory directly — the built copy
-`plugins/lisa/scripts/automation-run-record.mjs` or the source
-`plugins/src/base/scripts/automation-run-record.mjs`. If recording still fails, **degrade, never
-abort** (per `automation-runbook-contract`): note the recording failure in the run output and finish
-the run — a recording failure is a degradation to report, never a reason to block the loop.
+The `:-` default in that command is load-bearing, not decoration. `CLAUDE_PLUGIN_ROOT` is **not
+exported into an agent's Bash tool environment**, so the bare `"${CLAUDE_PLUGIN_ROOT}/scripts/…"`
+form expands to an absolute `/scripts/…` and exits 1. The default names the installed package copy,
+which resolves from the **consumer repository root** — which is where the recorder is actually
+invoked. Never substitute a bare `plugins/lisa/scripts/…` or `plugins/src/base/scripts/…` path:
+those are relative to the **Lisa package root**, not the repository you are standing in, and exit 1
+from there. If recording still fails, **degrade, never abort** (per `automation-runbook-contract`):
+note the recording failure in the run output and finish the run — a recording failure is a
+degradation to report, never a reason to block the loop.
 
 **Retirement evaluation (every run).** Evaluate this loop's runbook **Retirement condition** on
 every run, exactly as the `automation-runbook-contract` rule's Retirement section defines it — this

package/plugins/lisa-copilot/skills/lisa-repair-intake/SKILL.md

@@ -1218,17 +1218,21 @@ specific, actionable, e.g. `Examined 14 items; all active or in backoff — noth
 `nothing-needed`):
 
 ```bash
-node "${CLAUDE_PLUGIN_ROOT}/scripts/automation-run-record.mjs" \
+node "${CLAUDE_PLUGIN_ROOT:-node_modules/@codyswann/lisa/plugins/lisa}/scripts/automation-run-record.mjs" \
   --loop-id intake-repair --outcome change-proved \
   --summary "Recovered 3 stalled builds and closed out 2 rollups; all confirmed." \
   --runbook .lisa/automations/intake-repair.runbook.md [--ref <item-url>]...
 ```
 
-If `${CLAUDE_PLUGIN_ROOT}` is unset, resolve the plugin scripts directory directly — the built copy
-`plugins/lisa/scripts/automation-run-record.mjs` or the source
-`plugins/src/base/scripts/automation-run-record.mjs`. If recording still fails, **degrade, never
-abort** (per `automation-runbook-contract`): note the recording failure in the run output and finish
-the cycle — a recording failure is a degradation to report, never a reason to block the loop.
+The `:-` default in that command is load-bearing, not decoration. `CLAUDE_PLUGIN_ROOT` is **not
+exported into an agent's Bash tool environment**, so the bare `"${CLAUDE_PLUGIN_ROOT}/scripts/…"`
+form expands to an absolute `/scripts/…` and exits 1. The default names the installed package copy,
+which resolves from the **consumer repository root** — which is where the recorder is actually
+invoked. Never substitute a bare `plugins/lisa/scripts/…` or `plugins/src/base/scripts/…` path:
+those are relative to the **Lisa package root**, not the repository you are standing in, and exit 1
+from there. If recording still fails, **degrade, never abort** (per `automation-runbook-contract`):
+note the recording failure in the run output and finish the cycle — a recording failure is a
+degradation to report, never a reason to block the loop.
 
 **Retirement evaluation (every run).** The `intake-repair` loop is **structural to the
 factory — it does not retire.** Its runbook says so plainly instead of leaving the Retirement

package/plugins/lisa-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "4.27.6",
+  "version": "4.27.8",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"