mindsystem-cc 3.21.0 → 3.22.0

package/commands/ms/design-phase.md

@@ -41,6 +41,7 @@ ls .planning/phases/${PHASE}-*/*DESIGN.md 2>/dev/null
 ## 1. Parse and Validate Phase
 
 ```bash
+# ms-tools is on PATH — invoke directly, not as a script path
 ms-tools find-phase "$ARGUMENTS"
 ```
 
@@ -78,7 +79,10 @@ Scan skills in your system-reminder for matches. Look for skills related to:
 
 **3b. Confirm with user:**
 
-Use AskUserQuestion to present findings. Always include an escape hatch for the user to name a skill manually.
+Present via AskUserQuestion with `multiSelect: true`:
+- Each matching skill is one option (label: skill name, description: what it provides)
+- Always include a "None — skip skill loading" option
+- User selects which to load, skips, or types a skill name in the free-text field
 
 **3c. Load selected skills:**
 
@@ -429,10 +433,9 @@ Read `~/.claude/mindsystem/templates/design-iteration.md` and use the iteration
 
 ## 9. Update Last Command
 
-Update `.planning/STATE.md` Last Command field:
-- Find line starting with `Last Command:` in Current Position section
-- Replace with: `Last Command: ms:design-phase $ARGUMENTS | YYYY-MM-DD HH:MM`
-- If line doesn't exist, add it after `Status:` line
+```bash
+ms-tools set-last-command "ms:design-phase $ARGUMENTS"
+```
 
 </process>
 

package/commands/ms/discuss-phase.md

@@ -28,6 +28,7 @@ Phase number: $ARGUMENTS (required)
 
 **Resolve phase:**
 ```bash
+# ms-tools is on PATH — invoke directly, not as a script path
 ms-tools find-phase "$ARGUMENTS"
 ```
 
@@ -52,8 +53,7 @@ ms-tools find-phase "$ARGUMENTS"
 8. **Informed discussion** — follow discuss-phase.md workflow. ALL questions use AskUserQuestion.
 9. Create CONTEXT.md capturing their vision with reasoning-backed decisions
 10. Present pre-work status: Read `~/.claude/mindsystem/references/prework-status.md` and show what's done vs still needed for this phase
-11. Update `.planning/STATE.md` Last Command field:
-    - Format: `Last Command: ms:discuss-phase $ARGUMENTS | YYYY-MM-DD HH:MM`
+11. **Update last command:** `ms-tools set-last-command "ms:discuss-phase $ARGUMENTS"`
 
 **CRITICAL: ALL questions use AskUserQuestion. Never ask inline text questions.**
 </process>

package/commands/ms/doctor.md

@@ -13,7 +13,7 @@ allowed-tools:
 ---
 
 <objective>
-Run health checks on project configuration. Detect and fix structural drift across 8 categories: subsystem vocabulary, milestone directory structure, milestone naming convention, phase archival, knowledge files, phase summaries, PLAN cleanup, and CLI wrappers.
+Run health checks on project configuration. Detect and fix structural drift across 9 categories: subsystem vocabulary, milestone directory structure, milestone naming convention, phase archival, knowledge files, phase summaries, PLAN cleanup, CLI wrappers, and research API keys.
 
 Idempotent.
 </objective>
@@ -72,10 +72,11 @@ Proceed to next step.
 Run the diagnostic scan:
 
 ```bash
+# ms-tools is on PATH — invoke directly, not as a script path
 ms-tools doctor-scan
 ```
 
-Capture the full output. Parse each check's Status (PASS/FAIL/SKIP) and detail lines.
+Capture the full output. Parse each check's Status (PASS/FAIL/SKIP/WARN) and detail lines.
 </step>
 
 <step name="present_results">
@@ -94,11 +95,12 @@ Display results as a markdown table:
 | Phase summaries          | FAIL   | 2 milestones missing summaries   |
 | PLAN cleanup             | FAIL   | 9 leftover PLAN.md files         |
 | CLI wrappers             | FAIL   | ms-tools not on PATH             |
+| Research API Keys        | WARN   | PERPLEXITY_API_KEY not set        |
 ```
 
 Populate Result and Details from scan output. Use concise detail summaries.
 
-If all PASS → go to `report`.
+If all PASS (or WARN only) → go to `report`.
 If any FAIL → go to `confirm_action`.
 </step>
 
@@ -117,7 +119,7 @@ If "Review each" → use AskUserQuestion for each failed check with its details
 
 Apply fixes in dependency order: fix_subsystems → fix_milestone_dirs → fix_milestone_naming → fix_phase_archival → fix_plan_cleanup → fix_knowledge. Skip any fix whose check passed or was skipped by user.
 
-Phase summaries are resolved by fix_phase_archival. CLI wrappers require manual PATH configuration (no automated fix).
+Phase summaries are resolved by fix_phase_archival. CLI wrappers require manual PATH configuration (no automated fix). WARN checks (Research API Keys) are informational — no fix offered, only displayed in the report.
 </step>
 
 <step name="apply_fixes">
@@ -152,11 +154,12 @@ Final summary table:
 | Phase summaries          | PASS   | ...                              |
 | PLAN cleanup             | PASS   | ...                              |
 | CLI wrappers             | PASS   | ...                              |
+| Research API Keys        | PASS   | ...                              |
 
 All checks passed.
 ```
 
-Include counts: checks total, passed, fixed during this run.
+Include counts: checks total, passed, warned, fixed during this run.
 </step>
 
 </process>
@@ -167,6 +170,6 @@ Include counts: checks total, passed, fixed during this run.
 - [ ] Re-scan verifies all checks pass after fixes
 - [ ] Each fix group committed atomically
 - [ ] Fixes applied in dependency order: subsystems → dirs → milestone naming → archival → cleanup → knowledge
-- [ ] All 8 categories reported with PASS/FAIL/SKIP
+- [ ] All 9 categories reported with PASS/FAIL/WARN/SKIP
 - [ ] Clean project reports all PASS with no fix prompts
 </success_criteria>

package/commands/ms/execute-phase.md

@@ -32,6 +32,7 @@ Phase: $ARGUMENTS
 
 **Resolve phase:**
 ```bash
+# ms-tools is on PATH — invoke directly, not as a script path
 ms-tools find-phase "$ARGUMENTS"
 ```
 
@@ -74,7 +75,6 @@ ms-tools find-phase "$ARGUMENTS"
    - Creates VERIFICATION.md with detailed report
    - Route by status:
      - `passed` → continue to step 7
-     - `human_needed` → present items, get approval or feedback
      - `gaps_found` → present gaps, offer `/ms:plan-phase {X} --gaps`
 
 7. **Code review (optional)**
@@ -118,9 +118,7 @@ ms-tools find-phase "$ARGUMENTS"
 13. **Offer next steps**
     - Route to next action (see `<offer_next>`)
 
-14. **Update last command**
-    - Update `.planning/STATE.md` Last Command field
-    - Format: `Last Command: ms:execute-phase $ARGUMENTS | YYYY-MM-DD HH:MM`
+14. **Update last command:** `ms-tools set-last-command "ms:execute-phase $ARGUMENTS"`
 </process>
 
 <offer_next>
@@ -143,7 +141,6 @@ Then route based on status:
 | Status | Route |
 |--------|-------|
 | `gaps_found` | Route C (gap closure) |
-| `human_needed` | Present checklist, then re-route based on approval |
 | `passed` + more phases | Route A (next phase) |
 | `passed` + last phase | Route B (milestone complete) |
 

package/commands/ms/help.md

@@ -84,9 +84,9 @@ Initialize new project with brief and configuration.
 Usage: `/ms:new-project`
 
 **`/ms:config`**
-Configure Mindsystem preferences — code reviewers, gitignore patterns, git remote.
+Configure Mindsystem preferences — code reviewers, mockup preferences, gitignore patterns, git remote.
 
-- Use when: you want to set up code review agents, manage which .planning/ artifacts are git-ignored, or push your repo to GitHub.
+- Use when: you want to set up code review agents, mockup open behavior, manage which .planning/ artifacts are git-ignored, or push your repo to GitHub.
 - Edits `.planning/config.json` and `.gitignore`
 - Suggests code reviewers based on tech stack (needs PROJECT.md)
 - Idempotent — run anytime to reconfigure

package/commands/ms/insert-phase.md

@@ -216,10 +216,9 @@ After the "Next Up" section, add:
 </step>
 
 <step name="update_last_command">
-Update `.planning/STATE.md` Last Command field:
-- Find line starting with `Last Command:` in Current Position section
-- Replace with: `Last Command: ms:insert-phase $ARGUMENTS | YYYY-MM-DD HH:MM`
-- If line doesn't exist, add it after `Status:` line
+```bash
+ms-tools set-last-command "ms:insert-phase $ARGUMENTS"
+```
 </step>
 
 </process>

package/commands/ms/map-codebase.md

@@ -60,8 +60,7 @@ Check for .planning/STATE.md - loads context if project already initialized
 5. Verify all 7 documents exist with line counts
 6. Commit codebase map
 7. Offer next steps (typically: /ms:new-project or /ms:plan-phase)
-8. Update `.planning/STATE.md` Last Command field (if STATE.md exists):
-   - Format: `Last Command: ms:map-codebase $ARGUMENTS | YYYY-MM-DD HH:MM`
+8. **Update last command:** `ms-tools set-last-command "ms:map-codebase $ARGUMENTS"`
 </process>
 
 <success_criteria>

package/commands/ms/new-milestone.md

@@ -301,9 +301,7 @@ Milestone name: $ARGUMENTS (optional — will emerge during discovery if not pro
     ---
     ```
 
-20. **Update last command:**
-    - Update `.planning/STATE.md` Last Command field
-    - Format: `Last Command: ms:new-milestone $ARGUMENTS | YYYY-MM-DD HH:MM`
+20. **Update last command:** `ms-tools set-last-command "ms:new-milestone $ARGUMENTS"`
 
 </process>
 

package/commands/ms/new-project.md

@@ -265,11 +265,9 @@ Project updated:
 </step>
 
 <step name="update_last_command">
-Update `.planning/STATE.md` Last Command field (if STATE.md exists):
-- Find line starting with `Last Command:` in Current Position section
-- Replace with: `Last Command: ms:new-project | YYYY-MM-DD HH:MM`
-- If line doesn't exist, add it after `Status:` line
-- Note: STATE.md may not exist yet if this is the first command
+```bash
+ms-tools set-last-command "ms:new-project"
+```
 </step>
 
 </process>

package/commands/ms/plan-milestone-gaps.md

@@ -195,10 +195,9 @@ git commit -m "docs(roadmap): add gap closure phases {N}-{M}"
 
 ## 10. Update Last Command
 
-Update `.planning/STATE.md` Last Command field:
-- Find line starting with `Last Command:` in Current Position section
-- Replace with: `Last Command: ms:plan-milestone-gaps | YYYY-MM-DD HH:MM`
-- If line doesn't exist, add it after `Status:` line
+```bash
+ms-tools set-last-command "ms:plan-milestone-gaps"
+```
 
 </process>
 

package/commands/ms/plan-phase.md

@@ -36,6 +36,7 @@ Gap closure mode: `--gaps` flag triggers gap closure workflow
 
 **Resolve phase if provided:**
 ```bash
+# ms-tools is on PATH — invoke directly, not as a script path
 PHASE_ARG=$(echo "$ARGUMENTS" | grep -oE '^[0-9]+' | head -1)
 if [ -n "$PHASE_ARG" ]; then
   ms-tools find-phase "$PHASE_ARG"
@@ -104,9 +105,7 @@ Check for `.planning/codebase/` and load relevant documents based on phase type.
    - Number plans sequentially after existing (if 01-03 exist, create 04, 05...)
    - Create PLAN.md file(s) focused on closing specific gaps
 
-6. **Update last command**
-   - Update `.planning/STATE.md` Last Command field
-   - Format: `Last Command: ms:plan-phase $ARGUMENTS | YYYY-MM-DD HH:MM`
+6. **Update last command:** `ms-tools set-last-command "ms:plan-phase $ARGUMENTS"`
 
 7. **Risk assessment** (skip if `--gaps` flag present)
    - Calculate risk score from context already loaded (task count, plan count, external services, CONTEXT.md, cross-cutting concerns, new deps, complex domains)

package/commands/ms/progress.md

@@ -129,6 +129,7 @@ DESIGN: [✓ if DESIGN.md exists | - if not]
 List files in the current phase directory:
 
 ```bash
+# ms-tools is on PATH — invoke directly, not as a script path
 ms-tools list-artifacts [current-phase-number]
 ```
 

package/commands/ms/remove-phase.md

@@ -298,10 +298,9 @@ Would you like to:
 </step>
 
 <step name="update_last_command">
-Update `.planning/STATE.md` Last Command field:
-- Find line starting with `Last Command:` in Current Position section
-- Replace with: `Last Command: ms:remove-phase $ARGUMENTS | YYYY-MM-DD HH:MM`
-- If line doesn't exist, add it after `Status:` line
+```bash
+ms-tools set-last-command "ms:remove-phase $ARGUMENTS"
+```
 </step>
 
 </process>

package/commands/ms/research-phase.md

@@ -21,6 +21,7 @@ Phase number: $ARGUMENTS (required)
 
 **Resolve phase:**
 ```bash
+# ms-tools is on PATH — invoke directly, not as a script path
 ms-tools find-phase "$ARGUMENTS"
 ```
 
@@ -323,10 +324,9 @@ If any section has LOW confidence or significant open questions, flag the weak a
 
 ## 8. Update Last Command
 
-Update `.planning/STATE.md` Last Command field:
-- Find line starting with `Last Command:` in Current Position section
-- Replace with: `Last Command: ms:research-phase $ARGUMENTS | YYYY-MM-DD HH:MM`
-- If line doesn't exist, add it after `Status:` line
+```bash
+ms-tools set-last-command "ms:research-phase $ARGUMENTS"
+```
 
 </process>
 

package/commands/ms/research-project.md

@@ -299,18 +299,12 @@ Create SUMMARY.md with:
 - Confidence assessment
 - Gaps to address
 
-After creating SUMMARY.md, update config.json code_review fields with agent names:
-1. Read recommended stack from STACK.md
-2. Map to code review agent names:
-   - Flutter/Dart:
-     - adhoc: \"ms-flutter-code-quality\"
-     - phase: \"ms-flutter-code-quality\"
-     - milestone: \"ms-flutter-reviewer\"
-   - All others:
-     - adhoc: \"ms-code-simplifier\"
-     - phase: \"ms-code-simplifier\"
-     - milestone: (leave as null)
-3. Update .planning/config.json (create from template if needed)
+After creating SUMMARY.md, update config.json code_review fields with default agent names:
+1. Default for all frameworks:
+   - adhoc: \"ms-code-simplifier\"
+   - phase: \"ms-code-simplifier\"
+   - milestone: null
+2. Update .planning/config.json (create from template if needed)
 
 Then commit ALL research files together:
 git add .planning/research/
@@ -343,10 +337,9 @@ Key findings:
 
 ## 8. Update Last Command
 
-Update `.planning/STATE.md` Last Command field:
-- Find line starting with `Last Command:` in Current Position section
-- Replace with: `Last Command: ms:research-project | YYYY-MM-DD HH:MM`
-- If line doesn't exist, add it after `Status:` line
+```bash
+ms-tools set-last-command "ms:research-project"
+```
 
 </process>
 

package/commands/ms/review-design.md

@@ -76,7 +76,7 @@ Before analyzing, establish what this screen is trying to accomplish.
 - Read `.planning/PROJECT.md` for product type, core value, target audience
 - If phase-based, grep `.planning/ROADMAP.md` for phase requirements
 - Glob for existing DESIGN.md in `.planning/phases/` for design intent
-- Check available skills for one matching `*-ui` or `*-design` in name or description — if found, invoke via Skill tool for existing patterns
+- Scan available skills in system-reminder for matches related to UI, design, or the screen's platform/framework. If matches found, present via AskUserQuestion with `multiSelect: true`: each matching skill is one option (label: skill name, description: what it provides), always include a "None — skip skill loading" option. User selects which to load, skips, or types a skill name in the free-text field. Load selected skills via Skill tool for existing patterns.
 
 **State the screen's job in one sentence:**
 > "This screen helps the user [accomplish X]."
@@ -186,7 +186,9 @@ Run the app and check this screen — [describe the expected visual difference i
 
 ## Step 8: Update Last Command
 
-Run: `sed -i '' "s/^Last Command:.*/Last Command: ms:review-design $ARGUMENTS | $(date '+%Y-%m-%d %H:%M')/" .planning/STATE.md`
+```bash
+ms-tools set-last-command "ms:review-design $ARGUMENTS"
+```
 
 </process>
 

package/commands/ms/verify-work.md

@@ -47,10 +47,10 @@ Phase: $ARGUMENTS (optional)
 7. **For each batch:**
    - If mock needed: Apply inline mocks (1-4 direct edits, 5+ via ms-mock-generator subagent), tell user to hot reload
    - Present tests via AskUserQuestion (Pass / Can't test / Skip / Other)
-   - Process results, update UAT.md
+   - Process results — UAT.md updates happen via `ms-tools uat-update` (auto-recalculates progress)
    - **For each issue found:**
      - Lightweight investigation (2-3 tool calls)
-     - If simple: Fix inline, commit, ask for re-test
+     - If simple: Fix inline, commit (amend previous fix commit on retry when HEAD matches fix_commit), ask for re-test
      - If complex: Spawn ms-verify-fixer subagent
      - 2 retries on failed re-test, then offer options
 8. **On batch transition:**
@@ -60,14 +60,10 @@ Phase: $ARGUMENTS (optional)
    - Revert all mocks (`git checkout -- <mocked_files>`)
    - Generate UAT fixes patch
    - Restore user's pre-existing work (if stashed)
-   - Commit UAT.md, present summary
+   - Commit UAT.md + STATE.md together in one completion commit, present summary
    - **Update knowledge pitfalls** — if significant UAT issues (blocker/major) were fixed, append pitfall entries to relevant knowledge files
 
-10. **Update last command**
-    - Update `.planning/STATE.md` Last Command field
-    - Format: `Last Command: ms:verify-work $ARGUMENTS | YYYY-MM-DD HH:MM`
-
-11. **Present next steps**
+10. **Present next steps**
     - If this was the last phase in milestone: suggest `/ms:audit-milestone`
     - If more phases remain: Read `~/.claude/mindsystem/references/routing/next-phase-routing.md` and follow its instructions to present "Next Up" with pre-work context for the next phase
 </process>
@@ -80,6 +76,8 @@ Phase: $ARGUMENTS (optional)
 - Don't fix complex issues inline — spawn fixer subagent for multi-file or architectural changes
 - Don't commit mock code — stash mocked files before fixing, restore after
 - Don't re-present skipped tests — assumptions stand
+- Don't Read/Edit UAT.md for field updates — use `ms-tools uat-update`
+- Don't create separate commits for retry fixes — amend previous fix commit when HEAD matches fix_commit
 </anti_patterns>
 
 <success_criteria>

package/mindsystem/references/verification-patterns.md

@@ -556,40 +556,3 @@ Run these checks against each must-have artifact. Aggregate results into VERIFIC
 
 </automated_verification_script>
 
-<human_verification_triggers>
-
-## When to Require Human Verification
-
-Some things can't be verified programmatically. Flag these for human testing:
-
-**Always human:**
-- Visual appearance (does it look right?)
-- User flow completion (can you actually do the thing?)
-- Real-time behavior (WebSocket, SSE)
-- External service integration (Stripe, email sending)
-- Error message clarity (is the message helpful?)
-- Performance feel (does it feel fast?)
-
-**Human if uncertain:**
-- Complex wiring that grep can't trace
-- Dynamic behavior depending on state
-- Edge cases and error states
-- Mobile responsiveness
-- Accessibility
-
-**Format for human verification request:**
-```markdown
-## Human Verification Required
-
-### 1. Chat message sending
-**Test:** Type a message and click Send
-**Expected:** Message appears in list, input clears
-**Check:** Does message persist after refresh?
-
-### 2. Error handling
-**Test:** Disconnect network, try to send
-**Expected:** Error message appears, message not lost
-**Check:** Can retry after reconnect?
-```
-
-</human_verification_triggers>

package/mindsystem/templates/config.json

@@ -4,5 +4,6 @@
     "adhoc": null,
     "phase": null,
     "milestone": null
-  }
+  },
+  "open_mockups": "auto"
 }

package/mindsystem/templates/roadmap.md

@@ -135,7 +135,7 @@ Phases execute in numeric order: 2 → 2.1 → 2.2 → 3 → 3.1 → 4
 - 2-5 observable behaviors per phase (from user's perspective)
 - Cross-checked against requirements during roadmap creation
 - Flow downstream to `## Must-Haves` in plan-phase
-- Verified by verify-phase after execution
+- Verified by ms-verifier agent after execution
 - Format: "User can [action]" or "[Thing] works/exists"
 
 **Pre-work indicators** (all use Likely/Unlikely with parenthetical reason):

package/mindsystem/templates/state.md

@@ -115,8 +115,8 @@ STATE.md is the project's short-term memory spanning all phases and sessions.
 - adhoc: After adhoc work completed
   - Add entry to "Recent Adhoc Work" section
   - Keep last 5 entries (older entries remain in .planning/adhoc/)
-- Any state-changing command: Update Last Command field
-  - Format: `ms:{command} {args} | YYYY-MM-DD HH:MM`
+- Any state-changing command: `ms-tools set-last-command "ms:{command} {args}"`
+  - Appends real local timestamp via `datetime.now()`
   - Enables status line to show context without running /ms:progress
 
 </lifecycle>

package/mindsystem/templates/verification-report.md

@@ -10,15 +10,16 @@ Template for `.planning/phases/XX-name/{phase}-VERIFICATION.md` — phase goal v
 ---
 phase: XX-name
 verified: YYYY-MM-DDTHH:MM:SSZ
-status: passed | gaps_found | human_needed
+status: passed | gaps_found
 score: N/M must-haves verified
+uncertain: N  # UNCERTAIN truths + NEEDS HUMAN requirements
 ---
 
 # Phase {X}: {Name} Verification Report
 
 **Phase Goal:** {goal from ROADMAP.md}
 **Verified:** {timestamp}
-**Status:** {passed | gaps_found | human_needed}
+**Status:** {passed | gaps_found}
 
 ## Goal Achievement
 
@@ -72,23 +73,6 @@ score: N/M must-haves verified
 
 **Anti-patterns:** {N} found ({blockers} blockers, {warnings} warnings)
 
-## Human Verification Required
-
-{If no human verification needed:}
-None — all verifiable items checked programmatically.
-
-{If human verification needed:}
-
-### 1. {Test Name}
-**Test:** {What to do}
-**Expected:** {What should happen}
-**Why human:** {Why can't verify programmatically}
-
-### 2. {Test Name}
-**Test:** {What to do}
-**Expected:** {What should happen}
-**Why human:** {Why can't verify programmatically}
-
 ## Gaps Summary
 
 {If no gaps:}
@@ -149,7 +133,6 @@ None — all verifiable items checked programmatically.
 **Verification approach:** Goal-backward (derived from phase goal)
 **Must-haves source:** {PLAN.md ## Must-Haves section | derived from ROADMAP.md goal}
 **Automated checks:** {N} passed, {M} failed
-**Human checks required:** {N}
 **Total verification time:** {duration}
 
 ---
@@ -164,7 +147,6 @@ None — all verifiable items checked programmatically.
 **Status values:**
 - `passed` — All must-haves verified, no blockers
 - `gaps_found` — One or more critical gaps found
-- `human_needed` — Automated checks pass but human verification required
 
 **Evidence types:**
 - For EXISTS: "File at path, exports X"
@@ -257,10 +239,6 @@ score: 2/5 must-haves verified
 
 **Anti-patterns:** 3 found (2 blockers, 1 warning)
 
-## Human Verification Required
-
-None needed until automated gaps are fixed.
-
 ## Gaps Summary
 
 ### Critical Gaps (Block Progress)
@@ -313,7 +291,6 @@ None needed until automated gaps are fixed.
 **Verification approach:** Goal-backward (derived from phase goal)
 **Must-haves source:** 03-01-PLAN.md ## Must-Haves section
 **Automated checks:** 2 passed, 8 failed
-**Human checks required:** 0 (blocked by automated failures)
 **Total verification time:** 2 min
 
 ---

package/mindsystem/workflows/discuss-phase.md

@@ -130,6 +130,10 @@ Use AskUserQuestion:
 Spawn ms-product-researcher subagent via Task tool:
 
 ```
+<current_date>
+[Output of: date +%Y-%m]
+</current_date>
+
 <product_context>
 [Who It's For, Core Value, How It's Different from PROJECT.md]
 </product_context>
@@ -320,9 +324,9 @@ Read `~/.claude/mindsystem/references/prework-status.md` and present what's done
 </step>
 
 <step name="update_state">
-Update `.planning/STATE.md` Last Command field:
-
-Format: `Last Command: ms:discuss-phase ${PHASE} | YYYY-MM-DD HH:MM`
+```bash
+ms-tools set-last-command "ms:discuss-phase ${PHASE}"
+```
 </step>
 
 </process>

package/mindsystem/workflows/execute-phase.md

@@ -274,34 +274,18 @@ grep "^status:" "$PHASE_DIR"/*-VERIFICATION.md | cut -d: -f2 | tr -d ' '
 | Status | Action |
 |--------|--------|
 | `passed` | Continue to code_review |
-| `human_needed` | Present items to user, get approval or feedback |
 | `gaps_found` | Present gap summary, offer `/ms:plan-phase {phase} --gaps` |
 
 **If passed:**
 
 Phase goal verified. Proceed to code_review.
 
-**If human_needed:**
+If the verifier's return includes "Items Not Verified Programmatically" (uncertain > 0), surface that section to the user before proceeding:
 
 ```markdown
-## ✓ Phase {X}: {Name} — Human Verification Required
-
-All automated checks passed. {N} items need human testing:
-
-### Human Verification Checklist
-
-{Extract from VERIFICATION.md human_verification section}
-
----
-
-**After testing:**
-- "approved" → continue to code_review
-- Report issues → will route to gap closure planning
+**Note:** {N} items could not be verified by structural checks alone. Consider `/ms:verify-work {phase}` to validate these through UAT.
 ```
 
-If user approves → continue to code_review.
-If user reports issues → treat as gaps_found.
-
 **If gaps_found:**
 
 Present gaps and offer next command:

package/mindsystem/workflows/map-codebase.md

@@ -96,18 +96,12 @@ Write these documents to .planning/codebase/:
 - STACK.md - Languages, runtime, frameworks, dependencies, configuration
 - INTEGRATIONS.md - External APIs, databases, auth providers, webhooks
 
-After writing STACK.md, update config.json code_review fields with the appropriate agent names:
-1. Read STACK.md to detect primary framework
-2. Map framework to code review agent names:
-   - Flutter/Dart:
-     - adhoc: "ms-flutter-code-quality"
-     - phase: "ms-flutter-code-quality"
-     - milestone: "ms-flutter-reviewer"
-   - All others (React, Next.js, Node, Swift, Kotlin, etc.):
-     - adhoc: "ms-code-simplifier"
-     - phase: "ms-code-simplifier"
-     - milestone: (leave as null — runtime defaults to ms-flutter-reviewer)
-3. If .planning/config.json exists: update all three code_review fields
+After writing STACK.md, update config.json code_review fields with the default agent names:
+1. Default for all frameworks:
+   - adhoc: "ms-code-simplifier"
+   - phase: "ms-code-simplifier"
+   - milestone: null
+2. If .planning/config.json exists: update all three code_review fields
    If not: note the recommended code review agents for later config creation
 
 Explore thoroughly. Write documents directly using templates. Return confirmation only.