@hanzlaa/rcode 3.4.7 → 3.4.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hanzlaa/rcode",
-  "version": "3.4.7",
+  "version": "3.4.8",
   "description": "rcode — the memory bank for AI-driven SaaS teams. Persistent project context, distinctive engineering personas, and phase-based workflows. Built by Rihal. Works in Claude Code, Cursor, Gemini, VS Code, and Antigravity.",
   "main": "cli/index.js",
   "bin": {

package/rihal/references/auto-init-guard.md

@@ -0,0 +1,104 @@
+# Auto-Init Guard
+
+Run this check at the very start of any workflow that needs project state.
+
+## Step: Detect project initialization
+
+```bash
+test -f .rihal/config.yaml && echo "rihal-ready" || echo "rihal-not-initialized"
+```
+
+**If `rihal-ready`:** continue with the workflow normally.
+
+**If `rihal-not-initialized`:** the user has never set up Rihal for this project. Do NOT fail or continue blindly. Run the project init flow inline before proceeding:
+
+---
+
+### Inline init flow (when config.yaml is missing)
+
+Tell the user:
+
+```
+Rihal isn't configured for this project yet. Let me set it up — takes 30 seconds.
+```
+
+**1. Bootstrap local tooling** — copy bin and workflows from the global install:
+
+```bash
+GLOBAL_RIHAL="$HOME/.rihal"
+if [ -d "$GLOBAL_RIHAL/bin" ]; then
+  mkdir -p .rihal/bin .rihal/workflows .rihal/references
+  cp "$GLOBAL_RIHAL/bin/rihal-tools.cjs" .rihal/bin/ 2>/dev/null || true
+  # workflows and references are read from ~/.rihal at runtime via @.rihal/ resolution
+fi
+```
+
+**2. Ask the 5 config questions** using AskUserQuestion:
+
+| # | Question | Options | Default |
+|---|----------|---------|---------|
+| 1 | Your name (what Rihal calls you) | free text | `$USER` |
+| 2 | Language for agent responses | English / Arabic / Urdu / Roman Urdu | English |
+| 3 | Mode (how Rihal handles decision gates) | `guided` / `yolo` | guided |
+| 4 | Model profile (cost vs quality) | `quality` / `balanced` / `budget` | balanced |
+| 5 | Commit planning artifacts to git? | yes / no | yes |
+
+**3. Write `.rihal/config.yaml` directly** (no rihal-tools needed — plain Bash):
+
+```bash
+mkdir -p .rihal
+cat > .rihal/config.yaml << 'YAML'
+# Rihal project config — edit any time
+user_name: "{name}"
+project_name: "{basename_of_cwd}"
+communication_language: "{lang}"
+mode: "{mode}"
+model_profile: "{profile}"
+commit_planning: {commit_planning_bool}
+rihal_source_path: ""
+workflow:
+  research_by_default: false
+  plan_checker: true
+  post_execute_gates: true
+  ui_safety_gate: true
+git:
+  branching_strategy: "none"
+YAML
+```
+
+**4. Seed `.rihal/state.json` and `.planning/` structure**:
+
+```bash
+mkdir -p .planning/phases .planning/council-sessions .rihal/context
+
+# state.json
+cat > .rihal/state.json << 'JSON'
+{"project":"{project_name}","phase":null,"sprint":null,"sessions":[],"initialized":"now"}
+JSON
+
+# context stubs
+echo "# Active Context\n\n_Run /rihal-init for full setup._" > .rihal/context/active.md
+echo "# Project Brief\n\n_Run /rihal-init for full setup._" > .rihal/context/project-brief.md
+```
+
+**5. Tell the user:**
+
+```
+✓ Rihal configured for this project.
+
+Config saved to .rihal/config.yaml — edit any time.
+Run /rihal-init for a full project scan and context setup.
+
+Continuing with your original request...
+```
+
+**6. Continue** with the original workflow as if it had been initialized from the start.
+
+---
+
+## Notes
+
+- This guard is **non-blocking** — it asks questions but does not stop the session; once config is written it resumes the original request automatically.
+- If `AskUserQuestion` is unavailable (non-interactive mode), use all defaults and skip the questions.
+- If the bootstrap `cp` fails (global rihal not found), print a warning and attempt to continue — some workflows work without local rihal-tools if they only need config.
+- On **subsequent runs**, the guard exits immediately (config exists) with zero overhead.

package/rihal/workflows/council.md

@@ -28,6 +28,7 @@ Closure: `RIHAL ► COUNCIL COMPLETE ✓` + Next Up with decision options.
 </output_format>
 
 <required_reading>
+@.rihal/references/auto-init-guard.md
 @.rihal/references/output-format.md
 @.rihal/references/council-protocol.md
 </required_reading>

package/rihal/workflows/do.md

@@ -3,6 +3,7 @@ Analyze freeform text from the user and route to the most appropriate Rihal comm
 </purpose>
 
 <required_reading>
+@.rihal/references/auto-init-guard.md
 @.rihal/references/output-format.md
 @.rihal/references/verb-dictionary.md
 @.rihal/references/dispatch-banner.md
@@ -11,6 +12,11 @@ Read all files referenced by the invoking prompt's execution_context before star
 
 <process>
 
+<step name="auto_init_check">
+Run the auto-init guard from `@.rihal/references/auto-init-guard.md` before anything else.
+If the project is not initialized, complete the inline init flow, then continue.
+</step>
+
 <step name="parse_args">
 Extract `$ARGUMENTS`, detect `--auto` flag, and check config mode:
 

package/rihal/workflows/execute.md

@@ -143,6 +143,7 @@ via filesystem and git state.
 </runtime_compatibility>
 
 <required_reading>
+@.rihal/references/auto-init-guard.md
 @.rihal/references/output-format.md
 Read STATE.md before any operation to load project context.
 

package/rihal/workflows/init.md

@@ -1,9 +1,9 @@
 # Workflow: rihal-init
 
 <purpose>
-Begin the rihla. This is the first command a user runs after dropping Rihal files into a project. It detects project state, asks a handful of configuration questions, scans existing context (if any), writes `.rihal/RIHLA.md` as the journey baseline, and routes to the right next command.
+Begin the rihla. This is the entry point for configuring Rihal in a project. Runs automatically on first use of any rihal command (via auto-init-guard in do.md), or explicitly via /rihal-init for a full setup with codebase scan.
 
-This replaces the older `/rihal-generate-project-context` workflow — init is the single entry point for configuring Rihal in a project.
+No manual "rcode install" needed per project — just use any /rihal-* command and this triggers automatically when config is missing.
 </purpose>
 
 ## Step 0 — Usage check

package/rihal/workflows/new-project.md

@@ -4,6 +4,7 @@ Initialize a new project through unified flow: questioning, research (optional),
 </purpose>
 
 <required_reading>
+@.rihal/references/auto-init-guard.md
 @.rihal/references/output-format.md
 
 Read all files referenced by the invoking prompt's execution_context before starting.

package/rihal/workflows/plan.md

@@ -41,6 +41,7 @@ End with Next Up routing to /rihal-execute.
 </output_format>
 
 <required_reading>
+@.rihal/references/auto-init-guard.md
 @.rihal/references/output-format.md
 Read all files referenced by the invoking prompt's execution_context before starting.
 

package/rihal/workflows/status.md

@@ -7,6 +7,7 @@ Render a human-readable project status dashboard. All data comes from a single `
 </purpose>
 
 <required_reading>
+@.rihal/references/auto-init-guard.md
 @.rihal/references/output-format.md
 </required_reading>