@hanzlaa/rcode 2.2.0 → 2.3.2

package/rihal/team.yaml

@@ -6,6 +6,7 @@ agents:
   - id: rihal-sadiq
     name: Sadiq (صادق)
     file_path: rihal/agents/rihal-sadiq.md
+    skill_path: rihal/skills/agents/sadiq-analyst
     role: Director of Strategy
     authority_level: strategic
     domain_keywords:
@@ -21,6 +22,7 @@ agents:
   - id: rihal-waleed
     name: Waleed (وليد)
     file_path: rihal/agents/rihal-waleed.md
+    skill_path: rihal/skills/agents/waleed-architect
     role: Chief Technology Officer
     authority_level: technical
     domain_keywords:
@@ -38,6 +40,7 @@ agents:
   - id: rihal-fatima
     name: Fatima (فاطمة)
     file_path: rihal/agents/rihal-fatima.md
+    skill_path: rihal/skills/agents/fatima-qa
     role: QA Lead
     authority_level: quality
     domain_keywords:
@@ -54,6 +57,7 @@ agents:
   - id: rihal-mariam
     name: Mariam (مريم)
     file_path: rihal/agents/rihal-mariam.md
+    skill_path: rihal/skills/agents/mariam-marketing
     role: Marketing & Growth Lead
     authority_level: growth
     domain_keywords:
@@ -69,6 +73,7 @@ agents:
   - id: rihal-hussain-pm
     name: Hussain (حسين)
     file_path: rihal/agents/rihal-hussain-pm.md
+    skill_path: rihal/skills/agents/hussain-pm
     role: Product Manager
     authority_level: product
     domain_keywords:
@@ -97,6 +102,7 @@ agents:
   - id: rihal-yousef
     name: Yousef (يوسف)
     file_path: rihal/agents/rihal-yousef.md
+    skill_path: rihal/skills/agents/yousef-backend
     role: Senior Backend Engineer
     authority_level: technical
     domain_keywords:
@@ -115,6 +121,7 @@ agents:
   - id: rihal-haitham
     name: Haitham (هيثم)
     file_path: rihal/agents/rihal-haitham.md
+    skill_path: rihal/skills/agents/haitham-frontend
     role: Senior Frontend Engineer
     authority_level: technical
     domain_keywords:
@@ -132,6 +139,7 @@ agents:
   - id: rihal-zayd
     name: Zayd (زيد)
     file_path: rihal/agents/rihal-zayd.md
+    skill_path: rihal/skills/agents/zayd-ml
     role: Senior ML Engineer
     authority_level: technical
     domain_keywords:
@@ -150,6 +158,7 @@ agents:
   - id: rihal-layla
     name: Layla (ليلى)
     file_path: rihal/agents/rihal-layla.md
+    skill_path: rihal/skills/agents/layla-designer
     role: UX Designer
     authority_level: design
     domain_keywords:
@@ -166,6 +175,7 @@ agents:
   - id: rihal-zahra
     name: Zahra (زهرة)
     file_path: rihal/agents/rihal-zahra.md
+    skill_path: rihal/skills/agents/zahra-branding
     role: Branding & Creative Director
     authority_level: design
     domain_keywords:
@@ -182,6 +192,7 @@ agents:
   - id: rihal-nasser
     name: Nasser (ناصر)
     file_path: rihal/agents/rihal-nasser.md
+    skill_path: rihal/skills/agents/nasser-eng-manager
     role: Software Engineering Manager
     authority_level: management
     domain_keywords:
@@ -215,6 +226,7 @@ agents:
   - id: rihal-noor
     name: Noor (نور)
     file_path: rihal/agents/rihal-noor.md
+    skill_path: rihal/skills/agents/noor-writer
     role: Technical Writer & Presentation Lead
     authority_level: operational
     domain_keywords:
@@ -231,6 +243,7 @@ agents:
   - id: rihal-ahmed
     name: Ahmed Al Hassani (أحمد الحسني)
     file_path: rihal/agents/rihal-ahmed.md
+    skill_path: rihal/skills/agents/ahmed-hassani-director
     role: Technology & Development Director
     authority_level: strategic
     domain_keywords:
@@ -246,6 +259,7 @@ agents:
   - id: rihal-hanzla
     name: Hanzla (حنظلة)
     file_path: rihal/agents/rihal-hanzla.md
+    skill_path: rihal/skills/agents/hanzla-engineer
     role: Senior Full-Stack Engineer
     authority_level: technical
     domain_keywords:
@@ -341,3 +355,194 @@ routing:
     - rihal-hussain-pm  # scope
     - rihal-waleed      # feasibility
     - rihal-sadiq       # strategic fit
+
+# Tactical / Workflow Agents (spawned by workflows)
+tactical_agents:
+  - id: rihal-advisor-researcher
+    name: Advisor Researcher
+    file_path: rihal/agents/rihal-advisor-researcher.md
+    role: Advisor Researcher
+    authority_level: research
+    description: Advisor-level deep research for gray-area decisions
+
+  - id: rihal-architect
+    name: Architect
+    file_path: rihal/agents/rihal-architect.md
+    role: Architect
+    authority_level: technical
+    description: Enterprise architecture and system design reviews
+
+  - id: rihal-assumptions-analyzer
+    name: Assumptions Analyzer
+    file_path: rihal/agents/rihal-assumptions-analyzer.md
+    role: Assumptions Analyzer
+    authority_level: analysis
+    description: Analyzes phase assumptions with evidence from codebase
+
+  - id: rihal-code-fixer
+    name: Code Fixer
+    file_path: rihal/agents/rihal-code-fixer.md
+    role: Code Fixer
+    authority_level: implementation
+    description: Applies code review findings and implements fixes
+
+  - id: rihal-code-reviewer
+    name: Code Reviewer
+    file_path: rihal/agents/rihal-code-reviewer.md
+    role: Code Reviewer
+    authority_level: quality
+    description: Reviews code for bugs, security issues, quality problems
+
+  - id: rihal-codebase-mapper
+    name: Codebase Mapper
+    file_path: rihal/agents/rihal-codebase-mapper.md
+    role: Codebase Mapper
+    authority_level: analysis
+    description: Explores and documents codebase architecture
+
+  - id: rihal-debugger
+    name: Debugger
+    file_path: rihal/agents/rihal-debugger.md
+    role: Debugger
+    authority_level: implementation
+    description: Investigates bugs using scientific method
+
+  - id: rihal-deviation-analyzer
+    name: Deviation Analyzer
+    file_path: rihal/agents/rihal-deviation-analyzer.md
+    role: Deviation Analyzer
+    authority_level: analysis
+    description: Analyzes plan deviations and root causes
+
+  - id: rihal-docs-auditor
+    name: Docs Auditor
+    file_path: rihal/agents/rihal-docs-auditor.md
+    role: Docs Auditor
+    authority_level: quality
+    description: Audits documentation completeness and accuracy
+
+  - id: rihal-edge-case-hunter
+    name: Edge Case Hunter
+    file_path: rihal/agents/rihal-edge-case-hunter.md
+    role: Edge Case Hunter
+    authority_level: quality
+    description: Enumerates edge cases and boundary conditions
+
+  - id: rihal-executor
+    name: Executor
+    file_path: rihal/agents/rihal-executor.md
+    role: Executor
+    authority_level: implementation
+    description: Executes sprint plans with atomic commits
+
+  - id: rihal-integration-checker
+    name: Integration Checker
+    file_path: rihal/agents/rihal-integration-checker.md
+    role: Integration Checker
+    authority_level: quality
+    description: Verifies cross-phase integration and E2E flows
+
+  - id: rihal-nyquist-auditor
+    name: Nyquist Auditor
+    file_path: rihal/agents/rihal-nyquist-auditor.md
+    role: Nyquist Auditor
+    authority_level: quality
+    description: Fills test coverage gaps for phase requirements
+
+  - id: rihal-phase-researcher
+    name: Phase Researcher
+    file_path: rihal/agents/rihal-phase-researcher.md
+    role: Phase Researcher
+    authority_level: research
+    description: Researches how to implement a phase before planning
+
+  - id: rihal-planner
+    name: Planner
+    file_path: rihal/agents/rihal-planner.md
+    role: Planner
+    authority_level: planning
+    description: Creates executable phase plans with task breakdown
+
+  - id: rihal-profiler
+    name: Profiler
+    file_path: rihal/agents/rihal-profiler.md
+    role: Profiler
+    authority_level: analysis
+    description: Analyzes user behavior patterns and personas
+
+  - id: rihal-project-researcher
+    name: Project Researcher
+    file_path: rihal/agents/rihal-project-researcher.md
+    role: Project Researcher
+    authority_level: research
+    description: Researches domain ecosystem before roadmap creation
+
+  - id: rihal-remediation-planner
+    name: Remediation Planner
+    file_path: rihal/agents/rihal-remediation-planner.md
+    role: Remediation Planner
+    authority_level: planning
+    description: Plans remediation for issues and blockers
+
+  - id: rihal-research-synthesizer
+    name: Research Synthesizer
+    file_path: rihal/agents/rihal-research-synthesizer.md
+    role: Research Synthesizer
+    authority_level: research
+    description: Synthesizes parallel research outputs into summary
+
+  - id: rihal-roadmapper
+    name: Roadmapper
+    file_path: rihal/agents/rihal-roadmapper.md
+    role: Roadmapper
+    authority_level: planning
+    description: Creates project roadmaps with phase breakdown
+
+  - id: rihal-security-adversary
+    name: Security Adversary
+    file_path: rihal/agents/rihal-security-adversary.md
+    role: Security Adversary
+    authority_level: security
+    description: Adversarial security review and threat modeling
+
+  - id: rihal-security-auditor
+    name: Security Auditor
+    file_path: rihal/agents/rihal-security-auditor.md
+    role: Security Auditor
+    authority_level: security
+    description: Comprehensive security audit and compliance verification
+
+  - id: rihal-sprint-checker
+    name: Sprint Checker
+    file_path: rihal/agents/rihal-sprint-checker.md
+    role: Sprint Checker
+    authority_level: quality
+    description: Verifies sprint plans before execution
+
+  - id: rihal-ui-auditor
+    name: UI Auditor
+    file_path: rihal/agents/rihal-ui-auditor.md
+    role: UI Auditor
+    authority_level: quality
+    description: Audits UI for usability and design quality
+
+  - id: rihal-ux-designer
+    name: UX Designer
+    file_path: rihal/agents/rihal-ux-designer.md
+    role: UX Designer
+    authority_level: design
+    description: UX design, accessibility, and design system work
+
+  - id: rihal-plan-checker
+    name: Plan Checker
+    file_path: rihal/agents/rihal-sprint-checker.md
+    role: Plan Checker
+    authority_level: quality
+    description: Validates PLAN.md/SPRINT.md quality before execution (alias for sprint-checker)
+
+  - id: rihal-verifier
+    name: Verifier
+    file_path: rihal/agents/rihal-verifier.md
+    role: Verifier
+    authority_level: quality
+    description: Verifies phase goal achievement goal-backward

package/rihal/templates/UAT.md

@@ -0,0 +1,29 @@
+# UAT — {{phase_name}}
+
+**Phase:** {{phase_id}}
+**Generated:** {{date}}
+
+## How to use
+
+For each scenario below, mark status: ✅ pass | ❌ fail | ⏸ skipped |
+🔍 needs-human. Add notes inline.
+
+## Scenarios
+
+### Scenario 1: {{golden path title}}
+
+**Steps:**
+1. {{action}}
+2. {{action}}
+
+**Expected:** {{outcome}}
+**Status:** ⏸
+**Notes:**
+
+### Scenario 2: {{edge case title}}
+
+(Repeat as needed.)
+
+## Outstanding items
+
+Items left as ⏸ or 🔍 carry forward to the next milestone audit.

package/rihal/templates/milestone.md

@@ -1,5 +1,7 @@
 # Milestone Template
 
+<!-- P2: Omit any section with nothing substantive. Empty sections are noise. Omit STATE.md blockers/workstreams if none active. Omit REQUIREMENTS.md out-of-scope if it doesn't constrain execution. -->
+
 Use this template when starting a new milestone with `/rihal:new-milestone`.
 
 ## ROADMAP.md

package/rihal/templates/sprint.md

@@ -1,70 +1,53 @@
 # Sprint {sprint_id} — {sprint_goal}
 
+<!-- P2: Omit Dependencies and Risks sections if empty. Omit Retrospective until sprint is complete. -->
+
 **Phase:** {phase_number} — {phase_name}
 **Status:** {status}
 **Velocity target:** {velocity_target} points
 **Started:** {started_at}
 
----
-
 ## Sprint Goal
 
 {sprint_goal}
 
----
-
 ## Stories
 
-| ID | Title | Points | Status | Acceptance |
-|----|-------|--------|--------|------------|
-| {story_id} | {title} | {points} | {status} | {acceptance} |
-
----
+| ID | Title | Points | Status | Done when |
+|----|-------|--------|--------|-----------|
+| {story_id} | {title} | {points} | {status} | {verifiable_ac} |
 
 ## Capacity
 
 - **Velocity target:** {velocity_target} points
-- **Average velocity (last 3):** {avg_velocity} points
 - **Total committed:** {total_points} points
 - **Buffer:** {buffer_points} points ({buffer_pct}%)
 
----
-
+<!-- Omit if no cross-story dependencies exist -->
 ## Dependencies
 
 | Story | Depends on | Status |
 |-------|-----------|--------|
-| | | |
-
----
 
+<!-- Omit if no risks identified -->
 ## Risks
 
 | Risk | Impact | Mitigation |
 |------|--------|------------|
-| | | |
 
----
-
-## Sprint Review Notes
-
-_Filled at sprint completion._
+## Sprint Review
 
+<!-- Fill at sprint completion only — omit this section until then -->
 - Stories completed: {done_count}/{total_count}
 - Velocity actual: {velocity_actual} points
-- Carryover stories: {carryover}
-
----
+- Carryover: {carryover}
 
 ## Retrospective
 
-_Filled at sprint completion._
-
+<!-- Fill at sprint completion only — omit this section until then -->
 ### What went well
 -
-
 ### What didn't
 -
-
 ### Action items
 -

package/rihal/templates/summary.md

@@ -0,0 +1,30 @@
+# Phase Summary — {{phase_name}}
+
+<!-- P2: Omit any section that has nothing substantive to say. An empty section is worse than no section. -->
+
+**Phase ID:** {{phase_id}}
+**Closed:** {{closed_at}}
+**Plan:** PLAN.md
+
+## Outcomes
+
+- {{what was built, in user-visible terms}}
+
+## Decisions Made
+
+<!-- Omit if no decisions were made that aren't already in PLAN.md -->
+- {{key choices and their rationale}}
+
+## Deviations from Plan
+
+<!-- Omit if execution matched the plan exactly -->
+- {{anything that diverged from PLAN.md and why}}
+
+## Issues Encountered
+
+<!-- Omit if no tasks were pruned, escalated, or skipped -->
+- {{tasks pruned, escalated, or skipped}}
+
+## Hand-off
+
+Next phase: {{next phase id and goal}}

package/rihal/templates/verification-report.md

@@ -0,0 +1,28 @@
+# Verification Report — {{phase_name}}
+
+**Phase:** {{phase_id}}
+**Verified:** {{date}}
+**Verifier:** rihal-verifier
+
+## Goal-backward check
+
+**Original goal:** {{phase goal from PLAN.md}}
+
+**Met?** ✅ / ◐ partial / ❌ not met
+
+**Evidence:**
+- {{file:line or test name proving the goal is met}}
+
+## Per-task verification
+
+| # | Task | Status | Evidence |
+|---|------|--------|----------|
+| 1 | {{task}} | ✅ | {{evidence}} |
+
+## Gaps
+
+- {{what wasn't delivered + why}}
+
+## Recommendation
+
+- proceed / revise / block

package/rihal/workflows/audit-milestone.md

@@ -140,13 +140,45 @@ If `--report` flag set, also print the report to stdout. Otherwise, just save to
 
 ## On Error
 
-If no SUMMARY.md files found:
+If no SUMMARY.md files found, **do not dead-halt** (closes #234). Probe
+for executed-phase signals and offer recovery options:
 
+```bash
+PLANS=$(find "$MILESTONE_DIR" -name PLAN.md 2>/dev/null | wc -l)
+GIT_FEAT=$(git log --oneline --grep='^feat' 2>/dev/null | wc -l)
+APPS=$(ls -d apps packages src 2>/dev/null | wc -l)
 ```
-⚠ No phase summaries found. Have phases been executed?
+
+If `PLANS > 0` AND (`GIT_FEAT > 0` OR `APPS > 0`):
+
+```
+⚠ {PLANS} phases planned, 0 SUMMARY.md, {GIT_FEAT} feat commits, code present.
+  Phases were executed but never formally closed.
+
+  Options:
+    1. Synthesize SUMMARY.md per phase from PLAN.md + git log [recommended]
+       (groups commits by phase tag like "feat(03-1):", writes a
+        first-pass SUMMARY.md the user can edit)
+    2. Run /rihal:verify-phase NN per phase (manual close path)
+    3. Continue audit anyway (only assesses what is documented — likely
+       reports 0% goal coverage)
+    0. Cancel
+```
+
+In `mode: yolo` (read via `node .rihal/bin/rihal-tools.cjs config-get
+mode`), auto-pick option 1. In guided mode, ask. STOP after the user
+picks 0 or 2; resume audit at Step 4 after option 1 completes.
+
+If `PLANS == 0`:
+
+```
+⚠ No phase summaries and no plans found. Have phases been executed?
   Check: {MILESTONE_DIR}/phases/
+  Start one: /rihal:plan
 ```
 
+STOP.
+
 If ROADMAP missing:
 
 ```

package/rihal/workflows/audit.md

@@ -0,0 +1,172 @@
+# Workflow: rihal:audit
+
+<purpose>
+Single entry point for every kind of audit. Asks the user *what* to audit
+and dispatches to the right sub-workflow. Closes #234 — replaces the prior
+state where users had to know about six separate audit/verify commands by
+name (`audit-milestone`, `audit-uat`, `audit-fix`, `karpathy-audit`,
+`verify-phase`, `verify-work`).
+
+Honours `.rihal/config.yaml`: in `mode: yolo`, the router skips the menu
+and auto-picks the most-relevant target based on project state. In
+`mode: guided` (default), it asks.
+</purpose>
+
+## Step 0 — Usage check
+
+If `$ARGUMENTS` contains `--help` or `-h`:
+
+```
+/rihal:audit                       # interactive — asks what to audit
+/rihal:audit phase [<NN>]          # → /rihal:verify-phase
+/rihal:audit milestone [--strict]  # → /rihal:audit-milestone (with synth fallback)
+/rihal:audit uat                   # → /rihal:audit-uat
+/rihal:audit code [--scope=...]    # → /rihal:karpathy-audit
+/rihal:audit fix                   # → /rihal:audit-fix
+/rihal:audit work                  # → /rihal:verify-work
+```
+
+**Examples:**
+```
+/rihal:audit
+/rihal:audit milestone --strict
+/rihal:audit phase 03
+```
+
+## Step 1 — Resolve mode + arguments
+
+```bash
+TOOL="node .rihal/bin/rihal-tools.cjs"
+MODE=$($TOOL config-get mode 2>/dev/null || echo "guided")
+DISCUSS=$($TOOL config-get workflow.discuss_mode 2>/dev/null || echo "adaptive")
+```
+
+Parse `$ARGUMENTS`:
+- First word ∈ {phase, milestone, uat, code, fix, work} → set `$TARGET`, drop it from args, jump to Step 4.
+- Empty or unrecognised → continue to Step 2.
+
+## Step 2 — Detect project state
+
+Probe what's audit-able right now:
+
+```bash
+ROADMAP=$([ -f .planning/ROADMAP.md ] && echo yes || echo no)
+PHASES=$(ls -d .planning/phases/*/ 2>/dev/null | wc -l)
+PLANS=$(find .planning/phases -name PLAN.md 2>/dev/null | wc -l)
+SUMMARIES=$(find .planning/phases -name SUMMARY.md 2>/dev/null | wc -l)
+UAT_FILES=$(find .planning -name 'UAT*.md' 2>/dev/null | wc -l)
+ON_BRANCH=$(git rev-parse --abbrev-ref HEAD 2>/dev/null)
+DIRTY=$([ -n "$(git status --porcelain 2>/dev/null)" ] && echo yes || echo no)
+```
+
+Use these to decide which menu options are *relevant* and which to mark
+as `(no data — skip)`.
+
+## Step 3 — Ask user (guided mode only)
+
+If `$MODE` is `yolo`, skip this step and pick the most relevant target
+automatically (priority: `work` if dirty branch, else `phase` if PLANS>0
+and SUMMARIES<PLANS, else `milestone` if SUMMARIES>0, else `code`).
+
+Otherwise call AskUserQuestion:
+
+```
+Question:
+What do you want to audit?
+
+Options:
+  1. phase           — verify a single phase against its PLAN  ({PLANS} plans)
+  2. milestone       — cross-phase milestone goal coverage     ({SUMMARIES} summaries)
+  3. uat             — outstanding UAT / verification items    ({UAT_FILES} files)
+  4. code-quality    — Karpathy 4-principle code review        (current diff)
+  5. auto-fix        — audit then auto-fix findings            (uses #1–4 output)
+  6. work            — verify current branch / WIP             ({ON_BRANCH}, dirty={DIRTY})
+  0. cancel
+```
+
+Set `$TARGET` from the user's choice.
+
+## Step 4 — Pre-flight per target
+
+Each target has a precondition. Fail loudly with the fix step *before*
+dispatching, so the user doesn't get a surprise halt deep inside the
+sub-workflow.
+
+| target | precondition | failure message |
+|---|---|---|
+| phase | at least one `.planning/phases/*/PLAN.md` | `No PLAN.md found. Run /rihal:plan first.` |
+| milestone | ROADMAP.md exists | `No ROADMAP.md. Run /rihal:new-milestone first.` |
+| uat | at least one UAT*.md exists | `No UAT files yet. Run /rihal:execute on a phase first.` |
+| code | git repo with at least one commit | `Empty repo — nothing to audit yet.` |
+| fix | a prior audit report exists OR a prior `--report` artefact | `No audit findings yet. Run /rihal:audit first.` |
+| work | inside a git worktree | `Not in a git repo.` |
+
+For `milestone` specifically, check the **graceful-degrade** condition
+(closes #234 audit-milestone halt):
+
+```bash
+if [ "$TARGET" = "milestone" ] && [ "$SUMMARIES" -eq 0 ] && [ "$PLANS" -gt 0 ]; then
+  # Phases planned but no formal closes — offer to synthesize.
+  GIT_FEAT_COMMITS=$(git log --oneline --grep='^feat' 2>/dev/null | wc -l)
+  echo "⚠ $PLANS phases planned, 0 SUMMARY.md, $GIT_FEAT_COMMITS feat commits."
+  echo "  Phases were executed but never formally closed."
+  # Offer (yolo: auto-pick 1; guided: ask):
+  #   1. Synthesize SUMMARY.md per phase from PLAN.md + git log    [recommended]
+  #   2. Run /rihal:verify-phase per phase (manual close)
+  #   3. Continue audit anyway (will only assess what's documented)
+  #   0. Cancel
+fi
+```
+
+In `mode: yolo`, auto-pick option 1: group `git log --oneline` output by
+phase tag (e.g. commits matching `^feat\(0?(\d+)`) and write a first-pass
+`SUMMARY.md` per phase under `.planning/phases/<phase>/SUMMARY.md`
+containing the goal (from PLAN.md), the commit list, and a `# TODO:
+expand outcomes` marker. The user can then refine before re-running the
+audit.
+
+A native `phase synthesize-summaries` CLI subcommand is tracked separately
+(see #234 follow-ups) — until it lands, the LLM performs the synthesis
+inline using `git log` + `Read PLAN.md` + `Write SUMMARY.md`.
+
+## Step 5 — Dispatch
+
+Run the target's slash command, forwarding remaining args:
+
+| target | dispatch |
+|---|---|
+| phase | `/rihal:verify-phase $REST_ARGS` |
+| milestone | `/rihal:audit-milestone $REST_ARGS` |
+| uat | `/rihal:audit-uat $REST_ARGS` |
+| code | `/rihal:karpathy-audit $REST_ARGS` |
+| fix | `/rihal:audit-fix $REST_ARGS` |
+| work | `/rihal:verify-work $REST_ARGS` |
+
+## Step 6 — Closing summary
+
+After the sub-workflow returns:
+
+```
+RIHAL ► AUDIT ({TARGET}) ✓
+
+Report: {report_path or "(stdout only)"}
+Findings: {count}
+
+Next:
+  /rihal:audit fix         — auto-fix findings classified as auto-fixable
+  /rihal:audit code        — drill into code-quality issues
+  /rihal:settings show     — review which audit gates are enabled
+```
+
+## Success Criteria
+
+- [ ] `/rihal:audit` (no args) presents menu in guided mode, auto-picks in yolo
+- [ ] `/rihal:audit milestone` short-circuits the menu
+- [ ] When SUMMARY.md absent but PLAN.md present, milestone offers synthesize/verify/skip — does not dead-halt
+- [ ] Sub-workflow's closing report is surfaced unchanged
+
+## On Error
+
+- **Sub-workflow not installed** (slash file missing): `Audit subroute '/rihal:{target}' not found. Run: npx @hanzlaa/rcode install .`
+- **Precondition failed**: print the message from Step 4's table, suggest the unblocking command, STOP.
+- **`.rihal/config.yaml` missing**: treat as `mode: guided`, continue.