@hanzlaa/rcode 3.2.1 → 3.3.1

package/rihal/workflows/execute.md

@@ -61,7 +61,7 @@ Check config mode first:
 CONFIG_MODE=$(node .rihal/bin/rihal-tools.cjs config-get mode 2>/dev/null || echo "guided")
 ```
 
-**If `CONFIG_MODE == "yolo"` or `$ARGUMENTS` contains `--auto`:** Skip the menu. Auto-select **A) Autonomous run** and print one line: `▶ Auto-selecting Autonomous run (yolo mode). /rihal:settings set mode guided to change.`
+**If `CONFIG_MODE == "yolo"` or `$ARGUMENTS` contains `--auto`:** Skip the menu. Auto-select **A) Autonomous run** and print one line: `▶ Auto-selecting Autonomous run (yolo mode). /rihal-settings set mode guided to change.`
 
 Otherwise, offer three modes via AskUserQuestion. Each option names the tradeoff explicitly:
 
@@ -117,7 +117,7 @@ Closure:
  RIHAL ► PHASE {NN} COMPLETE ✓
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
-End with Next Up block routing to /rihal:verify-work or /rihal:next.
+End with Next Up block routing to /rihal-verify-work or /rihal-next.
 </output_format>
 
 <core_principle>
@@ -236,7 +236,7 @@ fi
 </step>
 
 <step name="create_phase_snapshot" priority="first">
-**Create a pre-execution git tag so `/rihal:undo --phase NN --to-snapshot` can restore to this exact state.**
+**Create a pre-execution git tag so `/rihal-undo --phase NN --to-snapshot` can restore to this exact state.**
 
 Only runs when inside a git repository with a valid HEAD (skip silently for fresh/empty repos).
 
@@ -847,13 +847,13 @@ If `SECURITY_CFG` is `true` AND `SECURITY_FILE` is empty (no SECURITY.md yet):
 Include in the next-steps routing output:
 ```
 ⚠ Security enforcement enabled — run before advancing:
-  /rihal:secure-phase {PHASE} ${Rihal_WS}
+  /rihal-secure-phase {PHASE} ${Rihal_WS}
 ```
 
 If `SECURITY_CFG` is `true` AND SECURITY.md exists: check frontmatter `threats_open`. If > 0:
 ```
 ⚠ Security gate: {threats_open} threats open
-  /rihal:secure-phase {PHASE} — resolve before advancing
+  /rihal-secure-phase {PHASE} — resolve before advancing
 ```
 </step>
 
@@ -879,8 +879,8 @@ Apply the same "incomplete" filtering rules as earlier:
 
 Selected wave finished successfully. This phase still has incomplete plans, so phase-level verification and completion were intentionally skipped.
 
-/rihal:execute {phase} ${Rihal_WS}                # Continue remaining waves
-/rihal:execute {phase} --wave {next} ${Rihal_WS}  # Run the next wave explicitly
+/rihal-execute {phase} ${Rihal_WS}                # Continue remaining waves
+/rihal-execute {phase} --wave {next} ${Rihal_WS}  # Run the next wave explicitly
 ```
 
 **If no incomplete plans remain after the selected wave finishes:**
@@ -969,7 +969,7 @@ Verifier is blocked until critical/high findings are resolved.
 ```
 
 AskUserQuestion with options:
-1. **"Run /rihal:code-review-fix first (recommended)"** — Stop. Print next command: `/rihal:code-review-fix ${PHASE_NUMBER} ${Rihal_WS}`. Do NOT spawn verifier.
+1. **"Run /rihal-code-review-fix first (recommended)"** — Stop. Print next command: `/rihal-code-review-fix ${PHASE_NUMBER} ${Rihal_WS}`. Do NOT spawn verifier.
 2. **"Proceed to verifier anyway (high findings unresolved)"** — Log override and continue to `close_parent_artifacts` → `regression_gate` → `verify_phase_goal`.
 3. **"Cancel execution"** — Stop. Report partial completion.
 
@@ -979,7 +979,7 @@ If `CRITICAL_COUNT == 0` AND `HIGH_COUNT == 0` AND (`MEDIUM_COUNT > 0` OR `LOW_C
 ```
 ⚠ Code review found non-blocking findings (medium: ${MEDIUM_COUNT}, low: ${LOW_COUNT}).
   Report: ${REVIEW_FILE}
-  Consider: /rihal:code-review-fix ${PHASE_NUMBER}
+  Consider: /rihal-code-review-fix ${PHASE_NUMBER}
 ```
 Then continue to `close_parent_artifacts`.
 
@@ -1209,7 +1209,7 @@ grep "^status:" "$PHASE_DIR"/*-VERIFICATION.md | cut -d: -f2 | tr -d ' '
 |--------|--------|
 | `passed` | → update_roadmap |
 | `human_needed` | Present items for human testing, get approval or feedback |
-| `gaps_found` | Present gap summary, offer `/rihal:plan {phase} --gaps ${Rihal_WS}` |
+| `gaps_found` | Present gap summary, offer `/rihal-plan {phase} --gaps ${Rihal_WS}` |
 
 **If human_needed:**
 
@@ -1264,12 +1264,12 @@ All automated checks passed. {N} items need human testing:
 
 {From VERIFICATION.md human_verification section}
 
-Items saved to `{phase_num}-HUMAN-UAT.md` — they will appear in `/rihal:progress` and `/rihal:audit-uat`.
+Items saved to `{phase_num}-HUMAN-UAT.md` — they will appear in `/rihal-progress` and `/rihal-audit-uat`.
 
 "approved" → continue | Report issues → gap closure
 ```
 
-**If user says "approved":** Proceed to `update_roadmap`. The HUMAN-UAT.md file persists with `status: partial` and will surface in future progress checks until the user runs `/rihal:verify-work` on it.
+**If user says "approved":** Proceed to `update_roadmap`. The HUMAN-UAT.md file persists with `status: partial` and will surface in future progress checks until the user runs `/rihal-verify-work` on it.
 
 **If user reports issues:** Proceed to gap closure as currently implemented.
 
@@ -1288,13 +1288,13 @@ Items saved to `{phase_num}-HUMAN-UAT.md` — they will appear in `/rihal:progre
 
 `/clear` then:
 
-`/rihal:plan {X} --gaps ${Rihal_WS}`
+`/rihal-plan {X} --gaps ${Rihal_WS}`
 
 Also: `cat {phase_dir}/{phase_num}-VERIFICATION.md` — full report
-Also: `/rihal:verify-work {X} ${Rihal_WS}` — manual testing first
+Also: `/rihal-verify-work {X} ${Rihal_WS}` — manual testing first
 ```
 
-Gap closure cycle: `/rihal:plan {X} --gaps ${Rihal_WS}` reads VERIFICATION.md → creates gap plans with `gap_closure: true` → user runs `/rihal:execute {X} --gaps-only ${Rihal_WS}` → verifier re-runs.
+Gap closure cycle: `/rihal-plan {X} --gaps ${Rihal_WS}` reads VERIFICATION.md → creates gap plans with `gap_closure: true` → user runs `/rihal-execute {X} --gaps-only ${Rihal_WS}` → verifier re-runs.
 </step>
 
 <step name="uat_gate" priority="blocker">
@@ -1331,20 +1331,20 @@ fi
 
    {list AC items from SPRINT.md}
 
-   Run /rihal:verify-work {X} to perform UAT and produce VERIFICATION.md.
-   /rihal:next will refuse to advance until this gate passes.
+   Run /rihal-verify-work {X} to perform UAT and produce VERIFICATION.md.
+   /rihal-next will refuse to advance until this gate passes.
    ```
 3. STOP the workflow. Do NOT proceed to `update_roadmap`. Do NOT call `phase complete`.
 
 **If `VERIFICATION_STATUS` is `fail`:**
 
-1. Mark the phase as `status: executed` (so /rihal:plan --gaps can run a closure cycle).
+1. Mark the phase as `status: executed` (so /rihal-plan --gaps can run a closure cycle).
 2. Surface the failed AC items.
 3. STOP. Don't mark complete on a failing verification.
 
 **Only when `VERIFICATION_STATUS` is `pass`** — proceed to `update_roadmap` below.
 
-The previous behaviour (printing "Next Up: /rihal:verify-work" without state-gating) caused phases to reach `status: complete` without any human-verified UAT — see #443 for the failure mode.
+The previous behaviour (printing "Next Up: /rihal-verify-work" without state-gating) caused phases to reach `status: complete` without any human-verified UAT — see #443 for the failure mode.
 </step>
 
 <step name="update_roadmap">
@@ -1370,7 +1370,7 @@ Extract from result: `next_phase`, `next_phase_name`, `is_last_phase`, `warnings
 
 {list each warning}
 
-These items are tracked and will appear in `/rihal:progress` and `/rihal:audit-uat`.
+These items are tracked and will appear in `/rihal-progress` and `/rihal-audit-uat`.
 ```
 
 ```bash
@@ -1443,12 +1443,12 @@ discord_webhook_url: "https://discord.com/api/webhooks/..."
 teams_webhook_url: "https://outlook.office.com/webhook/..."
 ```
 
-Then verify with `/rihal:notify-test`.
+Then verify with `/rihal-notify-test`.
 </step>
 
 <step name="offer_next">
 
-**Exception:** If `gaps_found`, the `verify_phase_goal` step already presents the gap-closure path (`/rihal:plan {X} --gaps`). No additional routing needed — skip auto-advance.
+**Exception:** If `gaps_found`, the `verify_phase_goal` step already presents the gap-closure path (`/rihal-plan {X} --gaps`). No additional routing needed — skip auto-advance.
 
 **No-transition check (spawned by auto-advance chain):**
 
@@ -1499,15 +1499,15 @@ Read and follow `.rihal/workflows/transition.md`, passing through the `--auto` f
 
 **STOP. Do not auto-advance. Do not execute transition. Do not plan next phase. Present options to the user and wait.**
 
-**IMPORTANT: There is NO `/rihal:transition` command. Never suggest it. The transition workflow is internal only.**
+**IMPORTANT: There is NO `/rihal-transition` command. Never suggest it. The transition workflow is internal only.**
 
 ```
 ## ✓ Phase {X}: {Name} Complete
 
-/rihal:progress ${Rihal_WS} — see updated roadmap
-/rihal:discuss-phase {next} ${Rihal_WS} — discuss next phase before planning
-/rihal:plan {next} ${Rihal_WS} — plan next phase
-/rihal:execute {next} ${Rihal_WS} — execute next phase
+/rihal-progress ${Rihal_WS} — see updated roadmap
+/rihal-discuss-phase {next} ${Rihal_WS} — discuss next phase before planning
+/rihal-plan {next} ${Rihal_WS} — plan next phase
+/rihal-execute {next} ${Rihal_WS} — execute next phase
 ```
 
 Only suggest the commands listed above. Do not invent or hallucinate command names.
@@ -1534,7 +1534,7 @@ For 1M+ context models, consider:
 </failure_handling>
 
 <resumption>
-Re-run `/rihal:execute {phase}` → discover_plans finds completed SUMMARYs → skips them → resumes from first incomplete plan → continues wave execution.
+Re-run `/rihal-execute {phase}` → discover_plans finds completed SUMMARYs → skips them → resumes from first incomplete plan → continues wave execution.
 
 STATE.md tracks: last completed plan, current wave, pending checkpoints.
 </resumption>

package/rihal/workflows/explore.md

@@ -9,13 +9,13 @@ offers mid-conversation research when useful, then routes crystallized outputs t
 If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 ```
-/rihal:explore <argument-here>
+/rihal-explore <argument-here>
 ```
 
 **Examples:**
 ```
-/rihal:explore example 1
-/rihal:explore example 2
+/rihal-explore example 1
+/rihal-explore example 2
 ```
 
 STOP — do not proceed.
@@ -124,7 +124,7 @@ For each selected output, write the file:
 - **Seeds:** Create `.planning/seeds/{slug}.md` with frontmatter (title, trigger_condition, planted_date)
 - **Research questions:** Append to `.planning/research/questions.md`
 - **Requirements:** Append to `.planning/REQUIREMENTS.md` with next available REQ ID
-- **Phases:** Use existing `/rihal:add-phase` command via SlashCommand
+- **Phases:** Use existing `/rihal-add-phase` command via SlashCommand
 
 Commit if `commit_docs` is enabled:
 ```bash
@@ -140,7 +140,7 @@ node "$PROJECT_ROOT/.rihal/bin/rihal-tools.cjs" commit "docs: capture exploratio
 **Outputs:** {count} artifact(s) created
 {list of created files}
 
-Continue exploring with `/rihal:explore` or start working with `/rihal:next`.
+Continue exploring with `/rihal-explore` or start working with `/rihal-next`.
 ```
 
 </process>

package/rihal/workflows/export-to-github.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:export-to-github
+# Workflow: rihal-export-to-github
 
 <purpose>
 Push Rihal state to GitHub as issues, milestones, and (optionally) a Project v2 board. Thin slash-command wrapper around the existing `rihal-code github-sync` CLI, plus a `--decisions` mode that publishes the project's recent decision log as a single tracking issue.
@@ -29,7 +29,7 @@ Always default to dry-run. Show a preview, then require `--execute` on a follow-
 If `$ARGUMENTS` is empty or contains `--help` / `-h`:
 
 ```
-/rihal:export-to-github [target] [flags]
+/rihal-export-to-github [target] [flags]
 
 Targets (mutually exclusive):
   (none)                    Sync all phases → milestones, epics/stories → issues
@@ -96,7 +96,7 @@ Render the decisions as a markdown table in the issue body:
 ```markdown
 # Decision Log — {project_name}
 
-_Generated by `/rihal:export-to-github --decisions` on {ISO date}. Source: `~/.rihal/decisions.jsonl` (this project only)._
+_Generated by `/rihal-export-to-github --decisions` on {ISO date}. Source: `~/.rihal/decisions.jsonl` (this project only)._
 
 | Date | Phase | Plan | Decision |
 |------|-------|------|----------|
@@ -154,7 +154,7 @@ node .rihal/bin/rihal-tools.cjs state add-decision \
   2>/dev/null || true
 ```
 
-This also mirrors to `~/.rihal/decisions.jsonl` so `/rihal:decisions` surfaces the export.
+This also mirrors to `~/.rihal/decisions.jsonl` so `/rihal-decisions` surfaces the export.
 </process>
 
 ## Success Criteria
@@ -171,4 +171,4 @@ This also mirrors to `~/.rihal/decisions.jsonl` so `/rihal:decisions` surfaces t
 - `gh auth status` fails → tell the user to run `gh auth login`, exit
 - `gh repo view` fails (no remote) → tell the user to pass `--repo owner/name`, exit
 - `rihal-code` missing from PATH → fall back to `node ./cli/index.js`; if that also fails, instruct the user to `pnpm install` from the repo root
-- Empty decision log under `--decisions` → print "No decisions to export{since_suffix}. Run /rihal:council or complete a sprint to create some." and exit cleanly
+- Empty decision log under `--decisions` → print "No decisions to export{since_suffix}. Run /rihal-council or complete a sprint to create some." and exit cleanly

package/rihal/workflows/forensics.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:forensics
+# Workflow: rihal-forensics
 
 <purpose>
 Analyze execution history in state.json and filesystem to detect incomplete work. Show timeline of what happened, where it broke, and suggest resume command.
@@ -10,13 +10,13 @@ Analyze execution history in state.json and filesystem to detect incomplete work
 If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 ```
-/rihal:forensics <argument-here>
+/rihal-forensics <argument-here>
 ```
 
 **Examples:**
 ```
-/rihal:forensics example 1
-/rihal:forensics example 2
+/rihal-forensics example 1
+/rihal-forensics example 2
 ```
 
 STOP — do not proceed.
@@ -111,7 +111,7 @@ Format as:
 ```
 Timeline of Execution
 
-T-5h: Started phase "Feature X" (/rihal:plan feature-x)
+T-5h: Started phase "Feature X" (/rihal-plan feature-x)
 T-3h: Phase created, plan saved to .planning/feature-x/SPRINT.md
 T-2h: Execution began — checkpoint at step 3/8
 T-0h: ❌ FAIL — Execution error: "Dependency not installed"
@@ -130,7 +130,7 @@ Based on what was found:
 You were working on phase "phase-name" and reached checkpoint 3.
 
 To resume:
-  /rihal:resume-work
+  /rihal-resume-work
 ```
 
 **If failed execution with error:**
@@ -142,7 +142,7 @@ Phase "phase-name" failed during execution:
 
 To retry:
   1. Fix the issue noted above
-  2. Run: /rihal:next
+  2. Run: /rihal-next
 ```
 
 **If incomplete plan (PLAN exists, no SUMMARY):**
@@ -152,7 +152,7 @@ To retry:
 Phase "phase-name" was planned but never executed.
 
 To continue:
-  /rihal:execute phase-name
+  /rihal-execute phase-name
 ```
 
 **If no incomplete work found:**

package/rihal/workflows/from-template.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:from-template
+# Workflow: rihal-from-template
 
 <purpose>
 Seed a fresh project's `.planning/` directory from a canonical starter template (saas-b2b, api-backend, mobile-app). Replaces the blank-page moment after `rihal init` with a PROJECT.md skeleton, a ROADMAP.md with typical phases for this kind of project, and a REQUIREMENTS.md of common REQ-IDs.
@@ -28,7 +28,7 @@ End with a file summary and Next Up routing.
 If `$ARGUMENTS` is empty, contains `--help`, `-h`, or `list` — print the catalog:
 
 ```
-/rihal:from-template <template-name> [--project-name "<name>"] [--force]
+/rihal-from-template <template-name> [--project-name "<name>"] [--force]
 
 Available templates:
   saas-b2b      Multi-tenant B2B SaaS — auth, orgs, billing, RBAC, admin
@@ -50,7 +50,7 @@ TEMPLATE_DIR=".rihal/templates/projects/${TEMPLATE}"
 
 if [ ! -d "$TEMPLATE_DIR" ]; then
   echo "Unknown template: ${TEMPLATE}"
-  echo "Run: /rihal:from-template --help  for the catalog."
+  echo "Run: /rihal-from-template --help  for the catalog."
   exit 0
 fi
 ```
@@ -88,7 +88,7 @@ If `EXISTING` is non-empty and `--force` was NOT passed:
 Refusing to overwrite. Options:
   - Pass --force to overwrite (destructive)
   - Delete the existing files first, then re-run
-  - Use /rihal:new-project for the interactive discovery flow instead
+  - Use /rihal-new-project for the interactive discovery flow instead
 ```
 
 STOP.
@@ -131,7 +131,7 @@ node .rihal/bin/rihal-tools.cjs state add-decision \
   "Seeded .planning/ from template '${TEMPLATE}' (project: ${PROJECT_NAME})" 2>/dev/null || true
 ```
 
-This surfaces the seeding both in local state AND `/rihal:decisions` cross-project memory.
+This surfaces the seeding both in local state AND `/rihal-decisions` cross-project memory.
 
 ## Step 6 — Commit
 
@@ -154,8 +154,8 @@ Next Up (from template.yaml.next_steps):
   {next_steps_block}
 
 Also consider:
-  /rihal:discuss-phase 01   — adapt phase 01 to your specifics
-  /rihal:council            — sanity-check the starter phases before committing to them
+  /rihal-discuss-phase 01   — adapt phase 01 to your specifics
+  /rihal-council            — sanity-check the starter phases before committing to them
 ```
 </process>
 
@@ -169,5 +169,5 @@ Also consider:
 
 ## On Error
 
-- Missing `.rihal/templates/projects/` directory → tell the user their install is missing the module; suggest `rihal:install`
+- Missing `.rihal/templates/projects/` directory → tell the user their install is missing the module; suggest `rihal-install`
 - `sed` substitution failure (unusual characters in project name) → fall back to literal-string `awk` substitution, or ask the user to pass a simpler name via `--project-name`

package/rihal/workflows/health.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:health
+# Workflow: rihal-health
 
 <purpose>
 Run 6-point compliance check on rihal installation. Each check is pass/fail. Summary at the end.
@@ -10,13 +10,13 @@ Run 6-point compliance check on rihal installation. Each check is pass/fail. Sum
 If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 ```
-/rihal:health <argument-here>
+/rihal-health <argument-here>
 ```
 
 **Examples:**
 ```
-/rihal:health example 1
-/rihal:health example 2
+/rihal-health example 1
+/rihal-health example 2
 ```
 
 STOP — do not proceed.
@@ -40,7 +40,7 @@ test -d .rihal && test -w .rihal
 
 **Output on fail:**
 ```
-❌ FAIL — .rihal/ does not exist or is not writable. Run: /rihal:update to repair
+❌ FAIL — .rihal/ does not exist or is not writable. Run: /rihal-update to repair
 ```
 
 ## Step 1 — Verify file manifest exists and is valid CSV
@@ -64,7 +64,7 @@ Verify:
 
 **Output on fail:**
 ```
-❌ FAIL — files-manifest.csv is missing or corrupted. Run: /rihal:update to repair
+❌ FAIL — files-manifest.csv is missing or corrupted. Run: /rihal-update to repair
 ```
 
 ## Step 2 — Verify all manifest files exist and hashes match
@@ -89,7 +89,7 @@ Detect drift: files that exist but hash doesn't match.
 ❌ FAIL — File drift detected: N files changed or missing
   Modified: file1.md, file2.js
   Missing: file3.md
-Run: /rihal:update to repair
+Run: /rihal-update to repair
 ```
 
 ## Step 3 — Verify state.json exists and is valid
@@ -118,7 +118,7 @@ Parse as JSON. Verify top-level keys present:
 
 **Output on fail:**
 ```
-❌ FAIL — state.json is missing or invalid. Run: /rihal:update to repair
+❌ FAIL — state.json is missing or invalid. Run: /rihal-update to repair
 ```
 
 ## Step 4 — Verify agent-manifest.csv is present and populated
@@ -141,7 +141,7 @@ Verify:
 
 **Output on fail:**
 ```
-❌ FAIL — agent-manifest.csv is missing or empty. Run: /rihal:update to repair
+❌ FAIL — agent-manifest.csv is missing or empty. Run: /rihal-update to repair
 ```
 
 ## Step 5 — Verify rihal-tools.cjs is executable and responsive
@@ -160,7 +160,7 @@ node .rihal/bin/rihal-tools.cjs version
 
 **Output on fail:**
 ```
-❌ FAIL — rihal-tools.cjs is missing or broken. Run: /rihal:update to repair
+❌ FAIL — rihal-tools.cjs is missing or broken. Run: /rihal-update to repair
 ```
 
 ## Step 6 — Count results and print final summary
@@ -177,7 +177,7 @@ If all 6 pass:
 If fewer than 6 pass:
 ```
 ⚠️ {N}/6 checks passed — {M} issue(s) found
-Run: /rihal:update to repair
+Run: /rihal-update to repair
 ```
 
 ## Success Criteria