dev-booster 1.16.7 → 1.16.8
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
CHANGED
|
@@ -382,9 +382,30 @@ Your response must use this structure:
|
|
|
382
382
|
## ARTIFACT GENERATION
|
|
383
383
|
During your execution, create a state file at `@booster-generated/audit/<slug>.md` tracking the history, decisions, rules, and outcomes in dense, non-conversational format.
|
|
384
384
|
|
|
385
|
+
This artifact is mandatory for this booster.
|
|
386
|
+
Create it even when:
|
|
387
|
+
- there is only one finding
|
|
388
|
+
- the setup is already healthy
|
|
389
|
+
- the audit result is small
|
|
390
|
+
- the user stops after Round 1
|
|
391
|
+
|
|
392
|
+
The artifact must begin in the first real audit round and then be updated continuously as the audit progresses.
|
|
393
|
+
Update it after every meaningful round-trip in the flow, especially when:
|
|
394
|
+
- pre-flight / Round 1 is completed
|
|
395
|
+
- Lot 1 is approved and executed
|
|
396
|
+
- Round 2 / deeper Lot 2 analysis begins
|
|
397
|
+
- deeper analysis reclassifies findings
|
|
398
|
+
- new fixes are applied
|
|
399
|
+
- the user asks follow-up questions that materially change the audit state
|
|
400
|
+
|
|
401
|
+
Treat this file as the persistent audit trail for the session.
|
|
402
|
+
It must preserve what was found, what was changed, what was intentionally left untouched, and what still needs review.
|
|
403
|
+
This is important both for continuity in a later session and for explaining regressions or side effects if something breaks afterward.
|
|
404
|
+
|
|
385
405
|
- **Uniqueness rule:** If the slug already exists in `@booster-generated/audit/`, generate a new variation of the name instead of overwriting
|
|
386
406
|
- **Notification rule:** After writing, notify the user with: 📝 Registo em `@booster-generated/audit/<slug>.md`
|
|
387
407
|
|
|
408
|
+
Do NOT skip artifact creation for small audits.
|
|
388
409
|
Do NOT update this file silently in the background.
|
|
389
410
|
|
|
390
|
-
**Reply:** On activation, immediately enter pre-flight mode, use `PROJECT.md` as the primary source of truth, realign runtime only when needed and repeat `nvm use` on each new terminal execution only for projects that actually required NVM alignment, make lint and typecheck operational in the terminal, detect bypasses, normalize only what is necessary, run a fast Round 1, classify findings into Setup Issues / Lint Findings / Typecheck Findings / Lot 1 / Lot 2, and answer in the active conversation language. After Lot 1 is resolved, offer the short Round 2 transition exactly as specified above.
|
|
411
|
+
**Reply:** On activation, immediately enter pre-flight mode, use `PROJECT.md` as the primary source of truth, realign runtime only when needed and repeat `nvm use` on each new terminal execution only for projects that actually required NVM alignment, make lint and typecheck operational in the terminal, detect bypasses, normalize only what is necessary, run a fast Round 1, classify findings into Setup Issues / Lint Findings / Typecheck Findings / Lot 1 / Lot 2, and answer in the active conversation language already established by the user and current conversation. After Lot 1 is resolved, offer the short Round 2 transition exactly as specified above.
|