@archme/cli 0.14.4 → 0.14.6
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/SKILL.md +4 -4
- package/dist/cli.js +9212 -9143
- package/package.json +1 -1
- package/sandbox-image.json +1 -1
package/SKILL.md
CHANGED
|
@@ -166,10 +166,10 @@ code + writes a proposal, exactly like a build sub-agent, and never touches the
|
|
|
166
166
|
user's code). Logging reuses the
|
|
167
167
|
proposals surface, not a bespoke mechanism: a prose-only proposal (empty graph
|
|
168
168
|
delta, `body` naming what's wrong, where by file:line/symbol, and why) under the
|
|
169
|
-
project's standing **"Bugs" folder**, `stage: 'backlog'` so it parks
|
|
170
|
-
triages. The daemon injects the
|
|
171
|
-
finds-or-creates it (`search_proposals({ kind: 'folder', text: 'Bugs' })`,
|
|
172
|
-
`create_proposal({ kind: 'folder', title: 'Bugs' })`). Dedup by searching the
|
|
169
|
+
project's standing **"Bugs found by ArchMe" folder**, `stage: 'backlog'` so it parks
|
|
170
|
+
until a human triages. The daemon injects the folder id for you; a manual scan
|
|
171
|
+
finds-or-creates it (`search_proposals({ kind: 'folder', text: 'Bugs found by ArchMe' })`,
|
|
172
|
+
else `create_proposal({ kind: 'folder', title: 'Bugs found by ArchMe' })`). Dedup by searching the
|
|
173
173
|
folder by title — the same standing bug is re-noticed on every commit. Keep the
|
|
174
174
|
bar high (a few per run at most, code-review-worthy only); logging a bug is
|
|
175
175
|
**orthogonal** to your architecture task — still call
|