@codyswann/lisa 2.79.0 → 2.80.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/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/skills/doctor/SKILL.md +38 -0
- package/plugins/lisa-cdk/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-cdk/.codex-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-harper-fabric/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-harper-fabric/.codex-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-openclaw/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-openclaw/.codex-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-typescript/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-typescript/.codex-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/src/base/skills/doctor/SKILL.md +38 -0
package/package.json
CHANGED
|
@@ -82,7 +82,7 @@
|
|
|
82
82
|
"lodash": ">=4.18.1"
|
|
83
83
|
},
|
|
84
84
|
"name": "@codyswann/lisa",
|
|
85
|
-
"version": "2.
|
|
85
|
+
"version": "2.80.0",
|
|
86
86
|
"description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
|
|
87
87
|
"main": "dist/index.js",
|
|
88
88
|
"exports": {
|
|
@@ -234,6 +234,44 @@ edit, delete, or reconcile automations on the default doctor path.
|
|
|
234
234
|
- `FAIL` when the repo's config cannot resolve the queue that an automation needs, because that
|
|
235
235
|
would make unattended runs ambiguous or broken before scheduling even starts.
|
|
236
236
|
|
|
237
|
+
### Minimum wiki-delegation checks
|
|
238
|
+
|
|
239
|
+
When a repo-local `wiki/` directory exists, doctor must surface the specialized wiki-readiness path
|
|
240
|
+
without turning the base doctor into a second `lisa-wiki-doctor`.
|
|
241
|
+
|
|
242
|
+
1. **Detect whether wiki delegation applies**
|
|
243
|
+
- If no repo-local `wiki/` directory exists, report the entire wiki group as `SKIP` with the
|
|
244
|
+
reason that no wiki surface is present in this repository.
|
|
245
|
+
- If `wiki/` exists, keep the group present in the final report; do not silently omit it.
|
|
246
|
+
2. **Prefer summary of an existing specialized verdict**
|
|
247
|
+
- If the repo already has a readable `wiki/state/migration/doctor-report.json`, doctor may
|
|
248
|
+
summarize the specialized verdict (`READY`, `READY_WITH_WARNINGS`, or `NOT_READY`) plus the
|
|
249
|
+
most relevant blocking/warning facts, clearly attributing them to `lisa-wiki-doctor`.
|
|
250
|
+
- Preserve the base doctor's narrower scope: summarize or quote the specialized verdict, but do
|
|
251
|
+
not inline the full migration/readiness checklist into the base doctor output.
|
|
252
|
+
3. **Otherwise advertise the deeper follow-up explicitly**
|
|
253
|
+
- If `wiki/` exists but no specialized report is available yet, doctor must still tell the
|
|
254
|
+
operator that deeper wiki checks live behind `lisa-wiki-doctor`.
|
|
255
|
+
- The report should make the next action explicit, for example:
|
|
256
|
+
|
|
257
|
+
```text
|
|
258
|
+
WARN wiki-follow-up: wiki/ detected; deeper wiki migration checks not yet summarized
|
|
259
|
+
Observed: wiki/ exists, but no wiki/state/migration/doctor-report.json was found.
|
|
260
|
+
Remediation: run lisa-wiki-doctor to produce the wiki-specific readiness verdict.
|
|
261
|
+
```
|
|
262
|
+
4. **Severity ladder**
|
|
263
|
+
- `SKIP` when `wiki/` is absent.
|
|
264
|
+
- `PASS` when `wiki/` exists and doctor successfully summarizes an existing
|
|
265
|
+
`lisa-wiki-doctor` verdict.
|
|
266
|
+
- `WARN` when `wiki/` exists and doctor can only advertise the specialized follow-up because no
|
|
267
|
+
persisted wiki verdict is available yet.
|
|
268
|
+
- `FAIL` only when `wiki/` exists but the repo cannot surface the specialized follow-up at all
|
|
269
|
+
(for example, the required `lisa-wiki-doctor` distribution surface is missing or the existing
|
|
270
|
+
report is unreadable/malformed enough that doctor cannot safely summarize it).
|
|
271
|
+
5. **Keep wiki readiness optional for non-wiki repos**
|
|
272
|
+
- Never require a wiki plugin surface when `wiki/` is absent.
|
|
273
|
+
- Never let wiki-specific checks downgrade unrelated non-wiki repositories.
|
|
274
|
+
|
|
237
275
|
## Output contract
|
|
238
276
|
|
|
239
277
|
The final report must:
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "lisa-openclaw",
|
|
3
|
-
"version": "2.
|
|
3
|
+
"version": "2.80.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.80.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"
|
|
@@ -234,6 +234,44 @@ edit, delete, or reconcile automations on the default doctor path.
|
|
|
234
234
|
- `FAIL` when the repo's config cannot resolve the queue that an automation needs, because that
|
|
235
235
|
would make unattended runs ambiguous or broken before scheduling even starts.
|
|
236
236
|
|
|
237
|
+
### Minimum wiki-delegation checks
|
|
238
|
+
|
|
239
|
+
When a repo-local `wiki/` directory exists, doctor must surface the specialized wiki-readiness path
|
|
240
|
+
without turning the base doctor into a second `lisa-wiki-doctor`.
|
|
241
|
+
|
|
242
|
+
1. **Detect whether wiki delegation applies**
|
|
243
|
+
- If no repo-local `wiki/` directory exists, report the entire wiki group as `SKIP` with the
|
|
244
|
+
reason that no wiki surface is present in this repository.
|
|
245
|
+
- If `wiki/` exists, keep the group present in the final report; do not silently omit it.
|
|
246
|
+
2. **Prefer summary of an existing specialized verdict**
|
|
247
|
+
- If the repo already has a readable `wiki/state/migration/doctor-report.json`, doctor may
|
|
248
|
+
summarize the specialized verdict (`READY`, `READY_WITH_WARNINGS`, or `NOT_READY`) plus the
|
|
249
|
+
most relevant blocking/warning facts, clearly attributing them to `lisa-wiki-doctor`.
|
|
250
|
+
- Preserve the base doctor's narrower scope: summarize or quote the specialized verdict, but do
|
|
251
|
+
not inline the full migration/readiness checklist into the base doctor output.
|
|
252
|
+
3. **Otherwise advertise the deeper follow-up explicitly**
|
|
253
|
+
- If `wiki/` exists but no specialized report is available yet, doctor must still tell the
|
|
254
|
+
operator that deeper wiki checks live behind `lisa-wiki-doctor`.
|
|
255
|
+
- The report should make the next action explicit, for example:
|
|
256
|
+
|
|
257
|
+
```text
|
|
258
|
+
WARN wiki-follow-up: wiki/ detected; deeper wiki migration checks not yet summarized
|
|
259
|
+
Observed: wiki/ exists, but no wiki/state/migration/doctor-report.json was found.
|
|
260
|
+
Remediation: run lisa-wiki-doctor to produce the wiki-specific readiness verdict.
|
|
261
|
+
```
|
|
262
|
+
4. **Severity ladder**
|
|
263
|
+
- `SKIP` when `wiki/` is absent.
|
|
264
|
+
- `PASS` when `wiki/` exists and doctor successfully summarizes an existing
|
|
265
|
+
`lisa-wiki-doctor` verdict.
|
|
266
|
+
- `WARN` when `wiki/` exists and doctor can only advertise the specialized follow-up because no
|
|
267
|
+
persisted wiki verdict is available yet.
|
|
268
|
+
- `FAIL` only when `wiki/` exists but the repo cannot surface the specialized follow-up at all
|
|
269
|
+
(for example, the required `lisa-wiki-doctor` distribution surface is missing or the existing
|
|
270
|
+
report is unreadable/malformed enough that doctor cannot safely summarize it).
|
|
271
|
+
5. **Keep wiki readiness optional for non-wiki repos**
|
|
272
|
+
- Never require a wiki plugin surface when `wiki/` is absent.
|
|
273
|
+
- Never let wiki-specific checks downgrade unrelated non-wiki repositories.
|
|
274
|
+
|
|
237
275
|
## Output contract
|
|
238
276
|
|
|
239
277
|
The final report must:
|