@hanzlaa/rcode 4.10.4 → 4.10.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hanzlaa/rcode",
-  "version": "4.10.4",
+  "version": "4.10.6",
   "description": "rcode — the AI team that never forgets. Persistent memory, specialist agents, and slash commands for AI IDEs. Works in Claude Code, Cursor, Gemini, VS Code, and Antigravity.",
   "main": "cli/index.js",
   "bin": {

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

@@ -5,11 +5,21 @@ Run this check at the very start of any workflow that needs project state.
 ## Step: Detect project initialization
 
 ```bash
-test -f .rcode/config.yaml && echo "rcode-ready" || echo "rcode-not-initialized"
+if [ ! -f .rcode/config.yaml ]; then
+  echo "rcode-not-initialized"
+elif grep -q "Generated by install" .rcode/config.yaml 2>/dev/null && [ ! -f .rcode/JOURNEY.md ]; then
+  echo "rcode-seeded-not-configured"
+else
+  echo "rcode-ready"
+fi
 ```
 
+**Why the middle case matters (confirmed live, issue class closed by #1034-#1036's fixes):** `rcode install` pre-seeds `config.yaml` with installer defaults (`user_name: "$USER"`, `mode: "guided"`, etc.) so the tool has something to read before the user ever runs `/rcode-init`. A plain `test -f .rcode/config.yaml` check can't tell "the user was actually asked their preferences" apart from "the installer wrote plausible-looking defaults nobody confirmed" — both produce a config.yaml that exists. `/rcode-init` itself distinguishes these correctly (via its own `JOURNEY.md`-presence check), but every OTHER workflow that dispatches through this lightweight guard (e.g. `/rcode-do`) was checking existence only, so a user routed entirely through `/rcode-do` could go through many sessions on installer defaults, never once asked their name/language/mode/model-profile — while a user who happened to run `/rcode-init` directly got asked properly. That inconsistency is now closed: `rcode-seeded-not-configured` routes to the same question flow as `rcode-not-initialized` below, just skipping the bin-bootstrap step (already done by install).
+
 **If `rcode-ready`:** continue with the workflow normally.
 
+**If `rcode-seeded-not-configured`:** skip Step 1 (bin bootstrap — install already did this) and go straight to Step 2 (ask the 5 config questions) below, then continue with Steps 3-6 as written (Step 3's `.rcode/config.yaml` write overwrites the installer-seeded stub with real answers).
+
 **If `rcode-not-initialized`:** the user has never set up rcode for this project. Do NOT fail or continue blindly. Run the project init flow inline before proceeding:
 
 ---

package/rcode/skills/actions/4-implementation/rcode-herdr-orchestration/SKILL.md

@@ -54,6 +54,14 @@ independent agents.
    fires when `/loop` is active — clarify the heartbeat path with the user first.
 6. **Ignore stray buffer text in panes.** Leftover user text at an idle prompt is NOT
    an agent question — do not Enter it.
+7. **First message to every newly spawned agent starts with `/rcode-do`.** After `cld`
+   launches in a pane and the agent is ready, the very first line sent via
+   `herdr pane send-text` must be the literal `/rcode-do <task description>`, followed by
+   the rest of the task context (worktree path, branch, scope). This routes the agent's
+   first action through rcode's command picker instead of a hand-rolled instruction, so
+   ad-hoc orchestration prompts stay consistent with the rest of the toolset. Applies to
+   both Mode 1 (single-shot) and Mode 2 (wave) dispatch — not to follow-up messages sent
+   later in the same pane.
 
 ---
 
@@ -95,7 +103,8 @@ Use when work is bounded and can finish in one batch.
 2. Create worktrees: `git worktree add ../sm-worktrees/$A -b audit-$A master` for each area.
 3. Create tab + split panes, one per worktree.
 4. Launch `cld` in every pane (`send-text "cld"` + `send-keys Enter`). Sleep 7s after.
-5. Send each agent a self-contained prompt with worktree path, branch, and task.
+5. Send each agent a self-contained prompt with worktree path, branch, and task —
+   the first line must be the literal `/rcode-do <task description>` (Golden rule 7).
    - Audits: diagnose-only first. Fixes: incremental edits, no rewrites, commit each fix.
 6. Monitor: `herdr pane list` every ~2 min. Unblock stuck panes via `send-keys`/`send-text`.
 7. Merge back: `git add -f .planning/audits/*.md && git commit` inside each worktree, then

package/rcode/skills/actions/4-implementation/rcode-herdr-orchestration/templates/wave-prompt.md

@@ -5,6 +5,8 @@ Use this as the body of `herdr pane send-text` when dispatching each agent in a
 ---
 
 ```
+/rcode-do fix top pending items from <AUDIT_DOC_PATH> on branch <BRANCH_NAME>
+
 You are in an isolated worktree at <WORKTREE_PATH> on branch <BRANCH_NAME>. <REPO_NAME> repo.
 
 YOUR PARENT BRANCH IS <INTEGRATION_BRANCH> (NOT master). Your branch was forked from <INTEGRATION_BRANCH>. When you finish, the orchestrator will merge your branch INTO <INTEGRATION_BRANCH> (not master). Master stays untouched throughout the campaign.

package/server/dashboard.js

@@ -35,7 +35,7 @@ const { handleApiState, handleApiFiles, handleApiFile, handleApiHierarchy, handl
 const { renderHtml } = require('./lib/html/shell');
 
 // ---------- Configuration ----------
-const PORT = parseInt(process.env.PORT || '7717', 10);
+let PORT = parseInt(process.env.PORT || '7717', 10);
 // #969 — the orchestrator's actual port, injected into the client so it never
 // has to hardcode 7718. Defaults match orchestrator.js's own default.
 const ORCH_PORT = parseInt(process.env.ORCH_PORT || '7718', 10);
@@ -191,6 +191,23 @@ function handleRequest(req, res) {
   res.end('Not found');
 }
 
+// If PORT is already taken (e.g. another dashboard instance is running),
+// retry on the next port up rather than crashing on an unhandled 'error' event.
+const MAX_PORT_ATTEMPTS = 20;
+let portAttempts = 0;
+
+server.on('error', err => {
+  if (err.code === 'EADDRINUSE' && portAttempts < MAX_PORT_ATTEMPTS) {
+    portAttempts++;
+    console.log(`[dashboard] port ${PORT} in use, trying ${PORT + 1}...`);
+    PORT++;
+    server.listen(PORT, '127.0.0.1');
+    return;
+  }
+  console.error('[dashboard] server error:', err.message);
+  process.exit(1);
+});
+
 server.listen(PORT, '127.0.0.1', () => {
   console.log(`\n🕌 Majlis (مجلس) — rcode Dashboard`);
   console.log(`━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━`);