the-frame-ai 0.11.1 → 0.11.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "the-frame-ai",
-  "version": "0.11.1",
+  "version": "0.11.3",
   "description": "FRAME — Framework for AI-Assisted Solo Development",
   "type": "module",
   "bin": {

package/src/update.js

@@ -53,13 +53,11 @@ export async function update(target, flags = {}) {
 
   // Ask frontend question early, before file operations
   let frontendDecided = config.frontend === true;
-  if (!config.frontend && !flags.yes) {
+  if (config.frontend === undefined && !flags.yes) {
     const frontend = await promptFrontend(false);
-    if (frontend) {
-      config.frontend = true;
-      frontendDecided = true;
-      writeFileSync(join(target, '.frame', 'config.json'), JSON.stringify(config, null, 2), 'utf-8');
-    }
+    config.frontend = frontend;
+    frontendDecided = frontend;
+    writeFileSync(join(target, '.frame', 'config.json'), JSON.stringify(config, null, 2), 'utf-8');
   }
 
   let updated = 0;

package/templates/commands/frame:perf-fix.md

@@ -37,64 +37,46 @@ Parse issues based on `$ARGUMENTS`:
 
 Output: "Found {N} issues to fix: {list of IDs and titles}."
 
-### Step 2: For Each Issue — Propose Fix
+### Step 2: Group Issues into Waves
 
-For each issue in the list:
+Before applying any fixes, analyze all issues and group them into waves:
 
-1. Read the file mentioned in the issue (`File: path/file.ts:42`)
-2. Understand the surrounding context (±20 lines)
-3. Draft the specific code change
+- **Wave 1**: issues in different files with no shared dependencies — apply all in this wave
+- **Wave 2**: issues that depend on Wave 1 changes (same module, shared types, etc.)
+- **Wave N**: remaining issues
 
-Then output a proposal block:
+Output:
+```
+Wave 1 ({N} issues — independent): PERF-1, PERF-3, PERF-5
+Wave 2 ({N} issues — depend on wave 1): PERF-2, PERF-4
+```
+
+### Step 3: Apply Wave by Wave
+
+For each wave:
 
+1. Apply all fixes in the wave (read file → apply change for each issue)
+2. Output before each fix:
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 [PERF-1] {title}
 File: path/file.ts:42
-Category: {category}
-Impact: {impact from report}
-
-Proposed fix:
-{description of what will change — 2-3 sentences}
-
---- BEFORE ---
-{relevant code snippet}
-
---- AFTER ---
-{fixed code snippet}
+Applying: {1 sentence}
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-Apply this fix? [y/n/skip]
 ```
-
-Wait for user confirmation before applying.
-
-- `y` → apply the fix, mark as done
-- `n` → stop entirely
-- `skip` → skip this issue, move to next
-
-### Step 3: Apply Fix
-
-After confirmation:
-
-1. Apply the code change to the file
-2. Run type check if available:
+3. After all fixes in the wave, run typecheck + tests once:
 ```bash
 {quality.commands.typecheck} 2>&1 | tail -10
-```
-3. Run tests if available:
-```bash
 {quality.commands.test} 2>&1 | tail -20
 ```
 
-If typecheck or tests fail → revert the change, report what broke, ask user how to proceed.
-
-Output: "✓ [PERF-1] fixed. {brief description of what changed}."
+If typecheck or tests fail → revert all fixes from this wave, report what broke, ask user how to proceed. Then continue to next wave.
 
-### Step 4: Continue to Next Issue
+Output after wave: "✓ Wave {N} complete: {list of fixed IDs}."
 
-After each fix (or skip), move to the next issue in the list.
+### Step 4: Summary
 
-After all issues processed, output summary:
+After all waves processed, output summary:
 ```
 Performance fixes complete.
 Fixed: {N} | Skipped: {N}
@@ -122,8 +104,8 @@ Update `.planning/STATE.md`:
 
 ## Rules
 
-- **ALWAYS show before/after** — never apply a fix silently
-- **ALWAYS ask confirmation** per issue — never batch-apply without asking
+- **ALWAYS show what's being fixed** before applying (issue ID, file, one-line description)
+- **NEVER ask confirmation** — apply all found issues automatically
 - **ALWAYS run typecheck + tests** after each fix
 - **REVERT on failure** — if tests break, undo the change immediately
 - **NEVER fix test files** — only production code