@codyswann/lisa 3.26.0 → 3.26.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (65) hide show
  1. package/all/copy-overwrite/scripts/lisa-hooks/block-managed-file-edits.sh +136 -15
  2. package/dist/cli/doctor-lisa-owned-artifacts.d.ts.map +1 -1
  3. package/dist/cli/doctor-lisa-owned-artifacts.js +13 -2
  4. package/dist/cli/doctor-lisa-owned-artifacts.js.map +1 -1
  5. package/dist/core/lisa-owned-hash-ledger.d.ts.map +1 -1
  6. package/dist/core/lisa-owned-hash-ledger.js +3 -0
  7. package/dist/core/lisa-owned-hash-ledger.js.map +1 -1
  8. package/dist/core/upstream-evidence-manifest.d.ts.map +1 -1
  9. package/dist/core/upstream-evidence-manifest.js +3 -2
  10. package/dist/core/upstream-evidence-manifest.js.map +1 -1
  11. package/package.json +1 -1
  12. package/plugins/lisa/.claude-plugin/plugin.json +1 -1
  13. package/plugins/lisa/.codex-plugin/plugin.json +1 -1
  14. package/plugins/lisa/hooks/block-managed-file-edits.sh +136 -15
  15. package/plugins/lisa-agy/plugin.json +1 -1
  16. package/plugins/lisa-cdk/.claude-plugin/plugin.json +1 -1
  17. package/plugins/lisa-cdk/.codex-plugin/plugin.json +1 -1
  18. package/plugins/lisa-cdk-agy/plugin.json +1 -1
  19. package/plugins/lisa-cdk-copilot/.claude-plugin/plugin.json +1 -1
  20. package/plugins/lisa-cdk-cursor/.claude-plugin/plugin.json +1 -1
  21. package/plugins/lisa-copilot/.claude-plugin/plugin.json +1 -1
  22. package/plugins/lisa-copilot/hooks/block-managed-file-edits.sh +136 -15
  23. package/plugins/lisa-cursor/.claude-plugin/plugin.json +1 -1
  24. package/plugins/lisa-cursor/hooks/block-managed-file-edits.sh +136 -15
  25. package/plugins/lisa-expo/.claude-plugin/plugin.json +1 -1
  26. package/plugins/lisa-expo/.codex-plugin/plugin.json +1 -1
  27. package/plugins/lisa-expo-agy/plugin.json +1 -1
  28. package/plugins/lisa-expo-copilot/.claude-plugin/plugin.json +1 -1
  29. package/plugins/lisa-expo-cursor/.claude-plugin/plugin.json +1 -1
  30. package/plugins/lisa-harper-fabric/.claude-plugin/plugin.json +1 -1
  31. package/plugins/lisa-harper-fabric/.codex-plugin/plugin.json +1 -1
  32. package/plugins/lisa-harper-fabric-agy/plugin.json +1 -1
  33. package/plugins/lisa-harper-fabric-copilot/.claude-plugin/plugin.json +1 -1
  34. package/plugins/lisa-harper-fabric-cursor/.claude-plugin/plugin.json +1 -1
  35. package/plugins/lisa-nestjs/.claude-plugin/plugin.json +1 -1
  36. package/plugins/lisa-nestjs/.codex-plugin/plugin.json +1 -1
  37. package/plugins/lisa-nestjs-agy/plugin.json +1 -1
  38. package/plugins/lisa-nestjs-copilot/.claude-plugin/plugin.json +1 -1
  39. package/plugins/lisa-nestjs-cursor/.claude-plugin/plugin.json +1 -1
  40. package/plugins/lisa-openclaw/.claude-plugin/plugin.json +1 -1
  41. package/plugins/lisa-openclaw/.codex-plugin/plugin.json +1 -1
  42. package/plugins/lisa-openclaw-agy/plugin.json +1 -1
  43. package/plugins/lisa-openclaw-copilot/.claude-plugin/plugin.json +1 -1
  44. package/plugins/lisa-openclaw-cursor/.claude-plugin/plugin.json +1 -1
  45. package/plugins/lisa-phaser/.claude-plugin/plugin.json +1 -1
  46. package/plugins/lisa-phaser/.codex-plugin/plugin.json +1 -1
  47. package/plugins/lisa-phaser-agy/plugin.json +1 -1
  48. package/plugins/lisa-phaser-copilot/.claude-plugin/plugin.json +1 -1
  49. package/plugins/lisa-phaser-cursor/.claude-plugin/plugin.json +1 -1
  50. package/plugins/lisa-rails/.claude-plugin/plugin.json +1 -1
  51. package/plugins/lisa-rails/.codex-plugin/plugin.json +1 -1
  52. package/plugins/lisa-rails-agy/plugin.json +1 -1
  53. package/plugins/lisa-rails-copilot/.claude-plugin/plugin.json +1 -1
  54. package/plugins/lisa-rails-cursor/.claude-plugin/plugin.json +1 -1
  55. package/plugins/lisa-typescript/.claude-plugin/plugin.json +1 -1
  56. package/plugins/lisa-typescript/.codex-plugin/plugin.json +1 -1
  57. package/plugins/lisa-typescript-agy/plugin.json +1 -1
  58. package/plugins/lisa-typescript-copilot/.claude-plugin/plugin.json +1 -1
  59. package/plugins/lisa-typescript-cursor/.claude-plugin/plugin.json +1 -1
  60. package/plugins/lisa-wiki/.claude-plugin/plugin.json +1 -1
  61. package/plugins/lisa-wiki/.codex-plugin/plugin.json +1 -1
  62. package/plugins/lisa-wiki-agy/plugin.json +1 -1
  63. package/plugins/lisa-wiki-copilot/.claude-plugin/plugin.json +1 -1
  64. package/plugins/lisa-wiki-cursor/.claude-plugin/plugin.json +1 -1
  65. package/plugins/src/base/hooks/block-managed-file-edits.sh +136 -15
@@ -1,10 +1,9 @@
1
1
  #!/usr/bin/env bash
2
2
  # PreToolUse hook: refuse agent writes to files Lisa overwrites on every apply.
3
3
  #
4
- # Lisa ships templates in three modes, and only one of them destroys host edits:
4
+ # Lisa ships templates in three modes, and only one of them is unsafe to edit:
5
5
  #
6
- # copy-overwrite — replaced wholesale on every `lisa apply`. An edit here is
7
- # gone at the next `bun install`, silently.
6
+ # copy-overwrite — see below; the harm depends on the file.
8
7
  # copy-contents — Lisa APPENDS its lines; host content survives.
9
8
  # create-only — skipped when the file exists; the host owns it outright.
10
9
  #
@@ -12,6 +11,21 @@
12
11
  # would stop agents editing files they are supposed to own, which is worse than
13
12
  # the problem being solved.
14
13
  #
14
+ # WITHIN copy-overwrite there are two populations with OPPOSITE consequences,
15
+ # and an earlier version of this guard described only one of them:
16
+ #
17
+ # hash-tracked guards (the `.mjs` scripts, listed in the Lisa-owned ledger)
18
+ # — an edit classifies as `host-modified` and `lisa apply` PRESERVES it.
19
+ # The file silently forks and stops receiving upstream fixes while looking
20
+ # current. Nothing is deleted; that is what makes it hard to notice.
21
+ # everything else (`.json` configs and friends)
22
+ # — replaced wholesale on the next apply, which runs on every install.
23
+ # The edit vanishes.
24
+ #
25
+ # The refusal branches on ledger membership so it states the consequence that
26
+ # actually applies, rather than describing both and leaving the reader to work
27
+ # out which they are in.
28
+ #
15
29
  # Measured, not hypothetical. Nothing enforced this, so downstream copies were
16
30
  # edited and then silently diverged: `classify-maestro-failures.mjs` reached
17
31
  # 36,061 bytes in one fleet repo against 29,586 shipped, and five gate files in
@@ -67,6 +81,71 @@ if [ -f "$project_root/package.json" ] &&
67
81
  exit 0
68
82
  fi
69
83
 
84
+ # Whether the project has claimed a path in `.lisaignore`.
85
+ #
86
+ # THIS IS THE OWNERSHIP QUESTION, and it decides whether blocking is right at
87
+ # all. `lisa apply` skips an ignored path — it logs `Kept (.lisaignore)` and
88
+ # counts it as ignored rather than overwritten — so the file is the project's,
89
+ # its edits survive, and refusing them would be refusing someone access to their
90
+ # own file. `doctor-lisa-owned-artifacts` already consults this list; this guard
91
+ # did not, which would have blocked deliberate forks.
92
+ #
93
+ # The real matcher is minimatch in `src/utils/ignore-patterns.ts` and cannot be
94
+ # reproduced faithfully in shell. This covers the common shapes — exact path,
95
+ # directory prefix, glob, and a bare pattern matching any segment — and where it
96
+ # is unsure it ALLOWS. Wrongly allowing costs an edit that apply may overwrite,
97
+ # which is the behaviour before this guard existed; wrongly blocking locks
98
+ # someone out of a file they own.
99
+ lisaignored() {
100
+ local rel="$1"
101
+ local list="$project_root/.lisaignore"
102
+ [ -f "$list" ] || return 1
103
+ local pattern
104
+ while IFS= read -r pattern || [ -n "$pattern" ]; do
105
+ pattern="${pattern#"${pattern%%[![:space:]]*}"}"
106
+ pattern="${pattern%"${pattern##*[![:space:]]}"}"
107
+ [ -n "$pattern" ] || continue
108
+ case "$pattern" in \#*) continue ;; esac
109
+ # A leading `!` is not gitignore negation here. The real matcher passes
110
+ # patterns to minimatch, which negates by default, and it combines them with
111
+ # `.some()` — so a single `!scripts/a.mjs` line reports EVERY OTHER PATH as
112
+ # ignored. Measured:
113
+ #
114
+ # patterns=["!scripts/a.mjs"] path=scripts/a.mjs -> ignored=false
115
+ # patterns=["!scripts/a.mjs"] path=scripts/b.mjs -> ignored=TRUE
116
+ #
117
+ # Reproducing that faithfully would mean disabling this guard on a typo.
118
+ # Reproducing the intuitive gitignore reading would mean blocking files the
119
+ # matcher considers ignored. Both are wrong, so the file is treated as
120
+ # claimed and the write is allowed — the same direction this function errs
121
+ # everywhere else. Filed upstream; when the matcher stops negating, delete
122
+ # this branch rather than teaching it a second wrong answer.
123
+ case "$pattern" in !*) return 0 ;; esac
124
+ case "$pattern" in
125
+ */)
126
+ case "$rel" in "${pattern%/}"/* | "${pattern%/}") return 0 ;; esac
127
+ ;;
128
+ esac
129
+ # shellcheck disable=SC2254 -- the pattern is a glob on purpose.
130
+ case "$rel" in $pattern) return 0 ;; esac
131
+ case "$pattern" in
132
+ */*) ;;
133
+ *)
134
+ # shellcheck disable=SC2254 -- ditto, matched against the basename.
135
+ case "${rel##*/}" in $pattern) return 0 ;; esac
136
+ ;;
137
+ esac
138
+ done <"$list"
139
+ return 1
140
+ }
141
+
142
+ # A candidate rewritten relative to the project, so an absolute target from a
143
+ # tool payload and a relative one from a shell command classify identically.
144
+ relative_path() {
145
+ local rel="${1#"$project_root"/}"
146
+ printf '%s' "${rel#./}"
147
+ }
148
+
70
149
  # Whether a host-relative path is shipped as a copy-overwrite template.
71
150
  #
72
151
  # A few stat calls rather than an enumeration: the same relative path is probed
@@ -77,10 +156,11 @@ managed_source() {
77
156
  case "$candidate" in
78
157
  */node_modules/* | node_modules/* | */dist/* | dist/*) return 1 ;;
79
158
  esac
80
- # Normalise to a project-relative path so an absolute target still matches.
81
- local rel="${candidate#"$project_root"/}"
82
- rel="${rel#./}"
159
+ local rel
160
+ rel="$(relative_path "$candidate")"
83
161
  [ -n "$rel" ] || return 1
162
+ # Claimed by the project, so not ours to refuse.
163
+ lisaignored "$rel" && return 1
84
164
  local stack
85
165
  for stack in "$package_root"/*/copy-overwrite; do
86
166
  [ -d "$stack" ] || continue
@@ -92,19 +172,44 @@ managed_source() {
92
172
  return 1
93
173
  }
94
174
 
175
+ # Whether a destination is a ledger-tracked Lisa-owned guard.
176
+ #
177
+ # The two populations behind this guard have OPPOSITE consequences, so the
178
+ # refusal has to know which one it is looking at rather than describing both and
179
+ # leaving the reader to guess. A guard in the content-hash ledger classifies as
180
+ # `host-modified` once edited and `lisa apply` PRESERVES it; anything else is
181
+ # replaced wholesale. Both are bad, for different reasons, and the right next
182
+ # step differs too.
183
+ ledger_tracked() {
184
+ local rel="$1"
185
+ local ledger="$package_root/dist/core/lisa-owned-hash-ledger.js"
186
+ [ -f "$ledger" ] || return 1
187
+ grep -q "\"$rel\"" "$ledger" 2>/dev/null
188
+ }
189
+
95
190
  refuse() {
96
191
  local target="$1"
97
192
  local source="$2"
193
+ local rel="$3"
194
+ local consequence
195
+ if ledger_tracked "$rel"; then
196
+ consequence="This is a Lisa-owned guard, tracked by content hash. \`lisa apply\`
197
+ will PRESERVE your edit rather than overwrite it — and that is the trap. The
198
+ file silently forks: it keeps looking current while every upstream fix stops
199
+ reaching it. One repository in this fleet is carrying 243 lines of divergence
200
+ nobody knew about, in a guard that had quietly stopped receiving fixes."
201
+ else
202
+ consequence="This template is not hash-tracked, so \`lisa apply\` REPLACES it
203
+ wholesale — and apply runs on every \`bun install\`. Your edit survives until the
204
+ next install and then vanishes, with nothing reporting that it had."
205
+ fi
98
206
  cat >&2 <<EOF
99
207
  BLOCKED: refusing to write \`$target\`.
100
208
 
101
- WHY: this file is Lisa-managed. It is shipped as a **copy-overwrite** template
102
- (\`$source\` in the installed package) and is replaced wholesale on every
103
- \`lisa apply\` — which runs on every \`bun install\`. Your edit would survive
104
- until the next install and then vanish, with nothing reporting that it had.
209
+ WHY: this file is Lisa-managed, shipped as a **copy-overwrite** template
210
+ (\`$source\` in the installed package).
105
211
 
106
- That is not hypothetical: downstream copies edited this way diverged silently
107
- until they stopped receiving upstream fixes entirely.
212
+ $consequence
108
213
 
109
214
  WHERE IT GOES INSTEAD — take the first one that fits:
110
215
 
@@ -122,7 +227,23 @@ WHERE IT GOES INSTEAD — take the first one that fits:
122
227
  proves each one, so a project can substitute its own task without touching a
123
228
  shipped file.
124
229
 
125
- 4. You believe this file should not be Lisa-managed at all. That is a real
230
+ 4. This project has deliberately FORKED this file and means to keep its own
231
+ version. What to do depends on which population it is, and \`.lisaignore\` is
232
+ the WRONG answer for a hash-tracked guard:
233
+
234
+ - **A Lisa-owned guard (hash-tracked).** Do NOT add it to \`.lisaignore\`. The
235
+ ledger already preserves your version, so ignoring it buys nothing — and it
236
+ silences the standoff \`lisa doctor\` reports on every run, replacing a true
237
+ warning with the line "Enforcement guards match the installed Lisa
238
+ version", which is then false. A visible, resolvable fork becomes a silent
239
+ permanent one. Keep the warning and resolve the fork: upstream what is
240
+ general, or accept the standoff knowingly. To make this one edit, use the
241
+ override below.
242
+ - **Any other template.** \`.lisaignore\` is the right answer. Nothing else
243
+ preserves it, and the entry declares the divergence where the next person
244
+ can see it.
245
+
246
+ 5. You believe this file should not be Lisa-managed at all. That is a real
126
247
  argument and it belongs upstream, not in a local edit that will be erased.
127
248
 
128
249
  If a human explicitly asked for this edit, they can re-run with
@@ -142,7 +263,7 @@ case "$tool_name" in
142
263
  while IFS= read -r candidate; do
143
264
  [ -n "$candidate" ] || continue
144
265
  if source_path="$(managed_source "$candidate")"; then
145
- refuse "$candidate" "$source_path"
266
+ refuse "$candidate" "$source_path" "$(relative_path "$candidate")"
146
267
  fi
147
268
  done <<EOF
148
269
  $paths
@@ -157,7 +278,7 @@ EOF
157
278
  while IFS= read -r token; do
158
279
  [ -n "$token" ] || continue
159
280
  if source_path="$(managed_source "$token")"; then
160
- refuse "$token" "$source_path"
281
+ refuse "$token" "$source_path" "$(relative_path "$token")"
161
282
  fi
162
283
  done <<EOF
163
284
  $(printf '%s' "$command_str" |
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-expo",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-expo",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "Expo and React Native-specific skills, agents, rules, and MCP servers.",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-expo",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-expo",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-expo",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-harper-fabric",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "Harper/Fabric-specific rules for TypeScript component apps",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-harper-fabric",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "Harper/Fabric-specific Lisa rules for TypeScript component apps.",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-harper-fabric",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "Harper/Fabric-specific rules for TypeScript component apps",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-harper-fabric",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "Harper/Fabric-specific rules for TypeScript component apps",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-harper-fabric",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "Harper/Fabric-specific rules for TypeScript component apps",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-nestjs",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-nestjs",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "NestJS-specific skills and migration write-protection hooks.",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-nestjs",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-nestjs",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-nestjs",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-openclaw",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "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",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-openclaw",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, across Claude and Codex.",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-openclaw",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "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",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-openclaw",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "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",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-openclaw",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "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",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-phaser",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "Phaser 4 game-development rules for TypeScript projects",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-phaser",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "Phaser 4 game-development rules for TypeScript projects",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-phaser",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "Phaser 4 game-development rules for TypeScript projects",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-phaser",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "Phaser 4 game-development rules for TypeScript projects",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-phaser",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "Phaser 4 game-development rules for TypeScript projects",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-rails",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-rails",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "Ruby on Rails-specific skills and hooks for RuboCop and ast-grep scanning on edit.",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-rails",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-rails",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-rails",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-typescript",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-typescript",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "TypeScript-specific hooks for formatting, linting, and ast-grep scanning on edit.",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-typescript",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-typescript",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-typescript",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-wiki",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-wiki",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "Distributable LLM Wiki kernel — ingest, query, lint, and maintain a git-native markdown knowledge base across Claude and Codex.",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-wiki",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-wiki",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-wiki",
3
- "version": "3.26.0",
3
+ "version": "3.26.1",
4
4
  "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
5
5
  "author": {
6
6
  "name": "Cody Swann"