@iamu-dev/iamu 0.2.0-beta.13 → 0.2.0-beta.15

package/dist/templates/skills/iamu-findings.md

@@ -126,27 +126,26 @@ If the finding references a run directory, mention the report path for context.
 Every finding must land on a decision — never silently skip. Match the user's intent to the closest option.
 
 **Interactive Triage Selection:**
-*Contextual Recommendation Rule:*
-- If finding is clear, localized, and has a straightforward fix → mark Option 1 as `[Recommended]`.
-- If finding requires architectural touch or redesign → mark Option 2 as `[Recommended]`.
-- If finding is a known trade-off or walker error → mark Option 4 as `[Recommended]`.
+- In list-mode iteration ("walk through them", "all critical", scenario group), the primary action is to decide the queue. Do NOT stop triage to edit code unless the user explicitly chooses "Fix immediately".
 
 - If your environment provides an interactive user-prompt tool (e.g. `ask_question`, `ask_followup_question`), invoke it:
-  - Question: "Triage Finding: '<finding title>'?"
+  - Question: "Triage Finding #<N>/<total>: '<finding title>'?"
   - Options:
-    1. "<[Recommended] if localized> Fix now (apply inline code fix & verify)"
-    2. "<[Recommended] if structural> Design change needed (open issue / design doc)"
-    3. "Defer (revisit in later milestone)"
-    4. "Dismiss / Won't fix (record reason & walker guidance rule)"
+    1. "[Recommended] Queue to fix (mark for fix & continue triage)"
+    2. "Dismiss / Won't fix (record reason & walker guidance rule)"
+    3. "Design change needed (open issue / design doc)"
+    4. "Defer (revisit in later milestone)"
+    5. "Fix immediately (leave triage now)"
 - Otherwise (in CLI or text-only environments):
 
-Triage Finding: '<finding title>'
-  1. Fix now (apply inline code fix & verify)
-  2. Design change needed (open issue / design doc)
-  3. Defer (revisit in later milestone)
-  4. Dismiss / Won't fix (record reason & walker guidance rule)
+Triage Finding #<N>/<total>: '<finding title>'
+  1. [Recommended] Queue to fix (mark for fix & continue triage)
+  2. Dismiss / Won't fix (record reason & walker guidance rule)
+  3. Design change needed (open issue / design doc)
+  4. Defer (revisit in later milestone)
+  5. Fix immediately (leave triage now)
 
-Press Enter to accept recommendation [1], enter 2-4, or type custom triage note:
+Press Enter to queue fix [1], enter 2-5, or type custom triage note:
 (Treat empty Enter as Option 1)
 
 Record the decision with `iamu triage` — it sets `triage_status` and `triage_note` in `iamu/findings/<slug>.md`, and for a dismissal it also teaches the next walk:
@@ -162,7 +161,9 @@ triage_status: addressed
 triage_note: "Made handoff notes optional on /sv/handoff; verified on screen."
 ```
 
-- **Fix now** → the change is small, one-or-two files, no architectural decision needed (label, field made optional, filter added, typo). Make the edit, verify it loads (if a dev server is running, open the affected screen and check), then record: `iamu triage <slug> --status addressed --note "<one-line change summary>"`. Do not close a finding as addressed before the change lands and is inspected. Tell the user the fix now awaits a re-run: only a later walkthrough of the scenario turns it verified.
+- **Queue to fix [Recommended in list-mode]** → add to the session's fix queue. Tell the user in 1 line: "✓ Queued for fix. Advancing to next finding..." and loop to the next finding. Complete the triage queue across all findings first.
+
+- **Fix immediately (leave triage now)** → the change is small, one-or-two files, and user explicitly chose to leave triage now. Make the edit, verify it loads (if a dev server is running, open the affected screen and check), then record: `iamu triage <slug> --status addressed --note "<one-line change summary>"`. Do not close a finding as addressed before the change lands and is inspected. Tell the user the fix now awaits a re-run: only a later walkthrough of the scenario turns it verified.
 
 - **Design change needed** → the change requires design thinking (restructuring a flow, new capability, API contract touch, multiple files). Do NOT fix inline. Use the project's own change process if it has one — check the agent docs and the repo for it (an `openspec/` directory and its change skills, an ADR or RFC folder, an issue tracker the docs name) and start the change there with the finding's persona + scenario context pre-filled. Only if the project has none, draft a short design doc. Then leave the finding `open` until the change ships. Attach the change reference in `triage_note`: `"Design change: <reference>. Re-triage when the change ships."`.
 
@@ -198,20 +199,35 @@ dismissed (not_relevant): <finding-slug>
 
 ### 5. Continue or close
 
-If the user is in list-mode iteration (picked "all critical" or a scenario group), loop to step 3 for the next finding in the queue. Otherwise close.
+If the user is in list-mode iteration (picked "walk through them", "all critical", or a scenario group), loop to step 3 for the next finding in the queue.
 
-Summary at the end (list-mode only):
+When all findings in the queue are triaged, present the summary:
 
-```
+```text
 Triage complete.
-  Fixed: <N>
+  Queued for fix: <N>
   Dismissed: <N>
   Rescoped (design change / defer): <N>
   Kept open: <N>
-
-<X> findings remain open. Use iamu-findings to resume later.
 ```
 
+If `<N> > 0` findings were queued for fix:
+- Prompt the user:
+  - If interactive tool available:
+    - Question: "Triage complete. Apply fixes for the <N> queued findings now?"
+    - Options:
+      1. "[Recommended] Apply queued fixes in workspace now"
+      2. "Done for now (keep fixes open in iamu/findings/)"
+  - Otherwise (CLI / text-only):
+    Apply fixes for the <N> queued findings now?
+      1. [Recommended] Apply queued fixes in workspace now
+      2. Done for now (keep fixes open in iamu/findings/)
+    Press Enter to apply fixes [1], select 2:
+
+- **Executing the queued fixes:**
+  When Option 1 is chosen, apply code edits for each queued finding sequentially in the workspace. Verify the changes once (run test/typecheck suite). Update each finding with `iamu triage <slug> --status addressed --note "<summary of fix>"`.
+  Tell the user: "✓ Applied fixes for <N> findings. All marked addressed."
+
 Run `iamu validate --all` to verify all entities before reporting done.
 
 ### 6. Publish and link (linked mode only)

package/dist/templates/skills/iamu-new.md

@@ -105,10 +105,10 @@ Press Enter to scaffold [1], select 2-3, or type adjustments:
 
 In Fast-Path mode or when customizing, present the complete scenario as a structured, scannable Spec-Sheet before creating anything. Every field shown here is written verbatim to disk on confirmation:
 
-Do NOT use markdown blockquote syntax (`>`), which renders as stray `|` pipe characters in terminal frontends. Keep the narrative capped at 2–3 punchy sentences (problem-space only, zero UI terms).
+Do NOT output markdown header hashes (`#`, `##`, `###`) or markdown blockquote syntax (`>`), which render as stray hashes or `|` pipe characters in terminal frontends. Keep the narrative capped at 2–3 punchy sentences (problem-space only, zero UI terms).
 
 ```
-### Scenario Spec-Sheet: <Outline Title>
+Scenario Spec-Sheet: <Outline Title>
 
 Situation & Stakes:
   Narrative:    <2–3 sentences problem-space only, zero UI terms>

package/dist/templates/skills/iamu-propose.md

@@ -25,9 +25,7 @@ Every persona candidate must have **diagnostic friction**:
 
 ## Prerequisites
 
-Before starting, check that `iamu/context.yml` exists and has content. If it is missing or empty, stop:
-
-> No project context found. Run `iamu-setup` first — proposals need domain grounding to avoid shallow thinking.
+Before starting, check that `iamu/context.yml` exists and has content. If it is missing or empty, stop and inform the user: "No project context found. Run `iamu-setup` first — proposals need domain grounding to avoid shallow thinking."
 
 If context is thin (few actors, sparse notes), say so upfront — "your context has few actors and sparse notes; proposals will be shallow. Consider enriching context first."
 

package/dist/templates/skills/iamu-run.md

@@ -41,8 +41,7 @@ Tell the user in one line which one you picked and why. If the project's own age
 A native app has no URL, and a browser tool is not a substitute for one. If the product is native, the target is a device plus a build (step 3).
 
 If no surface is available, stop and tell the user:
-
-> A walkthrough needs a driving surface. For a web product, `iamu browse` works wherever Chrome or Chromium is installed (or set `IAMU_BROWSER`); a browser-driving MCP that attaches to Chrome also works — restart your agent session after installing one and re-run `iamu-run`. For a native iOS app, a simulator control tool must be available in this session.
+"A walkthrough needs a driving surface. For a web product, `iamu browse` works wherever Chrome or Chromium is installed (or set `IAMU_BROWSER`); a browser-driving MCP that attaches to Chrome also works — restart your agent session after installing one and re-run `iamu-run`. For a native iOS app, a simulator control tool must be available in this session."
 
 Do NOT proceed to step 1 before a driving surface is confirmed.
 
@@ -204,7 +203,7 @@ Pass `--build <label>` to name the build (a version or release tag) and `--env <
 Use the returned `run_id` and `path` for all subsequent operations.
 
 **If `live_viewer_url` is returned**, immediately output it to the user so the operator can follow along live in their browser:
-> 🔴 **Live stream:** `<live_viewer_url>`
+🔴 **Live stream:** `<live_viewer_url>`
 
 **Size the browser for this persona** (`iamu browse` only), every run — also when a browser is already open from an earlier run:
 
@@ -225,7 +224,7 @@ iamu instructions walk --scenario <scenario-slug> --run <run-id> --surface brows
 The result's `walker_prompt` is the walker's entire prompt. Pass it verbatim — do not rewrite, summarize or trim it. The prompt already carries the dismissed findings, the active tester guidance rules (`iamu/guidance/`) for this scenario, and — when fixes await a re-run — the places they were seen (places only, never what was wrong; the list is in `revisit`). The rest of the bundle (`persona`, `outline`, `access`, `dismissed_findings`, `tester_guidance`, …) is there for you, not the walker. If `access` is missing a half, fill it in first (step 3) and re-run this command.
 
 **Preflight: Unattended execution check.** A walkthrough executes 15–30 terminal commands sequentially (`iamu browse step`, `iamu new-finding`). If your agent host requires manual confirmation for terminal/shell commands (standard interactive mode in Claude Code, Cursor, Antigravity, Cline, Windsurf, etc.), the walker subagent will stall waiting for approval on every step. Before dispatching, verify that command auto-approval / unattended execution is enabled in your environment, or warn the user once:
-> "Autonomous walkthroughs require auto-approving terminal commands so the walker can drive the product unattended. If command approvals are prompted, please enable auto-approval or expect to approve steps manually."
+"Autonomous walkthroughs require auto-approving terminal commands so the walker can drive the product unattended. If command approvals are prompted, please enable auto-approval or expect to approve steps manually."
 
 **CRITICAL: Dispatch the walker as an isolated subagent.** Spawn a fresh subagent using your host editor's subagent mechanism (e.g. `Agent(...)` in Claude Code, `invoke_subagent` in Antigravity, or host-native subagent launcher). The subagent gets ONLY the walking prompt (`walker_prompt`) — no prior conversation history.
 
@@ -444,25 +443,28 @@ When the user asks to review findings one by one:
    ```
    Followed immediately by the decision prompt:
    - If interactive tool available:
-     - Question: "Triage Finding #<N>: '<finding title>'?"
+     - Question: "Triage Finding #<N>/<total>: '<finding title>'?"
      - Options:
-       1. "[Recommended] Fix now (apply inline code fix & verify)"
+       1. "[Recommended] Queue to fix (mark for fix & continue triage)"
        2. "Dismiss / Skip (not relevant or walker error)"
        3. "Discuss / Explore trade-offs"
-       4. "Next finding (keep open)"
+       4. "Fix immediately (leave triage now)"
+       5. "Next finding (keep open / defer)"
      - Otherwise (CLI / text-only):
-       Triage Finding #<N>: '<finding title>'
-         1. [Recommended] Fix now (apply inline code fix & verify)
+       Triage Finding #<N>/<total>: '<finding title>'
+         1. [Recommended] Queue to fix (mark for fix & continue triage)
          2. Dismiss / Skip (not relevant or walker error)
          3. Discuss / Explore trade-offs
-         4. Next finding (keep open)
-       Press Enter to fix [1], select 2-4, or describe decision:
+         4. Fix immediately (leave triage now)
+         5. Next finding (keep open / defer)
+       Press Enter to queue fix [1], select 2-5, or describe decision:
        (Treat empty Enter as Option 1)
 
 2. **Handle the user's decision**:
-   - **Fix now**:
-     Make the code edit, verify it loads (or check local tests/types), update the finding with `iamu triage <slug> --status addressed --note "<summary of fix>"`.
-     Tell the user in 1 line: "✓ Applied fix to `<file>:<line>`. Finding #<N> marked addressed." and ask: "Ready for finding #<N+1>?".
+   - **Queue to fix [Recommended]**:
+     Add finding to the session's fix queue.
+     Tell the user in 1 line: "✓ Queued for fix. Ready for finding #<N+1>?" and advance immediately.
+     Do NOT edit code or leave triage yet — complete triage across all findings first.
    - **Skip / Dismiss**:
      If reason is not specified, ask or infer the appropriate category:
      - `out_of_scope`: Not relevant to this project/flow scope.
@@ -477,11 +479,38 @@ When the user asks to review findings one by one:
      • **Root Cause:** 1 sentence on why the code does this (`file:line`).
      • **Persona Friction:** 1 sentence on the practical operational consequence.
      • **Recommended Fix & Trade-off:** 1-2 sentences with concrete code approach and any trade-off.
-     Immediately re-prompt the triage decision.
-   - **Next**:
+     Immediately re-prompt the triage decision for finding #<N>.
+   - **Fix immediately (leave triage now)**:
+     If the user explicitly chooses to drop out of triage and fix right now:
+     Make the code edit, verify it loads (or check local tests/types), update the finding with `iamu triage <slug> --status addressed --note "<summary of fix>"`.
+     Tell the user in 1 line: "✓ Applied fix to `<file>:<line>`. Finding #<N> marked addressed."
+   - **Next finding (keep open / defer)**:
      Leave open (or set `triage_status: deferred` with note) and advance to finding #<N+1>.
 
 3. **Wrap up after all findings are reviewed**:
+   Report the triage recap in 1-2 lines:
+   ```text
+   Triage Complete: <K> queued for fix, <D> dismissed, <O> kept open/deferred.
+   ```
+   If `<K> > 0` (findings are queued for fix):
+   - Prompt the user to execute the batch:
+     - If interactive tool available:
+       - Question: "Triage complete. Apply fixes for the <K> queued findings now?"
+       - Options:
+         1. "[Recommended] Apply fixes for queued findings in workspace now"
+         2. "Re-run walkthrough to verify dismissed items first"
+         3. "Done for now (keep fixes open in iamu/findings/)"
+     - Otherwise (CLI / text-only):
+       Apply fixes for the <K> queued findings now?
+         1. [Recommended] Apply fixes for queued findings in workspace now
+         2. Re-run walkthrough to verify dismissed items first
+         3. Done for now (keep fixes open in iamu/findings/)
+       Press Enter to apply fixes [1], select 2-3:
+
+   - **Executing the queued fixes:**
+     When Option 1 is chosen, apply code edits for each queued finding sequentially in the workspace. Verify the changes once (run test/typecheck suite). Update each finding with `iamu triage <slug> --status addressed --note "<summary of fix>"`.
+     Tell the user: "✓ Applied fixes for <K> findings. All marked addressed."
+
    - Run `iamu validate --all`.
    - In linked mode, run `iamu sync --json` once so teammates see the triage decisions.
    - Suggest re-running the walkthrough: `iamu-run <scenario-slug>` to verify fixes.

package/dist/templates/skills/iamu-setup.md

@@ -68,18 +68,18 @@ Explore the codebase automatically — do NOT ask the user what files to read. E
    - Identify local mock fixtures (`msw`, seed SQL scripts, mock services).
 
 **If there is no code (greenfield, design phase, or test sandbox):** do NOT interrogate the user with a multi-part survey or ask for dev auth plumbing. Ask for a single entry point:
-> No local codebase detected. To seed context, provide one of:
-> - A target URL (staging, production, or docs — e.g., `https://app.example.com`)
-> - A one-sentence description of what this product does
-> - Or type `"sandbox"` to seed a pre-configured B2B SaaS demo
+No local codebase detected. To seed context, provide one of:
+• A target URL (staging, production, or docs — e.g., `https://app.example.com`)
+• A one-sentence description of what this product does
+• Or type `"sandbox"` to seed a pre-configured B2B SaaS demo
 
 ---
 
 ### 3. Step 1/3: Establish the Safety Fence (`iamu/testability.md`)
 
-Present the detected environment and safety fence. Explain clearly *why* this boundary is required before any autonomous agent runs:
+Present the detected environment and safety fence. Explain clearly *why* this boundary is required before any autonomous agent runs. Do NOT wrap in markdown code fences (` ``` `) when presenting to the user:
 
-```markdown
+```text
 Step 1/3: Safety Fence & Environment Boundary
 Why this matters: Iamu drives a real headless browser with full agency. This boundary guarantees the agent stays confined to your local environment and never touches external services or triggers real-world side effects.
 
@@ -145,9 +145,9 @@ harnesses:
 
 Explain the purpose of domain grounding: traditional tests only assert button clicks; Iamu evaluates user confusion, workflow friction, and whether a real person can succeed under operational pressure.
 
-Present the discovered domain reality and candidate roles:
+Present the discovered domain reality and candidate roles. Do NOT wrap in markdown code fences (` ``` `) when presenting to the user:
 
-```markdown
+```text
 Step 2/3: Product Domain & Candidate Roles
 Why this matters: Grounds the AI evaluator in your domain's real operational stakes, vocabulary, and regulations so it can spot human confusion rather than just syntax errors.
 
@@ -200,7 +200,7 @@ actors:
 ```
 
 *If user chooses Option 2 (Save context only):* write `context.yml` and exit cleanly:
-> ✓ Project context initialized. When you're ready to create your first test journey, run `/iamu:new`.
+"✓ Project context initialized. When you're ready to create your first test journey, run `/iamu:new`."
 
 ---
 
@@ -208,9 +208,9 @@ actors:
 
 Explain the journey model: an Iamu test binds a **Persona** (with habits, pressures, and impatience) to a **Situation** (a realistic high-stakes problem) with an **Evaluation Checkpoint** (a concrete binary question for the AI judge).
 
-Present the proposed test journey, including explicit **Auth Precondition Verification**:
+Present the proposed test journey, including explicit **Auth Precondition Verification**. Do NOT wrap in markdown code fences (` ``` `) when presenting to the user:
 
-```markdown
+```text
 Step 3/3: Co-Design Your First Test Journey
 Why this matters: Validates whether a real human with specific operational pressures can complete a critical task without getting blocked or frustrated.
 

package/dist/templates/skills/iamu-status.md

@@ -23,26 +23,22 @@ Do NOT use `find`, `grep`, or `cat` to dump raw `.md` files in `iamu/`. The CLI
 
 ### 2. Format entity responses with an executive tally and clickable links
 
-When the user asks for project status, lead with an executive tally banner, followed by scannable tables with clickable markdown file links:
+When the user asks for project status, lead with an executive tally banner, followed by compact 1-line bullet points with clickable markdown file links.
+
+**ANTI-BLOAT DIRECTIVE:** Do NOT output multi-column markdown tables (they wrap awkwardly and break borders in terminal viewports). Keep each entity to a single scannable line:
 
 ```
 Project Status: <P> Personas · <S> Scenarios (<R> Tested, <U> Untested) · <F> Open Findings · <C> Capabilities
 ```
 
 **Personas:**
-| Slug | Name | Role | Status |
-|---|---|---|---|
-| [`elin-dahl`](iamu/personas/elin-dahl.md) | Elin Dahl | Architect & first-time house owner in Falun | active |
+• [`elin-dahl`](iamu/personas/elin-dahl.md) — Elin Dahl · Architect & first-time house owner in Falun · active
 
 **Scenarios:**
-| Slug | Persona | Outline | Status / Target |
-|---|---|---|---|
-| [`replacing-windows`](iamu/scenarios/replacing-windows.md) | [`elin-dahl`](iamu/personas/elin-dahl.md) | [`measure-and-order`](iamu/outlines/measure-and-order.md) | ready |
+• [`replacing-windows`](iamu/scenarios/replacing-windows.md) — [`elin-dahl`](iamu/personas/elin-dahl.md) · outline: [`measure-and-order`](iamu/outlines/measure-and-order.md) · ready
 
 **Findings:**
-| # | Severity | Type | Finding | File |
-|---|---|---|---|---|
-| 1 | CRITICAL | hinders | Submit fails opaquely on empty field | [`view`](iamu/findings/<slug>.md) |
+• `1` [CRITICAL · hinders] Submit fails opaquely on empty field — [`view`](iamu/findings/<slug>.md)
 
 ### 3. Ignore internal templates
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@iamu-dev/iamu",
-  "version": "0.2.0-beta.13",
+  "version": "0.2.0-beta.15",
   "type": "module",
   "description": "Test your product as realistic personas — scenario-driven development CLI",
   "license": "UNLICENSED",
@@ -43,6 +43,16 @@
   "engines": {
     "node": ">=22"
   },
+  "scripts": {
+    "build": "tsup && tsc -b --force tsconfig.build.json --emitDeclarationOnly && node scripts/copy-assets.mjs",
+    "clean": "node -e \"fs.rmSync('dist', { recursive: true, force: true }); fs.rmSync('tsconfig.tsbuildinfo', { force: true }); fs.rmSync('tsconfig.build.tsbuildinfo', { force: true })\"",
+    "typecheck": "tsc --noEmit",
+    "test": "vitest run",
+    "test:coverage": "vitest run --coverage",
+    "eval:walkthroughs": "vitest run --config vitest.benchmark.config.ts",
+    "eval:gemini": "node dist/eval/gemini-eval-cli.js",
+    "pack:dry-run": "npm pack --dry-run"
+  },
   "dependencies": {
     "@clack/prompts": "^1.8.1",
     "@modelcontextprotocol/sdk": "^1.26.0",
@@ -52,24 +62,14 @@
     "zod": "^3.25.0"
   },
   "devDependencies": {
+    "@iamu-dev/local-store": "workspace:*",
+    "@iamu-dev/protocol": "workspace:*",
+    "@iamu/tsconfig": "workspace:*",
     "@types/node": "^22.0.0",
     "@vitest/coverage-v8": "^4.1.11",
     "google-auth-library": "^11.1.0",
     "tsup": "^8.5.1",
     "typescript": "^5.8.0",
-    "vitest": "^4.1.11",
-    "@iamu-dev/local-store": "0.1.0",
-    "@iamu/tsconfig": "0.1.0",
-    "@iamu-dev/protocol": "0.1.0"
-  },
-  "scripts": {
-    "build": "tsup && tsc -b --force tsconfig.build.json --emitDeclarationOnly && node scripts/copy-assets.mjs",
-    "clean": "node -e \"fs.rmSync('dist', { recursive: true, force: true }); fs.rmSync('tsconfig.tsbuildinfo', { force: true }); fs.rmSync('tsconfig.build.tsbuildinfo', { force: true })\"",
-    "typecheck": "tsc --noEmit",
-    "test": "vitest run",
-    "test:coverage": "vitest run --coverage",
-    "eval:walkthroughs": "vitest run --config vitest.benchmark.config.ts",
-    "eval:gemini": "node dist/eval/gemini-eval-cli.js",
-    "pack:dry-run": "npm pack --dry-run"
+    "vitest": "^4.1.11"
   }
-}
+}