@codyswann/lisa 3.54.7 → 3.55.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-hooks/sonar-secrets.sh +16 -1
- package/dist/core/lisa-owned-hash-ledger.d.ts.map +1 -1
- package/dist/core/lisa-owned-hash-ledger.js +1 -0
- package/dist/core/lisa-owned-hash-ledger.js.map +1 -1
- package/dist/core/upstream-evidence-manifest.d.ts.map +1 -1
- package/dist/core/upstream-evidence-manifest.js +4 -2
- package/dist/core/upstream-evidence-manifest.js.map +1 -1
- 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/hooks/sonar-secrets.sh +16 -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/sonar-secrets.sh +16 -1
- package/plugins/lisa-cursor/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-cursor/hooks/sonar-secrets.sh +16 -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/sonar-secrets.sh +16 -1
package/package.json
CHANGED
|
@@ -141,7 +141,7 @@
|
|
|
141
141
|
"zod-validation-error": "^4.0.0"
|
|
142
142
|
},
|
|
143
143
|
"name": "@codyswann/lisa",
|
|
144
|
-
"version": "3.
|
|
144
|
+
"version": "3.55.0",
|
|
145
145
|
"description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
|
|
146
146
|
"main": "dist/index.js",
|
|
147
147
|
"exports": {
|
|
@@ -83,6 +83,21 @@ is_inactive() {
|
|
|
83
83
|
# portable form. A timeout leaves `value` empty, which the caller treats as "the
|
|
84
84
|
# provider had nothing" — the warn path, never a block.
|
|
85
85
|
#
|
|
86
|
+
# Ten seconds is the ceiling a consumer gets, and that is a product decision, not
|
|
87
|
+
# a tuning constant: this runs in front of every prompt and every file read, so
|
|
88
|
+
# it must not hang a session. `LISA_SONAR_RESOLVER_TIMEOUT_S` lets a caller that
|
|
89
|
+
# is NOT a session say so. The only caller that is not a session is this repo's
|
|
90
|
+
# own suite, where the "provider" is a local `node` script rather than a network
|
|
91
|
+
# call and the cost of starting it is unbounded under load — a spawn measured
|
|
92
|
+
# 45-50ms here at a 1-minute load average of 50, against an 18ms quiet figure,
|
|
93
|
+
# and the read lost its whole ten seconds to one at ~98 concurrent test workers
|
|
94
|
+
# (CodySwannGT/lisa#2905). The suite scales this the same way it scales its own
|
|
95
|
+
# budgets, and stages a hang by shrinking it.
|
|
96
|
+
#
|
|
97
|
+
# Unset, empty, or unparseable all end in the warn path: `:-10` covers the first
|
|
98
|
+
# two, and `read -t garbage` fails immediately, which leaves `value` empty. There
|
|
99
|
+
# is no value of this variable that turns a warn into a block.
|
|
100
|
+
#
|
|
86
101
|
# Giving up on the read is not the same as stopping the work: a resolver blocked
|
|
87
102
|
# on the network otherwise outlives the hook that started it, and this runs in
|
|
88
103
|
# front of every prompt and every file read. So the child is killed and reaped,
|
|
@@ -108,7 +123,7 @@ resolve_secret() {
|
|
|
108
123
|
fi
|
|
109
124
|
node "$resolver" get "$name" >"$fifo" 2>/dev/null &
|
|
110
125
|
child=$!
|
|
111
|
-
IFS= read -r -t 10 value < "$fifo" || true
|
|
126
|
+
IFS= read -r -t "${LISA_SONAR_RESOLVER_TIMEOUT_S:-10}" value < "$fifo" || true
|
|
112
127
|
kill -9 "$child" 2>/dev/null
|
|
113
128
|
wait "$child" 2>/dev/null
|
|
114
129
|
rm -rf "$dir"
|
|
@@ -83,6 +83,21 @@ is_inactive() {
|
|
|
83
83
|
# portable form. A timeout leaves `value` empty, which the caller treats as "the
|
|
84
84
|
# provider had nothing" — the warn path, never a block.
|
|
85
85
|
#
|
|
86
|
+
# Ten seconds is the ceiling a consumer gets, and that is a product decision, not
|
|
87
|
+
# a tuning constant: this runs in front of every prompt and every file read, so
|
|
88
|
+
# it must not hang a session. `LISA_SONAR_RESOLVER_TIMEOUT_S` lets a caller that
|
|
89
|
+
# is NOT a session say so. The only caller that is not a session is this repo's
|
|
90
|
+
# own suite, where the "provider" is a local `node` script rather than a network
|
|
91
|
+
# call and the cost of starting it is unbounded under load — a spawn measured
|
|
92
|
+
# 45-50ms here at a 1-minute load average of 50, against an 18ms quiet figure,
|
|
93
|
+
# and the read lost its whole ten seconds to one at ~98 concurrent test workers
|
|
94
|
+
# (CodySwannGT/lisa#2905). The suite scales this the same way it scales its own
|
|
95
|
+
# budgets, and stages a hang by shrinking it.
|
|
96
|
+
#
|
|
97
|
+
# Unset, empty, or unparseable all end in the warn path: `:-10` covers the first
|
|
98
|
+
# two, and `read -t garbage` fails immediately, which leaves `value` empty. There
|
|
99
|
+
# is no value of this variable that turns a warn into a block.
|
|
100
|
+
#
|
|
86
101
|
# Giving up on the read is not the same as stopping the work: a resolver blocked
|
|
87
102
|
# on the network otherwise outlives the hook that started it, and this runs in
|
|
88
103
|
# front of every prompt and every file read. So the child is killed and reaped,
|
|
@@ -108,7 +123,7 @@ resolve_secret() {
|
|
|
108
123
|
fi
|
|
109
124
|
node "$resolver" get "$name" >"$fifo" 2>/dev/null &
|
|
110
125
|
child=$!
|
|
111
|
-
IFS= read -r -t 10 value < "$fifo" || true
|
|
126
|
+
IFS= read -r -t "${LISA_SONAR_RESOLVER_TIMEOUT_S:-10}" value < "$fifo" || true
|
|
112
127
|
kill -9 "$child" 2>/dev/null
|
|
113
128
|
wait "$child" 2>/dev/null
|
|
114
129
|
rm -rf "$dir"
|
|
@@ -83,6 +83,21 @@ is_inactive() {
|
|
|
83
83
|
# portable form. A timeout leaves `value` empty, which the caller treats as "the
|
|
84
84
|
# provider had nothing" — the warn path, never a block.
|
|
85
85
|
#
|
|
86
|
+
# Ten seconds is the ceiling a consumer gets, and that is a product decision, not
|
|
87
|
+
# a tuning constant: this runs in front of every prompt and every file read, so
|
|
88
|
+
# it must not hang a session. `LISA_SONAR_RESOLVER_TIMEOUT_S` lets a caller that
|
|
89
|
+
# is NOT a session say so. The only caller that is not a session is this repo's
|
|
90
|
+
# own suite, where the "provider" is a local `node` script rather than a network
|
|
91
|
+
# call and the cost of starting it is unbounded under load — a spawn measured
|
|
92
|
+
# 45-50ms here at a 1-minute load average of 50, against an 18ms quiet figure,
|
|
93
|
+
# and the read lost its whole ten seconds to one at ~98 concurrent test workers
|
|
94
|
+
# (CodySwannGT/lisa#2905). The suite scales this the same way it scales its own
|
|
95
|
+
# budgets, and stages a hang by shrinking it.
|
|
96
|
+
#
|
|
97
|
+
# Unset, empty, or unparseable all end in the warn path: `:-10` covers the first
|
|
98
|
+
# two, and `read -t garbage` fails immediately, which leaves `value` empty. There
|
|
99
|
+
# is no value of this variable that turns a warn into a block.
|
|
100
|
+
#
|
|
86
101
|
# Giving up on the read is not the same as stopping the work: a resolver blocked
|
|
87
102
|
# on the network otherwise outlives the hook that started it, and this runs in
|
|
88
103
|
# front of every prompt and every file read. So the child is killed and reaped,
|
|
@@ -108,7 +123,7 @@ resolve_secret() {
|
|
|
108
123
|
fi
|
|
109
124
|
node "$resolver" get "$name" >"$fifo" 2>/dev/null &
|
|
110
125
|
child=$!
|
|
111
|
-
IFS= read -r -t 10 value < "$fifo" || true
|
|
126
|
+
IFS= read -r -t "${LISA_SONAR_RESOLVER_TIMEOUT_S:-10}" value < "$fifo" || true
|
|
112
127
|
kill -9 "$child" 2>/dev/null
|
|
113
128
|
wait "$child" 2>/dev/null
|
|
114
129
|
rm -rf "$dir"
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "lisa-openclaw",
|
|
3
|
-
"version": "3.
|
|
3
|
+
"version": "3.55.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": "3.
|
|
3
|
+
"version": "3.55.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": "3.
|
|
3
|
+
"version": "3.55.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": "3.
|
|
3
|
+
"version": "3.55.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": "3.
|
|
3
|
+
"version": "3.55.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"
|
|
@@ -83,6 +83,21 @@ is_inactive() {
|
|
|
83
83
|
# portable form. A timeout leaves `value` empty, which the caller treats as "the
|
|
84
84
|
# provider had nothing" — the warn path, never a block.
|
|
85
85
|
#
|
|
86
|
+
# Ten seconds is the ceiling a consumer gets, and that is a product decision, not
|
|
87
|
+
# a tuning constant: this runs in front of every prompt and every file read, so
|
|
88
|
+
# it must not hang a session. `LISA_SONAR_RESOLVER_TIMEOUT_S` lets a caller that
|
|
89
|
+
# is NOT a session say so. The only caller that is not a session is this repo's
|
|
90
|
+
# own suite, where the "provider" is a local `node` script rather than a network
|
|
91
|
+
# call and the cost of starting it is unbounded under load — a spawn measured
|
|
92
|
+
# 45-50ms here at a 1-minute load average of 50, against an 18ms quiet figure,
|
|
93
|
+
# and the read lost its whole ten seconds to one at ~98 concurrent test workers
|
|
94
|
+
# (CodySwannGT/lisa#2905). The suite scales this the same way it scales its own
|
|
95
|
+
# budgets, and stages a hang by shrinking it.
|
|
96
|
+
#
|
|
97
|
+
# Unset, empty, or unparseable all end in the warn path: `:-10` covers the first
|
|
98
|
+
# two, and `read -t garbage` fails immediately, which leaves `value` empty. There
|
|
99
|
+
# is no value of this variable that turns a warn into a block.
|
|
100
|
+
#
|
|
86
101
|
# Giving up on the read is not the same as stopping the work: a resolver blocked
|
|
87
102
|
# on the network otherwise outlives the hook that started it, and this runs in
|
|
88
103
|
# front of every prompt and every file read. So the child is killed and reaped,
|
|
@@ -108,7 +123,7 @@ resolve_secret() {
|
|
|
108
123
|
fi
|
|
109
124
|
node "$resolver" get "$name" >"$fifo" 2>/dev/null &
|
|
110
125
|
child=$!
|
|
111
|
-
IFS= read -r -t 10 value < "$fifo" || true
|
|
126
|
+
IFS= read -r -t "${LISA_SONAR_RESOLVER_TIMEOUT_S:-10}" value < "$fifo" || true
|
|
112
127
|
kill -9 "$child" 2>/dev/null
|
|
113
128
|
wait "$child" 2>/dev/null
|
|
114
129
|
rm -rf "$dir"
|