@codyswann/lisa 3.11.6 → 3.11.7

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

@@ -571,7 +571,7 @@ export const UPSTREAM_EVIDENCE_MANIFEST = Object.freeze({
     "plugins/src/base/skills/lisa-parity-code-review/SKILL.md": "5805254747c4ed9081fd514236f06e078be86d41694bf74b480bf7592cd58c1f",
     "plugins/src/base/skills/lisa-parity-code-simplifier/SKILL.md": "c721ae772e73abff633c43d93267066afac188e911a77322fbb102db673849d7",
     "plugins/src/base/skills/lisa-parity-coderabbit/SKILL.md": "ae882837d43741293d1b639c4516331fa6124fa1f5da234a74ecb31c5d7e52cd",
-    "plugins/src/base/skills/lisa-parity-safety-net-rules/SKILL.md": "f240857de2f14938009ddd212c56601269fd9e1aec33a766cd09da5bea5656e0",
+    "plugins/src/base/skills/lisa-parity-safety-net-rules/SKILL.md": "4b00da1ced810e8604572a0ae36bbd3188835fce22413fc73a214741973f9255",
     "plugins/src/base/skills/lisa-parity-sentry-sdk-setup/SKILL.md": "edb513a9d29b3faeccce71d92596e12bc1f35e44fe3af1349bd7bd473fee98af",
     "plugins/src/base/skills/lisa-parity-sentry-seer/SKILL.md": "ec09515906a55e98ac0f619f048f14c4a16db74c1cd5744dda0cdfa42ce7fed6",
     "plugins/src/base/skills/lisa-parity-skill-creator/SKILL.md": "616e0493f75fe92c18137548d7c86a91a9b04d9844ca76fa3f14156e3e7814e5",
@@ -1037,7 +1037,7 @@ export const UPSTREAM_EVIDENCE_MANIFEST = Object.freeze({
     "scripts/check-duplicate-versions.mjs": "84d97e94eb834522848ddce951bb54ae9da1e4be252e2c51fed0c01c4f4d6b72",
     "scripts/check-learnings-budget.ts": "007430c2d6938efcc79ccbfd5717ebe2c7cf66b4de9a21a3e67b8db7f3600349",
     "scripts/check-plugins-sync.sh": "3a99cbff0e8ec5e7c944690eae003a6d51b51c85436d77bd37faea4d553728af",
-    "scripts/check-required-check-promotions.mjs": "2693787413a276f7493c0fac1407a2e61630b2978d20acebb0ee5463c4678660",
+    "scripts/check-required-check-promotions.mjs": "f644f0feb246f36a79efaa6b820409605c637813e158aea425982b863bb6ed7c",
     "scripts/check-rules-pairing.sh": "4d4a0d9e8d36794a22020f419c879d7336b1c5bfe883acdcc826d26764560c7a",
     "scripts/check-security-floors.mjs": "0060a0f65885b54fc93bd3885ca249cbb1ac822c52813817aae640bc1303827b",
     "scripts/check-state-classification.mjs": "26baaa85c0758fa41f1f66257f7d3a31ea4dd5cf17a9c0acaa3e89caaaf6265a",

package/package.json

@@ -122,7 +122,7 @@
     }
   },
   "name": "@codyswann/lisa",
-  "version": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "description": "Universal governance: agents, skills, commands, hooks, and rules for all projects.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa/.codex-plugin/skills/lisa-parity-safety-net-rules/SKILL.md

@@ -2,7 +2,7 @@
 name: lisa-parity-safety-net-rules
 description: "View, set, and verify the…"
 allowed-tools: ["Read", "Edit", "Write", "Bash"]
-synced-from: safety-net@cc-marketplace@2.0.3
+synced-from: safety-net@cc-marketplace@2.0.4
 ---
 
 # Parity Safety-Net Rules
@@ -24,7 +24,7 @@ project-specific rules on top of those built-ins.
 > against Lisa conventions — it does **not** port or invoke upstream plugin
 > code.
 >
-> **Drift tracking.** Pinned to `safety-net@cc-marketplace@2.0.3`.
+> **Drift tracking.** Pinned to `safety-net@cc-marketplace@2.0.4`.
 > `scripts/plugin-parity-drift.mjs` compares this pin against the upstream
 > version in the plugin cache and flags staleness. **Do not port or copy upstream
 > plugin code.**
@@ -34,7 +34,22 @@ project-specific rules on top of those built-ins.
 > rule-management skill or Lisa's project-local ERE rule contract, and Lisa does
 > not currently ship hooks for those runtimes, so no behavior is absorbed here.
 >
-> **Known gap at the 2.0.3 pin.** Upstream 2.0.0 rebuilt its engine and added two
+> **2.0.4 review.** Method, so the next person can re-run it rather than trust
+> it: hash the sorted (relative path, content) manifest of every rule-bearing
+> directory in the plugin cache under both versions, then diff the trees
+> excluding `dist/`, `.git/`, and `node_modules/`. Result — `src/` (230 files),
+> `skills/` (1), and `hooks/` (1) are byte-identical across 2.0.3 and 2.0.4
+> (`src` digest `7e346e205fbd1aa7` both sides). The only non-generated
+> differences are the `version` string in `package.json`, `kimi.plugin.json`,
+> and `.claude-plugin/plugin.json`, plus a test-harness fix in
+> `tests/cli/cli-statusline.test.ts` that tolerates EPIPE when an oversized
+> payload is flushed at the bounded reader's cap. Everything else is rebuilt
+> `dist/` output. No rule, guard family, or skill surface moved, so nothing is
+> absorbed here — and, critically, **2.0.4 does not close the gap recorded
+> below**, which therefore carries forward unchanged rather than being dropped
+> at the new pin.
+>
+> **Known gap at the 2.0.4 pin.** Upstream 2.0.0 rebuilt its engine and added two
 > guard families this hook does **not** mirror: `secret.*` (blocks reading or
 > copying SSH keys, `.env` files, cloud credentials, and coding-CLI credential
 > stores) and `rm.git-metadata` (blocks deleting the `.git` control plane). Both

package/plugins/lisa/skills/lisa-parity-safety-net-rules/SKILL.md

@@ -2,7 +2,7 @@
 name: lisa-parity-safety-net-rules
 description: "View, set, and verify the custom guard rules enforced by Lisa's safety-net PreToolUse Bash hook (parity-safety-net.sh). The consolidated cross-agent equivalent of the upstream safety-net plugin's set-custom-rules + verify-custom-rules skills — manages a project-local list of extended-regex patterns that block destructive shell commands, on Codex, agy, Copilot, Cursor, and Claude."
 allowed-tools: ["Read", "Edit", "Write", "Bash"]
-synced-from: safety-net@cc-marketplace@2.0.3
+synced-from: safety-net@cc-marketplace@2.0.4
 ---
 
 # Parity Safety-Net Rules
@@ -24,7 +24,7 @@ project-specific rules on top of those built-ins.
 > against Lisa conventions — it does **not** port or invoke upstream plugin
 > code.
 >
-> **Drift tracking.** Pinned to `safety-net@cc-marketplace@2.0.3`.
+> **Drift tracking.** Pinned to `safety-net@cc-marketplace@2.0.4`.
 > `scripts/plugin-parity-drift.mjs` compares this pin against the upstream
 > version in the plugin cache and flags staleness. **Do not port or copy upstream
 > plugin code.**
@@ -34,7 +34,22 @@ project-specific rules on top of those built-ins.
 > rule-management skill or Lisa's project-local ERE rule contract, and Lisa does
 > not currently ship hooks for those runtimes, so no behavior is absorbed here.
 >
-> **Known gap at the 2.0.3 pin.** Upstream 2.0.0 rebuilt its engine and added two
+> **2.0.4 review.** Method, so the next person can re-run it rather than trust
+> it: hash the sorted (relative path, content) manifest of every rule-bearing
+> directory in the plugin cache under both versions, then diff the trees
+> excluding `dist/`, `.git/`, and `node_modules/`. Result — `src/` (230 files),
+> `skills/` (1), and `hooks/` (1) are byte-identical across 2.0.3 and 2.0.4
+> (`src` digest `7e346e205fbd1aa7` both sides). The only non-generated
+> differences are the `version` string in `package.json`, `kimi.plugin.json`,
+> and `.claude-plugin/plugin.json`, plus a test-harness fix in
+> `tests/cli/cli-statusline.test.ts` that tolerates EPIPE when an oversized
+> payload is flushed at the bounded reader's cap. Everything else is rebuilt
+> `dist/` output. No rule, guard family, or skill surface moved, so nothing is
+> absorbed here — and, critically, **2.0.4 does not close the gap recorded
+> below**, which therefore carries forward unchanged rather than being dropped
+> at the new pin.
+>
+> **Known gap at the 2.0.4 pin.** Upstream 2.0.0 rebuilt its engine and added two
 > guard families this hook does **not** mirror: `secret.*` (blocks reading or
 > copying SSH keys, `.env` files, cloud credentials, and coding-CLI credential
 > stores) and `rm.git-metadata` (blocks deleting the `.git` control plane). Both

package/plugins/lisa-agy/plugin.json

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

package/plugins/lisa-agy/skills/lisa-parity-safety-net-rules/SKILL.md

@@ -2,7 +2,7 @@
 name: lisa-parity-safety-net-rules
 description: "View, set, and verify the custom guard rules enforced by Lisa's safety-net PreToolUse Bash hook (parity-safety-net.sh). The consolidated cross-agent equivalent of the upstream safety-net plugin's set-custom-rules + verify-custom-rules skills — manages a project-local list of extended-regex patterns that block destructive shell commands, on Codex, agy, Copilot, Cursor, and Claude."
 allowed-tools: ["Read", "Edit", "Write", "Bash"]
-synced-from: safety-net@cc-marketplace@2.0.3
+synced-from: safety-net@cc-marketplace@2.0.4
 ---
 
 # Parity Safety-Net Rules
@@ -24,7 +24,7 @@ project-specific rules on top of those built-ins.
 > against Lisa conventions — it does **not** port or invoke upstream plugin
 > code.
 >
-> **Drift tracking.** Pinned to `safety-net@cc-marketplace@2.0.3`.
+> **Drift tracking.** Pinned to `safety-net@cc-marketplace@2.0.4`.
 > `scripts/plugin-parity-drift.mjs` compares this pin against the upstream
 > version in the plugin cache and flags staleness. **Do not port or copy upstream
 > plugin code.**
@@ -34,7 +34,22 @@ project-specific rules on top of those built-ins.
 > rule-management skill or Lisa's project-local ERE rule contract, and Lisa does
 > not currently ship hooks for those runtimes, so no behavior is absorbed here.
 >
-> **Known gap at the 2.0.3 pin.** Upstream 2.0.0 rebuilt its engine and added two
+> **2.0.4 review.** Method, so the next person can re-run it rather than trust
+> it: hash the sorted (relative path, content) manifest of every rule-bearing
+> directory in the plugin cache under both versions, then diff the trees
+> excluding `dist/`, `.git/`, and `node_modules/`. Result — `src/` (230 files),
+> `skills/` (1), and `hooks/` (1) are byte-identical across 2.0.3 and 2.0.4
+> (`src` digest `7e346e205fbd1aa7` both sides). The only non-generated
+> differences are the `version` string in `package.json`, `kimi.plugin.json`,
+> and `.claude-plugin/plugin.json`, plus a test-harness fix in
+> `tests/cli/cli-statusline.test.ts` that tolerates EPIPE when an oversized
+> payload is flushed at the bounded reader's cap. Everything else is rebuilt
+> `dist/` output. No rule, guard family, or skill surface moved, so nothing is
+> absorbed here — and, critically, **2.0.4 does not close the gap recorded
+> below**, which therefore carries forward unchanged rather than being dropped
+> at the new pin.
+>
+> **Known gap at the 2.0.4 pin.** Upstream 2.0.0 rebuilt its engine and added two
 > guard families this hook does **not** mirror: `secret.*` (blocks reading or
 > copying SSH keys, `.env` files, cloud credentials, and coding-CLI credential
 > stores) and `rm.git-metadata` (blocks deleting the `.git` control plane). Both

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

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

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

package/plugins/lisa-copilot/skills/lisa-parity-safety-net-rules/SKILL.md

@@ -2,7 +2,7 @@
 name: lisa-parity-safety-net-rules
 description: "View, set, and verify the custom guard rules enforced by Lisa's safety-net PreToolUse Bash hook (parity-safety-net.sh). The consolidated cross-agent equivalent of the upstream safety-net plugin's set-custom-rules + verify-custom-rules skills — manages a project-local list of extended-regex patterns that block destructive shell commands, on Codex, agy, Copilot, Cursor, and Claude."
 allowed-tools: ["Read", "Edit", "Write", "Bash"]
-synced-from: safety-net@cc-marketplace@2.0.3
+synced-from: safety-net@cc-marketplace@2.0.4
 ---
 
 # Parity Safety-Net Rules
@@ -24,7 +24,7 @@ project-specific rules on top of those built-ins.
 > against Lisa conventions — it does **not** port or invoke upstream plugin
 > code.
 >
-> **Drift tracking.** Pinned to `safety-net@cc-marketplace@2.0.3`.
+> **Drift tracking.** Pinned to `safety-net@cc-marketplace@2.0.4`.
 > `scripts/plugin-parity-drift.mjs` compares this pin against the upstream
 > version in the plugin cache and flags staleness. **Do not port or copy upstream
 > plugin code.**
@@ -34,7 +34,22 @@ project-specific rules on top of those built-ins.
 > rule-management skill or Lisa's project-local ERE rule contract, and Lisa does
 > not currently ship hooks for those runtimes, so no behavior is absorbed here.
 >
-> **Known gap at the 2.0.3 pin.** Upstream 2.0.0 rebuilt its engine and added two
+> **2.0.4 review.** Method, so the next person can re-run it rather than trust
+> it: hash the sorted (relative path, content) manifest of every rule-bearing
+> directory in the plugin cache under both versions, then diff the trees
+> excluding `dist/`, `.git/`, and `node_modules/`. Result — `src/` (230 files),
+> `skills/` (1), and `hooks/` (1) are byte-identical across 2.0.3 and 2.0.4
+> (`src` digest `7e346e205fbd1aa7` both sides). The only non-generated
+> differences are the `version` string in `package.json`, `kimi.plugin.json`,
+> and `.claude-plugin/plugin.json`, plus a test-harness fix in
+> `tests/cli/cli-statusline.test.ts` that tolerates EPIPE when an oversized
+> payload is flushed at the bounded reader's cap. Everything else is rebuilt
+> `dist/` output. No rule, guard family, or skill surface moved, so nothing is
+> absorbed here — and, critically, **2.0.4 does not close the gap recorded
+> below**, which therefore carries forward unchanged rather than being dropped
+> at the new pin.
+>
+> **Known gap at the 2.0.4 pin.** Upstream 2.0.0 rebuilt its engine and added two
 > guard families this hook does **not** mirror: `secret.*` (blocks reading or
 > copying SSH keys, `.env` files, cloud credentials, and coding-CLI credential
 > stores) and `rm.git-metadata` (blocks deleting the `.git` control plane). Both

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

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

package/plugins/lisa-cursor/skills/lisa-parity-safety-net-rules/SKILL.md

@@ -2,7 +2,7 @@
 name: lisa-parity-safety-net-rules
 description: "View, set, and verify the custom guard rules enforced by Lisa's safety-net PreToolUse Bash hook (parity-safety-net.sh). The consolidated cross-agent equivalent of the upstream safety-net plugin's set-custom-rules + verify-custom-rules skills — manages a project-local list of extended-regex patterns that block destructive shell commands, on Codex, agy, Copilot, Cursor, and Claude."
 allowed-tools: ["Read", "Edit", "Write", "Bash"]
-synced-from: safety-net@cc-marketplace@2.0.3
+synced-from: safety-net@cc-marketplace@2.0.4
 ---
 
 # Parity Safety-Net Rules
@@ -24,7 +24,7 @@ project-specific rules on top of those built-ins.
 > against Lisa conventions — it does **not** port or invoke upstream plugin
 > code.
 >
-> **Drift tracking.** Pinned to `safety-net@cc-marketplace@2.0.3`.
+> **Drift tracking.** Pinned to `safety-net@cc-marketplace@2.0.4`.
 > `scripts/plugin-parity-drift.mjs` compares this pin against the upstream
 > version in the plugin cache and flags staleness. **Do not port or copy upstream
 > plugin code.**
@@ -34,7 +34,22 @@ project-specific rules on top of those built-ins.
 > rule-management skill or Lisa's project-local ERE rule contract, and Lisa does
 > not currently ship hooks for those runtimes, so no behavior is absorbed here.
 >
-> **Known gap at the 2.0.3 pin.** Upstream 2.0.0 rebuilt its engine and added two
+> **2.0.4 review.** Method, so the next person can re-run it rather than trust
+> it: hash the sorted (relative path, content) manifest of every rule-bearing
+> directory in the plugin cache under both versions, then diff the trees
+> excluding `dist/`, `.git/`, and `node_modules/`. Result — `src/` (230 files),
+> `skills/` (1), and `hooks/` (1) are byte-identical across 2.0.3 and 2.0.4
+> (`src` digest `7e346e205fbd1aa7` both sides). The only non-generated
+> differences are the `version` string in `package.json`, `kimi.plugin.json`,
+> and `.claude-plugin/plugin.json`, plus a test-harness fix in
+> `tests/cli/cli-statusline.test.ts` that tolerates EPIPE when an oversized
+> payload is flushed at the bounded reader's cap. Everything else is rebuilt
+> `dist/` output. No rule, guard family, or skill surface moved, so nothing is
+> absorbed here — and, critically, **2.0.4 does not close the gap recorded
+> below**, which therefore carries forward unchanged rather than being dropped
+> at the new pin.
+>
+> **Known gap at the 2.0.4 pin.** Upstream 2.0.0 rebuilt its engine and added two
 > guard families this hook does **not** mirror: `secret.*` (blocks reading or
 > copying SSH keys, `.env` files, cloud credentials, and coding-CLI credential
 > stores) and `rm.git-metadata` (blocks deleting the `.git` control plane). Both

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "3.11.6",
+  "version": "3.11.7",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "3.11.6",
+  "version": "3.11.7",
   "description": "Expo and React Native-specific skills, agents, rules, and MCP servers.",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "3.11.6",
+  "version": "3.11.7",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "3.11.6",
+  "version": "3.11.7",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "3.11.6",
+  "version": "3.11.7",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "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": "3.11.6",
+  "version": "3.11.7",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/src/base/skills/lisa-parity-safety-net-rules/SKILL.md

@@ -2,7 +2,7 @@
 name: lisa-parity-safety-net-rules
 description: "View, set, and verify the custom guard rules enforced by Lisa's safety-net PreToolUse Bash hook (parity-safety-net.sh). The consolidated cross-agent equivalent of the upstream safety-net plugin's set-custom-rules + verify-custom-rules skills — manages a project-local list of extended-regex patterns that block destructive shell commands, on Codex, agy, Copilot, Cursor, and Claude."
 allowed-tools: ["Read", "Edit", "Write", "Bash"]
-synced-from: safety-net@cc-marketplace@2.0.3
+synced-from: safety-net@cc-marketplace@2.0.4
 ---
 
 # Parity Safety-Net Rules
@@ -24,7 +24,7 @@ project-specific rules on top of those built-ins.
 > against Lisa conventions — it does **not** port or invoke upstream plugin
 > code.
 >
-> **Drift tracking.** Pinned to `safety-net@cc-marketplace@2.0.3`.
+> **Drift tracking.** Pinned to `safety-net@cc-marketplace@2.0.4`.
 > `scripts/plugin-parity-drift.mjs` compares this pin against the upstream
 > version in the plugin cache and flags staleness. **Do not port or copy upstream
 > plugin code.**
@@ -34,7 +34,22 @@ project-specific rules on top of those built-ins.
 > rule-management skill or Lisa's project-local ERE rule contract, and Lisa does
 > not currently ship hooks for those runtimes, so no behavior is absorbed here.
 >
-> **Known gap at the 2.0.3 pin.** Upstream 2.0.0 rebuilt its engine and added two
+> **2.0.4 review.** Method, so the next person can re-run it rather than trust
+> it: hash the sorted (relative path, content) manifest of every rule-bearing
+> directory in the plugin cache under both versions, then diff the trees
+> excluding `dist/`, `.git/`, and `node_modules/`. Result — `src/` (230 files),
+> `skills/` (1), and `hooks/` (1) are byte-identical across 2.0.3 and 2.0.4
+> (`src` digest `7e346e205fbd1aa7` both sides). The only non-generated
+> differences are the `version` string in `package.json`, `kimi.plugin.json`,
+> and `.claude-plugin/plugin.json`, plus a test-harness fix in
+> `tests/cli/cli-statusline.test.ts` that tolerates EPIPE when an oversized
+> payload is flushed at the bounded reader's cap. Everything else is rebuilt
+> `dist/` output. No rule, guard family, or skill surface moved, so nothing is
+> absorbed here — and, critically, **2.0.4 does not close the gap recorded
+> below**, which therefore carries forward unchanged rather than being dropped
+> at the new pin.
+>
+> **Known gap at the 2.0.4 pin.** Upstream 2.0.0 rebuilt its engine and added two
 > guard families this hook does **not** mirror: `secret.*` (blocks reading or
 > copying SSH keys, `.env` files, cloud credentials, and coding-CLI credential
 > stores) and `rm.git-metadata` (blocks deleting the `.git` control plane). Both

package/scripts/check-required-check-promotions.mjs

@@ -69,6 +69,48 @@
  *     `measured_on_subject` separately makes that mechanically visible instead
  *     of a footnote in a report.
  *
+ *  6. **A worst case must come from a run that COMPLETED, and must be below the
+ *     budget it justifies** (#2528). Two clauses, one rule:
+ *
+ *     *Do not size a budget from the duration of a run that failed on time.*
+ *     This is the mirror of clause 3. #2509 says do not size from runs that
+ *     passed, because the sample excludes the failure mode; the mirror says do
+ *     not size from the DURATION of a run the budget terminated, because that
+ *     duration is the starvation, not the work. The failing-run version is
+ *     strictly worse: it does not merely omit information, it INVERTS the
+ *     ratio — the more contended the box was, the safer the resulting budget
+ *     looks. So `observed_on` must say `"pass"`, meaning the measured run
+ *     completed inside its budget. (That is a statement about TIME, not about
+ *     the check's verdict: a run that reproduces a real violation and exits 1
+ *     in 30s completed, and is `"pass"` here.)
+ *
+ *     *And an entry claiming a worst case at or above its own budget refuses
+ *     itself*, needing no knowledge of the test, the machine, or the workload.
+ *     #2523 cited 60,245ms while setting the budget to 60,000ms. The ratio in
+ *     clause 4 already rejects that arithmetically at 0.996x, but it reports a
+ *     THIN MARGIN when the defect is an IMPOSSIBLE CLAIM, and a message that
+ *     misnames the defect sends the reader off to re-measure when they should
+ *     be re-reading. The tell was on the face of the number: a test cannot run
+ *     60s against a 10s budget, so 60,245ms was wall clock spent waiting.
+ *     Re-measured in isolation at load 31 the same test takes 2,499ms — 24x,
+ *     not 0.996x, a 24-fold error in the unsafe direction.
+ *
+ *     The class is not specific to test timeouts. #2520 chased an actionlint
+ *     invocation reported as taking "25 minutes". It was not slow: a
+ *     3,490-line workflow returns in 0s while a 217-line one hangs, and the
+ *     minimal repro is 28 lines. It is a spin inside actionlint's shellcheck
+ *     integration — ~850% CPU across 37 threads, zero children — so it never
+ *     terminates. The 25 minutes was the observer's patience, not the
+ *     command's cost, and NO budget would have been generous enough. That is
+ *     what `observed_on` refuses: a number produced by a run that did not
+ *     finish is not a measurement of how long the work takes.
+ *
+ *     A missing `observed_on` is refused rather than grandfathered. Every
+ *     `proven` entry in the ledger when this clause shipped had already
+ *     recorded, in prose, that its worst case came from runs that completed, so
+ *     backfilling the field only restates what was already proved. Exempting
+ *     them would have exempted the only entries the clause could bind on.
+ *
  * ## The ratchet, and why incumbents are not simply exempted
  *
  * Contexts already required when this guard shipped may declare
@@ -315,9 +357,47 @@ function budgetProblems(budget) {
       },
     ];
   }
+  // A budgets[] entry publishes its OWN observed_worst_ms, so it can be a
+  // starved figure exactly as the block-level one can. Checking provenance
+  // first: a ratio computed from a duration that measures contention is
+  // arithmetic on the wrong number, so the reader needs the provenance before
+  // the margin.
+  const provenance = provenanceProblems(budget.observed_on);
+  if (provenance.length > 0) return provenance;
   return ratioProblems(budget.budget_ms, budget.observed_worst_ms);
 }
 
+/**
+ * Validate where an observed worst case was measured (#2528).
+ *
+ * `observed_on` records whether the run that produced `observed_worst_ms`
+ * COMPLETED within its budget (`"pass"`) or was terminated by it (`"fail"`).
+ * That is a claim about time, not about the check's verdict — a run that
+ * reproduces a real violation and exits 1 well inside its budget completed.
+ *
+ * @param {unknown} observedOn - the declared provenance.
+ * @returns {{ rule: string, detail: string }[]} problems, empty when sound.
+ */
+function provenanceProblems(observedOn) {
+  if (observedOn === "pass") return [];
+  if (observedOn === "fail") {
+    return [
+      {
+        rule: "headroom-measured-on-failing-run",
+        detail:
+          'observed_worst_ms was taken from a run the budget terminated ("observed_on": "fail"); that duration is the starvation, not the work, and the more contended the box was the safer the budget looks — re-measure on a run that completed, in isolation',
+      },
+    ];
+  }
+  return [
+    {
+      rule: "headroom-evidence-missing",
+      detail:
+        'headroom.observed_on must be "pass": the run that produced observed_worst_ms must have COMPLETED within its budget, because a duration reported alongside a timeout measures contention, not cost',
+    },
+  ];
+}
+
 /**
  * Compare an observed worst case against its budget.
  *
@@ -340,6 +420,17 @@ function ratioProblems(budgetMs, observedMs) {
       },
     ];
   }
+  // Checked before the ratio, and reported as its own defect: an entry whose
+  // worst case is not below the budget it justifies can never be valid, and
+  // "thin margin" would misname it. See clause 6 in the module preamble.
+  if (observedMs >= budgetMs) {
+    return [
+      {
+        rule: "headroom-worst-case-exceeds-budget",
+        detail: `observed worst ${observedMs}ms is not below the ${budgetMs}ms budget it justifies, so the entry disproves itself; a worst case at or above its own budget is usually elapsed time from a run the budget terminated, which measures contention rather than cost (#2528)`,
+      },
+    ];
+  }
   const ratio = budgetMs / observedMs;
   if (ratio < MIN_HEADROOM_RATIO) {
     return [
@@ -394,6 +485,8 @@ export function headroomProblems(headroom) {
     }
   }
   if (problems.length > 0) return problems;
+  problems.push(...provenanceProblems(headroom.observed_on));
+  if (problems.length > 0) return problems;
   problems.push(
     ...ratioProblems(headroom.budget_ms, headroom.observed_worst_ms)
   );