@codyswann/lisa 4.24.1 → 4.24.2
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/check-orphaned-branches.mjs +218 -0
- package/dist/core/lisa-owned-hash-ledger.d.ts.map +1 -1
- package/dist/core/lisa-owned-hash-ledger.js +8 -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 +7 -4
- package/dist/core/upstream-evidence-manifest.js.map +1 -1
- package/package.json +3 -3
- package/plugins/lisa/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa/.codex-plugin/skills/lisa-git-submit-pr/SKILL.md +12 -0
- package/plugins/lisa/skills/lisa-git-submit-pr/SKILL.md +12 -0
- package/plugins/lisa-agy/plugin.json +1 -1
- package/plugins/lisa-agy/skills/lisa-git-submit-pr/SKILL.md +12 -0
- 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/skills/lisa-git-submit-pr/SKILL.md +12 -0
- package/plugins/lisa-cursor/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-cursor/skills/lisa-git-submit-pr/SKILL.md +12 -0
- 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/skills/lisa-git-submit-pr/SKILL.md +12 -0
- package/scripts/check-security-floors.mjs +290 -31
- package/scripts/two-channel-couplings.json +1 -1
- package/typescript/copy-overwrite/.prettierignore +1 -0
package/package.json
CHANGED
|
@@ -161,7 +161,7 @@
|
|
|
161
161
|
"zod-validation-error": "^4.0.0"
|
|
162
162
|
},
|
|
163
163
|
"name": "@codyswann/lisa",
|
|
164
|
-
"version": "4.24.
|
|
164
|
+
"version": "4.24.2",
|
|
165
165
|
"description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
|
|
166
166
|
"main": "dist/index.js",
|
|
167
167
|
"exports": {
|
|
@@ -305,6 +305,6 @@
|
|
|
305
305
|
"test": "tests"
|
|
306
306
|
},
|
|
307
307
|
"types": "./dist/index.d.ts",
|
|
308
|
-
"lisaReleaseCommit": "
|
|
309
|
-
"gitHead": "
|
|
308
|
+
"lisaReleaseCommit": "ca9a7fb972dee21294edb5ec0901acbb3ad064ae",
|
|
309
|
+
"gitHead": "ca9a7fb972dee21294edb5ec0901acbb3ad064ae"
|
|
310
310
|
}
|
|
@@ -117,6 +117,18 @@ Include in the PR description:
|
|
|
117
117
|
- use `--force` push without explicit user request
|
|
118
118
|
- create PR from protected branches (dev, staging, main)
|
|
119
119
|
- skip pushing before PR creation
|
|
120
|
+
- **stop after pushing without creating the pull request.** A pushed branch with
|
|
121
|
+
no PR is an INCOMPLETE flow, not a stopping point: the work is in no review, no
|
|
122
|
+
CI run and no report, the work item keeps its in-progress role so intake will
|
|
123
|
+
not re-dispatch it, and the branch drifts from the base until someone notices.
|
|
124
|
+
Nothing else detects this state — the pre-push hook's `no pull request exists
|
|
125
|
+
yet, so gates 4 and 5 could not be checked here` is accurate and reads as an
|
|
126
|
+
informational pass, so the last signal received is green. Measured once the
|
|
127
|
+
check existed to look: 64 such branches in this repository, 15 of them from a
|
|
128
|
+
single day. **This flow terminates with a pull request or it has not
|
|
129
|
+
terminated.** If you cannot create one, say so explicitly rather than ending
|
|
130
|
+
quietly; `node scripts/check-orphaned-branches.mjs` lists branches in this
|
|
131
|
+
state.
|
|
120
132
|
|
|
121
133
|
## Execute
|
|
122
134
|
|
|
@@ -117,6 +117,18 @@ Include in the PR description:
|
|
|
117
117
|
- use `--force` push without explicit user request
|
|
118
118
|
- create PR from protected branches (dev, staging, main)
|
|
119
119
|
- skip pushing before PR creation
|
|
120
|
+
- **stop after pushing without creating the pull request.** A pushed branch with
|
|
121
|
+
no PR is an INCOMPLETE flow, not a stopping point: the work is in no review, no
|
|
122
|
+
CI run and no report, the work item keeps its in-progress role so intake will
|
|
123
|
+
not re-dispatch it, and the branch drifts from the base until someone notices.
|
|
124
|
+
Nothing else detects this state — the pre-push hook's `no pull request exists
|
|
125
|
+
yet, so gates 4 and 5 could not be checked here` is accurate and reads as an
|
|
126
|
+
informational pass, so the last signal received is green. Measured once the
|
|
127
|
+
check existed to look: 64 such branches in this repository, 15 of them from a
|
|
128
|
+
single day. **This flow terminates with a pull request or it has not
|
|
129
|
+
terminated.** If you cannot create one, say so explicitly rather than ending
|
|
130
|
+
quietly; `node scripts/check-orphaned-branches.mjs` lists branches in this
|
|
131
|
+
state.
|
|
120
132
|
|
|
121
133
|
## Execute
|
|
122
134
|
|
|
@@ -117,6 +117,18 @@ Include in the PR description:
|
|
|
117
117
|
- use `--force` push without explicit user request
|
|
118
118
|
- create PR from protected branches (dev, staging, main)
|
|
119
119
|
- skip pushing before PR creation
|
|
120
|
+
- **stop after pushing without creating the pull request.** A pushed branch with
|
|
121
|
+
no PR is an INCOMPLETE flow, not a stopping point: the work is in no review, no
|
|
122
|
+
CI run and no report, the work item keeps its in-progress role so intake will
|
|
123
|
+
not re-dispatch it, and the branch drifts from the base until someone notices.
|
|
124
|
+
Nothing else detects this state — the pre-push hook's `no pull request exists
|
|
125
|
+
yet, so gates 4 and 5 could not be checked here` is accurate and reads as an
|
|
126
|
+
informational pass, so the last signal received is green. Measured once the
|
|
127
|
+
check existed to look: 64 such branches in this repository, 15 of them from a
|
|
128
|
+
single day. **This flow terminates with a pull request or it has not
|
|
129
|
+
terminated.** If you cannot create one, say so explicitly rather than ending
|
|
130
|
+
quietly; `node scripts/check-orphaned-branches.mjs` lists branches in this
|
|
131
|
+
state.
|
|
120
132
|
|
|
121
133
|
## Execute
|
|
122
134
|
|
|
@@ -117,6 +117,18 @@ Include in the PR description:
|
|
|
117
117
|
- use `--force` push without explicit user request
|
|
118
118
|
- create PR from protected branches (dev, staging, main)
|
|
119
119
|
- skip pushing before PR creation
|
|
120
|
+
- **stop after pushing without creating the pull request.** A pushed branch with
|
|
121
|
+
no PR is an INCOMPLETE flow, not a stopping point: the work is in no review, no
|
|
122
|
+
CI run and no report, the work item keeps its in-progress role so intake will
|
|
123
|
+
not re-dispatch it, and the branch drifts from the base until someone notices.
|
|
124
|
+
Nothing else detects this state — the pre-push hook's `no pull request exists
|
|
125
|
+
yet, so gates 4 and 5 could not be checked here` is accurate and reads as an
|
|
126
|
+
informational pass, so the last signal received is green. Measured once the
|
|
127
|
+
check existed to look: 64 such branches in this repository, 15 of them from a
|
|
128
|
+
single day. **This flow terminates with a pull request or it has not
|
|
129
|
+
terminated.** If you cannot create one, say so explicitly rather than ending
|
|
130
|
+
quietly; `node scripts/check-orphaned-branches.mjs` lists branches in this
|
|
131
|
+
state.
|
|
120
132
|
|
|
121
133
|
## Execute
|
|
122
134
|
|
|
@@ -117,6 +117,18 @@ Include in the PR description:
|
|
|
117
117
|
- use `--force` push without explicit user request
|
|
118
118
|
- create PR from protected branches (dev, staging, main)
|
|
119
119
|
- skip pushing before PR creation
|
|
120
|
+
- **stop after pushing without creating the pull request.** A pushed branch with
|
|
121
|
+
no PR is an INCOMPLETE flow, not a stopping point: the work is in no review, no
|
|
122
|
+
CI run and no report, the work item keeps its in-progress role so intake will
|
|
123
|
+
not re-dispatch it, and the branch drifts from the base until someone notices.
|
|
124
|
+
Nothing else detects this state — the pre-push hook's `no pull request exists
|
|
125
|
+
yet, so gates 4 and 5 could not be checked here` is accurate and reads as an
|
|
126
|
+
informational pass, so the last signal received is green. Measured once the
|
|
127
|
+
check existed to look: 64 such branches in this repository, 15 of them from a
|
|
128
|
+
single day. **This flow terminates with a pull request or it has not
|
|
129
|
+
terminated.** If you cannot create one, say so explicitly rather than ending
|
|
130
|
+
quietly; `node scripts/check-orphaned-branches.mjs` lists branches in this
|
|
131
|
+
state.
|
|
120
132
|
|
|
121
133
|
## Execute
|
|
122
134
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "lisa-openclaw",
|
|
3
|
-
"version": "4.24.
|
|
3
|
+
"version": "4.24.2",
|
|
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.24.
|
|
3
|
+
"version": "4.24.2",
|
|
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.24.
|
|
3
|
+
"version": "4.24.2",
|
|
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.24.
|
|
3
|
+
"version": "4.24.2",
|
|
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.24.
|
|
3
|
+
"version": "4.24.2",
|
|
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"
|
|
@@ -117,6 +117,18 @@ Include in the PR description:
|
|
|
117
117
|
- use `--force` push without explicit user request
|
|
118
118
|
- create PR from protected branches (dev, staging, main)
|
|
119
119
|
- skip pushing before PR creation
|
|
120
|
+
- **stop after pushing without creating the pull request.** A pushed branch with
|
|
121
|
+
no PR is an INCOMPLETE flow, not a stopping point: the work is in no review, no
|
|
122
|
+
CI run and no report, the work item keeps its in-progress role so intake will
|
|
123
|
+
not re-dispatch it, and the branch drifts from the base until someone notices.
|
|
124
|
+
Nothing else detects this state — the pre-push hook's `no pull request exists
|
|
125
|
+
yet, so gates 4 and 5 could not be checked here` is accurate and reads as an
|
|
126
|
+
informational pass, so the last signal received is green. Measured once the
|
|
127
|
+
check existed to look: 64 such branches in this repository, 15 of them from a
|
|
128
|
+
single day. **This flow terminates with a pull request or it has not
|
|
129
|
+
terminated.** If you cannot create one, say so explicitly rather than ending
|
|
130
|
+
quietly; `node scripts/check-orphaned-branches.mjs` lists branches in this
|
|
131
|
+
state.
|
|
120
132
|
|
|
121
133
|
## Execute
|
|
122
134
|
|