@codyswann/lisa 2.268.0 → 2.269.0

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.268.0",
+  "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.0",
+  "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.0",
+  "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.0",
+  "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.0",
+  "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.0",
+  "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-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.268.0",
+  "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-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.268.0",
+  "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-wiki/.claude-plugin/plugin.json

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

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.268.0",
+  "version": "2.269.0",
   "description": "Distributable LLM Wiki kernel — ingest, query, lint, and maintain a git-native markdown knowledge base across Claude and Codex.",
   "author": {
     "name": "Cody Swann"

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

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

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

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

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

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

package/plugins/src/base/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/src/base/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/src/expo/skills/expo-cicd-workflows/scripts/package.json

@@ -6,6 +6,6 @@
   "dependencies": {
     "ajv": "^8.17.1",
     "ajv-formats": "^3.0.1",
-    "js-yaml": "^4.1.0"
+    "js-yaml": "^4.3.0"
   }
 }