@hanzlaa/rcode 4.4.0 → 4.4.2

package/README.md

@@ -6,11 +6,11 @@
 
 ### An engineering org in a folder — and you can watch it work.
 
-*A roster of specialist agents, phase-driven delivery, and a persistent Memory Bank — running as plain files your IDE reads. Every number is reproducible with one command (`node benchmarks/facts.cjs`); marketing rounds up, this repo ships the receipts: **497 tests, 0 failing · 45 agents · 116 commands · 1 runtime dependency**.*
+*A roster of specialist agents, phase-driven delivery, and a persistent Memory Bank — running as plain files your IDE reads. **45 agents · 116 commands · 1 runtime dependency** — test count and CI status tracked by the badge above.*
 
 <p align="center"><img src="brand/dashboard-team.png" alt="rcode agent roster grouped by function — Leadership (Sadiq / strategy, Waleed / CTO, Ahmed / delivery, Nasser / eng manager), Engineering (Omar, Haitham / frontend, Yousef / backend, Zayd / ML, Khalid / DevOps), Product (Hussain / PM, Mariam / marketing), each card showing its role and tools" width="860"></p>
 
-<p align="center"><sub>The <a href="docs/install.md">Diwan dashboard</a> (view-only, <code>node server/dashboard.js</code>) — your project's phases, sprints, agents, decisions, and live orchestration, read straight from the files in <code>.rcode/</code>.</sub></p>
+<p align="center"><sub>The <a href="docs/install.md">Diwan dashboard</a> (<code>node server/dashboard.js</code>) — your project's phases, sprints, agents, decisions, and live orchestration, read straight from the files in <code>.rcode/</code>.</sub></p>
 
 > **A curated composition of the best AI-development practices — shipped as files.** Surgical-change discipline, parallel-agent orchestration, persistent Memory Bank patterns, phase-driven planning — packaged as one workflow for Claude Code power users. No multi-agent harness. No vector DB. Your IDE keeps the methodology; the project keeps the memory.
 
@@ -23,7 +23,7 @@ pnpm dlx @hanzlaa/rcode install
 [![CI](https://github.com/hanzlahabib/rcode/actions/workflows/test.yml/badge.svg)](https://github.com/hanzlahabib/rcode/actions/workflows/test.yml)
 [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
 
-Status: `@hanzlaa/rcode` v4.3.2 on npm. 497 automated tests (100% green) across 61 files · 45 agents · 116 commands · 129 workflows · 88 skills · **1 runtime dependency**. Every number here is reproducible — run `node benchmarks/facts.cjs`. Actively dogfooded on real projects every week.
+Status: `@hanzlaa/rcode` v4.4.2 on npm. 45 agents · 116 commands · 129 workflows · **1 runtime dependency**. Test status tracked by CI badge above. Actively dogfooded on real projects every week.
 
 ---
 
@@ -127,18 +127,18 @@ The point isn't "I beat LangChain." The point is **you don't need LangChain for
 > node benchmarks/facts.cjs
 > ```
 
-<p align="center"><img src="brand/hero-receipt.png" alt="benchmarks/facts.cjs output — 497 tests, 0 failing · 45 agents · 116 commands · 1 runtime dependency, computed from files on disk" width="720"></p>
-
 | Metric | Value | Why it's not a vanity number |
 |---|---|---|
-| **Portable methodology corpus** | **94,481 lines** of markdown | A 10-person eng org's playbooks (agents + commands + workflows + skills + references) — as files you own and grep, not a SaaS you rent. |
-| **Automated tests** | **497**, 100% passing across 61 files | The methodology is *guarded*, not vibes. CI runs them on every push; `node --test` reproduces locally in seconds. |
-| **Tested CLI engine** | **9,005 lines** (`rcode-tools.cjs` + `lib/`) | The deterministic brain — routing, state, planning math — is real code under test, not prompt soup. |
-| **Runtime dependencies** | **1** (`ws`, for the dashboard socket) | The view-only dashboard is pure Node stdlib. Almost nothing to audit, nothing to CVE-scan, nothing to break on `npm install`. |
-| **Specialist agents / commands / workflows / skills** | **45 / 116 / 129 / 88** | An entire engineering org, phrase-activated, that travels with you across Claude Code, Cursor, Codex, VS Code, Antigravity, Windsurf. |
-| **Core-op latency** | **~33 ms**, **0 LLM tokens** (best-of-7) | Intent routing, state reads, and milestone-health are deterministic *local* compute — a few ms over Node's own cold-start floor. The orchestration layer doesn't burn API tokens on bookkeeping the way pure-LLM agent frameworks do. |
+| **Portable methodology corpus** | **~105,000 lines** of markdown | A 10-person eng org's playbooks (agents + commands + workflows + skills + references) — as files you own and grep, not a SaaS you rent. |
+| **Automated tests** | **495** across 62 files | The methodology is *guarded*, not vibes. Live pass/fail status is on the CI badge above; `node --test` (or `node benchmarks/facts.cjs`) reproduces locally in seconds. |
+| **Tested CLI engine** | **~9,700 lines** (`rcode-tools.cjs` + `lib/`) | The deterministic brain — routing, state, planning math — is real code under test, not prompt soup. |
+| **Runtime dependencies** | **1** (`ws`, for the dashboard socket) | The dashboard is otherwise pure Node stdlib. Almost nothing to audit, nothing to CVE-scan, nothing to break on `npm install`. |
+| **Specialist agents / commands / workflows / skills** | **45 / 117 / 129 / 96** | An entire engineering org, phrase-activated, that travels with you across Claude Code, Cursor, Codex, VS Code, Antigravity, Windsurf. |
+| **Core-op latency** | **~60 ms**, **0 LLM tokens** (best-of-7) | Intent routing, state reads, and milestone-health are deterministic *local* compute — a few ms over Node's own cold-start floor. The orchestration layer doesn't burn API tokens on bookkeeping the way pure-LLM agent frameworks do. |
+
+> Counts above are produced by `node benchmarks/facts.cjs` and may drift slightly between releases — run it for the exact current figures.
 
-**The headline:** an entire software-delivery methodology — 94k lines of it — guarded by 497 tests, riding on a single runtime dependency, with an orchestration brain that costs **zero tokens** to think. Not a viral prompt. A system you can verify line by line.
+**The headline:** an entire software-delivery methodology — ~105k lines of it — guarded by a real test suite, riding on a single runtime dependency, with an orchestration brain that costs **zero tokens** to think. Not a viral prompt. A system you can verify line by line.
 
 ---
 
@@ -224,6 +224,23 @@ Named for the Arabic root **رحال** (rahhal) — the traveler. rcode walks al
 
 ---
 
+## 💙 Feedback welcome
+
+rcode is built and maintained by one person. If you hit a rough edge, a confusing command, or anything that doesn't work — please share it. Every report, even a one-liner, makes the tool better for everyone.
+
+**Post an issue in 30 seconds → [github.com/hanzlahabib/rcode/issues/new](https://github.com/hanzlahabib/rcode/issues/new)**
+
+Quick template:
+```
+Title:  what you were trying to do
+Body:   what happened vs what you expected
+        + the command or phrase you used
+```
+
+Thank you for using rcode. 🙏
+
+---
+
 ## Credits
 
 - [Andrej Karpathy's coding observations](https://github.com/forrestchang/andrej-karpathy-skills) (MIT) — wired into the code-review agents as hard constraints.

package/cli/generate-command-skills.cjs

@@ -100,7 +100,7 @@ description: >
   Sidebar entry — invokes the same workflow as /rcode-${cmdName}.
 triggers:
 ${triggers.map((t) => `  - "${t}"`).join('\n')}
-user-invocable: false
+user-invocable: true
 generated: true
 generated-by: rcode-install-v${version}
 source: rcode/commands/${cmdName}.md

package/cli/install.js

@@ -480,7 +480,8 @@ async function resolveIde(opts) {
  */
 async function resolveCommitPlanning(opts) {
   if (opts.commitPlanning !== null) return opts.commitPlanning;
-  if (opts.noPrompt || opts.global) return false; // global install: no planning artifacts
+  if (opts.global) return false; // global install: no planning artifacts
+  if (opts.noPrompt) return true; // non-interactive project install: commit planning by default (#936)
 
   // Issue #685: on re-install, read the existing .rcode/config.yaml and use
   // its commit_planning value as the default. Otherwise the new prompt
@@ -744,10 +745,8 @@ function seedStarterPlanning(target, projectName) {
     `**Milestone: M1 — Initial Delivery** (v1.0)\n` +
     `Started: ${today} · Current\n\n` +
     `---\n\n` +
-    `## Phase 01 — Setup & Scaffolding\n\n` +
-    `**Goal:** Lay the foundation. Replace this with your first phase when ready.\n\n` +
-    `**Status:** Planned\n\n` +
-    `**Acceptance:** Working dev environment; first feature in progress.\n\n` +
+    `> **No phases yet.** Run \`/rcode-new-project\` to design your roadmap,\n` +
+    `> or \`/rcode-add-phase <name>\` to add your first phase manually.\n\n` +
     `---\n\n` +
     `## Backlog\n\n` +
     `Ideas and future phases go here.\n`
@@ -758,7 +757,7 @@ function seedStarterPlanning(target, projectName) {
     `# ${name} — State\n\n` +
     `**Last updated:** ${today}\n` +
     `**Milestone:** M1 — Initial Delivery\n` +
-    `**Current phase:** 01 — Setup & Scaffolding\n` +
+    `**Current phase:** none — run /rcode-new-project or /rcode-add-phase\n` +
     `**Branch:** main\n\n` +
     `---\n\n` +
     `## Decisions\n\n_None yet._\n\n` +
@@ -826,15 +825,20 @@ function seedStarterPlanning(target, projectName) {
 
     const state = {
       version: '1',
-      project: resolvedProject,
+      // #940 — match the canonical schema (cli/lib/schemas.cjs stateSchema):
+      // schema_version is required, milestones is a plural array. Without these
+      // a freshly-installed state.json failed `rcode-tools validate` until the
+      // first migrateState() read. Write conformant state up front.
+      schema_version: 2,
+      project: resolvedProject || path.basename(target),
       ...(isStubProject ? { _seeded_stub: true } : {}),
       created: now,
       updated: now,
       current_phase: resolvedPhase,
       current_plan: 0,
       current_sprint: null,
-      milestone: null,
       phases: [],
+      milestones: [],
       executions: [],
       decisions: [],
       blockers: [],
@@ -1753,7 +1757,6 @@ function generateConfigYaml(opts) {
     `mode: "${sanitizeYamlValue(opts.mode)}"`,
     `model_profile: "balanced"`,
     `commit_planning: ${opts.commitPlanning !== false}`,
-    `rcode_source_path: "${sanitizeYamlValue(resolveStableSourcePath())}/"`,
     'workflow:',
     '  research_by_default: false',
     '  plan_checker: true',

package/cli/postinstall.js

@@ -132,9 +132,29 @@ To set up per-project state + planning structure, run inside your project:
 
 More:
   rcode help         # all commands (grouped)
-  rcode dashboard    # view-only Diwan on :7717
+  rcode dashboard    # Diwan project dashboard on :7717
 
 Docs: https://github.com/hanzlahabib/rcode
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ 💙 Thank you for using rcode!
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+ This package is built and maintained by one person.
+ Every piece of feedback — a bug, a rough edge, a
+ confusing command — makes it meaningfully better.
+
+ Hit a problem? Post it in 30 seconds:
+
+   https://github.com/hanzlahabib/rcode/issues/new
+
+ Quick template (just paste and fill):
+   Title:  what you were trying to do
+   Body:   what happened vs what you expected
+           + paste the command or phrase you used
+
+ Even a one-line report helps. Thank you. 🙏
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 `);
 }