@codyswann/lisa 2.268.1 → 2.269.0

package/package.json

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

package/plugins/lisa/rules/eager/convergent-review.md

@@ -7,7 +7,12 @@ Review exists to get correct work merged, not to keep a PR in review orbit.
   are non-blocking unless the work item or repository rules make them release
   criteria.
 - Every finding must state severity, blocking yes/no, a concrete failure
-  scenario, evidence, and the smallest actionable fix.
+  scenario, evidence, and the smallest actionable fix — plus
+  `invariant_violated` (the property at risk) and `machinery_to_remove` (what
+  becomes deletable, or `none`), required for `readiness-rubric` findings and
+  recommended elsewhere.
+- Present findings highest-consequence first, by severity and blast radius, not
+  by discovery order. Report section order stays stable.
 - A blocking finding without a concrete failure scenario is malformed by
   contract; downgrade it to non-blocking and ask for evidence.
 - Resolve each finding as `fixed`, `deferred`, or `pushed-back`. If the reviewer

package/plugins/lisa/rules/reference/convergent-review.md

@@ -33,12 +33,57 @@ Every finding must state:
 - Evidence: the file, command output, observed behavior, ticket text, or
   external constraint proving the scenario is reachable.
 - Fix: the smallest actionable correction, or the reason no code change is
-  needed.
+  needed. The correction belongs at the **owning boundary** that permitted the
+  failure, not at the symptom site.
+- `invariant_violated`: the named property the system is supposed to hold that
+  this finding puts at risk — for example "the artifact that ships is the
+  artifact CI validated". The invariant is the property; the failure scenario is
+  the outcome when it breaks. State both; they are not interchangeable.
+- `machinery_to_remove`: the redundant checks, workarounds, or scaffolding that
+  become deletable once the correction lands, or explicitly `none`. This is a
+  **scaffolding-subtraction candidate** — it is surfaced for a human or the
+  implementer to act on and is never auto-deleted by any review pass.
 
 A finding marked blocking without a concrete failure scenario is malformed by
 contract. Downgrade it to non-blocking and ask for evidence instead of treating
 it as a merge blocker.
 
+### Compatibility
+
+`invariant_violated` and `machinery_to_remove` are **required for findings
+emitted under the `readiness-rubric`** and **recommended everywhere else**. A
+finding from an existing product, quality, local, bot-parity, or suggestion
+implementation pass that omits them is still well-formed by contract — this
+extension is additive and never retroactively malforms a shipped review surface.
+
+### Readiness findings map onto this shape
+
+A readiness finding names five fields. All five bind to this contract, so there
+is no second findings format anywhere in the repository:
+
+| Readiness field | Contract field |
+|---|---|
+| the at-risk invariant | `invariant_violated` (above) |
+| `evidence` | `Evidence` |
+| `why_proof_missed` | `Evidence`, extended with a required proof-gap clause: why the existing proof machinery did not catch this |
+| `root_correction` | `Fix`, qualified: the correction goes at the owning boundary, not the symptom site |
+| redundant machinery | `machinery_to_remove` (above) |
+
+Anything that needs a sixth field extends this section rather than starting a
+parallel format.
+
+### Consequence Ordering
+
+Findings are presented **highest-consequence first**. Consequence is determined
+by severity and blast radius — how much of the system, how many users, and how
+irreversible the outcome — not by discovery order, file order, or the order a
+tool happened to emit them in. Two reviewers ordering the same finding set
+differently is a defect, not a preference.
+
+This governs the order of findings **within** a section only. Report section
+order stays stable and is unaffected: never reorder, merge, or silently omit a
+section to surface a finding earlier.
+
 ## Dispositions
 
 The implementer resolves each finding with exactly one disposition:

package/plugins/lisa-agy/plugin.json

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

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

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

package/plugins/lisa-copilot/rules/eager/convergent-review.md

@@ -7,7 +7,12 @@ Review exists to get correct work merged, not to keep a PR in review orbit.
   are non-blocking unless the work item or repository rules make them release
   criteria.
 - Every finding must state severity, blocking yes/no, a concrete failure
-  scenario, evidence, and the smallest actionable fix.
+  scenario, evidence, and the smallest actionable fix — plus
+  `invariant_violated` (the property at risk) and `machinery_to_remove` (what
+  becomes deletable, or `none`), required for `readiness-rubric` findings and
+  recommended elsewhere.
+- Present findings highest-consequence first, by severity and blast radius, not
+  by discovery order. Report section order stays stable.
 - A blocking finding without a concrete failure scenario is malformed by
   contract; downgrade it to non-blocking and ask for evidence.
 - Resolve each finding as `fixed`, `deferred`, or `pushed-back`. If the reviewer

package/plugins/lisa-copilot/rules/reference/convergent-review.md

@@ -33,12 +33,57 @@ Every finding must state:
 - Evidence: the file, command output, observed behavior, ticket text, or
   external constraint proving the scenario is reachable.
 - Fix: the smallest actionable correction, or the reason no code change is
-  needed.
+  needed. The correction belongs at the **owning boundary** that permitted the
+  failure, not at the symptom site.
+- `invariant_violated`: the named property the system is supposed to hold that
+  this finding puts at risk — for example "the artifact that ships is the
+  artifact CI validated". The invariant is the property; the failure scenario is
+  the outcome when it breaks. State both; they are not interchangeable.
+- `machinery_to_remove`: the redundant checks, workarounds, or scaffolding that
+  become deletable once the correction lands, or explicitly `none`. This is a
+  **scaffolding-subtraction candidate** — it is surfaced for a human or the
+  implementer to act on and is never auto-deleted by any review pass.
 
 A finding marked blocking without a concrete failure scenario is malformed by
 contract. Downgrade it to non-blocking and ask for evidence instead of treating
 it as a merge blocker.
 
+### Compatibility
+
+`invariant_violated` and `machinery_to_remove` are **required for findings
+emitted under the `readiness-rubric`** and **recommended everywhere else**. A
+finding from an existing product, quality, local, bot-parity, or suggestion
+implementation pass that omits them is still well-formed by contract — this
+extension is additive and never retroactively malforms a shipped review surface.
+
+### Readiness findings map onto this shape
+
+A readiness finding names five fields. All five bind to this contract, so there
+is no second findings format anywhere in the repository:
+
+| Readiness field | Contract field |
+|---|---|
+| the at-risk invariant | `invariant_violated` (above) |
+| `evidence` | `Evidence` |
+| `why_proof_missed` | `Evidence`, extended with a required proof-gap clause: why the existing proof machinery did not catch this |
+| `root_correction` | `Fix`, qualified: the correction goes at the owning boundary, not the symptom site |
+| redundant machinery | `machinery_to_remove` (above) |
+
+Anything that needs a sixth field extends this section rather than starting a
+parallel format.
+
+### Consequence Ordering
+
+Findings are presented **highest-consequence first**. Consequence is determined
+by severity and blast radius — how much of the system, how many users, and how
+irreversible the outcome — not by discovery order, file order, or the order a
+tool happened to emit them in. Two reviewers ordering the same finding set
+differently is a defect, not a preference.
+
+This governs the order of findings **within** a section only. Report section
+order stays stable and is unaffected: never reorder, merge, or silently omit a
+section to surface a finding earlier.
+
 ## Dispositions
 
 The implementer resolves each finding with exactly one disposition:

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

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

package/plugins/lisa-cursor/rules/convergent-review-reference.mdc

@@ -38,12 +38,57 @@ Every finding must state:
 - Evidence: the file, command output, observed behavior, ticket text, or
   external constraint proving the scenario is reachable.
 - Fix: the smallest actionable correction, or the reason no code change is
-  needed.
+  needed. The correction belongs at the **owning boundary** that permitted the
+  failure, not at the symptom site.
+- `invariant_violated`: the named property the system is supposed to hold that
+  this finding puts at risk — for example "the artifact that ships is the
+  artifact CI validated". The invariant is the property; the failure scenario is
+  the outcome when it breaks. State both; they are not interchangeable.
+- `machinery_to_remove`: the redundant checks, workarounds, or scaffolding that
+  become deletable once the correction lands, or explicitly `none`. This is a
+  **scaffolding-subtraction candidate** — it is surfaced for a human or the
+  implementer to act on and is never auto-deleted by any review pass.
 
 A finding marked blocking without a concrete failure scenario is malformed by
 contract. Downgrade it to non-blocking and ask for evidence instead of treating
 it as a merge blocker.
 
+### Compatibility
+
+`invariant_violated` and `machinery_to_remove` are **required for findings
+emitted under the `readiness-rubric`** and **recommended everywhere else**. A
+finding from an existing product, quality, local, bot-parity, or suggestion
+implementation pass that omits them is still well-formed by contract — this
+extension is additive and never retroactively malforms a shipped review surface.
+
+### Readiness findings map onto this shape
+
+A readiness finding names five fields. All five bind to this contract, so there
+is no second findings format anywhere in the repository:
+
+| Readiness field | Contract field |
+|---|---|
+| the at-risk invariant | `invariant_violated` (above) |
+| `evidence` | `Evidence` |
+| `why_proof_missed` | `Evidence`, extended with a required proof-gap clause: why the existing proof machinery did not catch this |
+| `root_correction` | `Fix`, qualified: the correction goes at the owning boundary, not the symptom site |
+| redundant machinery | `machinery_to_remove` (above) |
+
+Anything that needs a sixth field extends this section rather than starting a
+parallel format.
+
+### Consequence Ordering
+
+Findings are presented **highest-consequence first**. Consequence is determined
+by severity and blast radius — how much of the system, how many users, and how
+irreversible the outcome — not by discovery order, file order, or the order a
+tool happened to emit them in. Two reviewers ordering the same finding set
+differently is a defect, not a preference.
+
+This governs the order of findings **within** a section only. Report section
+order stays stable and is unaffected: never reorder, merge, or silently omit a
+section to surface a finding earlier.
+
 ## Dispositions
 
 The implementer resolves each finding with exactly one disposition:

package/plugins/lisa-cursor/rules/convergent-review.mdc

@@ -12,7 +12,12 @@ Review exists to get correct work merged, not to keep a PR in review orbit.
   are non-blocking unless the work item or repository rules make them release
   criteria.
 - Every finding must state severity, blocking yes/no, a concrete failure
-  scenario, evidence, and the smallest actionable fix.
+  scenario, evidence, and the smallest actionable fix — plus
+  `invariant_violated` (the property at risk) and `machinery_to_remove` (what
+  becomes deletable, or `none`), required for `readiness-rubric` findings and
+  recommended elsewhere.
+- Present findings highest-consequence first, by severity and blast radius, not
+  by discovery order. Report section order stays stable.
 - A blocking finding without a concrete failure scenario is malformed by
   contract; downgrade it to non-blocking and ask for evidence.
 - Resolve each finding as `fixed`, `deferred`, or `pushed-back`. If the reviewer

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.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.268.1",
+  "version": "2.269.0",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"