@iamu-dev/iamu 0.3.0-beta.5 → 0.3.0-beta.6

package/dist/bin.js

@@ -13647,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.5") {
-    return "0.3.0-beta.5";
+  if ("0.3.0-beta.6") {
+    return "0.3.0-beta.6";
   }
   try {
     const thisDir = dirname3(fileURLToPath2(import.meta.url));
@@ -15996,13 +15996,20 @@ async function report(scenario, opts) {
     console.log(JSON.stringify(rows, null, 2));
     return;
   }
-  if (scenario || completedRuns.length === 1) {
+  if (scenario || !opts?.all || completedRuns.length === 1) {
     const run = completedRuns[0];
     const c = run.canonical;
     console.log();
     console.log(
       chalk13.bold(`  ${run.manifest.scenario_slug}`) + chalk13.dim(` \u2014 ${run.runId.slice(0, 30)}\u2026`)
     );
+    if (!scenario && completedRuns.length > 1) {
+      console.log(
+        chalk13.dim(
+          `  (Showing latest run for ${run.manifest.scenario_slug}. Pass --all to list all recent runs)`
+        )
+      );
+    }
     console.log(
       `  ${chalk13.dim("url:")} ${run.manifest.target_url}  ${chalk13.dim("completed:")} ${run.manifest.completed_at}`
     );
@@ -16095,9 +16102,26 @@ async function report(scenario, opts) {
           }
         }
       }
+      if (c.human_tests && c.human_tests.length > 0) {
+        console.log();
+        console.log(chalk13.bold("  Human Tests:"));
+        for (const ht of c.human_tests) {
+          const v2 = ht.verdict ?? "pending";
+          const color = v2 === "yes" ? chalk13.green : v2 === "no" ? chalk13.red : chalk13.yellow;
+          console.log(
+            `    ${symbols.dot} ${chalk13.bold(ht.question)} \u2192 ${color(v2.toUpperCase())}`
+          );
+          if (ht.reasoning) {
+            console.log(`      ${chalk13.dim(ht.reasoning)}`);
+          }
+        }
+      }
       if (c.human_test_overall?.answer) {
         console.log();
         console.log(chalk13.bold("  Verdict: ") + c.human_test_overall.answer);
+        if (c.human_test_overall.reasoning) {
+          console.log(`    ${chalk13.dim(c.human_test_overall.reasoning)}`);
+        }
       }
     }
     console.log();
@@ -26110,13 +26134,15 @@ function registerFindingsCommands(program2) {
       await triage2(refs, opts);
     }
   );
-  program2.command("report [scenario]").helpGroup("Findings:").description("Show walkthrough results and findings summary").option("--json", "Output as JSON").addHelpText(
+  program2.command("report [scenario]").helpGroup("Findings:").description("Show walkthrough results and findings summary").option("--json", "Output as JSON").option("--all", "Show summary table of all recent runs").addHelpText(
     "after",
-    "\nExamples:\n  $ iamu report\n  $ iamu report checkout-flow\n  $ iamu report --json"
-  ).action(async (scenario, opts) => {
-    const { report: report3 } = await Promise.resolve().then(() => (init_report(), report_exports));
-    await report3(scenario, opts);
-  });
+    "\nExamples:\n  $ iamu report\n  $ iamu report checkout-flow\n  $ iamu report --all\n  $ iamu report --json"
+  ).action(
+    async (scenario, opts) => {
+      const { report: report3 } = await Promise.resolve().then(() => (init_report(), report_exports));
+      await report3(scenario, opts);
+    }
+  );
   program2.command("serve").helpGroup("Findings:").description("[deprecated] Open dashboard (formerly local web UI)").addOption(
     new Option2("--open", "Open the dashboard in a browser").hideHelp()
   ).option("--no-open", "Print the dashboard URL instead of opening a browser").addHelpText(

package/dist/commands/report.d.ts

@@ -1,3 +1,4 @@
 export declare function report(scenario?: string, opts?: {
     json?: boolean;
+    all?: boolean;
 }): Promise<void>;

package/dist/index.js

@@ -13592,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.5") {
-    return "0.3.0-beta.5";
+  if ("0.3.0-beta.6") {
+    return "0.3.0-beta.6";
   }
   try {
     const thisDir = dirname3(fileURLToPath2(import.meta.url));
@@ -15941,13 +15941,20 @@ async function report(scenario, opts) {
     console.log(JSON.stringify(rows, null, 2));
     return;
   }
-  if (scenario || completedRuns.length === 1) {
+  if (scenario || !opts?.all || completedRuns.length === 1) {
     const run = completedRuns[0];
     const c = run.canonical;
     console.log();
     console.log(
       chalk13.bold(`  ${run.manifest.scenario_slug}`) + chalk13.dim(` \u2014 ${run.runId.slice(0, 30)}\u2026`)
     );
+    if (!scenario && completedRuns.length > 1) {
+      console.log(
+        chalk13.dim(
+          `  (Showing latest run for ${run.manifest.scenario_slug}. Pass --all to list all recent runs)`
+        )
+      );
+    }
     console.log(
       `  ${chalk13.dim("url:")} ${run.manifest.target_url}  ${chalk13.dim("completed:")} ${run.manifest.completed_at}`
     );
@@ -16040,9 +16047,26 @@ async function report(scenario, opts) {
           }
         }
       }
+      if (c.human_tests && c.human_tests.length > 0) {
+        console.log();
+        console.log(chalk13.bold("  Human Tests:"));
+        for (const ht of c.human_tests) {
+          const v2 = ht.verdict ?? "pending";
+          const color = v2 === "yes" ? chalk13.green : v2 === "no" ? chalk13.red : chalk13.yellow;
+          console.log(
+            `    ${symbols.dot} ${chalk13.bold(ht.question)} \u2192 ${color(v2.toUpperCase())}`
+          );
+          if (ht.reasoning) {
+            console.log(`      ${chalk13.dim(ht.reasoning)}`);
+          }
+        }
+      }
       if (c.human_test_overall?.answer) {
         console.log();
         console.log(chalk13.bold("  Verdict: ") + c.human_test_overall.answer);
+        if (c.human_test_overall.reasoning) {
+          console.log(`    ${chalk13.dim(c.human_test_overall.reasoning)}`);
+        }
       }
     }
     console.log();
@@ -26047,13 +26071,15 @@ function registerFindingsCommands(program) {
       await triage2(refs, opts);
     }
   );
-  program.command("report [scenario]").helpGroup("Findings:").description("Show walkthrough results and findings summary").option("--json", "Output as JSON").addHelpText(
+  program.command("report [scenario]").helpGroup("Findings:").description("Show walkthrough results and findings summary").option("--json", "Output as JSON").option("--all", "Show summary table of all recent runs").addHelpText(
     "after",
-    "\nExamples:\n  $ iamu report\n  $ iamu report checkout-flow\n  $ iamu report --json"
-  ).action(async (scenario, opts) => {
-    const { report: report3 } = await Promise.resolve().then(() => (init_report(), report_exports));
-    await report3(scenario, opts);
-  });
+    "\nExamples:\n  $ iamu report\n  $ iamu report checkout-flow\n  $ iamu report --all\n  $ iamu report --json"
+  ).action(
+    async (scenario, opts) => {
+      const { report: report3 } = await Promise.resolve().then(() => (init_report(), report_exports));
+      await report3(scenario, opts);
+    }
+  );
   program.command("serve").helpGroup("Findings:").description("[deprecated] Open dashboard (formerly local web UI)").addOption(
     new Option2("--open", "Open the dashboard in a browser").hideHelp()
   ).option("--no-open", "Print the dashboard URL instead of opening a browser").addHelpText(

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

@@ -50,7 +50,11 @@ Determine the mode based on `$ARGUMENTS` and user intent:
   6. Run `iamu validate --all`.
   7. Summarize: persona created in `iamu/personas/<slug>.md`. Prompt user: "You can now pair `<slug>` with a scenario draft via `iamu-new`, or propose situations for them via `iamu-propose`." Stop here for standalone persona requests.
 
-- **Fast-Path Scenario mode** (when intent, topic, or a candidate from `iamu-propose` is provided or referenced from conversational context, e.g. `iamu-new "checkout friction"`, "let's do candidate 2", "draft that", "option 1"):
+- **Fast-Path Scenario mode** (when intent, topic, an Acceptance Criterion / User Story, or a candidate from `iamu-propose` is provided or referenced from conversational context, e.g. `iamu-new "checkout friction"`, `iamu-new "AC: System must require re-auth on payout change"`, "let's do candidate 2", "draft that", "option 1"):
+  - **Acceptance Criteria & User Stories:** When input contains an AC or user story:
+    1. *Walkability check:* If the requirement is pure backend/infra (DB encryption, cron jobs, latency) with no observable human/browser workflow, reject: *"Deterministic backend constraint — verify via unit/integration tests."*
+    2. *Entity mapping:* Map the requirement directly to the outline's `--human-test` question (framed as an observable outcome, not a DOM selector) and the story context to the outline's situation (`--narrative`), following the standard `outline.md` and `combine.md` methodologies (zero UI/screen language, evaluated at run completion).
+    3. *Cast matching:* Match the story's actor to an existing persona in `iamu/personas/` (`iamu list personas`). Only propose a new persona if no fitting role exists in the panel.
   If the user refers to a candidate proposed in the current session, resolve that candidate's details directly from the conversation history.
   Do NOT drag the user through multiple question modals. Skip Step 2 entirely!
   Jump directly to Step 3 and present the **Complete Scenario Spec-Sheet** (Situation + Bound Persona + Evaluation Checkpoint + Walker Brief) for **1-click / 1-key acceptance**.
@@ -76,10 +80,27 @@ Present 2–3 scannable scenario proposals. Each proposal MUST bundle the situat
    • Evaluation Checkpoint: "<Concrete binary question>"
 ```
 
-**Interactive Decision:**
+**Dual-Surface Candidate Selection (Sequencing Rule):**
+You MUST output the candidate proposals to the chat stream FIRST. In the SAME turn, invoke `ask_question` with the candidates and options embedded in the `question` argument:
+
 - If your environment provides an interactive user-prompt tool (e.g. `ask_question`, `ask_followup_question`), invoke it:
-  - Question: "Scaffold this scenario for walkthrough?"
-  - Options:
+  - **Question:**
+    """
+    Proposed Test Journey Candidates:
+
+    1. <Bundle 1 Title> (<Capability>)
+       • Persona: <Persona 1 Name> (<Role>)
+       • Tension: <1 concise sentence on human or organizational tension>
+       • Evaluation Checkpoint: "<Concrete binary yes/partial/no question>"
+
+    2. <Alternative Title> (<Capability>)
+       • Persona: <Alternative Persona Name> (<Role>)
+       • Tension: <1 concise sentence>
+       • Evaluation Checkpoint: "<Concrete binary question>"
+
+    Scaffold this scenario for walkthrough?
+    """
+  - **Options:**
     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>"
@@ -98,7 +119,7 @@ Present 2–3 scannable scenario proposals. Each proposal MUST bundle the situat
 
 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.
 
-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).
+Keep the narrative capped at 2–3 punchy sentences (problem-space only, zero UI terms).
 
 ```
 Scenario Spec-Sheet: <Outline Title>
@@ -119,10 +140,26 @@ Persona & Brief:
     "<First-person brief in persona voice (2–3 sentences). Describes what they intend to achieve before touching the product. Written verbatim to scenario markdown body.>"
 ```
 
-**Interactive Draft Confirmation:**
+**Dual-Surface Draft Confirmation (Sequencing Rule):**
+You MUST output the complete Scenario Spec-Sheet to the chat stream FIRST. In the SAME turn, invoke `ask_question` with the spec-sheet embedded in the `question` argument so the user can verify all details within the dialog:
+
 - If your environment provides an interactive user-prompt tool, invoke it:
-  - Question: "Scaffold scenario '<Outline Title>'?"
-  - Options:
+  - **Question:**
+    """
+    Scenario Spec-Sheet: <Outline Title>
+
+    Situation & Stakes:
+      Narrative:  <2–3 sentences problem-space only, zero UI terms>
+      Tension:    <Colliding needs in X vs Y format or "None">
+      Evaluation: <Concrete binary yes/partial/no question scored at evaluation>
+
+    Persona & Brief:
+      Persona:      <Name> (<Role>) — Friction: <Diagnostic friction trigger>
+      Walker Brief: "<First-person brief in persona voice (2–3 sentences)>"
+
+    Scaffold scenario '<Outline Title>'?
+    """
+  - **Options:**
     1. "[Recommended] Scaffold scenario and prepare walkthrough"
     2. "Switch persona: Walk as <Alternative Persona> (<Role>)"
     3. "Adjust situation, checkpoint, or brief"

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

@@ -55,12 +55,13 @@ Build a coverage picture: which capabilities have scenarios? Which actors from `
 
 ### 3. Determine focus
 
-Four entry paths based on `$ARGUMENTS`:
+Five entry paths based on `$ARGUMENTS`:
 
 - **Persona / Tester panel** (e.g. `iamu-propose "personas"`, `"who else should we test with?"`, `"propose new personas"`) — analyze which actors from `context.yml` lack personas in `iamu/personas/`. Focus proposals on creating durable, diagnostically biased personas for uncovered roles.
 - **Area or capability** (e.g. `iamu-propose "employee provisioning"`) — focus proposals on this area. Match against capabilities and context actors/workflows.
 - **Open-ended** (e.g. `iamu-propose`, `iamu-propose "what's missing?"`) — analyze coverage gaps across scenarios and persona diversity. Prioritize untested product areas and actors without personas.
 - **Specific tension** (e.g. `iamu-propose "what happens when the safety coordinator disagrees with HR?"`) — use as seed but ground in context. Verify the tension is real (do these actors and dynamics exist in the domain?).
+- **Requirement / Acceptance Criteria** (e.g. `iamu-propose "AC: require re-auth on payout change"`, user stories, or RFP clauses) — verify walkability first (reject pure backend/infra for unit/integration coverage). Ground the requirement in domain situations: propose 2–3 contrasting candidates showing how different actors from `context.yml` or the casting panel encounter this requirement under different pressures, with the AC mapped to each candidate's `--human-test` evaluation checkpoint.
 
 ### 4. Present candidates (Numbered Cards)
 
@@ -88,10 +89,24 @@ Existing coverage: <N> scenarios ([<slug1>](iamu/scenarios/<slug1>.md), ...). Un
    • Tension: <1-line human/domain tension>
    • Stress-tests: <What this reveals about the product>
 
-**Interactive Candidate Selection:**
+**Dual-Surface Candidate Selection (Sequencing Rule):**
+You MUST output the proposed candidates to the chat stream FIRST. In the SAME turn, invoke `ask_question` with the candidates and tensions embedded in the `question` argument:
+
 - If your environment provides an interactive user-prompt tool (e.g. `ask_question`, `ask_followup_question`), invoke it:
-  - Question: "Which scenario candidate would you like to scaffold?"
-  - Options:
+  - **Question:**
+    """
+    Proposed Scenario Candidates:
+
+    1. <Candidate 1 Title> (<Actor>)
+       • Capability: <Capability slug> · Tension: <1-line human tension>
+    2. <Candidate 2 Title> (<Actor>)
+       • Capability: <Capability slug> · Tension: <1-line human tension>
+    3. <Candidate 3 Title> (<Actor>)
+       • Capability: <Capability slug> · Tension: <1-line human tension>
+
+    Which scenario candidate would you like to scaffold?
+    """
+  - **Options:**
     1. "[Recommended] Scaffold '<Candidate 1 Title>' (<Actor>)"
     2. "Scaffold '<Candidate 2 Title>' (<Actor>)"
     3. "Scaffold '<Candidate 3 Title>' (<Actor>)"
@@ -119,10 +134,24 @@ Existing personas: [<slug1>](iamu/personas/<slug1>.md), ... Uncovered roles from
    • Key Expectations & Vocabulary: <Domain terms and spec requirements>
 ```
 
-**Interactive Persona Selection:**
+**Dual-Surface Persona Selection (Sequencing Rule):**
+You MUST output the proposed personas to the chat stream FIRST. In the SAME turn, invoke `ask_question` with the candidates embedded in the `question` argument:
+
 - If your environment provides an interactive user-prompt tool (e.g. `ask_question`, `ask_followup_question`), invoke it:
-  - Question: "Which persona would you like to add to the casting panel?"
-  - Options:
+  - **Question:**
+    """
+    Proposed Persona Candidates:
+
+    1. <Name 1> (<Actor role>)
+       • Friction: <Friction triggers and bounce risks>
+    2. <Name 2> (<Actor role>)
+       • Friction: <Friction triggers and bounce risks>
+    3. <Name 3> (<Actor role>)
+       • Friction: <Friction triggers and bounce risks>
+
+    Which persona would you like to add to the casting panel?
+    """
+  - **Options:**
     1. "[Recommended] Add <Name 1> (<Actor role>)"
     2. "Add <Name 2> (<Actor role>)"
     3. "Add <Name 3> (<Actor role>)"

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

@@ -427,17 +427,19 @@ The `walker_prompt` from `iamu instructions walk` is the source of truth and con
 
 ### 5. Present assessment — stay in the conversation
 
-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. Output as rich Markdown (do NOT wrap the entire summary in a triple-backtick code block so links render as clickable):
+You MUST output the complete Executive Scorecard to the chat stream FIRST. Output as rich Markdown (do NOT wrap the entire summary in code fences so links render as clickable):
 
 ### 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:
+> 🎯 **Human Test Checkpoint:**
+> **Question:** "<human_tests[0].question>"
+> **Verdict:** **<NO / PARTIAL / YES>** — <1-2 sentences evaluator reasoning from verdicts.json / report.md>
+
+> ☁️ **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)`)*
+
+#### Findings Overview:
 1. **[CRITICAL]** · *<type>* · <Short title> (Step <N> at `<short_url_path>`)
 2. **[MAJOR]** · *<type>* · <Short title> (Step <N> at `<short_url_path>`)
 ...
@@ -445,23 +447,17 @@ Keep the presentation under 15 lines total. Output as rich Markdown (do NOT wrap
 
 (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 scorecard scannable.
 
-Do NOT output `### What Worked` paragraphs or lengthy bullet essays. Keep the entire summary under 15 lines, then immediately present the triage prompt below.
+**Zero-Friction Triage Transition (Eliminate Meta-Prompt Gate):**
+Do NOT prompt the user with a generic "How would you like to proceed?" multiple-choice modal. That intermediate prompt adds cognitive friction, duplicates the triage options, and obscures the assessment scorecard.
 
-7. **Next actions (Interactive Triage Selection)**:
-   When the walkthrough completes and yields findings:
-   - If your environment provides an interactive user-prompt tool (e.g. `ask_question`, `ask_followup_question`), invoke it:
-     - Question: "Walkthrough complete: <F> findings reported. How would you like to proceed?"
-     - Options:
-       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"
-    - 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).
+- **If `<F> == 0` (Walkthrough Passed):**
+  Output: "✓ Walkthrough passed with zero friction points or blockers. Scenario validated successfully."
+  Do not enter triage.
+
+- **If `<F> > 0` (Walkthrough Has Findings):**
+  Output the Executive Scorecard above to chat FIRST, and advance IMMEDIATELY to triage on **Finding #1 of <total>** (Step 6 below) in the same turn. The user can choose to queue to fix, queue all remaining fixes (batch accept), dismiss, or discuss directly from Finding #1.
 
 ### 6. Conversational Triage & Guided Review
 

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

@@ -77,7 +77,10 @@ No local codebase detected. To seed context, provide one of:
 
 ### 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. Do NOT wrap in markdown code fences (` ``` `) when presenting to the user:
+Present the detected environment and safety fence. Explain clearly *why* this boundary is required before any autonomous agent runs.
+
+**Dual-Surface Prompting (Sequencing Rule):**
+You MUST output the safety fence card to the chat stream FIRST. In the SAME turn, invoke `ask_question` with the full context embedded in the `question` argument:
 
 ```text
 Step 1/3: Safety Fence & Environment Boundary
@@ -93,12 +96,30 @@ Detected Environment:
 **Interactive Decision Gate:**
 Prompt the user to verify the safety boundary:
 - If interactive user-prompt tools exist (`ask_question`, `ask_followup_question`), invoke it:
-  - Question: "Confirm safety fence and dev environment?"
-  - Options:
+  - **Question:**
+    """
+    Step 1/3: Confirm Safety Fence & Dev Environment
+
+    Target URL:    <target_url>
+    Dev Command:   <dev_command>
+    Safe Fixtures: <detected seed scripts or mock handlers>
+
+    DO NOT WALK (Untestable Boundaries):
+    <detected external services, real SMS/email gateways, external submission portals>
+
+    Confirm safety fence and dev environment?
+    """
+  - **Options:**
     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"
 - Otherwise (text-only/CLI):
+  Step 1/3: Safety Fence & Environment Boundary
+  Target URL:    <target_url>
+  Dev Command:   <dev_command>
+  Safe Fixtures: <detected seed scripts or mock handlers>
+  DO NOT WALK:   <detected external services>
+
   Safety boundaries look safe. I recommend saving fence and proceeding.
   Proceeding to save safety fence — say "adjust" to change boundaries or "skip" to defer.
 
@@ -138,7 +159,10 @@ iamu set testability \
 
 Explain the purpose of project context: traditional tests only assert button clicks; Iamu evaluates user confusion, workflow friction, and whether a real person can succeed under real-world constraints.
 
-Present the discovered domain and project description. Do NOT introduce or ask the user to approve personas or roles at this stage — personas are cast later when designing specific test journeys. Do NOT wrap in markdown code fences (` ``` `) when presenting to the user:
+Present the discovered domain and project description. Do NOT introduce or ask the user to approve personas or roles at this stage — personas are cast later when designing specific test journeys.
+
+**Dual-Surface Prompting (Sequencing Rule):**
+You MUST output the domain context and project description to the chat stream FIRST. In the SAME turn, invoke `ask_question` with the complete substantive project description embedded in the `question` argument so the reviewer can read the full text directly within the dialog modal:
 
 ```text
 Step 2/3: Project Domain & Description
@@ -154,15 +178,38 @@ Project Description:
 <1 cohesive paragraph: what the software fundamentally does, its primary user workflows, and the real-world conditions under which it is used. No marketing buzzwords, no hedging, and no tech stack trivia.>
 ```
 
-**Interactive Decision Gate:**
-Prompt the user to verify the project description:
+**CRITICAL: Embed Full Project Description in Interactive Prompt Modal:**
+Host interactive tools (`ask_question`, `ask_followup_question`) render a modal that obscures the terminal/chat and displays ONLY the tool's `question` argument. Never ask the user to confirm an invisible description. You MUST embed the full drafted project description text inside the `question` argument:
+
 - If interactive user-prompt tools exist (`ask_question`, `ask_followup_question`), invoke it:
-  - Question: "Confirm project domain & description?"
-  - Options:
+  - **Question:**
+    """
+    Step 2/3: Confirm Project Domain & Description
+
+    Domain:       <domain name>
+    Industry:     <industry>
+    Jurisdiction: <jurisdiction or omit if standard web app>
+    Governed By:  <statutory regulations or standards, or omit if unregulated>
+
+    PROJECT DESCRIPTION:
+    <1 cohesive paragraph: what the software fundamentally does, its primary user workflows, and the real-world conditions under which it is used>
+
+    Confirm project domain & description?
+    """
+  - **Options:**
     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"
 - Otherwise (text-only/CLI):
+  Step 2/3: Project Domain & Description
+  Domain:             <domain name>
+  Industry:           <industry>
+  Jurisdiction:       <jurisdiction>
+  Governed By:        <statutory regulations or standards>
+
+  Project Description:
+  <1 cohesive paragraph>
+
   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.
 
@@ -185,7 +232,10 @@ iamu set context \
 
 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**. Do NOT wrap in markdown code fences (` ``` `) when presenting to the user:
+Present the proposed test journey, including explicit **Auth Precondition Verification**.
+
+**Dual-Surface Prompting (Sequencing Rule):**
+You MUST output the baseline test proposal to the chat stream FIRST. In the SAME turn, invoke `ask_question` with the full journey spec embedded in the `question` argument:
 
 ```text
 Step 3/3: Co-Design Your First Test Journey
@@ -204,11 +254,26 @@ Baseline Test Proposal (WYSIWGW Spec-Sheet):
   Walker Brief:       "<2–3 sentence first-person test brief that will be written verbatim to disk. States immediate intent and constraints before opening tool. Zero UI terminology.>"
 ```
 
-**Interactive Decision Gate:**
-Prompt the user to verify the scenario and its auth precondition:
+**CRITICAL: Embed Journey Spec in Interactive Prompt Modal:**
 - If interactive user-prompt tools exist (`ask_question`, `ask_followup_question`), invoke it:
-  - Question: "Scaffold this baseline journey?"
-  - Options:
+  - **Question:**
+    """
+    Step 3/3: Confirm Baseline Test Journey
+
+    Capability:        <Capability Name> (<What staff can do in this area>)
+    Persona:           <Name> (<Role / Title>) — Friction: <Diagnostic friction trigger>
+    Situation:         <Outline Title>
+    Core Tension:      <Core problem-space tension in X vs Y format>
+    Evaluation Check:  <Concrete binary yes/partial/no question for evaluator>
+    Walk Surface:      Entry: `<entry_path>` | Target: `<target_url>`
+    Auth Precondition: <Detected auth mechanism>
+
+    WALKER BRIEF:
+    "<2–3 sentence first-person test brief>"
+
+    Scaffold this baseline journey?
+    """
+  - **Options:**
     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 (write-in)"

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

@@ -105,10 +105,25 @@ 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:**
+**Dual-Surface Staging Gate (Sequencing Rule):**
+You MUST output the staging options to the chat stream FIRST. In the SAME turn, invoke `ask_question` with the staging options and requirements embedded in the `question` argument:
+
 - 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:
+  - **Question:**
+    """
+    Staging Plan for '<scenario-slug>':
+
+    Entry Route: <route>
+    Required World State: <Description of required world in domain words>
+
+    Staging Options:
+    • Option A (Testability): <concrete seed or mock fixture proposal>
+    • Option B (Semantic Squinting): <squinting rule formula>
+    • Option C (Zero Setup): <why flow is public or self-contained>
+
+    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)"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@iamu-dev/iamu",
-  "version": "0.3.0-beta.5",
+  "version": "0.3.0-beta.6",
   "type": "module",
   "description": "Test your product as realistic personas — scenario-driven development CLI",
   "license": "UNLICENSED",
@@ -58,9 +58,9 @@
     "tsup": "^8.5.1",
     "typescript": "^5.8.0",
     "vitest": "^4.1.11",
-    "@iamu-dev/local-store": "0.1.0",
     "@iamu-dev/protocol": "0.1.0",
-    "@iamu/tsconfig": "0.1.0"
+    "@iamu/tsconfig": "0.1.0",
+    "@iamu-dev/local-store": "0.1.0"
   },
   "scripts": {
     "build": "tsup && tsc -b --force tsconfig.build.json --emitDeclarationOnly && node scripts/copy-assets.mjs",