@codyswann/lisa 2.220.1 → 2.221.1
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/dist/core/config.d.ts +1 -1
- package/dist/core/instruction-files-migration.d.ts +28 -0
- package/dist/core/instruction-files-migration.d.ts.map +1 -1
- package/dist/core/instruction-files-migration.js +116 -6
- package/dist/core/instruction-files-migration.js.map +1 -1
- package/dist/core/lisa.d.ts +6 -5
- package/dist/core/lisa.d.ts.map +1 -1
- package/dist/core/lisa.js +8 -6
- package/dist/core/lisa.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/.codex-plugin/skills/lisa-github-read-issue/SKILL.md +59 -4
- package/plugins/lisa/rules/eager/project-learnings.md +15 -0
- package/plugins/lisa/rules/reference/project-learnings.md +37 -0
- package/plugins/lisa/skills/lisa-github-read-issue/SKILL.md +59 -4
- package/plugins/lisa-agy/plugin.json +1 -1
- package/plugins/lisa-agy/skills/lisa-github-read-issue/SKILL.md +59 -4
- 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/rules/eager/project-learnings.md +15 -0
- package/plugins/lisa-copilot/rules/reference/project-learnings.md +37 -0
- package/plugins/lisa-copilot/skills/lisa-github-read-issue/SKILL.md +59 -4
- package/plugins/lisa-cursor/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-cursor/rules/project-learnings-reference.mdc +42 -0
- package/plugins/lisa-cursor/rules/project-learnings.mdc +20 -0
- package/plugins/lisa-cursor/skills/lisa-github-read-issue/SKILL.md +59 -4
- 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/rules/eager/project-learnings.md +15 -0
- package/plugins/src/base/rules/reference/project-learnings.md +37 -0
- package/plugins/src/base/skills/lisa-github-read-issue/SKILL.md +59 -4
- package/scripts/generate-agy-plugin-artifacts.mjs +4 -3
- package/scripts/lib/per-agent-hook-filter.mjs +2 -2
|
@@ -139,15 +139,64 @@ If the primary issue has a parent sub-issue (i.e., is a Story / Task / Sub-task
|
|
|
139
139
|
|
|
140
140
|
If the primary issue IS an Epic, capture all children via Phase 3's `subIssues` traversal (already done).
|
|
141
141
|
|
|
142
|
-
## Phase 6 — Fetch Linked PRs
|
|
142
|
+
## Phase 6 — Fetch Linked PRs and Label-Event History
|
|
143
143
|
|
|
144
|
-
GitHub's native `closingIssuesReferences` and timeline give the canonical PR↔Issue relationship
|
|
144
|
+
GitHub's native `closingIssuesReferences` and timeline give the canonical PR↔Issue relationship. The same timeline read also exposes label events, which are Lisa's GitHub-native transition history. Keep this as one GraphQL read path; do not add a second REST timeline fetch.
|
|
145
145
|
|
|
146
146
|
```bash
|
|
147
|
-
|
|
147
|
+
query='query($org:String!,$repo:String!,$number:Int!,$cursor:String){
|
|
148
|
+
repository(owner:$org,name:$repo){
|
|
149
|
+
issue(number:$number){
|
|
150
|
+
closedByPullRequestsReferences(first:50){
|
|
151
|
+
nodes{number title state merged mergedAt url repository{nameWithOwner}}
|
|
152
|
+
}
|
|
153
|
+
timelineItems(
|
|
154
|
+
first:100
|
|
155
|
+
after:$cursor
|
|
156
|
+
itemTypes:[CROSS_REFERENCED_EVENT,LABELED_EVENT,UNLABELED_EVENT]
|
|
157
|
+
){
|
|
158
|
+
pageInfo{hasNextPage endCursor}
|
|
159
|
+
nodes{
|
|
160
|
+
...on CrossReferencedEvent{
|
|
161
|
+
createdAt
|
|
162
|
+
actor{login}
|
|
163
|
+
source{...on PullRequest{number title state url repository{nameWithOwner}}}
|
|
164
|
+
}
|
|
165
|
+
...on LabeledEvent{
|
|
166
|
+
createdAt
|
|
167
|
+
actor{login}
|
|
168
|
+
label{name}
|
|
169
|
+
}
|
|
170
|
+
...on UnlabeledEvent{
|
|
171
|
+
createdAt
|
|
172
|
+
actor{login}
|
|
173
|
+
label{name}
|
|
174
|
+
}
|
|
175
|
+
}
|
|
176
|
+
}
|
|
177
|
+
}
|
|
178
|
+
}
|
|
179
|
+
}'
|
|
180
|
+
|
|
181
|
+
cursor=null
|
|
182
|
+
while :; do
|
|
183
|
+
if [ "$cursor" = null ]; then
|
|
184
|
+
page=$(gh api graphql -f query="$query" -F org=<org> -F repo=<repo> -F number=<number>)
|
|
185
|
+
else
|
|
186
|
+
page=$(gh api graphql -f query="$query" -F org=<org> -F repo=<repo> -F number=<number> -f cursor="$cursor")
|
|
187
|
+
fi
|
|
188
|
+
printf '%s\n' "$page"
|
|
189
|
+
has_next=$(printf '%s\n' "$page" | jq -r '.data.repository.issue.timelineItems.pageInfo.hasNextPage')
|
|
190
|
+
cursor=$(printf '%s\n' "$page" | jq -r '.data.repository.issue.timelineItems.pageInfo.endCursor')
|
|
191
|
+
[ "$has_next" = true ] || break
|
|
192
|
+
done
|
|
148
193
|
```
|
|
149
194
|
|
|
150
|
-
Capture:
|
|
195
|
+
Capture:
|
|
196
|
+
- **Linked PRs**: PR number, title, state, mergedAt, repo, url. Dedupe with PRs found in Phase 4. Preserve the existing `CrossReferencedEvent` behavior for PR linkage; widening the query must not change that consumer shape.
|
|
197
|
+
- **Label-event history**: chronological `LabeledEvent` and `UnlabeledEvent` entries with event kind, label name, actor login, and `createdAt`. Preserve oldest→newest order across all pages. Status labels (`status:*`) are the GitHub transition history that downstream rejection detection consumes, but keep non-status label events too so callers can audit the full label stream.
|
|
198
|
+
|
|
199
|
+
Pagination is mandatory. `timelineItems(first:100)` silently truncates busy issues unless `pageInfo.hasNextPage` / `endCursor` is followed. If a page fetch fails, record label-event history as `unknown` with the error and continue assembling the bundle; a history read failure must never block the build.
|
|
151
200
|
|
|
152
201
|
For each PR, fetch unresolved review comments via `gh pr view <num> --repo <org>/<repo> --json reviews,reviewThreads`.
|
|
153
202
|
|
|
@@ -227,6 +276,12 @@ Produce a single structured output that the caller can pass verbatim to downstre
|
|
|
227
276
|
### Body-referenced (`Resolves #<n>`)
|
|
228
277
|
<per-PR block>
|
|
229
278
|
|
|
279
|
+
## Label-Event History
|
|
280
|
+
- Status: <known|unknown>
|
|
281
|
+
- Events:
|
|
282
|
+
- <ISO> — <labeled|unlabeled> — <label-name> — <actor-login>
|
|
283
|
+
- ...
|
|
284
|
+
|
|
230
285
|
## Sibling Sub-issues (other children of the same parent, <count>)
|
|
231
286
|
- <ref> — <type> — <status> — <assignee> — <title> **[FLAG: in progress by other assignee]**
|
|
232
287
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "lisa-openclaw",
|
|
3
|
-
"version": "2.
|
|
3
|
+
"version": "2.221.1",
|
|
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.221.1",
|
|
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.221.1",
|
|
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.221.1",
|
|
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.221.1",
|
|
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"
|
|
@@ -0,0 +1,15 @@
|
|
|
1
|
+
# Project Learnings (load-bearing)
|
|
2
|
+
|
|
3
|
+
Before normal task work, resolve this repository's committed `.lisa.config.json`
|
|
4
|
+
and derive the canonical learnings file as the sibling of `projectRulesFile`
|
|
5
|
+
(default: `.claude/rules/PROJECT_LEARNINGS.md`). If that file exists, consume it
|
|
6
|
+
through the executable Lisa learnings contract exported by
|
|
7
|
+
`@codyswann/lisa/learnings` before relying on ad-hoc memory or prior-session
|
|
8
|
+
notes.
|
|
9
|
+
|
|
10
|
+
Missing learnings are a silent no-op. Malformed, non-canonical, unsafe, or
|
|
11
|
+
over-budget learnings produce one readable warning, apply no entry, and must not
|
|
12
|
+
block unrelated task work. Never append automated learnings to
|
|
13
|
+
`PROJECT_RULES.md`; project learnings are a separate machine-managed document.
|
|
14
|
+
|
|
15
|
+
Full prose: [reference/project-learnings.md](../reference/project-learnings.md).
|
|
@@ -0,0 +1,37 @@
|
|
|
1
|
+
# Project Learnings
|
|
2
|
+
|
|
3
|
+
Project learnings are Lisa's bounded, repo-local memory surface. They are stored
|
|
4
|
+
in `PROJECT_LEARNINGS.md`, derived as the sibling of the configured
|
|
5
|
+
`.lisa.config.json` `projectRulesFile` value. With no config override, the path
|
|
6
|
+
is `.claude/rules/PROJECT_LEARNINGS.md`.
|
|
7
|
+
|
|
8
|
+
Consume learnings before normal task work whenever the file exists. Use the
|
|
9
|
+
executable contract from `@codyswann/lisa/learnings` to parse, validate, and
|
|
10
|
+
budget-check the document. Do not duplicate numeric caps in rules or prompts;
|
|
11
|
+
the exported contract is the source of truth.
|
|
12
|
+
|
|
13
|
+
Each persisted entry has seven fields:
|
|
14
|
+
|
|
15
|
+
- `id`
|
|
16
|
+
- `rule`
|
|
17
|
+
- `why`
|
|
18
|
+
- `provenance`
|
|
19
|
+
- `first_learned`
|
|
20
|
+
- `last_confirmed`
|
|
21
|
+
- `confidence`
|
|
22
|
+
|
|
23
|
+
Only entries accepted by the executable contract may influence the session. A
|
|
24
|
+
missing file is expected and silent. Malformed Markdown, invalid JSONL, unsafe
|
|
25
|
+
paths, non-canonical content, or over-budget documents produce one readable
|
|
26
|
+
warning, apply no entry, and do not block unrelated work.
|
|
27
|
+
|
|
28
|
+
Precedence:
|
|
29
|
+
|
|
30
|
+
1. System, developer, user, and repo instructions still outrank learnings.
|
|
31
|
+
2. Committed project rules remain durable human-authored guidance.
|
|
32
|
+
3. Project learnings add recent operational knowledge, but never rewrite or
|
|
33
|
+
append to `PROJECT_RULES.md`.
|
|
34
|
+
|
|
35
|
+
Antigravity note: agy does not receive the plugin `rules/` tree. Lisa reconciles
|
|
36
|
+
a bounded `AGENTS.md` bridge that points agy at this same file without copying
|
|
37
|
+
learning bodies or restoring the retired full rules bake.
|
|
@@ -139,15 +139,64 @@ If the primary issue has a parent sub-issue (i.e., is a Story / Task / Sub-task
|
|
|
139
139
|
|
|
140
140
|
If the primary issue IS an Epic, capture all children via Phase 3's `subIssues` traversal (already done).
|
|
141
141
|
|
|
142
|
-
## Phase 6 — Fetch Linked PRs
|
|
142
|
+
## Phase 6 — Fetch Linked PRs and Label-Event History
|
|
143
143
|
|
|
144
|
-
GitHub's native `closingIssuesReferences` and timeline give the canonical PR↔Issue relationship
|
|
144
|
+
GitHub's native `closingIssuesReferences` and timeline give the canonical PR↔Issue relationship. The same timeline read also exposes label events, which are Lisa's GitHub-native transition history. Keep this as one GraphQL read path; do not add a second REST timeline fetch.
|
|
145
145
|
|
|
146
146
|
```bash
|
|
147
|
-
|
|
147
|
+
query='query($org:String!,$repo:String!,$number:Int!,$cursor:String){
|
|
148
|
+
repository(owner:$org,name:$repo){
|
|
149
|
+
issue(number:$number){
|
|
150
|
+
closedByPullRequestsReferences(first:50){
|
|
151
|
+
nodes{number title state merged mergedAt url repository{nameWithOwner}}
|
|
152
|
+
}
|
|
153
|
+
timelineItems(
|
|
154
|
+
first:100
|
|
155
|
+
after:$cursor
|
|
156
|
+
itemTypes:[CROSS_REFERENCED_EVENT,LABELED_EVENT,UNLABELED_EVENT]
|
|
157
|
+
){
|
|
158
|
+
pageInfo{hasNextPage endCursor}
|
|
159
|
+
nodes{
|
|
160
|
+
...on CrossReferencedEvent{
|
|
161
|
+
createdAt
|
|
162
|
+
actor{login}
|
|
163
|
+
source{...on PullRequest{number title state url repository{nameWithOwner}}}
|
|
164
|
+
}
|
|
165
|
+
...on LabeledEvent{
|
|
166
|
+
createdAt
|
|
167
|
+
actor{login}
|
|
168
|
+
label{name}
|
|
169
|
+
}
|
|
170
|
+
...on UnlabeledEvent{
|
|
171
|
+
createdAt
|
|
172
|
+
actor{login}
|
|
173
|
+
label{name}
|
|
174
|
+
}
|
|
175
|
+
}
|
|
176
|
+
}
|
|
177
|
+
}
|
|
178
|
+
}
|
|
179
|
+
}'
|
|
180
|
+
|
|
181
|
+
cursor=null
|
|
182
|
+
while :; do
|
|
183
|
+
if [ "$cursor" = null ]; then
|
|
184
|
+
page=$(gh api graphql -f query="$query" -F org=<org> -F repo=<repo> -F number=<number>)
|
|
185
|
+
else
|
|
186
|
+
page=$(gh api graphql -f query="$query" -F org=<org> -F repo=<repo> -F number=<number> -f cursor="$cursor")
|
|
187
|
+
fi
|
|
188
|
+
printf '%s\n' "$page"
|
|
189
|
+
has_next=$(printf '%s\n' "$page" | jq -r '.data.repository.issue.timelineItems.pageInfo.hasNextPage')
|
|
190
|
+
cursor=$(printf '%s\n' "$page" | jq -r '.data.repository.issue.timelineItems.pageInfo.endCursor')
|
|
191
|
+
[ "$has_next" = true ] || break
|
|
192
|
+
done
|
|
148
193
|
```
|
|
149
194
|
|
|
150
|
-
Capture:
|
|
195
|
+
Capture:
|
|
196
|
+
- **Linked PRs**: PR number, title, state, mergedAt, repo, url. Dedupe with PRs found in Phase 4. Preserve the existing `CrossReferencedEvent` behavior for PR linkage; widening the query must not change that consumer shape.
|
|
197
|
+
- **Label-event history**: chronological `LabeledEvent` and `UnlabeledEvent` entries with event kind, label name, actor login, and `createdAt`. Preserve oldest→newest order across all pages. Status labels (`status:*`) are the GitHub transition history that downstream rejection detection consumes, but keep non-status label events too so callers can audit the full label stream.
|
|
198
|
+
|
|
199
|
+
Pagination is mandatory. `timelineItems(first:100)` silently truncates busy issues unless `pageInfo.hasNextPage` / `endCursor` is followed. If a page fetch fails, record label-event history as `unknown` with the error and continue assembling the bundle; a history read failure must never block the build.
|
|
151
200
|
|
|
152
201
|
For each PR, fetch unresolved review comments via `gh pr view <num> --repo <org>/<repo> --json reviews,reviewThreads`.
|
|
153
202
|
|
|
@@ -227,6 +276,12 @@ Produce a single structured output that the caller can pass verbatim to downstre
|
|
|
227
276
|
### Body-referenced (`Resolves #<n>`)
|
|
228
277
|
<per-PR block>
|
|
229
278
|
|
|
279
|
+
## Label-Event History
|
|
280
|
+
- Status: <known|unknown>
|
|
281
|
+
- Events:
|
|
282
|
+
- <ISO> — <labeled|unlabeled> — <label-name> — <actor-login>
|
|
283
|
+
- ...
|
|
284
|
+
|
|
230
285
|
## Sibling Sub-issues (other children of the same parent, <count>)
|
|
231
286
|
- <ref> — <type> — <status> — <assignee> — <title> **[FLAG: in progress by other assignee]**
|
|
232
287
|
|
|
@@ -25,7 +25,8 @@
|
|
|
25
25
|
* MCP (user-global, NOT plugin-bundled): agy ignores plugin-bundled MCP and only
|
|
26
26
|
* reads the user-global `~/.gemini/config/mcp_config.json`, so MCP is delivered
|
|
27
27
|
* by the runtime installer (`src/agy/mcp-installer.ts`), and this generator
|
|
28
|
-
* drops `.mcp.json`. Rules
|
|
28
|
+
* drops `.mcp.json`. Rules remain out of agy artifacts; the runtime reconciles
|
|
29
|
+
* only a bounded AGENTS.md project-learnings bridge.
|
|
29
30
|
*
|
|
30
31
|
* Net: the agy variant ships a root `hooks.json` (base only) + its agy-protocol
|
|
31
32
|
* script under `hooks/`, but NO `mcp_config.json`, NO `.mcp.json`, NO `rules/`,
|
|
@@ -132,7 +133,7 @@ export function generateAgyVariant(srcDir, outDir, version) {
|
|
|
132
133
|
// hooks.json (root) + the agy-protocol script are re-emitted by
|
|
133
134
|
// emitAgyPluginHooks below.
|
|
134
135
|
if (relPath.startsWith("hooks/") || relPath === "hooks") return false;
|
|
135
|
-
if (relPath.startsWith("rules/") || relPath === "rules") return false; // rules
|
|
136
|
+
if (relPath.startsWith("rules/") || relPath === "rules") return false; // no full rules tree in agy artifacts
|
|
136
137
|
// Drop the untranslated Claude .mcp.json — agy ignores it (and the agy
|
|
137
138
|
// MCP shape differs); MCP is delivered by the user-global runtime MCP installer.
|
|
138
139
|
if (relPath === ".mcp.json") return false;
|
|
@@ -206,7 +207,7 @@ export function generateAgyVariant(srcDir, outDir, version) {
|
|
|
206
207
|
* agy-protocol script copied into the variant's hooks/ and referenced by the
|
|
207
208
|
* command. NOTE: install-pkgs / setup-jira-cli are SessionStart-only, which agy
|
|
208
209
|
* hooks don't support, so they are intentionally absent. inject-rules is absent
|
|
209
|
-
* too (rules
|
|
210
|
+
* too (rules stay out of agy artifacts).
|
|
210
211
|
*/
|
|
211
212
|
const AGY_PLUGIN_HOOKS = [
|
|
212
213
|
{
|