@hanzlaa/rcode 2.2.0 → 2.3.1

package/rihal/workflows/update.md

@@ -1,39 +1,56 @@
 # Workflow: rihal:update
 
 <purpose>
-Detect package updates for rihal-code by comparing installed file hashes against source package hashes. Show changelog (added/changed/removed files), ask user confirmation, then run installer with --force --yes if approved.
+Pull the latest rcode from npm and install it **non-destructively** —
+overwrite only files the user hasn't customized since their last install.
+User-modified files are preserved and reported. Closes #232.
+
+Default invocation:
+```
+npx @hanzlaa/rcode@latest install . --non-destructive --yes
+```
+
+The `--non-destructive` flag (set by default in this workflow) makes the
+installer compare each file's current SHA256 to the SHA256 stored in
+`.rihal/_config/files-manifest.csv` from the previous install:
+- Hashes match → file is pristine → safe to overwrite with new version
+- Hashes differ → user has edited it → SKIP and report
+
+Per-project state is ALWAYS preserved (never touched by either mode):
+- `.rihal/config.yaml`
+- `.rihal/state.json` (and `.lock`)
+- `.planning/` (PRD, ROADMAP, sprints, SUMMARY files)
+- `.rihal/brain/` content (refreshed via `brain pull` separately)
 </purpose>
 
 
 ## Step 0 — Usage check
 
-If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
+If `$ARGUMENTS` contains `--help` or `-h`:
 
 ```
-/rihal:update <argument-here>
+/rihal:update                       # pull latest, preserve user-modified files
+/rihal:update v2.4.0                # pin to a specific version
+/rihal:update --force-overwrite     # discard local edits, overwrite all rcode files
 ```
 
 **Examples:**
 ```
-/rihal:update example 1
-/rihal:update example 2
+/rihal:update
+/rihal:update v2.4.0
+/rihal:update --force-overwrite
 ```
 
-STOP — do not proceed.
-
 ## Step 1 — Locate installed package
 
-Find the rihal-code package using one of these strategies (in order):
-1. Check `$(npm root -g)/rihal-code/cli/install-v2.js` (global install)
-2. Check `./cli/install-v2.js` (local install)
-3. If neither exists, print:
-   ```
-   ❌ rihal-code package not found. Install with:
-   npm install -g rihal-code
-   ```
-   Exit.
+Find the local rcode installer (used as the network-fallback path in
+Step 7). Try in order:
+
+1. `$(npm root -g)/@hanzlaa/rcode/cli/install.js` (global install)
+2. `./cli/install.js` (local clone)
+3. If neither exists, skip — Step 7's primary path uses `npx @hanzlaa/rcode@latest` and works without a local installer.
 
-Store the installer path in `$INSTALLER_PATH`.
+Store the resolved path (or empty) in `$INSTALLER_PATH`.
 
 ## Step 2 — Read installed manifest
 
@@ -45,8 +62,8 @@ cat .rihal/_config/files-manifest.csv
 
 If the file doesn't exist:
 ```
-ℹ️ No rihal installation detected in this project.
-Run: node <installer-path> . --force --yes
+ℹ️ No rcode installation detected in this project.
+Run: npx @hanzlaa/rcode@latest install . --yes
 ```
 Exit.
 
@@ -121,20 +138,61 @@ Options:
 - If user chooses [1], proceed to Step 7
 - If user chooses [2], print "Update cancelled" and exit
 
-## Step 7 — Apply update
+## Step 7 — Apply update (non-destructive by default per #232)
 
-Run the installer with `--force --yes`:
+Pull from npm AND install non-destructively. User-modified files are
+preserved automatically; the installer reports each one in the summary.
 
 ```bash
-node "$INSTALLER_PATH" . --force --yes
+npx @hanzlaa/rcode@latest install . --non-destructive --yes
+```
+
+**If the user explicitly wants destructive overwrite** (rare — only
+when they intentionally want to discard their customizations):
+
+```bash
+npx @hanzlaa/rcode@latest install . --force-overwrite --yes
+```
+
+**Version pinning** — if the user passed `/rihal:update v2.4.0`, pass
+the version through:
+
+```bash
+npx @hanzlaa/rcode@2.4.0 install . --non-destructive --yes
+```
+
+**Local fallback** — if the user's network can't reach npm, fall back
+to the locally-cached installer (still non-destructive):
+
+```bash
+node "$INSTALLER_PATH" . --non-destructive --yes
 ```
 
 If the command exits with non-zero status, print:
+
 ```
 ❌ Update failed. Check the output above.
+   Tip: try --force-overwrite if you intentionally want to overwrite
+   your customizations, or run with the local installer fallback.
 ```
+
 Exit with error code.
 
+## Step 7.5 — Surface preserved files
+
+The installer's stdout will include a "user-modified preserved" report
+when relevant. Capture it and re-print as a callout so users notice:
+
+```
+ℹ Files preserved (your customizations were kept):
+   - .claude/skills/rihal-create-prd/workflow.md
+   - rihal/workflows/sprint-planning.md
+   - .rihal/references/output-format.md
+
+These will not auto-update on future /rihal:update calls. To force
+their update next time, run /rihal:update --force-overwrite.
+```
+
 ## Step 8 — Pull Rihal brain content (v2.0)
 
 After installer finishes, refresh the brain content from configured sources (issue #158). This is idempotent and safe to re-run.

package/rihal/workflows/validate-phase.md

@@ -83,7 +83,13 @@ No gaps → skip to Step 6, set `nyquist_compliant: true`.
 
 ## 4. Present Gap Plan
 
-Call AskUserQuestion with gap table and options:
+```bash
+CONFIG_MODE=$(node .rihal/bin/rihal-tools.cjs config-get mode 2>/dev/null || echo "guided")
+```
+
+**If `CONFIG_MODE == "yolo"`:** Auto-select option 1 ("Fix all gaps") and proceed to Step 5 without asking. Print: `▶ Auto-fixing all gaps (yolo mode).`
+
+Otherwise call AskUserQuestion with gap table and options:
 1. "Fix all gaps" → Step 5
 2. "Skip — mark manual-only" → add to Manual-Only, Step 6
 3. "Cancel" → exit

package/rihal/agents/rihal-ui-designer.md

@@ -1,6 +0,0 @@
----
-name: rihal-ui-designer
-description: Alias for rihal-ux-designer. Use that agent type instead.
----
-
-This agent is an alias for `rihal-ux-designer`. Spawn `rihal-ux-designer` directly.

package/rihal/workflows/config.md

@@ -1,105 +0,0 @@
-# Workflow: rihal:config
-
-<purpose>
-View or interactively edit Rihal project configuration (language, mode, model profile, branching strategy).
-</purpose>
-
-## Step 0 — Usage check
-
-If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
-
-```
-/rihal:config [show | set <key> <value>]
-```
-
-**Examples:**
-```
-/rihal:config show
-/rihal:config set communication_language Arabic
-/rihal:config set mode yolo
-```
-
-If no arguments provided, enter interactive mode (Step 2).
-
-## Step 1 — Parse input
-
-- If first argument is `show` (or no args): proceed to Step 1.5 (display current config)
-- If first argument is `set`: proceed to Step 2 (update value)
-- Otherwise: treat as interactive mode
-
-## Step 1.5 — Display current config
-
-Read `.rihal/config.yaml` and print in formatted table:
-
-```
-Current Rihal Configuration:
-  user_name              : {value}
-  project_name           : {value}
-  communication_language : {value}
-  mode                   : {value}
-  model_profile          : {value}
-  branching_strategy     : {value}
-```
-
-STOP — do not proceed further.
-
-## Step 2 — Interactive or set mode
-
-### If `set <key> <value>`:
-
-Validate key is one of: `communication_language`, `mode`, `model_profile`, `branching_strategy`.
-
-If invalid, print error and STOP:
-```
-Unknown config key: {key}
-Allowed keys: communication_language, mode, model_profile, branching_strategy
-```
-
-Call:
-```bash
-node .rihal/bin/rihal-tools.cjs config set --key {key} --value {value}
-```
-
-Print success:
-```
-✓ Updated: {key} = {value}
-```
-
-STOP.
-
-### If no arguments (interactive mode):
-
-Use AskUserQuestion for each setting:
-
-1. Ask: "Communication language?" (show current value)
-   - Options: English, Arabic, Spanish, French, Chinese, etc.
-2. Ask: "Mode?" (guided or yolo?)
-   - guided = confirm at gates
-   - yolo = autonomous execution
-3. Ask: "Model profile?" (balanced, fast, or thorough?)
-4. Ask: "Branching strategy?" (none, auto-branch, feature-branch, trunk-based?)
-
-After each selection, call the config set command from Step 2.
-
-Print summary:
-```
-✓ Configuration updated:
-  communication_language : {value}
-  mode                   : {value}
-  model_profile          : {value}
-  branching_strategy     : {value}
-```
-
-STOP.
-
-## Success Criteria
-
-- [ ] Current config displayed or updated successfully
-- [ ] No validation errors
-- [ ] .rihal/config.yaml reflects changes
-
-## On Error
-
-- **Invalid key:** print allowed keys and stop.
-- **.rihal/config.yaml missing:** print "No config found. Run /rihal:init first."
-- **rihal-tools.cjs missing:** tell user to run `rihal-code install-v2`.