@codyswann/lisa 2.325.1 → 2.325.3

package/dist/core/upstream-evidence-manifest.js

@@ -425,7 +425,7 @@ export const UPSTREAM_EVIDENCE_MANIFEST = Object.freeze({
     "plugins/src/base/skills/lisa-debrief/SKILL.md": "47e4cda36b07994ff47ab15fb04a17dd6b0c310ad804f9cae9d69637edaaa72a",
     "plugins/src/base/skills/lisa-delivery-effectiveness/SKILL.md": "21bc55fa0e86a9694bd22269fd089dbfae0c54c199262f46a4955447acea0f35",
     "plugins/src/base/skills/lisa-detect-tooling/SKILL.md": "1778a009d06099b3bd2d9a33b37bec34836b295e21fad220ae926491d3557208",
-    "plugins/src/base/skills/lisa-detect-tooling/scripts/detect-tooling.mjs": "90086ca11dafb5250ee930fa78fd3cc7d4bd601ad57f3e3c1a49920f7d7a1493",
+    "plugins/src/base/skills/lisa-detect-tooling/scripts/detect-tooling.mjs": "05e0c4808e64fbdc277419ad00b6a68da96766a9261a5b97f3a4961bbab107c4",
     "plugins/src/base/skills/lisa-doctor/SKILL.md": "fb41a1e63c5332d47a46e715aff52551f3df867033b5e4f37dfaeee30019b891",
     "plugins/src/base/skills/lisa-drive-pr-to-merge/SKILL.md": "c78ae2ba32c830d0b2cd7d24de91adf99e2b3cef4c7cab1c417580d86f41351f",
     "plugins/src/base/skills/lisa-epic-triage/SKILL.md": "d02760411249bddbd396f283191fe3e82bb7b95bf9393a19a7025dc5a57c3ab7",

package/package.json

@@ -115,7 +115,7 @@
     "brace-expansion": ">=5.0.9"
   },
   "name": "@codyswann/lisa",
-  "version": "2.325.1",
+  "version": "2.325.3",
   "description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
   "main": "dist/index.js",
   "exports": {

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

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

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

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

package/plugins/lisa/.codex-plugin/skills/lisa-detect-tooling/scripts/detect-tooling.mjs

@@ -51,8 +51,13 @@ const KNOWN_TOOLS = Object.freeze({
     viaNpm: "@playwright/test",
   },
   linear: {
-    why: "Linear is wired as an MCP server, which needs browser OAuth and so cannot authenticate in a container.",
+    why: "Linear reaches a container through lisa-linear-access with LINEAR_API_KEY; only the MCP path needs browser OAuth, and there is no official CLI to pin.",
     mcpFallback: "linear-server",
+    // No official Linear CLI exists, so no proposal can name one. Kept even
+    // though the substrate allowlist normally removes Linear before this
+    // point: a second signal reaching here must not resurrect a binary that
+    // does not exist.
+    noCli: true,
   },
 });
 
@@ -107,18 +112,35 @@ export function toolsFromScripts(pkg) {
  * Treating the MCP server as CLI evidence would push operators toward an
  * arbitrary third-party executable instead of the access-layer contract.
  */
+/** Prefix marking evidence that shows a path is missing, not what fills it. */
+const MCP_EVIDENCE = "MCP";
+
+/** What to ask when the only evidence is an MCP-only integration. */
+const REMOTE_PATH_QUESTION =
+  "no manifest entry proposed — confirm how this reaches a container: a CLI, " +
+  "a key-authenticated API call, or deliberately local-only";
+
 const MCP_ACCESS_LAYER_SUBSTRATES = Object.freeze({
   "linear-server":
     "lisa-linear-access uses LINEAR_API_KEY in headless sessions",
 });
 
 /**
- * Tools implied by MCP servers that also have a CLI.
+ * Integrations wired only as an MCP server — the weakest signal here, and the
+ * easiest to over-read.
+ *
+ * True: an MCP server that authenticates interactively cannot authenticate in a
+ * container, so THAT path does not survive the trip.
+ *
+ * Not implied: that the integration is unavailable, or that a CLI is the
+ * answer. Linear proves both halves — its MCP server needs browser OAuth, and
+ * its GraphQL API is key-authenticated, so `lisa-linear-access` already reaches
+ * it headlessly with LINEAR_API_KEY and there is no official CLI to pin at all.
+ * A server whose access layer owns headless auth is skipped entirely.
  *
- * An MCP server is not a substitute for the binary. Several authenticate by
- * browser OAuth, which a container cannot do at all, so a project relying on one
- * remotely has no integration rather than a degraded one — the CLI is the form
- * that survives the trip.
+ * For anything else, this raises a QUESTION rather than asserting a need: this
+ * integration has no remote path as configured, confirm it has one. The answer
+ * may be a CLI, may be a direct API call, and may be "local-only on purpose".
  * @param {object|null} mcp Parsed .mcp.json.
  * @returns {Map<string, string>} Tool name to the server that implies it.
  */
@@ -139,7 +161,8 @@ export function toolsFromMcp(mcp) {
     if (server) {
       found.set(
         tool,
-        `MCP server "${server}" (browser OAuth cannot run remotely)`
+        `${MCP_EVIDENCE} server "${server}" — an interactively authenticated ` +
+          `MCP server has no remote path; confirm this integration has one`
       );
     }
   }
@@ -182,8 +205,16 @@ export function toolsFromSecretNotes(notes) {
  */
 export function toolsFromQuality(config) {
   const found = new Map();
-  if (config?.quality?.e2eCoverage?.playwright) {
-    found.set("playwright", "quality.e2eCoverage.playwright is configured");
+  // Every runner under e2eCoverage, not a hardcoded one. Naming `playwright`
+  // explicitly meant `quality.e2eCoverage.maestro` — configured in this very
+  // repository — produced no signal at all, so the one tool that genuinely
+  // needs a pinned binary and genuinely was not declared stayed invisible to
+  // the detector built to find it. A gate that reports "nothing outstanding"
+  // while the gap is right there is worse than no gate.
+  for (const runner of Object.keys(config?.quality?.e2eCoverage ?? {})) {
+    if (Object.hasOwn(KNOWN_TOOLS, runner)) {
+      found.set(runner, `quality.e2eCoverage.${runner} is configured`);
+    }
   }
   if (config?.quality?.sonar || config?.sonar) {
     found.set("sonar-scanner", "Sonar analysis is configured");
@@ -215,6 +246,32 @@ export function declaredTools(config, surface = "remote") {
   );
 }
 
+/**
+ * Whether a tool already reaches this project as an npm dependency.
+ *
+ * A package that declares `@playwright/test` gets the `playwright` binary in
+ * `node_modules/.bin`, and its npm scripts resolve it from there. It never
+ * needs to be on PATH, so proposing a manifest entry for it is noise — and
+ * noise is how a detector teaches people to skim it, which is the one failure
+ * this skill's own documentation warns about.
+ *
+ * Only the CLI is covered by this. Anything else the tool needs at runtime —
+ * Playwright's browsers, for instance — is a separate concern that a package
+ * manager does not solve and this function does not claim to.
+ * @param {object|null} pkg Parsed package.json.
+ * @param {string} tool Tool name.
+ * @returns {boolean} Whether npm already provides the binary.
+ */
+export function satisfiedByNpm(pkg, tool) {
+  const viaNpm = KNOWN_TOOLS[tool]?.viaNpm;
+  if (!viaNpm) return false;
+  const declared = {
+    ...(pkg?.dependencies ?? {}),
+    ...(pkg?.devDependencies ?? {}),
+  };
+  return Object.hasOwn(declared, viaNpm);
+}
+
 /**
  * Collect every signal and subtract what the manifest already covers.
  * @param {string} [cwd] Project root.
@@ -238,6 +295,8 @@ export function detectTooling(cwd = process.cwd()) {
   for (const signal of signals) {
     for (const [tool, evidence] of signal) {
       if (declared.has(tool)) continue;
+      // Already provided by the package manager, so there is nothing to pin.
+      if (satisfiedByNpm(pkg, tool)) continue;
       const entry = merged.get(tool) ?? { evidence: [] };
       entry.evidence.push(evidence);
       merged.set(tool, entry);
@@ -263,6 +322,17 @@ export function detectTooling(cwd = process.cwd()) {
  * @returns {{install: object[], require: object[]}} Manifest skeletons.
  */
 export function proposedEntries(proposal) {
+  // Whether a binary can be proposed is a fact about the TOOL, not about how it
+  // was detected. Keying this on "the evidence was an MCP server" suppressed
+  // exactly the wrong case: the substrate allowlist already removes Linear
+  // before it becomes evidence, so the only tools reaching that branch were
+  // ones like Maestro that genuinely do have a CLI — the binary the Expo
+  // template invokes and nothing installs.
+  //
+  // So the question is asked only where there is no pinnable CLI to name.
+  if (KNOWN_TOOLS[proposal.name]?.noCli) {
+    return { install: [], require: [], question: REMOTE_PATH_QUESTION };
+  }
   const viaNpm = KNOWN_TOOLS[proposal.name]?.viaNpm;
   if (viaNpm) {
     // npm resolves per platform, so one entry serves every surface.
@@ -317,6 +387,7 @@ if (process.argv[1] && import.meta.url === `file://${process.argv[1]}`) {
         console.log(`    evidence: ${evidence}`);
       }
       const entries = proposedEntries(proposal);
+      if (entries.question) console.log(`    ${entries.question}`);
       for (const entry of entries.install) {
         console.log(`    tools.install: ${JSON.stringify(entry)}`);
       }

package/plugins/lisa/skills/lisa-detect-tooling/scripts/detect-tooling.mjs

@@ -51,8 +51,13 @@ const KNOWN_TOOLS = Object.freeze({
     viaNpm: "@playwright/test",
   },
   linear: {
-    why: "Linear is wired as an MCP server, which needs browser OAuth and so cannot authenticate in a container.",
+    why: "Linear reaches a container through lisa-linear-access with LINEAR_API_KEY; only the MCP path needs browser OAuth, and there is no official CLI to pin.",
     mcpFallback: "linear-server",
+    // No official Linear CLI exists, so no proposal can name one. Kept even
+    // though the substrate allowlist normally removes Linear before this
+    // point: a second signal reaching here must not resurrect a binary that
+    // does not exist.
+    noCli: true,
   },
 });
 
@@ -107,18 +112,35 @@ export function toolsFromScripts(pkg) {
  * Treating the MCP server as CLI evidence would push operators toward an
  * arbitrary third-party executable instead of the access-layer contract.
  */
+/** Prefix marking evidence that shows a path is missing, not what fills it. */
+const MCP_EVIDENCE = "MCP";
+
+/** What to ask when the only evidence is an MCP-only integration. */
+const REMOTE_PATH_QUESTION =
+  "no manifest entry proposed — confirm how this reaches a container: a CLI, " +
+  "a key-authenticated API call, or deliberately local-only";
+
 const MCP_ACCESS_LAYER_SUBSTRATES = Object.freeze({
   "linear-server":
     "lisa-linear-access uses LINEAR_API_KEY in headless sessions",
 });
 
 /**
- * Tools implied by MCP servers that also have a CLI.
+ * Integrations wired only as an MCP server — the weakest signal here, and the
+ * easiest to over-read.
+ *
+ * True: an MCP server that authenticates interactively cannot authenticate in a
+ * container, so THAT path does not survive the trip.
+ *
+ * Not implied: that the integration is unavailable, or that a CLI is the
+ * answer. Linear proves both halves — its MCP server needs browser OAuth, and
+ * its GraphQL API is key-authenticated, so `lisa-linear-access` already reaches
+ * it headlessly with LINEAR_API_KEY and there is no official CLI to pin at all.
+ * A server whose access layer owns headless auth is skipped entirely.
  *
- * An MCP server is not a substitute for the binary. Several authenticate by
- * browser OAuth, which a container cannot do at all, so a project relying on one
- * remotely has no integration rather than a degraded one — the CLI is the form
- * that survives the trip.
+ * For anything else, this raises a QUESTION rather than asserting a need: this
+ * integration has no remote path as configured, confirm it has one. The answer
+ * may be a CLI, may be a direct API call, and may be "local-only on purpose".
  * @param {object|null} mcp Parsed .mcp.json.
  * @returns {Map<string, string>} Tool name to the server that implies it.
  */
@@ -139,7 +161,8 @@ export function toolsFromMcp(mcp) {
     if (server) {
       found.set(
         tool,
-        `MCP server "${server}" (browser OAuth cannot run remotely)`
+        `${MCP_EVIDENCE} server "${server}" — an interactively authenticated ` +
+          `MCP server has no remote path; confirm this integration has one`
       );
     }
   }
@@ -182,8 +205,16 @@ export function toolsFromSecretNotes(notes) {
  */
 export function toolsFromQuality(config) {
   const found = new Map();
-  if (config?.quality?.e2eCoverage?.playwright) {
-    found.set("playwright", "quality.e2eCoverage.playwright is configured");
+  // Every runner under e2eCoverage, not a hardcoded one. Naming `playwright`
+  // explicitly meant `quality.e2eCoverage.maestro` — configured in this very
+  // repository — produced no signal at all, so the one tool that genuinely
+  // needs a pinned binary and genuinely was not declared stayed invisible to
+  // the detector built to find it. A gate that reports "nothing outstanding"
+  // while the gap is right there is worse than no gate.
+  for (const runner of Object.keys(config?.quality?.e2eCoverage ?? {})) {
+    if (Object.hasOwn(KNOWN_TOOLS, runner)) {
+      found.set(runner, `quality.e2eCoverage.${runner} is configured`);
+    }
   }
   if (config?.quality?.sonar || config?.sonar) {
     found.set("sonar-scanner", "Sonar analysis is configured");
@@ -215,6 +246,32 @@ export function declaredTools(config, surface = "remote") {
   );
 }
 
+/**
+ * Whether a tool already reaches this project as an npm dependency.
+ *
+ * A package that declares `@playwright/test` gets the `playwright` binary in
+ * `node_modules/.bin`, and its npm scripts resolve it from there. It never
+ * needs to be on PATH, so proposing a manifest entry for it is noise — and
+ * noise is how a detector teaches people to skim it, which is the one failure
+ * this skill's own documentation warns about.
+ *
+ * Only the CLI is covered by this. Anything else the tool needs at runtime —
+ * Playwright's browsers, for instance — is a separate concern that a package
+ * manager does not solve and this function does not claim to.
+ * @param {object|null} pkg Parsed package.json.
+ * @param {string} tool Tool name.
+ * @returns {boolean} Whether npm already provides the binary.
+ */
+export function satisfiedByNpm(pkg, tool) {
+  const viaNpm = KNOWN_TOOLS[tool]?.viaNpm;
+  if (!viaNpm) return false;
+  const declared = {
+    ...(pkg?.dependencies ?? {}),
+    ...(pkg?.devDependencies ?? {}),
+  };
+  return Object.hasOwn(declared, viaNpm);
+}
+
 /**
  * Collect every signal and subtract what the manifest already covers.
  * @param {string} [cwd] Project root.
@@ -238,6 +295,8 @@ export function detectTooling(cwd = process.cwd()) {
   for (const signal of signals) {
     for (const [tool, evidence] of signal) {
       if (declared.has(tool)) continue;
+      // Already provided by the package manager, so there is nothing to pin.
+      if (satisfiedByNpm(pkg, tool)) continue;
       const entry = merged.get(tool) ?? { evidence: [] };
       entry.evidence.push(evidence);
       merged.set(tool, entry);
@@ -263,6 +322,17 @@ export function detectTooling(cwd = process.cwd()) {
  * @returns {{install: object[], require: object[]}} Manifest skeletons.
  */
 export function proposedEntries(proposal) {
+  // Whether a binary can be proposed is a fact about the TOOL, not about how it
+  // was detected. Keying this on "the evidence was an MCP server" suppressed
+  // exactly the wrong case: the substrate allowlist already removes Linear
+  // before it becomes evidence, so the only tools reaching that branch were
+  // ones like Maestro that genuinely do have a CLI — the binary the Expo
+  // template invokes and nothing installs.
+  //
+  // So the question is asked only where there is no pinnable CLI to name.
+  if (KNOWN_TOOLS[proposal.name]?.noCli) {
+    return { install: [], require: [], question: REMOTE_PATH_QUESTION };
+  }
   const viaNpm = KNOWN_TOOLS[proposal.name]?.viaNpm;
   if (viaNpm) {
     // npm resolves per platform, so one entry serves every surface.
@@ -317,6 +387,7 @@ if (process.argv[1] && import.meta.url === `file://${process.argv[1]}`) {
         console.log(`    evidence: ${evidence}`);
       }
       const entries = proposedEntries(proposal);
+      if (entries.question) console.log(`    ${entries.question}`);
       for (const entry of entries.install) {
         console.log(`    tools.install: ${JSON.stringify(entry)}`);
       }

package/plugins/lisa-agy/plugin.json

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

package/plugins/lisa-agy/skills/lisa-detect-tooling/scripts/detect-tooling.mjs

@@ -51,8 +51,13 @@ const KNOWN_TOOLS = Object.freeze({
     viaNpm: "@playwright/test",
   },
   linear: {
-    why: "Linear is wired as an MCP server, which needs browser OAuth and so cannot authenticate in a container.",
+    why: "Linear reaches a container through lisa-linear-access with LINEAR_API_KEY; only the MCP path needs browser OAuth, and there is no official CLI to pin.",
     mcpFallback: "linear-server",
+    // No official Linear CLI exists, so no proposal can name one. Kept even
+    // though the substrate allowlist normally removes Linear before this
+    // point: a second signal reaching here must not resurrect a binary that
+    // does not exist.
+    noCli: true,
   },
 });
 
@@ -107,18 +112,35 @@ export function toolsFromScripts(pkg) {
  * Treating the MCP server as CLI evidence would push operators toward an
  * arbitrary third-party executable instead of the access-layer contract.
  */
+/** Prefix marking evidence that shows a path is missing, not what fills it. */
+const MCP_EVIDENCE = "MCP";
+
+/** What to ask when the only evidence is an MCP-only integration. */
+const REMOTE_PATH_QUESTION =
+  "no manifest entry proposed — confirm how this reaches a container: a CLI, " +
+  "a key-authenticated API call, or deliberately local-only";
+
 const MCP_ACCESS_LAYER_SUBSTRATES = Object.freeze({
   "linear-server":
     "lisa-linear-access uses LINEAR_API_KEY in headless sessions",
 });
 
 /**
- * Tools implied by MCP servers that also have a CLI.
+ * Integrations wired only as an MCP server — the weakest signal here, and the
+ * easiest to over-read.
+ *
+ * True: an MCP server that authenticates interactively cannot authenticate in a
+ * container, so THAT path does not survive the trip.
+ *
+ * Not implied: that the integration is unavailable, or that a CLI is the
+ * answer. Linear proves both halves — its MCP server needs browser OAuth, and
+ * its GraphQL API is key-authenticated, so `lisa-linear-access` already reaches
+ * it headlessly with LINEAR_API_KEY and there is no official CLI to pin at all.
+ * A server whose access layer owns headless auth is skipped entirely.
  *
- * An MCP server is not a substitute for the binary. Several authenticate by
- * browser OAuth, which a container cannot do at all, so a project relying on one
- * remotely has no integration rather than a degraded one — the CLI is the form
- * that survives the trip.
+ * For anything else, this raises a QUESTION rather than asserting a need: this
+ * integration has no remote path as configured, confirm it has one. The answer
+ * may be a CLI, may be a direct API call, and may be "local-only on purpose".
  * @param {object|null} mcp Parsed .mcp.json.
  * @returns {Map<string, string>} Tool name to the server that implies it.
  */
@@ -139,7 +161,8 @@ export function toolsFromMcp(mcp) {
     if (server) {
       found.set(
         tool,
-        `MCP server "${server}" (browser OAuth cannot run remotely)`
+        `${MCP_EVIDENCE} server "${server}" — an interactively authenticated ` +
+          `MCP server has no remote path; confirm this integration has one`
       );
     }
   }
@@ -182,8 +205,16 @@ export function toolsFromSecretNotes(notes) {
  */
 export function toolsFromQuality(config) {
   const found = new Map();
-  if (config?.quality?.e2eCoverage?.playwright) {
-    found.set("playwright", "quality.e2eCoverage.playwright is configured");
+  // Every runner under e2eCoverage, not a hardcoded one. Naming `playwright`
+  // explicitly meant `quality.e2eCoverage.maestro` — configured in this very
+  // repository — produced no signal at all, so the one tool that genuinely
+  // needs a pinned binary and genuinely was not declared stayed invisible to
+  // the detector built to find it. A gate that reports "nothing outstanding"
+  // while the gap is right there is worse than no gate.
+  for (const runner of Object.keys(config?.quality?.e2eCoverage ?? {})) {
+    if (Object.hasOwn(KNOWN_TOOLS, runner)) {
+      found.set(runner, `quality.e2eCoverage.${runner} is configured`);
+    }
   }
   if (config?.quality?.sonar || config?.sonar) {
     found.set("sonar-scanner", "Sonar analysis is configured");
@@ -215,6 +246,32 @@ export function declaredTools(config, surface = "remote") {
   );
 }
 
+/**
+ * Whether a tool already reaches this project as an npm dependency.
+ *
+ * A package that declares `@playwright/test` gets the `playwright` binary in
+ * `node_modules/.bin`, and its npm scripts resolve it from there. It never
+ * needs to be on PATH, so proposing a manifest entry for it is noise — and
+ * noise is how a detector teaches people to skim it, which is the one failure
+ * this skill's own documentation warns about.
+ *
+ * Only the CLI is covered by this. Anything else the tool needs at runtime —
+ * Playwright's browsers, for instance — is a separate concern that a package
+ * manager does not solve and this function does not claim to.
+ * @param {object|null} pkg Parsed package.json.
+ * @param {string} tool Tool name.
+ * @returns {boolean} Whether npm already provides the binary.
+ */
+export function satisfiedByNpm(pkg, tool) {
+  const viaNpm = KNOWN_TOOLS[tool]?.viaNpm;
+  if (!viaNpm) return false;
+  const declared = {
+    ...(pkg?.dependencies ?? {}),
+    ...(pkg?.devDependencies ?? {}),
+  };
+  return Object.hasOwn(declared, viaNpm);
+}
+
 /**
  * Collect every signal and subtract what the manifest already covers.
  * @param {string} [cwd] Project root.
@@ -238,6 +295,8 @@ export function detectTooling(cwd = process.cwd()) {
   for (const signal of signals) {
     for (const [tool, evidence] of signal) {
       if (declared.has(tool)) continue;
+      // Already provided by the package manager, so there is nothing to pin.
+      if (satisfiedByNpm(pkg, tool)) continue;
       const entry = merged.get(tool) ?? { evidence: [] };
       entry.evidence.push(evidence);
       merged.set(tool, entry);
@@ -263,6 +322,17 @@ export function detectTooling(cwd = process.cwd()) {
  * @returns {{install: object[], require: object[]}} Manifest skeletons.
  */
 export function proposedEntries(proposal) {
+  // Whether a binary can be proposed is a fact about the TOOL, not about how it
+  // was detected. Keying this on "the evidence was an MCP server" suppressed
+  // exactly the wrong case: the substrate allowlist already removes Linear
+  // before it becomes evidence, so the only tools reaching that branch were
+  // ones like Maestro that genuinely do have a CLI — the binary the Expo
+  // template invokes and nothing installs.
+  //
+  // So the question is asked only where there is no pinnable CLI to name.
+  if (KNOWN_TOOLS[proposal.name]?.noCli) {
+    return { install: [], require: [], question: REMOTE_PATH_QUESTION };
+  }
   const viaNpm = KNOWN_TOOLS[proposal.name]?.viaNpm;
   if (viaNpm) {
     // npm resolves per platform, so one entry serves every surface.
@@ -317,6 +387,7 @@ if (process.argv[1] && import.meta.url === `file://${process.argv[1]}`) {
         console.log(`    evidence: ${evidence}`);
       }
       const entries = proposedEntries(proposal);
+      if (entries.question) console.log(`    ${entries.question}`);
       for (const entry of entries.install) {
         console.log(`    tools.install: ${JSON.stringify(entry)}`);
       }

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.325.1",
+  "version": "2.325.3",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.325.1",
+  "version": "2.325.3",
   "description": "AWS CDK-specific Lisa plugin.",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.325.1",
+  "version": "2.325.3",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.325.1",
+  "version": "2.325.3",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.325.1",
+  "version": "2.325.3",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

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

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