@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.
- package/all/copy-overwrite/scripts/lisa-hooks/parity-safety-net.sh +9 -1
- package/all/copy-overwrite/scripts/lisa-work-item.mjs +67 -3
- package/dist/core/lisa-owned-hash-ledger.d.ts.map +1 -1
- package/dist/core/lisa-owned-hash-ledger.js +4 -0
- package/dist/core/lisa-owned-hash-ledger.js.map +1 -1
- package/dist/core/nightly-e2e-guard-behavior-certificate.js +2 -2
- package/dist/core/upstream-evidence-manifest.d.ts.map +1 -1
- package/dist/core/upstream-evidence-manifest.js +6 -4
- package/dist/core/upstream-evidence-manifest.js.map +1 -1
- package/dist/opencode/plugin-templates/parity-safety-net.sh +9 -1
- package/package.json +4 -4
- package/plugins/lisa/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa/hooks/parity-safety-net.sh +9 -1
- package/plugins/lisa-agy/hooks/parity-safety-net.sh +9 -1
- package/plugins/lisa-agy/plugin.json +1 -1
- package/plugins/lisa-cdk/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-cdk/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-cdk-agy/plugin.json +1 -1
- package/plugins/lisa-cdk-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-cdk-cursor/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-copilot/hooks/parity-safety-net.sh +9 -1
- package/plugins/lisa-cursor/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-cursor/hooks/parity-safety-net.sh +9 -1
- package/plugins/lisa-expo/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-expo/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-expo-agy/plugin.json +1 -1
- package/plugins/lisa-expo-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-expo-cursor/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-harper-fabric/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-harper-fabric/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-harper-fabric-agy/plugin.json +1 -1
- package/plugins/lisa-harper-fabric-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-harper-fabric-cursor/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-nestjs/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-nestjs/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-nestjs-agy/plugin.json +1 -1
- package/plugins/lisa-nestjs-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-nestjs-cursor/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-openclaw/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-openclaw/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-openclaw-agy/plugin.json +1 -1
- package/plugins/lisa-openclaw-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-openclaw-cursor/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-phaser/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-phaser/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-phaser-agy/plugin.json +1 -1
- package/plugins/lisa-phaser-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-phaser-cursor/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-rails/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-rails/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-rails-agy/plugin.json +1 -1
- package/plugins/lisa-rails-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-rails-cursor/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-typescript/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-typescript/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-typescript-agy/plugin.json +1 -1
- package/plugins/lisa-typescript-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-typescript-cursor/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-wiki/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-wiki/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-wiki-agy/plugin.json +1 -1
- package/plugins/lisa-wiki-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-wiki-cursor/.claude-plugin/plugin.json +1 -1
- package/plugins/src/base/hooks/parity-safety-net.sh +9 -1
- 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 —
|
|
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.
|
|
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": "
|
|
328
|
-
"gitHead": "
|
|
329
|
-
"lisaReleaseTag": "v4.45.
|
|
327
|
+
"lisaReleaseCommit": "89d592bbcd9e5cd5746a7a1fe65168fbf9dde810",
|
|
328
|
+
"gitHead": "89d592bbcd9e5cd5746a7a1fe65168fbf9dde810",
|
|
329
|
+
"lisaReleaseTag": "v4.45.12"
|
|
330
330
|
}
|
|
@@ -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 —
|
|
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 —
|
|
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 —
|
|
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 —
|
|
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-openclaw",
|
|
3
|
-
"version": "4.45.
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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"
|
|
@@ -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 —
|
|
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
|