dev-booster 1.7.0 → 1.9.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dev-booster",
-  "version": "1.7.0",
+  "version": "1.9.0",
   "description": "Reusable AI development kit with manual boosters, governance, and project bootstrap",
   "type": "module",
   "scripts": {

package/template/.devbooster/boosters/code-audit.md

@@ -57,7 +57,7 @@ Only switch to execution mode after the user provides the commit scope.
     - **Execute & Wait**: Run `npx -y react-doctor@latest --json --diff <scope> --yes > @booster-generated/diagnostics/<slug-name-audit>.json` synchronously. You MUST wait for the command to fully complete before moving to the next step. Do not run it in the background.
     - **Timeout Safety**: If the command hangs for more than 120 seconds, manually abort it (Kill/Ctrl+C) and proceed with the rest of the audit, gracefully skipping the React Doctor step.
     - **Filter (Python)**: Run `.devbooster/hub/scripts/doctor_parser.py @booster-generated/diagnostics/<slug-name-audit>.json` to process the JSON.
-    - **Report & Decide**: Present "Immediate Actions" (Critical errors) in detail by line. Present "Cosmetic Debt" (Style rules) as a grouped numerical summary. Append "Content extracted from diagnostics.json".
+    - **Report & Decide**: Present "Immediate Actions" (Critical errors) in detail by line. For "Cosmetic Debt" (Warnings), create a dedicated section that groups the warnings by Rule/Category (e.g., "Tailwind Sorting: 70 issues", "Unused Variables: 20 issues"). Provide a 1-line explanation for the most frequent categories so the user understands the nature of the debt without being overwhelmed.
     - **ZERO Auto-Fix**: Do NOT modify code automatically. Ask the user: "Do you want to fix only the critical recommendations, everything, or specific items?" and wait for authorization.
 
 ## 4. OUTPUT STRUCTURE (MANDATORY)
@@ -69,10 +69,13 @@ Your response MUST be an **Audit Report**:
 - [Findings based on the project's specific stack (React, Angular, Vue, etc.)]
 
 **2. Specialized Diagnostics**
-- *(If React)*: [React Doctor Findings (Critical Issues by Line & Cosmetic Debt Summary)]
+- *(If React)*: 
+  - **Critical Issues:** [Detailed list by line]
+  - **Cosmetic Debt (Warnings):** [Grouped by Rule/Category with issue counts and short explanations]
 - *(If Non-React)*: [Framework-specific standard violations or architectural anti-patterns]
 
 **3. Action Plan**
+- [Explicitly state that the full line-by-line list of all warnings/errors is available in `@booster-generated/diagnostics/<slug-name-audit>.json` for manual review]
 - [Waiting for user permission to apply fixes]
 
 ## ARTIFACT GENERATION & STATE BACKUP

package/template/.devbooster/rules/USER_PREFERENCES.md

@@ -8,11 +8,9 @@ description: Dynamic Scratchpad - Experimental patterns and recently approved ru
 
 This file operates as a "real-time scratchpad" for the AI and the Developer. The core of the project's architecture lives in `FRONTEND.md`, `BACKEND.md`, and `PROJECT.md`.
 
-## 🛠️ THE ENCYCLOPEDIA TRIGGER
-Every time the user strictly types the phrase **"bota na enciclopédia"** (or variations like "bota na enciclopedia"), referring to a code pattern we just resolved and approved in the current session, the AI **must extract the technical rule** and annotate it here.
+- This file captures development preferences and emergent decisions using the `@SavePattern` trigger (defined in `PROTOCOL.md`).
+- It ensures consistency in the short term. Periodically, the consolidated patterns born here will be migrated to the official frontend or backend files and removed from here.
 
-- This file captures development preferences and emergent decisions to ensure consistency in the short term.
-- Periodically (or when refactoring the base), the consolidated patterns born here will be migrated to the official frontend or backend folders and removed from here.
 
 ---