@iamu-dev/iamu 0.8.0-beta.0 → 0.8.0-beta.1

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

@@ -68,22 +68,41 @@ Inspect the project to understand what the system under test already supports:
 4. **Running Dev Server:**
    - Verify the target URL (e.g. `http://localhost:3000`). If a local server is running, check what port it uses.
 
-### 3. Audit Gaps & Present the Strategic Fork
+### 3. Audit Gaps & Confirm Target, Entry & Login
 
 Present an honest, concise audit of what the scenario needs vs. what the system currently provides:
 
 ```markdown
 ### Staging Audit for `<scenario-slug>`
 
-- **Persona Role:** Maria Gomez (Shift Coordinator)
-  - Need: Account with site-coordinator privileges.
-  - Found: `coordinator@site-a.test` in seed scripts.
-- **Entry Route:** `/incidents` (verified in `src/app/(dashboard)/incidents/page.tsx`).
-- **World State:** 5 open incidents, 1 serious and unassigned.
-  - Current DB / Seed: Default seed only creates 0 incidents, or empty demo state.
+- **Target URL:** `http://localhost:3000` (`pnpm dev`, from `iamu/testability.md`)
+- **Entry Route:** `/incidents` (verified in `src/app/(dashboard)/incidents/page.tsx`)
+- **Persona Login:** Maria Gomez (Shift Coordinator) → `coordinator@site-a.test` (`dev_bypass` / `seed_accounts` / `interactive_browser`)
+- **World State:** 5 open incidents, 1 serious and unassigned (Current DB / Seed: 0 incidents)
 ```
 
-Now present the **Strategic Fork** to the user. Do not be an unyielding bureaucrat. Give the user two clear options:
+#### Step 3a: Confirm Target URL, Entry Route & Persona Login
+Never bury the Target URL, Entry Route, or Login mechanism inside a world-state prompt where the user cannot easily override them. Before asking about database seeds, confirm where the walk starts and how it signs in (one focused question):
+
+- If your environment provides an interactive user-prompt tool (e.g. `ask_question`, `ask_followup_question`), invoke it:
+  - **Question:** "Start URL & Login for `<scenario-slug>`: Should Iamu start at `<target_url><entry_route>` and sign in via `<detected_access_or_strategy>`?"
+  - **Options:**
+    1. "[Recommended] Confirm `<target_url><entry_route>` & `<detected_access_or_strategy>`"
+    2. "Change Target URL or Entry Route — tell me the URL or `/path`"
+    3. "Change how tests log in as `<persona.name>` (e.g. interactive Chrome login, different test account, or dev switcher)"
+    4. "No login needed (public / unauthenticated flow)"
+- Otherwise, state the recommended Target URL, Entry Route, and Login mechanism and ask the user to confirm or override any of them.
+
+Persist any Target URL, Entry Route, or Login updates immediately:
+```bash
+iamu set testability --target <url> --auth-strategy <strategy> --access "<project-auth-mechanism>"
+iamu set scenario <slug> --entry "/<route>"
+iamu set persona <persona-slug> --access "<account-or-role-key>"
+```
+
+#### Step 3b: Present the Strategic Fork (World State & Seeds)
+
+Now present the **Strategic Fork** for the scenario's world state. Do not be an unyielding bureaucrat. Give the user clear options:
 
 #### Option A: Build Testability (The High-Integrity Path)
 *Recommend this when a clean seed script or preset is easy to add.*
@@ -106,23 +125,10 @@ Now present the **Strategic Fork** to the user. Do not be an unyielding bureaucr
 - Mark `--state-description "No particular data needed"`.
 
 **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:
+You MUST output the staging options to the chat stream FIRST. In the SAME turn, invoke `ask_question` with the world-state options:
 
 - If your environment provides an interactive user-prompt tool (e.g. `ask_question`, `ask_followup_question`), invoke it:
-  - **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?
-    """
+  - **Question:** "World State for '<scenario-slug>' (<Required World State in domain words>): How should we stage the data?"
   - **Options:**
     1. "[Recommended] Option A: Build Testability (<brief seed proposal>)"
     2. "Option B: Semantic Squinting (test immediately against current dev database)"

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

@@ -29,6 +29,7 @@ When the user asks for project status, lead with an executive tally banner, foll
 
 ```
 Project Status: <P> Personas · <S> Scenarios (<R> Tested, <U> Untested) · <F> Open Findings · <C> Capabilities
+Design Docs:    <recorded design doc paths, or "none (designer reviews by general craft only — run iamu-design so runs check your own design rules)">
 Product Map:    <T> Surfaces (<R> Reached · <U> Unreached) [if explore map exists]
 ```
 
@@ -68,6 +69,7 @@ Conclude with exact copy-pasteable commands:
 ```
 Next actions:
   iamu-run <scenario-slug>              # Run a walkthrough for this scenario
+  iamu-design                           # Record or create DESIGN.md so runs check your own design rules
   iamu-propose                          # Propose missing personas or scenarios
   iamu-new                              # Draft a new scenario or persona
   iamu-findings                         # Triage open findings

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@iamu-dev/iamu",
-  "version": "0.8.0-beta.0",
+  "version": "0.8.0-beta.1",
   "type": "module",
   "description": "Test your product as realistic personas — scenario-driven development CLI",
   "license": "MIT",
@@ -59,8 +59,8 @@
     "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"
+    "@iamu-dev/protocol": "0.1.0",
+    "@iamu/tsconfig": "0.1.0"
   },
   "scripts": {
     "build": "tsup && tsc -b --force tsconfig.build.json --emitDeclarationOnly && node scripts/copy-assets.mjs",