@codyswann/lisa 2.334.1 → 2.335.0
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-enforcement-fallback.sh +32 -9
- package/dist/core/upstream-evidence-manifest.js +2 -2
- package/package.json +1 -1
- package/plugins/lisa/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa/.codex-plugin/plugin.json +1 -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-cursor/.claude-plugin/plugin.json +1 -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/scripts/lisa-enforcement-fallback.sh +32 -9
|
@@ -24,16 +24,39 @@ payload="$(cat)"
|
|
|
24
24
|
repo_root="${CLAUDE_PROJECT_DIR:-$(git rev-parse --show-toplevel 2>/dev/null)}"
|
|
25
25
|
[ -n "$repo_root" ] || exit 0
|
|
26
26
|
|
|
27
|
-
#
|
|
28
|
-
# guard twice and print every refusal twice. Absence is the interesting case and
|
|
29
|
-
# the only one this exists for.
|
|
27
|
+
# There is deliberately no skip here, and that is the whole point.
|
|
30
28
|
#
|
|
31
|
-
#
|
|
32
|
-
#
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
29
|
+
# This used to stand down when `installed_plugins.json` mentioned `lisa@lisa`,
|
|
30
|
+
# to avoid running every guard twice on a developer machine. The question that
|
|
31
|
+
# has to be answered is "are the plugin's guards running in this session?" and
|
|
32
|
+
# the file being consulted answers "has this plugin ever been installed, for any
|
|
33
|
+
# project, on this machine?". Those come apart three ways, and in each one both
|
|
34
|
+
# layers were off:
|
|
35
|
+
#
|
|
36
|
+
# - Project-blind. The registry is keyed by plugin with an array of per-project
|
|
37
|
+
# entries, so the grep matched the key. One project installing Lisa disabled
|
|
38
|
+
# the fallback for every other project on the machine.
|
|
39
|
+
# - Enablement-blind. `enabledPlugins` can set a plugin to false without
|
|
40
|
+
# removing its registry entry, so the plugin guards were off while this file
|
|
41
|
+
# believed they were on.
|
|
42
|
+
# - Session-blind. Hooks load at session start; the registry is written on any
|
|
43
|
+
# install or update. A plugin updated four minutes into a session leaves the
|
|
44
|
+
# registry saying "installed" for the rest of it, with no plugin hooks
|
|
45
|
+
# loaded. That is the one that was caught in the wild: a write to AGENTS.md
|
|
46
|
+
# went through in a session where both guard copies exit 2 for that exact
|
|
47
|
+
# payload.
|
|
48
|
+
#
|
|
49
|
+
# The first two are fixable with a better lookup. The third is not: plugin-hook
|
|
50
|
+
# liveness is not observable from a repository hook. CLAUDE_PLUGIN_ROOT is set
|
|
51
|
+
# only for plugin hooks, and nothing on disk distinguishes "registered" from
|
|
52
|
+
# "loaded into this session". Any check against a file answers a different
|
|
53
|
+
# question and will drift from the real one again.
|
|
54
|
+
#
|
|
55
|
+
# So the guards run unconditionally. On a machine where the plugin hooks are also
|
|
56
|
+
# live that costs a duplicated sweep (~170ms) and a refusal printed twice, and
|
|
57
|
+
# that is the correct trade against enforcement silently switching itself off.
|
|
58
|
+
# Recovering it belongs in the guards — a marker keyed on session and payload, so
|
|
59
|
+
# whichever layer fires first does the work — not in a liveness guess here.
|
|
37
60
|
|
|
38
61
|
# Where the guards live depends on which repository this is.
|
|
39
62
|
#
|
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
export const UPSTREAM_EVIDENCE_MANIFEST = Object.freeze({
|
|
4
4
|
"all/copy-contents/.gitattributes": "9d3831007e681186a3673e1037ef3fc82980cab2fc04e27c0868e562912c9e9f",
|
|
5
5
|
"all/copy-contents/gitignore": "2dbf7fd2f2020fc7824c432342002d9ca3ebb57b2872e761b14e942b23479a11",
|
|
6
|
-
"all/copy-overwrite/scripts/lisa-enforcement-fallback.sh": "
|
|
6
|
+
"all/copy-overwrite/scripts/lisa-enforcement-fallback.sh": "d7d88e44763694bed5eae998cd3663922c957e49f9f9621d9201f0417a4128ad",
|
|
7
7
|
"all/copy-overwrite/scripts/lisa-floor-collisions.mjs": "a612f172282d13ba9318fe5e03689d7c6ff42a0122d0c9d5d39051e1967b93dc",
|
|
8
8
|
"all/copy-overwrite/scripts/lisa-hooks/block-instruction-file-edits.sh": "8996e0bcbf1db085a5d99734e797c91f5025997bd967bc374efff8348dac14c2",
|
|
9
9
|
"all/copy-overwrite/scripts/lisa-hooks/block-no-verify.sh": "a6ed91576efebb6ba40cfa4e9d8a3e8566314909210ae8d5860be62a3feb4cff",
|
|
@@ -1008,7 +1008,7 @@ export const UPSTREAM_EVIDENCE_MANIFEST = Object.freeze({
|
|
|
1008
1008
|
"scripts/lib/reusable-workflow-contract.d.mts": "791f01b55dd7a6b5d9a5f4cb9c44167caa146c2fc3c31a2ae4c2d8a350adc2f1",
|
|
1009
1009
|
"scripts/lib/reusable-workflow-contract.mjs": "134ee2a327290f066f1eb318b5ed53c711557c3e10ed462c00ff5c97cfb20863",
|
|
1010
1010
|
"scripts/lisa-commit-and-pr-local.sh": "605409c3ce6ec38ad3275604291a1ceae98f7807a605654263bc14f811c03903",
|
|
1011
|
-
"scripts/lisa-enforcement-fallback.sh": "
|
|
1011
|
+
"scripts/lisa-enforcement-fallback.sh": "d7d88e44763694bed5eae998cd3663922c957e49f9f9621d9201f0417a4128ad",
|
|
1012
1012
|
"scripts/lisa-github-environments.sh": "0a76e92f108519abaf3e29991299ec3b0db20ea533e69e6d2a53d802dba9c370",
|
|
1013
1013
|
"scripts/lisa-github-repo-settings.sh": "4afbccdfb08c62ba13afee42ec8561a28facf87c61f6f4b80000115328364d54",
|
|
1014
1014
|
"scripts/lisa-github-repo-setup.sh": "dc2f1c9d718aa34ba57161120d9319b5f78fe6b0b496d8e3c77226a08795aa36",
|
package/package.json
CHANGED
|
@@ -115,7 +115,7 @@
|
|
|
115
115
|
"brace-expansion": ">=5.0.9"
|
|
116
116
|
},
|
|
117
117
|
"name": "@codyswann/lisa",
|
|
118
|
-
"version": "2.
|
|
118
|
+
"version": "2.335.0",
|
|
119
119
|
"description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
|
|
120
120
|
"main": "dist/index.js",
|
|
121
121
|
"exports": {
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "lisa-openclaw",
|
|
3
|
-
"version": "2.
|
|
3
|
+
"version": "2.335.0",
|
|
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": "2.
|
|
3
|
+
"version": "2.335.0",
|
|
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": "2.
|
|
3
|
+
"version": "2.335.0",
|
|
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": "2.
|
|
3
|
+
"version": "2.335.0",
|
|
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": "2.
|
|
3
|
+
"version": "2.335.0",
|
|
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"
|
|
@@ -24,16 +24,39 @@ payload="$(cat)"
|
|
|
24
24
|
repo_root="${CLAUDE_PROJECT_DIR:-$(git rev-parse --show-toplevel 2>/dev/null)}"
|
|
25
25
|
[ -n "$repo_root" ] || exit 0
|
|
26
26
|
|
|
27
|
-
#
|
|
28
|
-
# guard twice and print every refusal twice. Absence is the interesting case and
|
|
29
|
-
# the only one this exists for.
|
|
27
|
+
# There is deliberately no skip here, and that is the whole point.
|
|
30
28
|
#
|
|
31
|
-
#
|
|
32
|
-
#
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
29
|
+
# This used to stand down when `installed_plugins.json` mentioned `lisa@lisa`,
|
|
30
|
+
# to avoid running every guard twice on a developer machine. The question that
|
|
31
|
+
# has to be answered is "are the plugin's guards running in this session?" and
|
|
32
|
+
# the file being consulted answers "has this plugin ever been installed, for any
|
|
33
|
+
# project, on this machine?". Those come apart three ways, and in each one both
|
|
34
|
+
# layers were off:
|
|
35
|
+
#
|
|
36
|
+
# - Project-blind. The registry is keyed by plugin with an array of per-project
|
|
37
|
+
# entries, so the grep matched the key. One project installing Lisa disabled
|
|
38
|
+
# the fallback for every other project on the machine.
|
|
39
|
+
# - Enablement-blind. `enabledPlugins` can set a plugin to false without
|
|
40
|
+
# removing its registry entry, so the plugin guards were off while this file
|
|
41
|
+
# believed they were on.
|
|
42
|
+
# - Session-blind. Hooks load at session start; the registry is written on any
|
|
43
|
+
# install or update. A plugin updated four minutes into a session leaves the
|
|
44
|
+
# registry saying "installed" for the rest of it, with no plugin hooks
|
|
45
|
+
# loaded. That is the one that was caught in the wild: a write to AGENTS.md
|
|
46
|
+
# went through in a session where both guard copies exit 2 for that exact
|
|
47
|
+
# payload.
|
|
48
|
+
#
|
|
49
|
+
# The first two are fixable with a better lookup. The third is not: plugin-hook
|
|
50
|
+
# liveness is not observable from a repository hook. CLAUDE_PLUGIN_ROOT is set
|
|
51
|
+
# only for plugin hooks, and nothing on disk distinguishes "registered" from
|
|
52
|
+
# "loaded into this session". Any check against a file answers a different
|
|
53
|
+
# question and will drift from the real one again.
|
|
54
|
+
#
|
|
55
|
+
# So the guards run unconditionally. On a machine where the plugin hooks are also
|
|
56
|
+
# live that costs a duplicated sweep (~170ms) and a refusal printed twice, and
|
|
57
|
+
# that is the correct trade against enforcement silently switching itself off.
|
|
58
|
+
# Recovering it belongs in the guards — a marker keyed on session and payload, so
|
|
59
|
+
# whichever layer fires first does the work — not in a liveness guess here.
|
|
37
60
|
|
|
38
61
|
# Where the guards live depends on which repository this is.
|
|
39
62
|
#
|