@codyswann/lisa 2.276.0 → 2.277.0

package/package.json

@@ -112,7 +112,7 @@
     "brace-expansion": ">=5.0.6"
   },
   "name": "@codyswann/lisa",
-  "version": "2.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "description": "Universal governance: agents, skills, commands, hooks, and rules for all projects.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa/.codex-plugin/skills/lisa-setup-automations/SKILL.md

@@ -49,6 +49,36 @@ without a human between the loops and the pipeline. Pass `false` explicitly to o
 human triage. The two auto-start flags affect **only** the two exploratory automations; the intake
 gates' adversarial validation remains the quality control either way.
 
+## Repository-readiness advisory
+
+Before creating or updating registrations, locate the standing repository-readiness report through
+RRR-3's canonical `resolveReadinessReportPath` contract (currently `.lisa/readiness.json` under the
+resolved project root). This consumes the shared report; it never creates a second readiness
+assessment. Read the report exactly once. Do not re-run `lisa doctor --readiness`, because doing so
+would execute journeys and replace the standing evidence the operator is about to act on.
+
+A report is usable for this advisory only when all of these are true:
+
+- the file parses to a JSON object whose `schema_version` is `1` and whose `verdict` is `NOT_READY`;
+- `blocker_count` is a positive integer and the `blockers` array length exactly equals
+  `blocker_count`;
+- each blocker has a unique `id` in the closed set B1 through B7 (duplicate blocker ids make the
+  report internally inconsistent, and uniqueness caps the count at seven) and a non-empty
+  operator-facing `label`; and
+- `narrowed_claim` is a non-empty string.
+
+For one usable report, emit exactly one warning naming the blocker count, each blocker's `id` and
+`label`, and the narrowed claim. For example: "Repository readiness warning — 3 standing ship
+blockers: B2 Release path bypasses validation; B4 Failing loop has no recovery; B7 Operability
+cannot be proved. Narrowed claim: ready for supervised changes only." This is a warning only:
+setup continues, and no registration or runbook step is skipped because blockers stand.
+
+Treat a missing or unreadable file, invalid JSON, unsupported schema, or internally inconsistent
+report as unavailable: emit no readiness warning and no error, then continue setup normally. Do not
+invent an artifact freshness, age, or TTL rule; the persisted contract defines no such field. This
+advisory is never a precondition and follows the same never-block-always-degrade posture as runbook
+scaffolding below.
+
 ## The automations to create
 
 Each automation runs **one cycle** of a Lisa command and respects that command's confirmation policy

package/plugins/lisa/skills/lisa-setup-automations/SKILL.md

@@ -49,6 +49,36 @@ without a human between the loops and the pipeline. Pass `false` explicitly to o
 human triage. The two auto-start flags affect **only** the two exploratory automations; the intake
 gates' adversarial validation remains the quality control either way.
 
+## Repository-readiness advisory
+
+Before creating or updating registrations, locate the standing repository-readiness report through
+RRR-3's canonical `resolveReadinessReportPath` contract (currently `.lisa/readiness.json` under the
+resolved project root). This consumes the shared report; it never creates a second readiness
+assessment. Read the report exactly once. Do not re-run `lisa doctor --readiness`, because doing so
+would execute journeys and replace the standing evidence the operator is about to act on.
+
+A report is usable for this advisory only when all of these are true:
+
+- the file parses to a JSON object whose `schema_version` is `1` and whose `verdict` is `NOT_READY`;
+- `blocker_count` is a positive integer and the `blockers` array length exactly equals
+  `blocker_count`;
+- each blocker has a unique `id` in the closed set B1 through B7 (duplicate blocker ids make the
+  report internally inconsistent, and uniqueness caps the count at seven) and a non-empty
+  operator-facing `label`; and
+- `narrowed_claim` is a non-empty string.
+
+For one usable report, emit exactly one warning naming the blocker count, each blocker's `id` and
+`label`, and the narrowed claim. For example: "Repository readiness warning — 3 standing ship
+blockers: B2 Release path bypasses validation; B4 Failing loop has no recovery; B7 Operability
+cannot be proved. Narrowed claim: ready for supervised changes only." This is a warning only:
+setup continues, and no registration or runbook step is skipped because blockers stand.
+
+Treat a missing or unreadable file, invalid JSON, unsupported schema, or internally inconsistent
+report as unavailable: emit no readiness warning and no error, then continue setup normally. Do not
+invent an artifact freshness, age, or TTL rule; the persisted contract defines no such field. This
+advisory is never a precondition and follows the same never-block-always-degrade posture as runbook
+scaffolding below.
+
 ## The automations to create
 
 Each automation runs **one cycle** of a Lisa command and respects that command's confirmation policy

package/plugins/lisa-agy/plugin.json

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

package/plugins/lisa-agy/skills/lisa-setup-automations/SKILL.md

@@ -49,6 +49,36 @@ without a human between the loops and the pipeline. Pass `false` explicitly to o
 human triage. The two auto-start flags affect **only** the two exploratory automations; the intake
 gates' adversarial validation remains the quality control either way.
 
+## Repository-readiness advisory
+
+Before creating or updating registrations, locate the standing repository-readiness report through
+RRR-3's canonical `resolveReadinessReportPath` contract (currently `.lisa/readiness.json` under the
+resolved project root). This consumes the shared report; it never creates a second readiness
+assessment. Read the report exactly once. Do not re-run `lisa doctor --readiness`, because doing so
+would execute journeys and replace the standing evidence the operator is about to act on.
+
+A report is usable for this advisory only when all of these are true:
+
+- the file parses to a JSON object whose `schema_version` is `1` and whose `verdict` is `NOT_READY`;
+- `blocker_count` is a positive integer and the `blockers` array length exactly equals
+  `blocker_count`;
+- each blocker has a unique `id` in the closed set B1 through B7 (duplicate blocker ids make the
+  report internally inconsistent, and uniqueness caps the count at seven) and a non-empty
+  operator-facing `label`; and
+- `narrowed_claim` is a non-empty string.
+
+For one usable report, emit exactly one warning naming the blocker count, each blocker's `id` and
+`label`, and the narrowed claim. For example: "Repository readiness warning — 3 standing ship
+blockers: B2 Release path bypasses validation; B4 Failing loop has no recovery; B7 Operability
+cannot be proved. Narrowed claim: ready for supervised changes only." This is a warning only:
+setup continues, and no registration or runbook step is skipped because blockers stand.
+
+Treat a missing or unreadable file, invalid JSON, unsupported schema, or internally inconsistent
+report as unavailable: emit no readiness warning and no error, then continue setup normally. Do not
+invent an artifact freshness, age, or TTL rule; the persisted contract defines no such field. This
+advisory is never a precondition and follows the same never-block-always-degrade posture as runbook
+scaffolding below.
+
 ## The automations to create
 
 Each automation runs **one cycle** of a Lisa command and respects that command's confirmation policy

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

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

package/plugins/lisa-copilot/skills/lisa-setup-automations/SKILL.md

@@ -49,6 +49,36 @@ without a human between the loops and the pipeline. Pass `false` explicitly to o
 human triage. The two auto-start flags affect **only** the two exploratory automations; the intake
 gates' adversarial validation remains the quality control either way.
 
+## Repository-readiness advisory
+
+Before creating or updating registrations, locate the standing repository-readiness report through
+RRR-3's canonical `resolveReadinessReportPath` contract (currently `.lisa/readiness.json` under the
+resolved project root). This consumes the shared report; it never creates a second readiness
+assessment. Read the report exactly once. Do not re-run `lisa doctor --readiness`, because doing so
+would execute journeys and replace the standing evidence the operator is about to act on.
+
+A report is usable for this advisory only when all of these are true:
+
+- the file parses to a JSON object whose `schema_version` is `1` and whose `verdict` is `NOT_READY`;
+- `blocker_count` is a positive integer and the `blockers` array length exactly equals
+  `blocker_count`;
+- each blocker has a unique `id` in the closed set B1 through B7 (duplicate blocker ids make the
+  report internally inconsistent, and uniqueness caps the count at seven) and a non-empty
+  operator-facing `label`; and
+- `narrowed_claim` is a non-empty string.
+
+For one usable report, emit exactly one warning naming the blocker count, each blocker's `id` and
+`label`, and the narrowed claim. For example: "Repository readiness warning — 3 standing ship
+blockers: B2 Release path bypasses validation; B4 Failing loop has no recovery; B7 Operability
+cannot be proved. Narrowed claim: ready for supervised changes only." This is a warning only:
+setup continues, and no registration or runbook step is skipped because blockers stand.
+
+Treat a missing or unreadable file, invalid JSON, unsupported schema, or internally inconsistent
+report as unavailable: emit no readiness warning and no error, then continue setup normally. Do not
+invent an artifact freshness, age, or TTL rule; the persisted contract defines no such field. This
+advisory is never a precondition and follows the same never-block-always-degrade posture as runbook
+scaffolding below.
+
 ## The automations to create
 
 Each automation runs **one cycle** of a Lisa command and respects that command's confirmation policy

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

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

package/plugins/lisa-cursor/skills/lisa-setup-automations/SKILL.md

@@ -49,6 +49,36 @@ without a human between the loops and the pipeline. Pass `false` explicitly to o
 human triage. The two auto-start flags affect **only** the two exploratory automations; the intake
 gates' adversarial validation remains the quality control either way.
 
+## Repository-readiness advisory
+
+Before creating or updating registrations, locate the standing repository-readiness report through
+RRR-3's canonical `resolveReadinessReportPath` contract (currently `.lisa/readiness.json` under the
+resolved project root). This consumes the shared report; it never creates a second readiness
+assessment. Read the report exactly once. Do not re-run `lisa doctor --readiness`, because doing so
+would execute journeys and replace the standing evidence the operator is about to act on.
+
+A report is usable for this advisory only when all of these are true:
+
+- the file parses to a JSON object whose `schema_version` is `1` and whose `verdict` is `NOT_READY`;
+- `blocker_count` is a positive integer and the `blockers` array length exactly equals
+  `blocker_count`;
+- each blocker has a unique `id` in the closed set B1 through B7 (duplicate blocker ids make the
+  report internally inconsistent, and uniqueness caps the count at seven) and a non-empty
+  operator-facing `label`; and
+- `narrowed_claim` is a non-empty string.
+
+For one usable report, emit exactly one warning naming the blocker count, each blocker's `id` and
+`label`, and the narrowed claim. For example: "Repository readiness warning — 3 standing ship
+blockers: B2 Release path bypasses validation; B4 Failing loop has no recovery; B7 Operability
+cannot be proved. Narrowed claim: ready for supervised changes only." This is a warning only:
+setup continues, and no registration or runbook step is skipped because blockers stand.
+
+Treat a missing or unreadable file, invalid JSON, unsupported schema, or internally inconsistent
+report as unavailable: emit no readiness warning and no error, then continue setup normally. Do not
+invent an artifact freshness, age, or TTL rule; the persisted contract defines no such field. This
+advisory is never a precondition and follows the same never-block-always-degrade posture as runbook
+scaffolding below.
+
 ## The automations to create
 
 Each automation runs **one cycle** of a Lisa command and respects that command's confirmation policy

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "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.276.0",
+  "version": "2.277.0",
   "description": "TypeScript-specific hooks for formatting, linting, and ast-grep scanning on edit.",
   "author": {
     "name": "Cody Swann"

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

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

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

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

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

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

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

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