@codyswann/lisa 4.45.11 → 4.45.12

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 (67) hide show
  1. package/all/copy-overwrite/scripts/lisa-hooks/parity-safety-net.sh +9 -1
  2. package/all/copy-overwrite/scripts/lisa-work-item.mjs +67 -3
  3. package/dist/core/lisa-owned-hash-ledger.d.ts.map +1 -1
  4. package/dist/core/lisa-owned-hash-ledger.js +4 -0
  5. package/dist/core/lisa-owned-hash-ledger.js.map +1 -1
  6. package/dist/core/nightly-e2e-guard-behavior-certificate.js +2 -2
  7. package/dist/core/upstream-evidence-manifest.d.ts.map +1 -1
  8. package/dist/core/upstream-evidence-manifest.js +6 -4
  9. package/dist/core/upstream-evidence-manifest.js.map +1 -1
  10. package/dist/opencode/plugin-templates/parity-safety-net.sh +9 -1
  11. package/package.json +4 -4
  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/parity-safety-net.sh +9 -1
  15. package/plugins/lisa-agy/hooks/parity-safety-net.sh +9 -1
  16. package/plugins/lisa-agy/plugin.json +1 -1
  17. package/plugins/lisa-cdk/.claude-plugin/plugin.json +1 -1
  18. package/plugins/lisa-cdk/.codex-plugin/plugin.json +1 -1
  19. package/plugins/lisa-cdk-agy/plugin.json +1 -1
  20. package/plugins/lisa-cdk-copilot/.claude-plugin/plugin.json +1 -1
  21. package/plugins/lisa-cdk-cursor/.claude-plugin/plugin.json +1 -1
  22. package/plugins/lisa-copilot/.claude-plugin/plugin.json +1 -1
  23. package/plugins/lisa-copilot/hooks/parity-safety-net.sh +9 -1
  24. package/plugins/lisa-cursor/.claude-plugin/plugin.json +1 -1
  25. package/plugins/lisa-cursor/hooks/parity-safety-net.sh +9 -1
  26. package/plugins/lisa-expo/.claude-plugin/plugin.json +1 -1
  27. package/plugins/lisa-expo/.codex-plugin/plugin.json +1 -1
  28. package/plugins/lisa-expo-agy/plugin.json +1 -1
  29. package/plugins/lisa-expo-copilot/.claude-plugin/plugin.json +1 -1
  30. package/plugins/lisa-expo-cursor/.claude-plugin/plugin.json +1 -1
  31. package/plugins/lisa-harper-fabric/.claude-plugin/plugin.json +1 -1
  32. package/plugins/lisa-harper-fabric/.codex-plugin/plugin.json +1 -1
  33. package/plugins/lisa-harper-fabric-agy/plugin.json +1 -1
  34. package/plugins/lisa-harper-fabric-copilot/.claude-plugin/plugin.json +1 -1
  35. package/plugins/lisa-harper-fabric-cursor/.claude-plugin/plugin.json +1 -1
  36. package/plugins/lisa-nestjs/.claude-plugin/plugin.json +1 -1
  37. package/plugins/lisa-nestjs/.codex-plugin/plugin.json +1 -1
  38. package/plugins/lisa-nestjs-agy/plugin.json +1 -1
  39. package/plugins/lisa-nestjs-copilot/.claude-plugin/plugin.json +1 -1
  40. package/plugins/lisa-nestjs-cursor/.claude-plugin/plugin.json +1 -1
  41. package/plugins/lisa-openclaw/.claude-plugin/plugin.json +1 -1
  42. package/plugins/lisa-openclaw/.codex-plugin/plugin.json +1 -1
  43. package/plugins/lisa-openclaw-agy/plugin.json +1 -1
  44. package/plugins/lisa-openclaw-copilot/.claude-plugin/plugin.json +1 -1
  45. package/plugins/lisa-openclaw-cursor/.claude-plugin/plugin.json +1 -1
  46. package/plugins/lisa-phaser/.claude-plugin/plugin.json +1 -1
  47. package/plugins/lisa-phaser/.codex-plugin/plugin.json +1 -1
  48. package/plugins/lisa-phaser-agy/plugin.json +1 -1
  49. package/plugins/lisa-phaser-copilot/.claude-plugin/plugin.json +1 -1
  50. package/plugins/lisa-phaser-cursor/.claude-plugin/plugin.json +1 -1
  51. package/plugins/lisa-rails/.claude-plugin/plugin.json +1 -1
  52. package/plugins/lisa-rails/.codex-plugin/plugin.json +1 -1
  53. package/plugins/lisa-rails-agy/plugin.json +1 -1
  54. package/plugins/lisa-rails-copilot/.claude-plugin/plugin.json +1 -1
  55. package/plugins/lisa-rails-cursor/.claude-plugin/plugin.json +1 -1
  56. package/plugins/lisa-typescript/.claude-plugin/plugin.json +1 -1
  57. package/plugins/lisa-typescript/.codex-plugin/plugin.json +1 -1
  58. package/plugins/lisa-typescript-agy/plugin.json +1 -1
  59. package/plugins/lisa-typescript-copilot/.claude-plugin/plugin.json +1 -1
  60. package/plugins/lisa-typescript-cursor/.claude-plugin/plugin.json +1 -1
  61. package/plugins/lisa-wiki/.claude-plugin/plugin.json +1 -1
  62. package/plugins/lisa-wiki/.codex-plugin/plugin.json +1 -1
  63. package/plugins/lisa-wiki-agy/plugin.json +1 -1
  64. package/plugins/lisa-wiki-copilot/.claude-plugin/plugin.json +1 -1
  65. package/plugins/lisa-wiki-cursor/.claude-plugin/plugin.json +1 -1
  66. package/plugins/src/base/hooks/parity-safety-net.sh +9 -1
  67. package/scripts/merge-generated-artifact.mjs +31 -2
@@ -1827,7 +1827,15 @@ if matches "${GIT_CMD}"'restore([[:space:]]|$)'; then
1827
1827
  fi
1828
1828
 
1829
1829
  # 7. `git stash drop` / `git stash clear` destroy stashed work. push/pop/list/
1830
- # apply — the safe alternatives the reset guard recommends — stay allowed.
1830
+ # apply stay ALLOWED — this guard moves no verdict on them — but they are no
1831
+ # longer RECOMMENDED anywhere in this file, and this comment used to say the
1832
+ # opposite (issue #3692). It called them "the safe alternatives the reset
1833
+ # guard recommends", which stopped being true when #3722 rewrote guards 3
1834
+ # and 4 to point at $PRESERVE_GUIDANCE instead. A stale comment endorsing
1835
+ # the stash is the same hazard as a stale message doing it: the next reader
1836
+ # takes the file's word for what the file does. See $PRESERVE_GUIDANCE for
1837
+ # why one stack shared by every worktree of a clone makes push/pop unsafe
1838
+ # under this project's concurrency.
1831
1839
  if matches "${GIT_CMD}"'stash[[:space:]]+(drop|clear)([[:space:]]|$)'; then
1832
1840
  block "git stash drop/clear destroys stashed work"
1833
1841
  fi
package/package.json CHANGED
@@ -176,7 +176,7 @@
176
176
  "zod-validation-error": "^4.0.0"
177
177
  },
178
178
  "name": "@codyswann/lisa",
179
- "version": "4.45.11",
179
+ "version": "4.45.12",
180
180
  "description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
181
181
  "main": "dist/index.js",
182
182
  "exports": {
@@ -324,7 +324,7 @@
324
324
  "test": "tests"
325
325
  },
326
326
  "types": "./dist/index.d.ts",
327
- "lisaReleaseCommit": "d2d6f1de6bfd7610aaa0d777b6daa268419a48e8",
328
- "gitHead": "d2d6f1de6bfd7610aaa0d777b6daa268419a48e8",
329
- "lisaReleaseTag": "v4.45.11"
327
+ "lisaReleaseCommit": "89d592bbcd9e5cd5746a7a1fe65168fbf9dde810",
328
+ "gitHead": "89d592bbcd9e5cd5746a7a1fe65168fbf9dde810",
329
+ "lisaReleaseTag": "v4.45.12"
330
330
  }
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa",
3
- "version": "4.45.11",
3
+ "version": "4.45.12",
4
4
  "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa",
3
- "version": "4.45.11",
3
+ "version": "4.45.12",
4
4
  "description": "Universal governance: agents, skills, commands, hooks, and rules for all projects.",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1827,7 +1827,15 @@ if matches "${GIT_CMD}"'restore([[:space:]]|$)'; then
1827
1827
  fi
1828
1828
 
1829
1829
  # 7. `git stash drop` / `git stash clear` destroy stashed work. push/pop/list/
1830
- # apply — the safe alternatives the reset guard recommends — stay allowed.
1830
+ # apply stay ALLOWED — this guard moves no verdict on them — but they are no
1831
+ # longer RECOMMENDED anywhere in this file, and this comment used to say the
1832
+ # opposite (issue #3692). It called them "the safe alternatives the reset
1833
+ # guard recommends", which stopped being true when #3722 rewrote guards 3
1834
+ # and 4 to point at $PRESERVE_GUIDANCE instead. A stale comment endorsing
1835
+ # the stash is the same hazard as a stale message doing it: the next reader
1836
+ # takes the file's word for what the file does. See $PRESERVE_GUIDANCE for
1837
+ # why one stack shared by every worktree of a clone makes push/pop unsafe
1838
+ # under this project's concurrency.
1831
1839
  if matches "${GIT_CMD}"'stash[[:space:]]+(drop|clear)([[:space:]]|$)'; then
1832
1840
  block "git stash drop/clear destroys stashed work"
1833
1841
  fi
@@ -1827,7 +1827,15 @@ if matches "${GIT_CMD}"'restore([[:space:]]|$)'; then
1827
1827
  fi
1828
1828
 
1829
1829
  # 7. `git stash drop` / `git stash clear` destroy stashed work. push/pop/list/
1830
- # apply — the safe alternatives the reset guard recommends — stay allowed.
1830
+ # apply stay ALLOWED — this guard moves no verdict on them — but they are no
1831
+ # longer RECOMMENDED anywhere in this file, and this comment used to say the
1832
+ # opposite (issue #3692). It called them "the safe alternatives the reset
1833
+ # guard recommends", which stopped being true when #3722 rewrote guards 3
1834
+ # and 4 to point at $PRESERVE_GUIDANCE instead. A stale comment endorsing
1835
+ # the stash is the same hazard as a stale message doing it: the next reader
1836
+ # takes the file's word for what the file does. See $PRESERVE_GUIDANCE for
1837
+ # why one stack shared by every worktree of a clone makes push/pop unsafe
1838
+ # under this project's concurrency.
1831
1839
  if matches "${GIT_CMD}"'stash[[:space:]]+(drop|clear)([[:space:]]|$)'; then
1832
1840
  block "git stash drop/clear destroys stashed work"
1833
1841
  fi
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa",
3
- "version": "4.45.11",
3
+ "version": "4.45.12",
4
4
  "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-cdk",
3
- "version": "4.45.11",
3
+ "version": "4.45.12",
4
4
  "description": "AWS CDK-specific plugin",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-cdk",
3
- "version": "4.45.11",
3
+ "version": "4.45.12",
4
4
  "description": "AWS CDK-specific Lisa plugin.",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-cdk",
3
- "version": "4.45.11",
3
+ "version": "4.45.12",
4
4
  "description": "AWS CDK-specific plugin",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-cdk",
3
- "version": "4.45.11",
3
+ "version": "4.45.12",
4
4
  "description": "AWS CDK-specific plugin",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-cdk",
3
- "version": "4.45.11",
3
+ "version": "4.45.12",
4
4
  "description": "AWS CDK-specific plugin",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa",
3
- "version": "4.45.11",
3
+ "version": "4.45.12",
4
4
  "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1827,7 +1827,15 @@ if matches "${GIT_CMD}"'restore([[:space:]]|$)'; then
1827
1827
  fi
1828
1828
 
1829
1829
  # 7. `git stash drop` / `git stash clear` destroy stashed work. push/pop/list/
1830
- # apply — the safe alternatives the reset guard recommends — stay allowed.
1830
+ # apply stay ALLOWED — this guard moves no verdict on them — but they are no
1831
+ # longer RECOMMENDED anywhere in this file, and this comment used to say the
1832
+ # opposite (issue #3692). It called them "the safe alternatives the reset
1833
+ # guard recommends", which stopped being true when #3722 rewrote guards 3
1834
+ # and 4 to point at $PRESERVE_GUIDANCE instead. A stale comment endorsing
1835
+ # the stash is the same hazard as a stale message doing it: the next reader
1836
+ # takes the file's word for what the file does. See $PRESERVE_GUIDANCE for
1837
+ # why one stack shared by every worktree of a clone makes push/pop unsafe
1838
+ # under this project's concurrency.
1831
1839
  if matches "${GIT_CMD}"'stash[[:space:]]+(drop|clear)([[:space:]]|$)'; then
1832
1840
  block "git stash drop/clear destroys stashed work"
1833
1841
  fi
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa",
3
- "version": "4.45.11",
3
+ "version": "4.45.12",
4
4
  "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
5
5
  "author": {
6
6
  "name": "Cody Swann"
@@ -1827,7 +1827,15 @@ if matches "${GIT_CMD}"'restore([[:space:]]|$)'; then
1827
1827
  fi
1828
1828
 
1829
1829
  # 7. `git stash drop` / `git stash clear` destroy stashed work. push/pop/list/
1830
- # apply — the safe alternatives the reset guard recommends — stay allowed.
1830
+ # apply stay ALLOWED — this guard moves no verdict on them — but they are no
1831
+ # longer RECOMMENDED anywhere in this file, and this comment used to say the
1832
+ # opposite (issue #3692). It called them "the safe alternatives the reset
1833
+ # guard recommends", which stopped being true when #3722 rewrote guards 3
1834
+ # and 4 to point at $PRESERVE_GUIDANCE instead. A stale comment endorsing
1835
+ # the stash is the same hazard as a stale message doing it: the next reader
1836
+ # takes the file's word for what the file does. See $PRESERVE_GUIDANCE for
1837
+ # why one stack shared by every worktree of a clone makes push/pop unsafe
1838
+ # under this project's concurrency.
1831
1839
  if matches "${GIT_CMD}"'stash[[:space:]]+(drop|clear)([[:space:]]|$)'; then
1832
1840
  block "git stash drop/clear destroys stashed work"
1833
1841
  fi
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lisa-expo",
3
- "version": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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": "4.45.11",
3
+ "version": "4.45.12",
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"
@@ -1827,7 +1827,15 @@ if matches "${GIT_CMD}"'restore([[:space:]]|$)'; then
1827
1827
  fi
1828
1828
 
1829
1829
  # 7. `git stash drop` / `git stash clear` destroy stashed work. push/pop/list/
1830
- # apply — the safe alternatives the reset guard recommends — stay allowed.
1830
+ # apply stay ALLOWED — this guard moves no verdict on them — but they are no
1831
+ # longer RECOMMENDED anywhere in this file, and this comment used to say the
1832
+ # opposite (issue #3692). It called them "the safe alternatives the reset
1833
+ # guard recommends", which stopped being true when #3722 rewrote guards 3
1834
+ # and 4 to point at $PRESERVE_GUIDANCE instead. A stale comment endorsing
1835
+ # the stash is the same hazard as a stale message doing it: the next reader
1836
+ # takes the file's word for what the file does. See $PRESERVE_GUIDANCE for
1837
+ # why one stack shared by every worktree of a clone makes push/pop unsafe
1838
+ # under this project's concurrency.
1831
1839
  if matches "${GIT_CMD}"'stash[[:space:]]+(drop|clear)([[:space:]]|$)'; then
1832
1840
  block "git stash drop/clear destroys stashed work"
1833
1841
  fi