@codyswann/lisa 2.286.12 → 2.287.1

package/plugins/lisa-expo-cursor/skills/maestro-mcp-setup/SKILL.md

@@ -0,0 +1,144 @@
+---
+name: maestro-mcp-setup
+description: Enable the Maestro CLI's built-in MCP server (`maestro mcp`, STDIO) for this machine, robustly. Detects the Maestro CLI and a usable Java runtime, installs/guides what is missing, and registers the MCP server at LOCAL (per-machine, uncommitted) scope with an absolute command path and injected JAVA_HOME/PATH so the spawn never dies on a non-login PATH. Use when an Expo project needs Maestro device-automation tools (list_devices, inspect_screen, take_screenshot, run flows). Never registers at project/committed scope — that reintroduces the fleet-wide "-32000" failure.
+allowed-tools:
+  - Bash
+  - Read
+---
+
+# Maestro MCP Setup
+
+Wire the Maestro CLI's built-in MCP server (`maestro mcp`, STDIO) into the
+current coding agent for **this machine only**, in a way that actually works.
+
+## Why this skill exists (read before changing it)
+
+The Maestro MCP server is intentionally **NOT** in the distributed plugin
+`.mcp.json`. A static, committed entry always attempts to spawn, and coding
+agents spawn stdio servers with a **non-login PATH**. So an always-on entry
+fails visibly — Claude Code shows `Failed to reconnect … -32000` **every
+session** — on any machine missing the Maestro CLI *or* a resolvable Java
+runtime, which is most of a typical fleet (CI runners, unattended QA/intake
+agent boxes). That exact regression shipped once (expo plugin commit b12d5d3)
+and was reverted (b1f3efd).
+
+This skill fixes both failure modes without poisoning the fleet:
+
+1. **Missing CLI / Java** → detect, and install or guide install.
+2. **Installed but PATH-less spawn** → register with an **absolute `command`
+   path** plus injected **`JAVA_HOME` / `PATH`** env, so the server finds Java
+   regardless of the spawn's inherited PATH.
+
+Registration is always **`--scope local`** (per-machine, uncommitted). Never use
+`--scope project` / a committed `.mcp.json` entry — that is the always-on form
+that reds out every other machine.
+
+## Steps
+
+### 1. Locate the Maestro CLI
+
+```bash
+MAESTRO_BIN="$(command -v maestro || true)"
+[ -z "$MAESTRO_BIN" ] && [ -x "$HOME/.maestro/bin/maestro" ] && MAESTRO_BIN="$HOME/.maestro/bin/maestro"
+echo "maestro: ${MAESTRO_BIN:-NOT FOUND}"
+```
+
+If not found, install it (official installer — confirm with the user first,
+since it writes to `~/.maestro`):
+
+```bash
+curl -fsSL "https://get.maestro.mobile.dev" | bash
+MAESTRO_BIN="$HOME/.maestro/bin/maestro"
+```
+
+Resolve to an **absolute** path — a bare `maestro` in the registration relies on
+the very PATH that is missing at spawn time.
+
+### 2. Locate a usable Java runtime
+
+Maestro needs a JDK (8+). Resolve `JAVA_HOME` **honoring the project's version
+manager** — do not install a parallel global JDK when one is already managed:
+
+```bash
+# Prefer an already-active/managed Java before installing anything. Covers the
+# common version managers (mise, asdf, SDKMAN) plus an ambient install.
+if command -v mise >/dev/null 2>&1 && mise which java >/dev/null 2>&1; then
+  JAVA_BIN="$(mise which java)"
+elif command -v asdf >/dev/null 2>&1 && asdf which java >/dev/null 2>&1; then
+  JAVA_BIN="$(asdf which java)"
+elif [ -x "${SDKMAN_DIR:-$HOME/.sdkman}/candidates/java/current/bin/java" ]; then
+  # SDKMAN's `sdk` is a shell function absent in non-login shells; use its stable
+  # `candidates/java/current` symlink directly instead.
+  JAVA_BIN="${SDKMAN_DIR:-$HOME/.sdkman}/candidates/java/current/bin/java"
+elif command -v java >/dev/null 2>&1; then
+  JAVA_BIN="$(command -v java)"
+fi
+echo "java: ${JAVA_BIN:-NOT FOUND}"
+
+# Derive JAVA_HOME by asking the JVM itself — NOT `dirname "$JAVA_BIN"/..`, which
+# is wrong when `java` is a mise/asdf shim or a symlink whose parent is not a JDK
+# root. Fall back to the bin/.. parent only if the JVM query yields nothing usable.
+if [ -n "$JAVA_BIN" ]; then
+  JAVA_HOME="$("$JAVA_BIN" -XshowSettings:properties -version 2>&1 \
+    | sed -n 's/^[[:space:]]*java\.home = //p' | head -n 1)"
+  { [ -z "$JAVA_HOME" ] || [ ! -x "$JAVA_HOME/bin/java" ]; } &&
+    JAVA_HOME="$(cd "$(dirname "$JAVA_BIN")/.." && pwd)"
+fi
+```
+
+If no Java is found: install through the project's version manager when present
+(`mise use -g java@21`, `asdf install java …`, or `sdk install java`), or guide
+the user to install a JDK. Prefer the managed path; only fall back to a global
+install with explicit consent. Re-resolve `JAVA_HOME` afterward.
+
+### 3. Register at local scope with injected env
+
+Build a `PATH` that puts the Maestro and Java `bin` dirs first, then register for
+the **current** coding agent. `$JAVA_BIN`/`$MAESTRO_BIN` are absolute.
+
+Claude Code:
+
+```bash
+# Refuse to register a broken server — both toolchain paths must resolve and be
+# executable, or `claude mcp add` would create the exact -32000 entry this skill
+# exists to avoid.
+[ -n "$MAESTRO_BIN" ] && [ -x "$MAESTRO_BIN" ] || { echo "Maestro CLI unresolved — abort"; exit 1; }
+[ -n "$JAVA_HOME" ] && [ -x "$JAVA_HOME/bin/java" ] || { echo "Java runtime unresolved — abort"; exit 1; }
+
+# Use the real JDK bin (from JAVA_HOME), not the shim dir, on PATH.
+JBIN_DIR="$JAVA_HOME/bin"; MBIN_DIR="$(dirname "$MAESTRO_BIN")"
+claude mcp add --scope local maestro \
+  --env "JAVA_HOME=$JAVA_HOME" \
+  --env "PATH=$JBIN_DIR:$MBIN_DIR:$PATH" \
+  -- "$MAESTRO_BIN" mcp
+```
+
+Parity — same intent on other harnesses (local/per-machine scope, absolute
+command, injected `JAVA_HOME`/`PATH`); translate the registration verb only:
+
+- **Codex** — `codex mcp add maestro --env JAVA_HOME=… --env PATH=… -- "$MAESTRO_BIN" mcp` (writes `~/.codex/config.toml`; keep it out of the committed project config).
+- **Cursor** — add the server to the user-scope `~/.cursor/mcp.json` (not the project `.cursor/mcp.json`) with `command`, `args: ["mcp"]`, and `env: { JAVA_HOME, PATH }`.
+- **OpenCode** — add to the user config (`~/.config/opencode/opencode.json`) `mcp` block with the absolute command and `environment`.
+- **Antigravity (agy) / Copilot** — add to the per-user MCP config with the absolute command + `env`; Copilot uses `type: "local"` for stdio servers.
+
+In every case: **local/user scope, never the committed project file.**
+
+### 4. Verify
+
+```bash
+claude mcp list        # or the harness equivalent
+```
+
+Confirm `maestro` shows connected. If it still fails, the usual cause is
+`JAVA_HOME` pointing at a JRE without `bin/java`, or a Maestro path that moved —
+re-resolve both and re-register. Do not "fix" it by dropping to a bare
+`maestro mcp` command; that reintroduces the PATH-less failure.
+
+## Guardrails
+
+- **Local scope only.** If you catch yourself typing `--scope project` or editing
+  a committed `.mcp.json`, stop — that is the reverted fleet-wide regression.
+- **Absolute paths + injected env are mandatory**, not optional — they are the
+  whole reason this is a skill and not a one-line doc.
+- Installing the CLI or a JDK mutates the machine — confirm before installing,
+  and prefer the project's version manager over a parallel global install.

package/plugins/lisa-harper-fabric/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "Harper/Fabric-specific rules for TypeScript component apps",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "Harper/Fabric-specific Lisa rules for TypeScript component apps.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "Harper/Fabric-specific rules for TypeScript component apps",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "Harper/Fabric-specific rules for TypeScript component apps",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "Harper/Fabric-specific rules for TypeScript component apps",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-nestjs/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "NestJS-specific skills and migration write-protection hooks.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-nestjs-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-nestjs-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, across Claude and Codex.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-phaser/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-phaser-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-phaser-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-rails/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "Ruby on Rails-specific skills and hooks for RuboCop and ast-grep scanning on edit.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-rails-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-rails-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-typescript/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "TypeScript-specific hooks for formatting, linting, and ast-grep scanning on edit.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-typescript-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-typescript-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "Distributable LLM Wiki kernel — ingest, query, lint, and maintain a git-native markdown knowledge base across Claude and Codex.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.286.12",
+  "version": "2.287.1",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/src/base/rules/reference/prd-lifecycle-rollup.md

@@ -66,13 +66,13 @@ A generated top-level child is **terminal** (counts as done for rollup) when it
 | Vendor | A generated top-level child is terminal when… |
 |---|---|
 | **GitHub Issues** | the issue is **closed** *and* (where the build-status label is used) carries the resolved `done` role label (`status:done` by default — env-keyed; see below). A closed-as-not-planned issue is terminal-but-dropped: it does not hold the PRD open but is excluded from "shipped" (treated like a won't-do leaf). |
-| **Linear** | the Issue/Project is in a **completed** workflow state (`done`-category), **or** a **canceled** state (terminal-but-dropped, like not-planned — does not hold the PRD open, excluded from shipped). |
+| **Linear** | the Issue/Project is in a **completed** workflow state (`done`-category), **or** a **canceled** or **duplicate** state (both terminal-but-dropped, like not-planned — do not hold the PRD open, excluded from shipped). Linear exposes `duplicate` as its own first-class `state.type`, distinct from `canceled`; an Issue marked as a duplicate (via Linear's native action or a team's Duplicate workflow state) is terminal and must be treated like canceled, never as still-open. |
 | **JIRA** | the issue's status is in the **Done status category** (`statusCategory.key == "done"`). |
 | **Confluence / Notion** | the documented generated-work entry is marked **done** in the PRD's machine-readable section (the durable equivalent of a closed ticket, since these sources have no native ticket state). |
 
 Notes:
 
-- **Required vs. optional children.** Only the generated top-level children that must ship for the PRD to be complete are counted toward the all-terminal check. Won't-do / canceled / not-planned children are terminal-but-dropped: they do not hold the PRD open and are excluded from the shipped set. This mirrors `leaf-only-lifecycle`'s "required leaves" qualifier.
+- **Required vs. optional children.** Only the generated top-level children that must ship for the PRD to be complete are counted toward the all-terminal check. Won't-do / canceled / duplicate / not-planned children are terminal-but-dropped: they do not hold the PRD open and are excluded from the shipped set. This mirrors `leaf-only-lifecycle`'s "required leaves" qualifier.
 - **Recursion is delegated, not duplicated.** A generated Epic is terminal only when *it* has rolled up to its own terminal state per `leaf-only-lifecycle`'s parent-status-rollup (all its required Stories/Sub-tasks terminal). This rule does not re-derive an Epic's state from its leaves — it reads the top-level child's own resolved state and trusts `leaf-only-lifecycle` to have rolled that up bottom-up.
 - **Blocked dominates at the report level.** If any required generated top-level child is blocked or incomplete, rollup leaves the PRD open and reports the incomplete child set (PRD #525: "rollup leaving a PRD open when at least one generated top-level child is incomplete"). The PRD is only advanced when **all** required top-level children are terminal.
 

package/plugins/src/base/skills/lisa-exploratory-qa/SKILL.md

@@ -78,7 +78,7 @@ Re-running a pass must not refile the same finding. Before creating a ticket, se
 
 - **Open** ticket carrying the marker → reference/update it instead; do not create a second.
 - **Closed as _completed_** → does **not** suppress. A recurrence after a fix is a genuine **regression**, so file the finding.
-- **Closed as _not planned_** (GitHub `stateReason == "not_planned"`; the config-resolved won't-do/canceled equivalent on JIRA/Linear) → a human **declined** this finding, so **suppress it**. Re-file only with evidence that **postdates the decline**, carrying BOTH the machine token (`declined <date>; recurred <date> in <ref>`) and a human acknowledgment sentence (`You declined this on <date>. It has recurred (<date>, <ref>), so we're raising it once more for your review.`).
+- **Closed as _not planned_** (GitHub `stateReason == "not_planned"`; the config-resolved won't-do/canceled equivalent on JIRA/Linear, including a Linear `duplicate` state) → a human **declined** this finding, so **suppress it**. Re-file only with evidence that **postdates the decline**, carrying BOTH the machine token (`declined <date>; recurred <date> in <ref>`) and a human acknowledgment sentence (`You declined this on <date>. It has recurred (<date>, <ref>), so we're raising it once more for your review.`).
 
 Every filed finding ticket MUST end with the `rejection-detection` **operator footer** as a visible prose line so the operator knows which close-reason silences it:
 

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

@@ -151,15 +151,17 @@ Run this gate **before** the claim relabel, starting with the oldest/highest-pri
 
 **Resolve container vs. leaf — structural first, then nominal.** Per `leaf-only-lifecycle` the classification is structural: an Issue is a **container** if it has **open** child work, whatever its declared type; otherwise the **type label** decides. Resolve child work using the same hierarchy `lisa-linear-read-issue` uses — Linear's native parentage: an Issue groups **sub-issues** via `parentId`, and a **Project** (the Epic equivalent) groups Issues via `projectId`. Relations (`save_issue_relation` — `blocks` / `is blocked by`) express dependencies and are **not** parentage — do not count them as children.
 
-Fetch the Issue's sub-issues via `lisa-linear-access operation: get-issue` (which returns the children) or `lisa-linear-access operation: list-issues({parentId: <issueId>})`, then count those still open (Linear `state.type` not in the completed/canceled set):
+Fetch the Issue's sub-issues via `lisa-linear-access operation: get-issue` (which returns the children) or `lisa-linear-access operation: list-issues({parentId: <issueId>})`, then count those still open (Linear `state.type` not in the completed/canceled/duplicate set):
 
 ```text
 # Children of <issueId>: native sub-issues via parentId.
-# Count children whose Linear state.type is NOT terminal ("completed" / "canceled").
-# A parent whose children are all completed is no longer holding open work and
+# Count children whose Linear state.type is NOT terminal ("completed" / "canceled" / "duplicate").
+# "duplicate" is a first-class Linear state.type (distinct from "canceled"): an Issue marked
+# as a duplicate is closed and must NOT be counted as open, or the parent never rolls up.
+# A parent whose children are all terminal is no longer holding open work and
 # rolls up via leaf-only-lifecycle's rollup, not here.
 OPEN_CHILDREN = count(list_issues({parentId: <issueId>})
-                       where state.type not in {"completed", "canceled"})
+                       where state.type not in {"completed", "canceled", "duplicate"})
 ```
 
 For a Project-level parent (an Issue that itself anchors a `projectId` grouping rather than a `parentId` tree), resolve membership the same way `lisa-linear-read-issue` does and treat the parent as a container if any grouped Issue is still open. If sub-issue resolution is unavailable, fall back to the parentage `lisa-linear-read-issue` derives and treat the Issue as a container if any derived child is open. Note "sub-issues unavailable — parentage derived" so the operator knows how children were resolved.

package/plugins/src/base/skills/lisa-verify-prd/SKILL.md

@@ -70,7 +70,7 @@ If neither source yields any generated top-level child (the PRD generated nothin
 Apply the **per-vendor terminal-state predicate from the `prd-lifecycle-rollup` rule** to every generated **top-level** work item (cite the rule by slug — do not restate its predicate table here). In summary, a top-level child is:
 
 - **Terminal** — it has reached its source/tracker's done/shipped state (GitHub: closed + the resolved build `done` role label where used; Linear: a `done`-category completed state; JIRA: `statusCategory.key == "done"`; Notion/Confluence: the documented generated-work entry marked done). A generated Epic is terminal only when *it* has rolled up to its own terminal state per `leaf-only-lifecycle` — read the child's own resolved state; do not re-derive it from its leaves.
-- **Terminal-but-dropped** — closed-as-not-planned (GitHub `stateReason == "not_planned"`) / canceled (Linear) / won't-do. It does **not** hold the PRD open and is excluded from the required set.
+- **Terminal-but-dropped** — closed-as-not-planned (GitHub `stateReason == "not_planned"`) / canceled or duplicate (Linear — both are terminal `state.type`s; `duplicate` is distinct from `canceled`) / won't-do. It does **not** hold the PRD open and is excluded from the required set.
 - **Incomplete / blocked** — anything else (still open, or closed without the `done` role). It holds the PRD open.
 
 The **required** set is the top-level children minus the terminal-but-dropped ones. Branch:

package/plugins/src/expo/.claude-plugin/plugin.json

@@ -4,6 +4,17 @@
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": { "name": "Cody Swann" },
   "dependencies": ["lisa-typescript"],
-  "hooks": {}
-
+  "hooks": {
+    "SessionStart": [
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "${CLAUDE_PLUGIN_ROOT}/hooks/register-maestro-mcp.sh"
+          }
+        ]
+      }
+    ]
+  }
 }

package/plugins/src/expo/THIRD-PARTY-NOTICES.md

@@ -35,15 +35,27 @@ NOT registered in `.mcp.json`. Coding agents spawn stdio servers with a
 non-login PATH, so an always-on entry fails visibly (Claude Code shows a
 "Failed to reconnect … -32000" error every session) on any machine missing the
 Maestro CLI or a resolvable Java runtime — which is most of the fleet. Opt in
-per machine instead, e.g.:
+per machine instead.
+
+The supported path is the **`/lisa-expo:maestro-mcp-setup`** skill (Codex:
+`$maestro-mcp-setup`), which detects the Maestro CLI and a usable Java runtime,
+installs or guides whatever is missing, and registers `maestro mcp` at
+**local/per-machine scope** with an absolute command path and injected
+`JAVA_HOME`/`PATH` — so the spawn works even under a non-login PATH.
+
+To register by hand instead, keep it at local scope and inject the toolchain,
+e.g.:
 
 ```
-claude mcp add --scope local maestro -- maestro mcp
+# Resolve a real JAVA_HOME from the JVM (robust when `java` is a shim/symlink):
+JAVA_HOME="$(java -XshowSettings:properties -version 2>&1 | sed -n 's/^[[:space:]]*java\.home = //p' | head -n1)"
+claude mcp add --scope local maestro \
+  --env "JAVA_HOME=$JAVA_HOME" --env "PATH=$JAVA_HOME/bin:$HOME/.maestro/bin:$PATH" \
+  -- "$HOME/.maestro/bin/maestro" mcp
 ```
 
-ensuring `maestro` and a Java runtime are on the non-interactive PATH (mise
-users: `claude mcp add --scope local maestro -- mise exec java -- maestro mcp`
-from a directory where Java is active).
+Never register at `--scope project` / a committed `.mcp.json` — that is the
+always-on form that reds out every other machine in the fleet.
 
 ### MIT License
 

package/plugins/src/expo/commands/maestro-mcp-setup.md

@@ -0,0 +1,7 @@
+---
+description: "Enable the Maestro CLI's MCP server (maestro mcp, STDIO) for this machine, robustly. Detects the Maestro CLI + a usable Java runtime (honoring mise/asdf/sdkman), installs or guides what is missing, and registers the server at LOCAL/per-machine scope with an absolute command path and injected JAVA_HOME/PATH so the spawn never dies on a non-login PATH. Never registers at committed/project scope, which would reintroduce the fleet-wide -32000 failure."
+allowed-tools: ["Skill"]
+argument-hint: ""
+---
+
+Use the /lisa-expo:maestro-mcp-setup skill to enable the Maestro MCP server for this machine: detect the Maestro CLI and a usable Java runtime, install or guide whatever is missing (preferring the project's version manager), and register `maestro mcp` at local/per-machine scope with an absolute command path plus injected JAVA_HOME/PATH env. Local scope only — never a committed project `.mcp.json`. $ARGUMENTS