@iamu-dev/iamu 0.3.0-beta.1 → 0.3.0-beta.2

package/dist/bin.js

@@ -13040,7 +13040,8 @@ var init_symbols = __esm({
       add: chalk3.cyan("+"),
       info: chalk3.blue(supportsUnicode ? "\u2139" : "i"),
       dot: chalk3.dim(supportsUnicode ? "\u2022" : "*"),
-      question: chalk3.yellow("?")
+      question: chalk3.yellow("?"),
+      step: chalk3.blue(supportsUnicode ? "\u25B6" : ">")
     };
   }
 });
@@ -13646,8 +13647,8 @@ import { dirname as dirname3, join as join4, resolve as resolve2 } from "path";
 import { fileURLToPath as fileURLToPath2 } from "url";
 import chalk6 from "chalk";
 function getVersion() {
-  if ("0.3.0-beta.1") {
-    return "0.3.0-beta.1";
+  if ("0.3.0-beta.2") {
+    return "0.3.0-beta.2";
   }
   try {
     const thisDir = dirname3(fileURLToPath2(import.meta.url));
@@ -16017,9 +16018,16 @@ async function report(scenario, opts) {
     if (viewport) {
       console.log(`  ${chalk13.dim("device:")}    ${formatViewport(viewport)}`);
     }
-    const viewUrl = await pushedRunUrl(projectRoot, run.runId);
-    if (viewUrl) {
-      console.log(`  ${chalk13.dim("view:")} ${chalk13.underline(viewUrl)}`);
+    const config = await readConfig(projectRoot);
+    if (config.cloud_linked && config.cloud_project_id) {
+      const viewUrl = await pushedRunUrl(projectRoot, run.runId);
+      if (viewUrl) {
+        console.log(`  ${chalk13.dim("view:")}      ${chalk13.underline(viewUrl)}`);
+      } else {
+        console.log(
+          `  ${chalk13.dim("view:")}      ${chalk13.dim("not synced yet")} ${chalk13.dim("(run `iamu sync` to view in cloud)")}`
+        );
+      }
     }
     if (c) {
       const v = c.verification;
@@ -18700,23 +18708,38 @@ async function stepCommand(runArg, opts) {
       );
       return;
     }
-    console.log();
-    console.log(
-      `  ${symbols.success} Step ${chalk20.cyan(String(res.step.step_number))} recorded: ${res.step.action}`
-    );
-    if (res.step.note) {
-      console.log(`  ${chalk20.dim("note:")}       ${res.step.note}`);
-    }
-    if (res.step.url) {
-      console.log(`  ${chalk20.dim("url:")}        ${res.step.url}`);
-    }
-    if (res.step.screenshot) {
-      console.log(`  ${chalk20.dim("shot:")}       ${res.step.screenshot}`);
+    const stepNumStr = String(res.step.step_number).padStart(2, "0");
+    if (isVerbose()) {
+      console.log();
+      console.log(
+        `  ${symbols.success} Step ${chalk20.cyan(stepNumStr)} recorded: ${res.step.action}`
+      );
+      if (res.step.note) {
+        console.log(`  ${chalk20.dim("note:")}       ${res.step.note}`);
+      }
+      if (res.step.url) {
+        console.log(`  ${chalk20.dim("url:")}        ${res.step.url}`);
+      }
+      if (res.step.screenshot) {
+        console.log(`  ${chalk20.dim("shot:")}       ${res.step.screenshot}`);
+      }
+      console.log(
+        `  ${chalk20.dim("file:")}       ${path25.relative(projectRoot, res.stepPath)}`
+      );
+      console.log();
+    } else {
+      let route = "";
+      if (res.step.url) {
+        try {
+          route = new URL(res.step.url).pathname;
+        } catch {
+          route = res.step.url;
+        }
+      }
+      console.log(
+        `  ${symbols.step} Step ${chalk20.cyan(stepNumStr)} \xB7 ${chalk20.bold(res.step.action)}${route ? chalk20.dim(` \xB7 ${route}`) : ""}`
+      );
     }
-    console.log(
-      `  ${chalk20.dim("file:")}       ${path25.relative(projectRoot, res.stepPath)}`
-    );
-    console.log();
   } catch (err) {
     commandError(err.message, opts);
   }
@@ -18727,6 +18750,7 @@ var init_step = __esm({
     "use strict";
     init_dist2();
     init_dist();
+    init_logger();
     init_symbols();
     init_context4();
     init_live_run_client();
@@ -19311,16 +19335,34 @@ function printStep(opts, record, projectRoot, stagnationWarning, challengeWarnin
     console.log(JSON.stringify(doc, null, 2));
     return;
   }
-  console.log(
-    `  ${chalk21.green("\u2713")} Step ${chalk21.cyan(String(step.step_number))} recorded: ${step.action}`
-  );
-  for (const w of warnings) {
-    console.log(`    ${chalk21.yellow("\u26A0\uFE0F ")}  ${chalk21.yellow(w)}`);
-  }
-  if (step.note) console.log(`    ${chalk21.dim("note:")}       ${step.note}`);
-  if (step.url) console.log(`    ${chalk21.dim("url:")}        ${step.url}`);
-  if (step.screenshot) {
-    console.log(`    ${chalk21.dim("screenshot:")} ${step.screenshot}`);
+  const stepNumStr = String(step.step_number).padStart(2, "0");
+  if (isVerbose()) {
+    console.log(
+      `  ${symbols.success} Step ${chalk21.cyan(stepNumStr)} recorded: ${step.action}`
+    );
+    for (const w of warnings) {
+      console.log(`    ${symbols.warning}  ${chalk21.yellow(w)}`);
+    }
+    if (step.note) console.log(`    ${chalk21.dim("note:")}       ${step.note}`);
+    if (step.url) console.log(`    ${chalk21.dim("url:")}        ${step.url}`);
+    if (step.screenshot) {
+      console.log(`    ${chalk21.dim("screenshot:")} ${step.screenshot}`);
+    }
+  } else {
+    let route = "";
+    if (step.url) {
+      try {
+        route = new URL(step.url).pathname;
+      } catch {
+        route = step.url;
+      }
+    }
+    console.log(
+      `  ${symbols.step} Step ${chalk21.cyan(stepNumStr)} \xB7 ${chalk21.bold(step.action)}${route ? chalk21.dim(` \xB7 ${route}`) : ""}`
+    );
+    for (const w of warnings) {
+      console.log(`    ${symbols.warning}  ${chalk21.yellow(w)}`);
+    }
   }
 }
 async function browseStep(args, opts, driver) {
@@ -19627,6 +19669,8 @@ var init_browse = __esm({
     "use strict";
     init_dist2();
     init_dist();
+    init_logger();
+    init_symbols();
     init_browse_actions();
     init_browse_driver();
     init_context4();

package/dist/index.js

@@ -12646,7 +12646,8 @@ var init_symbols = __esm({
       add: chalk.cyan("+"),
       info: chalk.blue(supportsUnicode ? "\u2139" : "i"),
       dot: chalk.dim(supportsUnicode ? "\u2022" : "*"),
-      question: chalk.yellow("?")
+      question: chalk.yellow("?"),
+      step: chalk.blue(supportsUnicode ? "\u25B6" : ">")
     };
   }
 });
@@ -13591,8 +13592,8 @@ import { dirname as dirname3, join as join4, resolve as resolve2 } from "path";
 import { fileURLToPath as fileURLToPath2 } from "url";
 import chalk6 from "chalk";
 function getVersion() {
-  if ("0.3.0-beta.1") {
-    return "0.3.0-beta.1";
+  if ("0.3.0-beta.2") {
+    return "0.3.0-beta.2";
   }
   try {
     const thisDir = dirname3(fileURLToPath2(import.meta.url));
@@ -15962,9 +15963,16 @@ async function report(scenario, opts) {
     if (viewport) {
       console.log(`  ${chalk13.dim("device:")}    ${formatViewport(viewport)}`);
     }
-    const viewUrl = await pushedRunUrl(projectRoot, run.runId);
-    if (viewUrl) {
-      console.log(`  ${chalk13.dim("view:")} ${chalk13.underline(viewUrl)}`);
+    const config = await readConfig(projectRoot);
+    if (config.cloud_linked && config.cloud_project_id) {
+      const viewUrl = await pushedRunUrl(projectRoot, run.runId);
+      if (viewUrl) {
+        console.log(`  ${chalk13.dim("view:")}      ${chalk13.underline(viewUrl)}`);
+      } else {
+        console.log(
+          `  ${chalk13.dim("view:")}      ${chalk13.dim("not synced yet")} ${chalk13.dim("(run `iamu sync` to view in cloud)")}`
+        );
+      }
     }
     if (c) {
       const v = c.verification;
@@ -18645,23 +18653,38 @@ async function stepCommand(runArg, opts) {
       );
       return;
     }
-    console.log();
-    console.log(
-      `  ${symbols.success} Step ${chalk20.cyan(String(res.step.step_number))} recorded: ${res.step.action}`
-    );
-    if (res.step.note) {
-      console.log(`  ${chalk20.dim("note:")}       ${res.step.note}`);
-    }
-    if (res.step.url) {
-      console.log(`  ${chalk20.dim("url:")}        ${res.step.url}`);
-    }
-    if (res.step.screenshot) {
-      console.log(`  ${chalk20.dim("shot:")}       ${res.step.screenshot}`);
+    const stepNumStr = String(res.step.step_number).padStart(2, "0");
+    if (isVerbose()) {
+      console.log();
+      console.log(
+        `  ${symbols.success} Step ${chalk20.cyan(stepNumStr)} recorded: ${res.step.action}`
+      );
+      if (res.step.note) {
+        console.log(`  ${chalk20.dim("note:")}       ${res.step.note}`);
+      }
+      if (res.step.url) {
+        console.log(`  ${chalk20.dim("url:")}        ${res.step.url}`);
+      }
+      if (res.step.screenshot) {
+        console.log(`  ${chalk20.dim("shot:")}       ${res.step.screenshot}`);
+      }
+      console.log(
+        `  ${chalk20.dim("file:")}       ${path25.relative(projectRoot, res.stepPath)}`
+      );
+      console.log();
+    } else {
+      let route = "";
+      if (res.step.url) {
+        try {
+          route = new URL(res.step.url).pathname;
+        } catch {
+          route = res.step.url;
+        }
+      }
+      console.log(
+        `  ${symbols.step} Step ${chalk20.cyan(stepNumStr)} \xB7 ${chalk20.bold(res.step.action)}${route ? chalk20.dim(` \xB7 ${route}`) : ""}`
+      );
     }
-    console.log(
-      `  ${chalk20.dim("file:")}       ${path25.relative(projectRoot, res.stepPath)}`
-    );
-    console.log();
   } catch (err) {
     commandError(err.message, opts);
   }
@@ -18672,6 +18695,7 @@ var init_step = __esm({
     "use strict";
     init_dist2();
     init_dist();
+    init_logger();
     init_symbols();
     init_context4();
     init_live_run_client();
@@ -19256,16 +19280,34 @@ function printStep(opts, record, projectRoot, stagnationWarning, challengeWarnin
     console.log(JSON.stringify(doc, null, 2));
     return;
   }
-  console.log(
-    `  ${chalk21.green("\u2713")} Step ${chalk21.cyan(String(step.step_number))} recorded: ${step.action}`
-  );
-  for (const w of warnings) {
-    console.log(`    ${chalk21.yellow("\u26A0\uFE0F ")}  ${chalk21.yellow(w)}`);
-  }
-  if (step.note) console.log(`    ${chalk21.dim("note:")}       ${step.note}`);
-  if (step.url) console.log(`    ${chalk21.dim("url:")}        ${step.url}`);
-  if (step.screenshot) {
-    console.log(`    ${chalk21.dim("screenshot:")} ${step.screenshot}`);
+  const stepNumStr = String(step.step_number).padStart(2, "0");
+  if (isVerbose()) {
+    console.log(
+      `  ${symbols.success} Step ${chalk21.cyan(stepNumStr)} recorded: ${step.action}`
+    );
+    for (const w of warnings) {
+      console.log(`    ${symbols.warning}  ${chalk21.yellow(w)}`);
+    }
+    if (step.note) console.log(`    ${chalk21.dim("note:")}       ${step.note}`);
+    if (step.url) console.log(`    ${chalk21.dim("url:")}        ${step.url}`);
+    if (step.screenshot) {
+      console.log(`    ${chalk21.dim("screenshot:")} ${step.screenshot}`);
+    }
+  } else {
+    let route = "";
+    if (step.url) {
+      try {
+        route = new URL(step.url).pathname;
+      } catch {
+        route = step.url;
+      }
+    }
+    console.log(
+      `  ${symbols.step} Step ${chalk21.cyan(stepNumStr)} \xB7 ${chalk21.bold(step.action)}${route ? chalk21.dim(` \xB7 ${route}`) : ""}`
+    );
+    for (const w of warnings) {
+      console.log(`    ${symbols.warning}  ${chalk21.yellow(w)}`);
+    }
   }
 }
 async function browseStep(args, opts, driver) {
@@ -19572,6 +19614,8 @@ var init_browse = __esm({
     "use strict";
     init_dist2();
     init_dist();
+    init_logger();
+    init_symbols();
     init_browse_actions();
     init_browse_driver();
     init_context4();

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

@@ -103,13 +103,8 @@ Ask the user how they would like to triage:
     2. "Focus only on Critical findings (<C> items)"
     3. "Review by scenario group: <Top Scenario>"
 - Otherwise (in CLI or text-only environments):
-
-How would you like to triage these <N> open findings?
-  1. [Recommended] Walk through findings one by one
-  2. Focus only on Critical findings (<C> items)
-  3. Review by scenario group: <Top Scenario>
-
-Reply '1' to walk through all [default], select 2-3, or enter a finding number/slug:
+  How would you like to triage these <N> open findings? I recommend walking through findings one by one.
+  Proceeding with one-by-one triage. (Say "critical only", specify a scenario group, or enter a finding number/slug).
 
 ### 3. Direct triage: review one finding
 
@@ -122,7 +117,7 @@ Format the visible finding in chat:
 ```markdown
 ### Finding #<N>/<total> [<SEVERITY>] — <title>
 > **Where:** `<Screen title or URL>` (Step <N>) · **Persona:** <Persona Name> (<Role>)
-> **Evidence:** `iamu/.runs/<run>/screenshots/step-<N>.png` [Dashboard](<url if cloud_linked>)
+> **Evidence:** [step-<N>.png](iamu/.runs/<run>/screenshots/step-<N>.png) · [View in Cloud Walkthrough](<url from iamu open <run-id> --print>)
 
 **❌ Problem:**
 <What went wrong on screen and why it hinders the persona (synthesizing ui_fact and consequence in 1–2 clear, direct sentences)>
@@ -130,8 +125,9 @@ Format the visible finding in chat:
 **💡 Recommendation:**
 <Concrete fix proposal from finding body>
 ```
+*(For `type: "helps"` findings, omit `**❌ Problem:**` and `**💡 Recommendation:**`; render `**✓ Strength:** <Observation>`)*.
 
-If the project is cloud-linked, include the link to the finding in Iamu Cloud (from `iamu open --print`).
+If the project is cloud-linked, include the direct link to the walkthrough in Iamu Cloud (from `iamu open <run-id> --print`).
 
 Emit this card visibly into the conversation.
 
@@ -139,47 +135,20 @@ Emit this card visibly into the conversation.
 
 Every finding must land on a decision — never silently skip. Match the user's intent to the closest option.
 
-**CRITICAL: Embed Scannable Finding in Interactive Prompt Modals:**
-Host interactive tools (e.g. `ask_question`, `ask_followup_question`) render a modal that obscures the terminal and displays ONLY the tool's `question` argument. **Embed this exact scannable structure inside the `question` argument** with blank lines separating the sections:
+**Dual-Surface Triage Prompting (Sequencing Rule):**
+You MUST output the rich markdown finding card to the chat stream FIRST. In the SAME turn, invoke `ask_question`:
 
 - If your environment provides an interactive user-prompt tool (e.g. `ask_question`, `ask_followup_question`), invoke it:
-  - **Question:**
-    """
-    Finding #<N>/<total> [<SEVERITY>]: <title>
-    Where: <Screen title or URL, Step N> · Persona: <Persona Name> (<Role>)
-
-    ❌ PROBLEM:
-    <What is broken or awkward on screen and why it hinders the persona in 1–2 direct sentences>
-
-    💡 RECOMMENDATION:
-    <Concrete fix proposal from finding body>
-
-    How should we triage this finding?
-    """
+  - **Question:** "Finding #<N>/<total> [<SEVERITY>]: <title> on <Screen title or URL, Step N> — How to triage?"
   - **Options:**
     1. "[Recommended] Queue to fix (<brief 3-5 word fix summary>)"
-    2. "Dismiss / Skip (<brief reason if obvious, e.g. keep current design>)"
-    3. "Discuss / Explore trade-offs"
-    4. "Fix immediately (leave triage now)"
-    5. "Next finding (keep open / defer)"
-- Otherwise (in CLI or text-only environments):
-
-Finding #<N>/<total> [<SEVERITY>]: <title>
-Where: <Screen title or URL, Step N> · Persona: <Persona Name> (<Role>)
-
-❌ PROBLEM:
-<What went wrong and why it hinders the persona in 1–2 direct sentences>
-
-💡 RECOMMENDATION:
-<Concrete fix proposal>
-
-  1. [Recommended] Queue to fix (<brief 3-5 word fix summary>)
-  2. Dismiss / Skip (not relevant or walker error)
-  3. Discuss / Explore trade-offs
-  4. Fix immediately (leave triage now)
-  5. Next finding (keep open / defer)
-
-Reply '1' to queue fix [default], enter 2-5, or describe your decision:
+    2. "Queue all remaining recommended fixes (batch accept)"
+    3. "Dismiss / Skip (<brief reason if obvious, e.g. keep current design>)"
+    4. "Discuss / Explore trade-offs"
+    5. "Fix immediately (leave triage now)"
+- Otherwise (CLI / text-only conversational fallback):
+  > **Recommended Action:** Queue to fix (<brief 3-5 word fix summary>).
+  > Say **"queue"** (or **"queue all"**), **"dismiss"** (to teach a rule), or **"discuss"** to explore trade-offs.
 
 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:
 
@@ -195,7 +164,8 @@ triage_note: "Made handoff notes optional on /sv/handoff; verified on screen."
 ```
 
 - **Discuss / Explore trade-offs (Conversational Dialogue Mode — NO MODAL LOOPS)** → when the user chooses "Discuss", asks a question, or wants to explore architectural trade-offs:
-  **DO NOT invoke `ask_question` or present multiple-choice menus.** Stay in natural conversational chat as a senior pair programmer. Answer follow-up questions, inspect code, benchmark against competitors, and discuss options in plain markdown. Converse naturally back and forth until you reach a conclusion together. Only when a consensus or decision is reached ("let's queue it", "dismiss it", "fix it now"), record the decision and proceed. Do NOT trap the user with modal dialogs after each conversational turn.
+  **DO NOT invoke `ask_question` or present multiple-choice menus.** Stay in natural conversational chat as a senior pair programmer. Answer follow-up questions, inspect code, benchmark against competitors, and discuss options in plain markdown. Converse naturally back and forth until you reach a conclusion together.
+  Once the user says "queue it", "dismiss it", "fix it now", or "let's do that", execute `iamu triage`, confirm in 1 line: "✓ Decision recorded. Ready for finding #<N+1>?", and immediately emit Finding #<N+1> to chat with its triage prompt. Do NOT trap the user with modal dialogs after each conversational turn.
 
 - **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.
 
@@ -262,10 +232,8 @@ If `<N> > 0` findings were queued for fix:
       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/)
-    Reply '1' to apply fixes [default], or select 2:
+    Triage complete. I recommend: Apply queued fixes in workspace now.
+    Proceeding with code edits — say "done" to keep fixes open in iamu/findings/.
 
 - **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>"`.
@@ -279,10 +247,8 @@ If `<N> > 0` findings were queued for fix:
       1. "[Recommended] Re-run walkthrough for <scenario-slug> to verify fixes hold"
       2. "Done for now (leave verification for later)"
   - Otherwise (CLI / text-only):
-    Verify fixes now?
-      1. [Recommended] Re-run walkthrough for <scenario-slug> to verify fixes hold
-      2. Done for now (leave verification for later)
-    Reply '1' to re-run [default], or select 2:
+    Fixes applied and validated. I recommend: Re-run walkthrough for <scenario-slug> to verify fixes hold.
+    Proceeding with verification re-run — say "done" to leave verification for later.
 
   When Option 1 is chosen, hand off to `iamu-run <scenario-slug>` to re-run the walkthrough, visit the revisit places, verify resolutions in `canonical.json`, and report the verified delta.
 
@@ -298,9 +264,7 @@ Report it in one line: `Synced <N> findings to Iamu Cloud.` If the result has `c
 
 Then end with the dashboard link from `iamu open --print` (step replay, screenshots side by side, the team's view of the same findings):
 
-```
-Team view: <url>
-```
+> ☁️ **Cloud Walkthrough:** [Open in Iamu Cloud](<url from iamu open --print>)
 
 In linked-no-credentials mode, end with `Decisions are local only — iamu auth login, then iamu sync, to share them.` Skip this section entirely in local-only mode. The terminal surface is complete.
 

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

@@ -85,26 +85,20 @@ Present 2–3 scannable scenario proposals. Each proposal MUST bundle the situat
     3. "Select alternative: '<Bundle 2 Title>' as <Persona 2 Name>"
     4. "Customize situation, checkpoint, or brief"
 - Otherwise (in CLI or text-only environments):
-
-Scaffold this scenario for walkthrough?
-  1. [Recommended] Scaffold '<Bundle 1 Title>' as <Persona 1 Name>
-  2. Switch persona: Walk as <Alternative Persona Name> (<Role>)
-  3. Select alternative: '<Bundle 2 Title>' as <Persona 2 Name>
-  4. Customize situation, checkpoint, or brief
-
-Reply '1' to scaffold [default], select 2-3, or type adjustments:
+  I recommend scaffolding '<Bundle 1 Title>' as <Persona 1 Name>.
+  Proceeding to scaffold scenario — say "switch persona", "select alternative", or describe adjustments to customize.
 
 *Execution Flow:*
-- **Selecting Option 1 (or hitting Enter):** Proceed IMMEDIATELY to Step 6 (Persist everything). Zero intermediate question modals.
+- **Selecting Option 1 (or conversational confirmation):** Proceed IMMEDIATELY to Step 6 (Persist everything). Zero intermediate question modals.
 - **Selecting Option 2:** Present the persona switcher (Step 4) then persist.
 - **Selecting Option 3:** Swap primary bundle and prompt to persist.
 - **Selecting Option 4 / typing adjustments:** Expand into Step 3 to refine details before persisting.
 
 ### 3. Develop the situation (Scenario Spec-Sheet)
 
-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:
+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 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).
+Keep the narrative capped at 2–3 punchy sentences (problem-space only, zero UI terms). (Note: When passing text to modal prompt tools like `ask_question`, use plain text without header hashes or blockquotes; in normal chat output, format clearly with standard markdown).
 
 ```
 Scenario Spec-Sheet: <Outline Title>
@@ -133,15 +127,10 @@ Persona & Brief:
     2. "Switch persona: Walk as <Alternative Persona> (<Role>)"
     3. "Adjust situation, checkpoint, or brief"
 - Otherwise (in CLI or text-only environments):
+  I recommend scaffolding scenario '<Outline Title>' and preparing the walkthrough.
+  Proceeding to scaffold scenario — say "switch persona" or describe adjustments.
 
-Scaffold scenario '<Outline Title>'?
-  1. [Recommended] Scaffold scenario and prepare walkthrough
-  2. Switch persona: Walk as <Alternative Persona> (<Role>)
-  3. Adjust situation, checkpoint, or brief
-
-Reply '1' to scaffold [default], select 2, or type adjustments:
-
-*Selecting Option 1 or hitting Enter proceeds IMMEDIATELY to Step 6 (Persist everything).*
+*Selecting Option 1 proceeds IMMEDIATELY to Step 6 (Persist everything).*
 
 ### 4. Pick or swap personas (on demand)
 
@@ -170,7 +159,8 @@ If no existing persona fits, or if testing an uncovered perspective is needed, p
     1. "[Recommended] Bind existing persona: <slug> (<role>)" (if one fits)
     2. "Create candidate: <Name> (<Role>)"
     3. "Leave as draft (no persona bound yet)"
-- Otherwise, prompt: "Pick a persona (1–N), 'new' to propose candidates, or 'skip' to save as draft without a persona."
+- Otherwise, state the recommended persona and conversational default:
+  "I recommend binding <slug> (<role>). Proceeding with this persona — name a candidate or say 'skip' to save as draft."
 
 ### 5. Classify into capabilities
 

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

@@ -96,7 +96,8 @@ Existing coverage: <N> scenarios ([<slug1>](iamu/scenarios/<slug1>.md), ...). Un
     2. "Scaffold '<Candidate 2 Title>' (<Actor>)"
     3. "Scaffold '<Candidate 3 Title>' (<Actor>)"
 - Otherwise (in CLI or text-only environments):
-Reply '1' to scaffold [default], select 2-3, or describe adjustments:
+  I recommend scaffolding Candidate 1: '<Candidate 1 Title>' (<Actor>).
+  Proceeding to scaffold scenario — name another candidate or describe adjustments.
 
 #### B. When proposing Personas:
 
@@ -126,7 +127,8 @@ Existing personas: [<slug1>](iamu/personas/<slug1>.md), ... Uncovered roles from
     2. "Add <Name 2> (<Actor role>)"
     3. "Add <Name 3> (<Actor role>)"
 - Otherwise (in CLI or text-only environments):
-Reply '1' to add [default], select 2-3, or describe adjustments:
+  I recommend adding Candidate 1: <Name 1> (<Actor role>).
+  Proceeding to add persona — name another candidate or describe adjustments.
 
 Ground rules for generation:
 

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

@@ -57,8 +57,8 @@ When `$ARGUMENTS` is empty and no active scenario exists in context, check `iamu
     1. "[Recommended] Ignore and continue with new run"
     2. "Finish run `<run-id>`: Run post-walk assembly on existing steps"
     3. "Discard empty unfinished runs"
-- Otherwise (in text-only/conversational environments), state that you are proceeding with Option 1 by default:
-  "Note: Found <N> unfinished walkthrough run(s). Proceeding with a new run [1]. (Reply 2 to finish run `<run-id>` or 3 to discard empty runs)."
+- Otherwise (in text-only/conversational environments), state the recommended action and default:
+  "Found <N> unfinished walkthrough run(s). Proceeding with a new run. (Say 'finish <run-id>' or 'discard empty' to adjust)."
 
 Do not block the new run on this, and do not ask again in the same session.
 
@@ -110,7 +110,8 @@ Omit the first group when `rerun` is empty. If `requests.open` in the status out
     1. "[Recommended] <Slug or Title>" (e.g. top rerun needing proof, or primary ready scenario)
     2. "<Alternative Scenario Slug or Title>"
     3. "Draft a new scenario..."
-- Otherwise, prompt: "Pick a scenario number (1–N), enter a slug, or type an intent to draft a new one."
+- Otherwise, state the recommended scenario and conversational default:
+  "Recommended scenario: `<Slug or Title>`. Proceeding with this scenario — say '<Alternative Slug>' or describe a new intent to change course."
 
 Drafts get a bind prompt before execution (step 2); ready-to-run scenarios skip to step 3.
 
@@ -125,7 +126,8 @@ If the resolved scenario has `persona: null`, prompt to bind before executing:
     1. "[Recommended] <Existing Persona 1> (<Role>)"
     2. "<Existing Persona 2> (<Role>)"
     3. "Draft a new persona candidate"
-- Otherwise, ask: "This scenario is a draft — no persona bound. Pick an existing persona (1–N), or type 'new' to propose candidates."
+- Otherwise, state the recommended persona and conversational default:
+  "This scenario is a draft with no persona bound. I recommend binding `<Existing Persona 1>` (<Role>). Proceeding with this persona — name another persona or type 'new' to propose candidates."
 
 1. Read `iamu/personas/` directory or run `iamu list personas`; present as pickable list + "new" option.
 2. Picked existing → bind that persona by updating the scenario file's `persona` field.
@@ -162,11 +164,8 @@ If the target is a local URL (e.g. `http://localhost:*`, `http://127.0.0.1:*`) a
        2. "I will start the dev server manually (wait for port)"
        3. "Specify a different target URL"
    - Otherwise (CLI / text-only):
-     Target URL <url> is unreachable. Boot dev server now?
-       1. [Recommended] Boot dev server in background (`<dev_command>`) and proceed
-       2. I will start the dev server manually (wait for port)
-       3. Specify a different target URL
-     Reply '1' to boot dev server [default], select 2-3, or provide target URL:
+     Target URL <url> is unreachable. I recommend Option 1: Boot dev server in background (`<dev_command>`) and proceed.
+     Proceeding with dev server boot — say "wait" to start manually or provide a different target URL.
 3. If Option 1 is chosen:
    - Launch `<dev_command>` in the background as a managed daemon process.
    - Poll `<url>` with HTTP requests until it responds (timeout: 30s).
@@ -432,23 +431,23 @@ Render results **inline** as a concise executive scorecard.
 
 **ANTI-BLOAT DIRECTIVE:** Terminal viewports are small. Never output multi-screen walls of markdown text. The overview exists only to present the top-line score and orient the user for triage. Do NOT dump long quotes, recommendations, full descriptions, or "What Worked" essays here — those belong in the interactive triage step below.
 
-Keep the presentation under 15 lines total:
+Keep the presentation under 15 lines total. Output as rich Markdown (do NOT wrap the entire summary in a triple-backtick code block so links render as clickable):
 
-```
-Walkthrough: [<scenario-slug>](iamu/scenarios/<scenario-slug>.md) ([<persona>](iamu/personas/<persona>.md))
-Verdict: <FAIL / PARTIAL / PASS> · <N> Blockers (Critical) · <M> Friction points (Major/Minor) · <K> Helpers (Steps: <N>)
-Focus Checkpoint: "<human_tests[0].question>" → <No / Partial / Yes>: <1-sentence direct answer>
+### Walkthrough Complete: [<scenario-slug>](iamu/scenarios/<scenario-slug>.md) ([<persona>](iamu/personas/<persona>.md))
+**Verdict:** <FAIL / PARTIAL / PASS> · <N> Blockers (Critical) · <M> Friction points (Major/Minor) · <K> Helpers (<StepCount> steps)
+**Checkpoint:** "<human_tests[0].question>" → <No / Partial / Yes>: <1-sentence direct answer>
 
-Findings:
-1. [<CRITICAL|MAJOR|MINOR> · <type>] <Short title> (Step <N> at <short_url_path>)
-2. [<CRITICAL|MAJOR|MINOR> · <type>] <Short title> (Step <N> at <short_url_path>)
+#### Findings:
+1. **[CRITICAL]** · *<type>* · <Short title> (Step <N> at `<short_url_path>`)
+2. **[MAJOR]** · *<type>* · <Short title> (Step <N> at `<short_url_path>`)
 ...
 (Helps: • [helps] <short title> (Step <N>))
 
-Cloud: <Shareable report: <url> | Local only>
-```
-
 (If canonical.json contains a `verification` section, include a 1-line delta: `Since last run: ✓ <N> fixed · ✗ <M> persist · + <K> new`.)
+
+> ☁️ **Cloud Walkthrough:** [Open in Iamu Cloud](<url from iamu open <run-id> --print>)
+*(If local-only, render instead: `> **Artifact:** [iamu/.runs/<run-id>/report.md](iamu/.runs/<run-id>/report.md) (Local only)`)*
+
 Do NOT output `### What Worked` paragraphs or lengthy bullet essays. Keep the entire summary under 15 lines, then immediately present the triage prompt below.
 
 7. **Next actions (Interactive Triage Selection)**:
@@ -460,15 +459,9 @@ Do NOT output `### What Worked` paragraphs or lengthy bullet essays. Keep the en
        2. "Apply fixes for all clear findings (batch fix)"
        3. "Discuss findings and persona friction points"
        4. "Re-run walkthrough to test changes"
-   - Otherwise (in CLI or text-only environments):
-
-   Walkthrough complete: <F> findings reported.
-     1. [Recommended] Walk through findings one by one
-     2. Apply fixes for all clear findings (batch fix)
-     3. Discuss findings and persona friction points
-     4. Re-run walkthrough to test changes
-
-   Reply '1' to review findings [default], enter 2-4, or tell me how to proceed:
+    - Otherwise (in CLI or text-only environments):
+      Walkthrough complete: <F> findings reported. I recommend walking through findings one by one.
+      Proceeding with one-by-one triage. (Say "batch fix", "discuss", or "re-run" to change course).
 
 ### 6. Conversational Triage & Guided Review
 
@@ -483,7 +476,7 @@ When the user asks to review findings one by one:
    ```markdown
    ### Finding #<N>/<total> [<SEVERITY>] — <title>
    > **Where:** `<Screen title or URL>` (Step <N>) · **Persona:** <Persona Name> (<Role>)
-   > **Evidence:** `iamu/.runs/<run>/screenshots/step-<N>.png` [Dashboard](<url if cloud_linked>)
+   > **Evidence:** [step-<N>.png](iamu/.runs/<run>/screenshots/step-<N>.png) · [View in Cloud Walkthrough](<url from iamu open <run-id> --print>)
 
    **❌ Problem:**
    <What went wrong on screen and why it hinders the persona (synthesizing ui_fact and consequence in 1–2 clear, direct sentences)>
@@ -491,49 +484,26 @@ When the user asks to review findings one by one:
    **💡 Recommendation:**
    <Concrete fix proposal from finding body>
    ```
-   If the project is cloud-linked, include the link to the finding in Iamu Cloud (from `iamu open --print`).
+   *(For `type: "helps"` findings, omit `**❌ Problem:**` and `**💡 Recommendation:**`; render `**✓ Strength:** <Observation>`)*.
+
+   If the project is cloud-linked, include the direct link to the walkthrough in Iamu Cloud (from `iamu open <run-id> --print`).
 
    Followed immediately by the decision prompt:
 
-   **CRITICAL: Embed Scannable Finding in Interactive Prompt Modals:**
-   Host interactive tools (e.g. `ask_question`, `ask_followup_question`) render a modal that obscures the terminal and displays ONLY the tool's `question` argument. **Embed this exact scannable structure inside the `question` argument** with blank lines separating the sections (never a solid block of bullets):
+   **Dual-Surface Triage Prompting (Sequencing Rule):**
+   You MUST output the rich markdown finding card to the chat stream FIRST. In the SAME turn, invoke `ask_question`:
 
    - If interactive tool available (e.g. `ask_question`, `ask_followup_question`), invoke it:
-     - **Question:**
-       """
-       Finding #<N>/<total> [<SEVERITY>]: <title>
-       Where: <Screen title or URL, Step N> · Persona: <Persona Name> (<Role>)
-
-       ❌ PROBLEM:
-       <What is broken or awkward on screen and why it hinders the persona in 1–2 direct sentences>
-
-       💡 RECOMMENDATION:
-       <Concrete fix proposal from finding body>
-
-       How should we triage this finding?
-       """
+     - **Question:** "Finding #<N>/<total> [<SEVERITY>]: <title> on <Screen title or URL, Step N> — How to triage?"
      - **Options:**
        1. "[Recommended] Queue to fix (<brief 3-5 word fix summary>)"
-       2. "Dismiss / Skip (<brief reason if obvious, e.g. keep current design>)"
-       3. "Discuss / Explore trade-offs"
-       4. "Fix immediately (leave triage now)"
-       5. "Next finding (keep open / defer)"
-   - Otherwise (CLI / text-only):
-     Finding #<N>/<total> [<SEVERITY>]: <title>
-     Where: <Screen title or URL, Step N> · Persona: <Persona Name> (<Role>)
-
-     ❌ PROBLEM:
-     <What went wrong and why it hinders the persona in 1–2 direct sentences>
-
-     💡 RECOMMENDATION:
-     <Concrete fix proposal>
-
-     1. [Recommended] Queue to fix (<brief 3-5 word fix summary>)
-     2. Dismiss / Skip (not relevant or walker error)
-     3. Discuss / Explore trade-offs
-     4. Fix immediately (leave triage now)
-     5. Next finding (keep open / defer)
-     Reply '1' to queue fix [default], select 2-5, or describe your decision:
+       2. "Queue all remaining recommended fixes (batch accept)"
+       3. "Dismiss / Skip (<brief reason if obvious, e.g. keep current design>)"
+       4. "Discuss / Explore trade-offs"
+       5. "Fix immediately (leave triage now)"
+   - Otherwise (CLI / text-only conversational fallback):
+     > **Recommended Action:** Queue to fix (<brief 3-5 word fix summary>).
+     > Say **"queue"** (or **"queue all"**), **"dismiss"** (to teach a rule), or **"discuss"** to explore trade-offs.
 
 2. **Handle the user's decision**:
    - **Queue to fix [Recommended]**:
@@ -584,11 +554,8 @@ When the user asks to review findings one by one:
          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/)
-       Reply '1' to apply fixes [default], or select 2-3:
+       Triage complete. I recommend: Apply fixes for queued findings in workspace now.
+       Proceeding with code fixes — say "re-run first" or "done for now" to adjust.
 
    - **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>"`.
@@ -604,10 +571,8 @@ When the user asks to review findings one by one:
          1. "[Recommended] Re-run walkthrough to verify fixes hold"
          2. "Done for now (leave verification for later)"
      - Otherwise (CLI / text-only):
-       Verify fixes now?
-         1. [Recommended] Re-run walkthrough to verify fixes hold
-         2. Done for now (leave verification for later)
-       Reply '1' to re-run [default], or select 2:
+       Fixes applied and validated. I recommend: Re-run walkthrough to verify fixes hold.
+       Proceeding with verification re-run — say "done" to leave verification for later.
 
      When Option 1 is chosen:
      1. Start the verification run: `iamu start-run <scenario-slug> --target <target> --json`. Note: `start-run` automatically pulls all awaiting findings into `revisit` places in `walkthrough.json`.

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

@@ -99,15 +99,8 @@ Prompt the user to verify the safety boundary:
     2. "Adjust boundaries (add forbidden external URLs, change dev command or port)"
     3. "Skip safety fence for now"
 - Otherwise (text-only/CLI):
-
-```text
-Confirm safety fence and dev environment?
-  1. [Recommended] Safety boundaries look safe — save fence and proceed
-  2. Adjust boundaries (add forbidden external URLs, change dev command or port)
-  3. Skip safety fence for now
-
-Reply '1' to accept [default], select 2-3, or tell me what to adjust:
-```
+  Safety boundaries look safe. I recommend saving fence and proceeding.
+  Proceeding to save safety fence — say "adjust" to change boundaries or "skip" to defer.
 
 **Action on confirmation (Option 1):**
 Persist the safety fence using `iamu set testability` (never invoke host file creation or edit tools):
@@ -170,15 +163,8 @@ Prompt the user to verify the project description:
     2. "Save project description only (skip scenario creation for now)"
     3. "Adjust domain or description"
 - Otherwise (text-only/CLI):
-
-```text
-Confirm project domain & description?
-  1. [Recommended] Project description is accurate — proceed to design first test
-  2. Save project description only (skip scenario creation for now)
-  3. Adjust domain or description
-
-Reply '1' to accept [default], select 2-3, or tell me what to adjust:
-```
+  Project description is accurate. I recommend proceeding to design your first test.
+  Proceeding to first test design — say "save only" or describe adjustments to change course.
 
 **Action on confirmation (Option 1):**
 Persist the domain context using `iamu set context` (never invoke host file creation or edit tools). Put structured fields in frontmatter and the project description in the markdown body below the `---` via `--body`:
@@ -228,16 +214,8 @@ Prompt the user to verify the scenario and its auth precondition:
     3. "Switch role / design a different scenario (write-in)"
     4. "Skip scenario for now"
 - Otherwise (text-only/CLI):
-
-```text
-Scaffold this baseline journey?
-  1. [Recommended] Scaffold journey with <detected auth mechanism>
-  2. Use interactive human login handshake (pause browser for live login)
-  3. Switch role / design a different scenario
-  4. Skip scenario for now
-
-Reply '1' to accept [default], select 2-4, or tell me what to adjust:
-```
+  I recommend Option 1: Scaffold journey with <detected auth mechanism>.
+  Proceeding to scaffold baseline journey — say "interactive login", "switch role", or "skip" to adjust.
 
 **Action on confirmation (Option 1 or Option 2):**
 1. **Scaffold Primary Capability** (if not already existing):

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

@@ -105,6 +105,17 @@ Now present the **Strategic Fork** to the user. Do not be an unyielding bureaucr
 - State: "This situation reads a public page and requires no pre-existing world state."
 - Mark `--state-description "No particular data needed"`.
 
+**Interactive Decision Gate:**
+- If your environment provides an interactive user-prompt tool (e.g. `ask_question`, `ask_followup_question`), invoke it:
+  - Question: "How should we stage '<scenario-slug>' for walkthrough?"
+  - Options:
+    1. "[Recommended] Option A: Build Testability (<brief seed proposal>)"
+    2. "Option B: Semantic Squinting (test immediately against current dev database)"
+    3. "Option C: Zero Setup Needed (public or self-contained flow)"
+- Otherwise (in CLI or text-only environments):
+  I recommend Option A: Build Testability (<brief seed proposal>).
+  Proceeding with testability setup — say "squint" for Option B, or "zero setup" for Option C to change course.
+
 ### 4. Apply & Persist Staging
 
 Once the user chooses (or confirms):

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

@@ -57,7 +57,7 @@ The directory `iamu/.prompts/` contains internal prompt templates (`persona.md`,
 
 For a project-status question, add one line on the cloud from `iamu status --json` (`mode`, `sync`, `requests`) and `iamu auth status --json` (`authenticated`):
 
-- **Linked** → `Cloud: linked — <url from iamu open --print>`, then only what needs action: unpushed changes (`sync.pending_new` + `sync.pending_updates` + `walkthroughs.pending`, and `sync.local_deletions.count`) → `iamu sync`; `requests.open` above zero → `<N> team requests — iamu-findings`.
+- **Linked** → `Cloud: linked — [Open Project in Iamu Cloud](<url from iamu open --print>)`, then only what needs action: unpushed changes (`sync.pending_new` + `sync.pending_updates` + `walkthroughs.pending`, and `sync.local_deletions.count`) → `iamu sync`; `requests.open` above zero → `<N> team requests — iamu-findings`.
 - **Linked, no credentials** → `Cloud: linked, but this machine has no credentials — iamu auth login.`
 - **Local-only** → `Cloud: local-only.` Nothing more; no upgrade pitch.
 

package/dist/ui/symbols.d.ts

@@ -8,4 +8,5 @@ export declare const symbols: {
     info: string;
     dot: string;
     question: string;
+    step: string;
 };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@iamu-dev/iamu",
-  "version": "0.3.0-beta.1",
+  "version": "0.3.0-beta.2",
   "type": "module",
   "description": "Test your product as realistic personas — scenario-driven development CLI",
   "license": "UNLICENSED",