@codyswann/lisa 2.277.1 → 2.277.3

package/package.json

@@ -112,7 +112,7 @@
     "brace-expansion": ">=5.0.6"
   },
   "name": "@codyswann/lisa",
-  "version": "2.277.1",
+  "version": "2.277.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.277.1",
+  "version": "2.277.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.277.1",
+  "version": "2.277.3",
   "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

@@ -323,8 +323,11 @@ default doctor path never renders it and stays byte-identical.
    where the evidence-gathering surfaces (RRR-4/5/6) are not yet wired, every dimension renders `SKIP`
    with that reason.
 4. **Reuse the shipped verdict ladder and consequence ordering.** No new verdict value and no new
-   severity: reuse `READY` / `READY_WITH_WARNINGS` / `NOT_READY`. Section order stays stable; the
-   findings **within** each dimension check order highest-consequence-first.
+   severity: reuse `READY` / `READY_WITH_WARNINGS` / `NOT_READY`. `READY` requires *positive*
+   evidence — every readiness dimension assessed and clean, with no blocker standing. An unassessed
+   (`SKIP`) dimension is silence, not health, so any readiness report carrying one tops out at
+   `READY_WITH_WARNINGS`; only a standing ship blocker yields `NOT_READY`. Section order stays
+   stable; the findings **within** each dimension check order highest-consequence-first.
 5. **Persist to a versioned, relocatable artifact.** Writing the report to `.lisa/readiness.json`
    (`schema_version: 1`, with `verdict`, `blocker_count`, and per-dimension findings) is resolved
    through a single resolver so the location is one line to change. The write is atomic and must

package/plugins/lisa/scripts/doctor-report.mjs

@@ -211,6 +211,22 @@ export function createRepositoryReadinessDoctorGroup(root = process.cwd()) {
 }
 
 /**
+ * Group id of the orthogonal repository-readiness assessment. Named once so the
+ * verdict scorer can hold that group — and only that group — to the stricter
+ * "assessed or it does not count" bar.
+ */
+const REPOSITORY_READINESS_GROUP_ID = "repository-readiness";
+
+/**
+ * Score the doctor groups onto the shipped verdict ladder.
+ *
+ * `SKIP` is benign for the installation groups — "no wiki/ directory here" is a
+ * genuine not-applicable, so an all-SKIP installation report is still `READY`.
+ * It is NOT benign for the repository-readiness group: there a `SKIP` means the
+ * ownership dimension was never assessed, and calling zero evidence `READY`
+ * emits a green unattended-fleet claim backed by nothing (#1897). So an
+ * unassessed readiness dimension downgrades to `READY_WITH_WARNINGS`, while a
+ * fully-`PASS` readiness group still reaches `READY`.
  * @param {readonly DoctorGroup[]} groups
  * @returns {DoctorVerdict}
  */
@@ -222,7 +238,11 @@ export function computeDoctorVerdict(groups) {
   if (checks.some(check => check.status === "WARN")) {
     return "READY_WITH_WARNINGS";
   }
-  return "READY";
+  const readinessUnassessed = groups
+    .filter(group => group.id === REPOSITORY_READINESS_GROUP_ID)
+    .flatMap(group => group.checks.map(normalizeCheck))
+    .some(check => check.status === "SKIP");
+  return readinessUnassessed ? "READY_WITH_WARNINGS" : "READY";
 }
 
 /**

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

@@ -323,8 +323,11 @@ default doctor path never renders it and stays byte-identical.
    where the evidence-gathering surfaces (RRR-4/5/6) are not yet wired, every dimension renders `SKIP`
    with that reason.
 4. **Reuse the shipped verdict ladder and consequence ordering.** No new verdict value and no new
-   severity: reuse `READY` / `READY_WITH_WARNINGS` / `NOT_READY`. Section order stays stable; the
-   findings **within** each dimension check order highest-consequence-first.
+   severity: reuse `READY` / `READY_WITH_WARNINGS` / `NOT_READY`. `READY` requires *positive*
+   evidence — every readiness dimension assessed and clean, with no blocker standing. An unassessed
+   (`SKIP`) dimension is silence, not health, so any readiness report carrying one tops out at
+   `READY_WITH_WARNINGS`; only a standing ship blocker yields `NOT_READY`. Section order stays
+   stable; the findings **within** each dimension check order highest-consequence-first.
 5. **Persist to a versioned, relocatable artifact.** Writing the report to `.lisa/readiness.json`
    (`schema_version: 1`, with `verdict`, `blocker_count`, and per-dimension findings) is resolved
    through a single resolver so the location is one line to change. The write is atomic and must

package/plugins/lisa-agy/plugin.json

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

package/plugins/lisa-agy/scripts/doctor-report.mjs

@@ -211,6 +211,22 @@ export function createRepositoryReadinessDoctorGroup(root = process.cwd()) {
 }
 
 /**
+ * Group id of the orthogonal repository-readiness assessment. Named once so the
+ * verdict scorer can hold that group — and only that group — to the stricter
+ * "assessed or it does not count" bar.
+ */
+const REPOSITORY_READINESS_GROUP_ID = "repository-readiness";
+
+/**
+ * Score the doctor groups onto the shipped verdict ladder.
+ *
+ * `SKIP` is benign for the installation groups — "no wiki/ directory here" is a
+ * genuine not-applicable, so an all-SKIP installation report is still `READY`.
+ * It is NOT benign for the repository-readiness group: there a `SKIP` means the
+ * ownership dimension was never assessed, and calling zero evidence `READY`
+ * emits a green unattended-fleet claim backed by nothing (#1897). So an
+ * unassessed readiness dimension downgrades to `READY_WITH_WARNINGS`, while a
+ * fully-`PASS` readiness group still reaches `READY`.
  * @param {readonly DoctorGroup[]} groups
  * @returns {DoctorVerdict}
  */
@@ -222,7 +238,11 @@ export function computeDoctorVerdict(groups) {
   if (checks.some(check => check.status === "WARN")) {
     return "READY_WITH_WARNINGS";
   }
-  return "READY";
+  const readinessUnassessed = groups
+    .filter(group => group.id === REPOSITORY_READINESS_GROUP_ID)
+    .flatMap(group => group.checks.map(normalizeCheck))
+    .some(check => check.status === "SKIP");
+  return readinessUnassessed ? "READY_WITH_WARNINGS" : "READY";
 }
 
 /**

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

@@ -323,8 +323,11 @@ default doctor path never renders it and stays byte-identical.
    where the evidence-gathering surfaces (RRR-4/5/6) are not yet wired, every dimension renders `SKIP`
    with that reason.
 4. **Reuse the shipped verdict ladder and consequence ordering.** No new verdict value and no new
-   severity: reuse `READY` / `READY_WITH_WARNINGS` / `NOT_READY`. Section order stays stable; the
-   findings **within** each dimension check order highest-consequence-first.
+   severity: reuse `READY` / `READY_WITH_WARNINGS` / `NOT_READY`. `READY` requires *positive*
+   evidence — every readiness dimension assessed and clean, with no blocker standing. An unassessed
+   (`SKIP`) dimension is silence, not health, so any readiness report carrying one tops out at
+   `READY_WITH_WARNINGS`; only a standing ship blocker yields `NOT_READY`. Section order stays
+   stable; the findings **within** each dimension check order highest-consequence-first.
 5. **Persist to a versioned, relocatable artifact.** Writing the report to `.lisa/readiness.json`
    (`schema_version: 1`, with `verdict`, `blocker_count`, and per-dimension findings) is resolved
    through a single resolver so the location is one line to change. The write is atomic and must

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

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

package/plugins/lisa-copilot/scripts/doctor-report.mjs

@@ -211,6 +211,22 @@ export function createRepositoryReadinessDoctorGroup(root = process.cwd()) {
 }
 
 /**
+ * Group id of the orthogonal repository-readiness assessment. Named once so the
+ * verdict scorer can hold that group — and only that group — to the stricter
+ * "assessed or it does not count" bar.
+ */
+const REPOSITORY_READINESS_GROUP_ID = "repository-readiness";
+
+/**
+ * Score the doctor groups onto the shipped verdict ladder.
+ *
+ * `SKIP` is benign for the installation groups — "no wiki/ directory here" is a
+ * genuine not-applicable, so an all-SKIP installation report is still `READY`.
+ * It is NOT benign for the repository-readiness group: there a `SKIP` means the
+ * ownership dimension was never assessed, and calling zero evidence `READY`
+ * emits a green unattended-fleet claim backed by nothing (#1897). So an
+ * unassessed readiness dimension downgrades to `READY_WITH_WARNINGS`, while a
+ * fully-`PASS` readiness group still reaches `READY`.
  * @param {readonly DoctorGroup[]} groups
  * @returns {DoctorVerdict}
  */
@@ -222,7 +238,11 @@ export function computeDoctorVerdict(groups) {
   if (checks.some(check => check.status === "WARN")) {
     return "READY_WITH_WARNINGS";
   }
-  return "READY";
+  const readinessUnassessed = groups
+    .filter(group => group.id === REPOSITORY_READINESS_GROUP_ID)
+    .flatMap(group => group.checks.map(normalizeCheck))
+    .some(check => check.status === "SKIP");
+  return readinessUnassessed ? "READY_WITH_WARNINGS" : "READY";
 }
 
 /**

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

@@ -323,8 +323,11 @@ default doctor path never renders it and stays byte-identical.
    where the evidence-gathering surfaces (RRR-4/5/6) are not yet wired, every dimension renders `SKIP`
    with that reason.
 4. **Reuse the shipped verdict ladder and consequence ordering.** No new verdict value and no new
-   severity: reuse `READY` / `READY_WITH_WARNINGS` / `NOT_READY`. Section order stays stable; the
-   findings **within** each dimension check order highest-consequence-first.
+   severity: reuse `READY` / `READY_WITH_WARNINGS` / `NOT_READY`. `READY` requires *positive*
+   evidence — every readiness dimension assessed and clean, with no blocker standing. An unassessed
+   (`SKIP`) dimension is silence, not health, so any readiness report carrying one tops out at
+   `READY_WITH_WARNINGS`; only a standing ship blocker yields `NOT_READY`. Section order stays
+   stable; the findings **within** each dimension check order highest-consequence-first.
 5. **Persist to a versioned, relocatable artifact.** Writing the report to `.lisa/readiness.json`
    (`schema_version: 1`, with `verdict`, `blocker_count`, and per-dimension findings) is resolved
    through a single resolver so the location is one line to change. The write is atomic and must

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

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

package/plugins/lisa-cursor/scripts/doctor-report.mjs

@@ -211,6 +211,22 @@ export function createRepositoryReadinessDoctorGroup(root = process.cwd()) {
 }
 
 /**
+ * Group id of the orthogonal repository-readiness assessment. Named once so the
+ * verdict scorer can hold that group — and only that group — to the stricter
+ * "assessed or it does not count" bar.
+ */
+const REPOSITORY_READINESS_GROUP_ID = "repository-readiness";
+
+/**
+ * Score the doctor groups onto the shipped verdict ladder.
+ *
+ * `SKIP` is benign for the installation groups — "no wiki/ directory here" is a
+ * genuine not-applicable, so an all-SKIP installation report is still `READY`.
+ * It is NOT benign for the repository-readiness group: there a `SKIP` means the
+ * ownership dimension was never assessed, and calling zero evidence `READY`
+ * emits a green unattended-fleet claim backed by nothing (#1897). So an
+ * unassessed readiness dimension downgrades to `READY_WITH_WARNINGS`, while a
+ * fully-`PASS` readiness group still reaches `READY`.
  * @param {readonly DoctorGroup[]} groups
  * @returns {DoctorVerdict}
  */
@@ -222,7 +238,11 @@ export function computeDoctorVerdict(groups) {
   if (checks.some(check => check.status === "WARN")) {
     return "READY_WITH_WARNINGS";
   }
-  return "READY";
+  const readinessUnassessed = groups
+    .filter(group => group.id === REPOSITORY_READINESS_GROUP_ID)
+    .flatMap(group => group.checks.map(normalizeCheck))
+    .some(check => check.status === "SKIP");
+  return readinessUnassessed ? "READY_WITH_WARNINGS" : "READY";
 }
 
 /**

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

@@ -323,8 +323,11 @@ default doctor path never renders it and stays byte-identical.
    where the evidence-gathering surfaces (RRR-4/5/6) are not yet wired, every dimension renders `SKIP`
    with that reason.
 4. **Reuse the shipped verdict ladder and consequence ordering.** No new verdict value and no new
-   severity: reuse `READY` / `READY_WITH_WARNINGS` / `NOT_READY`. Section order stays stable; the
-   findings **within** each dimension check order highest-consequence-first.
+   severity: reuse `READY` / `READY_WITH_WARNINGS` / `NOT_READY`. `READY` requires *positive*
+   evidence — every readiness dimension assessed and clean, with no blocker standing. An unassessed
+   (`SKIP`) dimension is silence, not health, so any readiness report carrying one tops out at
+   `READY_WITH_WARNINGS`; only a standing ship blocker yields `NOT_READY`. Section order stays
+   stable; the findings **within** each dimension check order highest-consequence-first.
 5. **Persist to a versioned, relocatable artifact.** Writing the report to `.lisa/readiness.json`
    (`schema_version: 1`, with `verdict`, `blocker_count`, and per-dimension findings) is resolved
    through a single resolver so the location is one line to change. The write is atomic and must

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.277.1",
+  "version": "2.277.3",
   "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": "2.277.1",
+  "version": "2.277.3",
   "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": "2.277.1",
+  "version": "2.277.3",
   "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": "2.277.1",
+  "version": "2.277.3",
   "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": "2.277.1",
+  "version": "2.277.3",
   "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": "2.277.1",
+  "version": "2.277.3",
   "description": "Harper/Fabric-specific rules for TypeScript component apps",
   "author": {
     "name": "Cody Swann"

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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