@codyswann/lisa 3.40.5 → 3.41.1

package/package.json

@@ -108,7 +108,7 @@
     "multer": ">=2.2.0",
     "nanoid": "^3.3.18",
     "postcss": ">=8.5.18",
-    "undici": "^6.27.0",
+    "undici": "^6.28.0",
     "vite": "$vite",
     "ws": ">=8.21.0"
   },
@@ -127,12 +127,12 @@
     "multer": ">=2.2.0",
     "nanoid": "^3.3.18",
     "postcss": ">=8.5.18",
-    "undici": "^6.27.0",
+    "undici": "^6.28.0",
     "vite": "$vite",
     "ws": ">=8.21.0"
   },
   "name": "@codyswann/lisa",
-  "version": "3.40.5",
+  "version": "3.41.1",
   "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.40.5",
+  "version": "3.41.1",
   "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.40.5",
+  "version": "3.41.1",
   "description": "Universal governance: agents, skills, commands, hooks, and rules for all projects.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa/.codex-plugin/skills/lisa-doctor/SKILL.md

@@ -426,6 +426,7 @@ The verdict ladder is:
 node scripts/lisa-gates.mjs validate                    # shape + unknown gate ids
 node scripts/lisa-gates.mjs list --moment=pull-request
 node scripts/lisa-gates.mjs contexts                    # branch-protection contexts
+node scripts/lisa-gates.mjs skip-jobs                   # what replaces each skip_jobs token
 ```
 
 A gate is a **property** — *credential leakage* — not a tool. `gitleaks` is one way to prove
@@ -437,6 +438,25 @@ would otherwise read as an enabled guarantee and run nothing at all — the same
 as a skipped required check. Gates a project invents carry an `x-` prefix, which Lisa runs without
 pretending to understand.
 
+`skip-jobs` answers the migration off the `skip_jobs` workflow input. Eleven of the token → gate
+pairs cannot be recovered by transforming the name — `lint` is `code-style`, `sg_scan` is
+`structural-rules`, `work_item_traceability` is `traceability` — and being wrong does not break a
+build: it declares the WRONG gate `off`, so a check silently stops running while the configuration
+reads deliberate. Pass `--moment=` to match the moment the caller passes to `quality.yml`, because a
+gate's legal moments are a closed set and a declaration outside it is refused by `validate` — after
+the token has already been deleted.
+
+Four of its six answers are refusals, and they are the point. `unmappable` means the job was never
+converted to a gate façade, so keep the token. `partial` means one job behind the token has a gate
+and the others do not, so the declaration alone would leave work running. `inert` means no job
+honours that token at all. `unknown` means nothing matches it — usually a space after a comma, which
+GitHub matches against nothing, so that job has been RUNNING all along. None of them produce a gate
+id, because a confident wrong answer here is worse than no answer.
+
+`lisa doctor` reports the same thing per caller workflow and does NOT edit the workflow. `lisa apply`
+runs on postinstall, and an automated rewrite of a caller that gets it wrong is silent; an agent
+performing the edit can read the surrounding code and confirm afterwards that the same checks ran.
+
 `contexts` is the value that replaces a hand-transcribed branch-protection list. It is scoped to
 one environment: a gate required before a production deploy is **not** thereby a merge blocker on a
 pull request, and collapsing the two would promote every deploy-time gate into branch protection.

package/plugins/lisa/skills/lisa-doctor/SKILL.md

@@ -426,6 +426,7 @@ The verdict ladder is:
 node scripts/lisa-gates.mjs validate                    # shape + unknown gate ids
 node scripts/lisa-gates.mjs list --moment=pull-request
 node scripts/lisa-gates.mjs contexts                    # branch-protection contexts
+node scripts/lisa-gates.mjs skip-jobs                   # what replaces each skip_jobs token
 ```
 
 A gate is a **property** — *credential leakage* — not a tool. `gitleaks` is one way to prove
@@ -437,6 +438,25 @@ would otherwise read as an enabled guarantee and run nothing at all — the same
 as a skipped required check. Gates a project invents carry an `x-` prefix, which Lisa runs without
 pretending to understand.
 
+`skip-jobs` answers the migration off the `skip_jobs` workflow input. Eleven of the token → gate
+pairs cannot be recovered by transforming the name — `lint` is `code-style`, `sg_scan` is
+`structural-rules`, `work_item_traceability` is `traceability` — and being wrong does not break a
+build: it declares the WRONG gate `off`, so a check silently stops running while the configuration
+reads deliberate. Pass `--moment=` to match the moment the caller passes to `quality.yml`, because a
+gate's legal moments are a closed set and a declaration outside it is refused by `validate` — after
+the token has already been deleted.
+
+Four of its six answers are refusals, and they are the point. `unmappable` means the job was never
+converted to a gate façade, so keep the token. `partial` means one job behind the token has a gate
+and the others do not, so the declaration alone would leave work running. `inert` means no job
+honours that token at all. `unknown` means nothing matches it — usually a space after a comma, which
+GitHub matches against nothing, so that job has been RUNNING all along. None of them produce a gate
+id, because a confident wrong answer here is worse than no answer.
+
+`lisa doctor` reports the same thing per caller workflow and does NOT edit the workflow. `lisa apply`
+runs on postinstall, and an automated rewrite of a caller that gets it wrong is silent; an agent
+performing the edit can read the surrounding code and confirm afterwards that the same checks ran.
+
 `contexts` is the value that replaces a hand-transcribed branch-protection list. It is scoped to
 one environment: a gate required before a production deploy is **not** thereby a merge blocker on a
 pull request, and collapsing the two would promote every deploy-time gate into branch protection.

package/plugins/lisa-agy/plugin.json

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

package/plugins/lisa-agy/skills/lisa-doctor/SKILL.md

@@ -426,6 +426,7 @@ The verdict ladder is:
 node scripts/lisa-gates.mjs validate                    # shape + unknown gate ids
 node scripts/lisa-gates.mjs list --moment=pull-request
 node scripts/lisa-gates.mjs contexts                    # branch-protection contexts
+node scripts/lisa-gates.mjs skip-jobs                   # what replaces each skip_jobs token
 ```
 
 A gate is a **property** — *credential leakage* — not a tool. `gitleaks` is one way to prove
@@ -437,6 +438,25 @@ would otherwise read as an enabled guarantee and run nothing at all — the same
 as a skipped required check. Gates a project invents carry an `x-` prefix, which Lisa runs without
 pretending to understand.
 
+`skip-jobs` answers the migration off the `skip_jobs` workflow input. Eleven of the token → gate
+pairs cannot be recovered by transforming the name — `lint` is `code-style`, `sg_scan` is
+`structural-rules`, `work_item_traceability` is `traceability` — and being wrong does not break a
+build: it declares the WRONG gate `off`, so a check silently stops running while the configuration
+reads deliberate. Pass `--moment=` to match the moment the caller passes to `quality.yml`, because a
+gate's legal moments are a closed set and a declaration outside it is refused by `validate` — after
+the token has already been deleted.
+
+Four of its six answers are refusals, and they are the point. `unmappable` means the job was never
+converted to a gate façade, so keep the token. `partial` means one job behind the token has a gate
+and the others do not, so the declaration alone would leave work running. `inert` means no job
+honours that token at all. `unknown` means nothing matches it — usually a space after a comma, which
+GitHub matches against nothing, so that job has been RUNNING all along. None of them produce a gate
+id, because a confident wrong answer here is worse than no answer.
+
+`lisa doctor` reports the same thing per caller workflow and does NOT edit the workflow. `lisa apply`
+runs on postinstall, and an automated rewrite of a caller that gets it wrong is silent; an agent
+performing the edit can read the surrounding code and confirm afterwards that the same checks ran.
+
 `contexts` is the value that replaces a hand-transcribed branch-protection list. It is scoped to
 one environment: a gate required before a production deploy is **not** thereby a merge blocker on a
 pull request, and collapsing the two would promote every deploy-time gate into branch protection.

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "3.40.5",
+  "version": "3.41.1",
   "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.40.5",
+  "version": "3.41.1",
   "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.40.5",
+  "version": "3.41.1",
   "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.40.5",
+  "version": "3.41.1",
   "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.40.5",
+  "version": "3.41.1",
   "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.40.5",
+  "version": "3.41.1",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

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

@@ -426,6 +426,7 @@ The verdict ladder is:
 node scripts/lisa-gates.mjs validate                    # shape + unknown gate ids
 node scripts/lisa-gates.mjs list --moment=pull-request
 node scripts/lisa-gates.mjs contexts                    # branch-protection contexts
+node scripts/lisa-gates.mjs skip-jobs                   # what replaces each skip_jobs token
 ```
 
 A gate is a **property** — *credential leakage* — not a tool. `gitleaks` is one way to prove
@@ -437,6 +438,25 @@ would otherwise read as an enabled guarantee and run nothing at all — the same
 as a skipped required check. Gates a project invents carry an `x-` prefix, which Lisa runs without
 pretending to understand.
 
+`skip-jobs` answers the migration off the `skip_jobs` workflow input. Eleven of the token → gate
+pairs cannot be recovered by transforming the name — `lint` is `code-style`, `sg_scan` is
+`structural-rules`, `work_item_traceability` is `traceability` — and being wrong does not break a
+build: it declares the WRONG gate `off`, so a check silently stops running while the configuration
+reads deliberate. Pass `--moment=` to match the moment the caller passes to `quality.yml`, because a
+gate's legal moments are a closed set and a declaration outside it is refused by `validate` — after
+the token has already been deleted.
+
+Four of its six answers are refusals, and they are the point. `unmappable` means the job was never
+converted to a gate façade, so keep the token. `partial` means one job behind the token has a gate
+and the others do not, so the declaration alone would leave work running. `inert` means no job
+honours that token at all. `unknown` means nothing matches it — usually a space after a comma, which
+GitHub matches against nothing, so that job has been RUNNING all along. None of them produce a gate
+id, because a confident wrong answer here is worse than no answer.
+
+`lisa doctor` reports the same thing per caller workflow and does NOT edit the workflow. `lisa apply`
+runs on postinstall, and an automated rewrite of a caller that gets it wrong is silent; an agent
+performing the edit can read the surrounding code and confirm afterwards that the same checks ran.
+
 `contexts` is the value that replaces a hand-transcribed branch-protection list. It is scoped to
 one environment: a gate required before a production deploy is **not** thereby a merge blocker on a
 pull request, and collapsing the two would promote every deploy-time gate into branch protection.

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

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

package/plugins/lisa-cursor/skills/lisa-doctor/SKILL.md

@@ -426,6 +426,7 @@ The verdict ladder is:
 node scripts/lisa-gates.mjs validate                    # shape + unknown gate ids
 node scripts/lisa-gates.mjs list --moment=pull-request
 node scripts/lisa-gates.mjs contexts                    # branch-protection contexts
+node scripts/lisa-gates.mjs skip-jobs                   # what replaces each skip_jobs token
 ```
 
 A gate is a **property** — *credential leakage* — not a tool. `gitleaks` is one way to prove
@@ -437,6 +438,25 @@ would otherwise read as an enabled guarantee and run nothing at all — the same
 as a skipped required check. Gates a project invents carry an `x-` prefix, which Lisa runs without
 pretending to understand.
 
+`skip-jobs` answers the migration off the `skip_jobs` workflow input. Eleven of the token → gate
+pairs cannot be recovered by transforming the name — `lint` is `code-style`, `sg_scan` is
+`structural-rules`, `work_item_traceability` is `traceability` — and being wrong does not break a
+build: it declares the WRONG gate `off`, so a check silently stops running while the configuration
+reads deliberate. Pass `--moment=` to match the moment the caller passes to `quality.yml`, because a
+gate's legal moments are a closed set and a declaration outside it is refused by `validate` — after
+the token has already been deleted.
+
+Four of its six answers are refusals, and they are the point. `unmappable` means the job was never
+converted to a gate façade, so keep the token. `partial` means one job behind the token has a gate
+and the others do not, so the declaration alone would leave work running. `inert` means no job
+honours that token at all. `unknown` means nothing matches it — usually a space after a comma, which
+GitHub matches against nothing, so that job has been RUNNING all along. None of them produce a gate
+id, because a confident wrong answer here is worse than no answer.
+
+`lisa doctor` reports the same thing per caller workflow and does NOT edit the workflow. `lisa apply`
+runs on postinstall, and an automated rewrite of a caller that gets it wrong is silent; an agent
+performing the edit can read the surrounding code and confirm afterwards that the same checks ran.
+
 `contexts` is the value that replaces a hand-transcribed branch-protection list. It is scoped to
 one environment: a gate required before a production deploy is **not** thereby a merge blocker on a
 pull request, and collapsing the two would promote every deploy-time gate into branch protection.

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "3.40.5",
+  "version": "3.41.1",
   "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.40.5",
+  "version": "3.41.1",
   "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.40.5",
+  "version": "3.41.1",
   "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.40.5",
+  "version": "3.41.1",
   "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.40.5",
+  "version": "3.41.1",
   "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.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.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": "3.40.5",
+  "version": "3.41.1",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"