rcf-lite 0.32.4 → 0.32.5

package/CHANGELOG.md

@@ -6,6 +6,15 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 
 ## [Unreleased]
 
+## [0.32.5] - 2026-10-07
+
+0.32.5 ships two chain-shape fixes surfaced by Dex on branch `dex/discovery-viewer-command-page` (reporter), closing issues 321 and 322. The dogfood walker in `test/rcf-tree.test.js` now mirrors the sidecar-ledger carve-out from `src/define/ledgers.js` and ignores `rcf/define/`, so the first `pnpm rcf define ledger brief add` on a fresh tree no longer blows up three dogfood assertions. A new `packages/rcf-lite/guidance/discovery/` (and companion `packages/rcf-lite/docs/discovery/`) subdir gives project discovery artefacts a predictable home outside the locked methodology inventories. The three locked slug lists in `test/guidance/inventory.test.js`, `test/mcp/resources.test.js` and `test/docs/links.test.js` are untouched and `guidance/manifest.json` is untouched, so an in-package methodology addition still requires a coordinated test-code change. breaking: false; the 0.32.1 through 0.32.4 fixes carry forward unchanged. minAgentAction: null.
+
+### Fixed
+
+- **Dogfood walker ignores `rcf/define/` ledgers (issue 321, reporter Dex, w-2026-10-07-dave-006).** `src/define/ledgers.js` exports the new `DEFINE_RELATIVE_DIR` constant; `test/rcf-tree.test.js:walk()` imports it and skips the directory the exact same way the ledger module writes to it, so the four sidecar ledgers (`brief-ledger.json`, `decisions-ledger.json`, `concern-ledger.json`, `probe-ledger.json`) plus the freeze record never surface to `classify()` or `loadAll()`. `loadAll()` additionally takes an optional project-root override so the carve-out works regardless of where the caller rooted the walk. Regression fixture seeds the four ledgers plus a bug-bait REQ-shaped file under `rcf/define/` and proves none of them surface, while a real chain document outside the carve-out does.
+- **Project discovery home carved out of the locked inventories (issue 322, reporter Dex, w-2026-10-07-dave-006).** `packages/rcf-lite/guidance/discovery/` and `packages/rcf-lite/docs/discovery/` are the new home for DISCOVERY-stage artefacts: discovery briefs, prototype notes, exploratory write-ups, infographic sketches. The subdirs sit outside the top-level non-recursive readdir enumerations the methodology locks use, so a first-time contributor can land a discovery brief without touching the methodology lock or the pack manifest. The guidance posture (no em-dash, no non-canonical external URLs, filename stem is a well-formed slug) still runs over the subdir via a new `test/guidance/discovery-home.test.js`. CONTRIBUTING.md documents the home under chain-first discipline.
+
 ## [0.32.4] - 2026-10-07
 
 0.32.4 is the stop-word follow-up to 0.32.3 after Dex's second-consumer check of PR 318 on WESPA main 34ebceba (2026-10-07T10:38Z, issue 319). 0.32.3 moved the English stop-word skip onto the pattern 4 (dot-notation) branch but left patterns 2 and 3 (prose `<name> field` and `fields: <name>`) with no stop-word filter at all; the AC-130-1 then-clause `declares NO join-shaped fields: the earlier jurisdiction ...` fed the word `the` to the extractor and false-failed D6 on WESPA (Ready-to-build no on 0.32.3 against yes on 0.31.0). breaking: false; the 0.32.1, 0.32.2 and 0.32.3 fixes carry forward unchanged. minAgentAction: null.

package/fixtures/canary-manifest.json

@@ -2,8 +2,8 @@
   "registerCanary": [
     {
       "id": "rc-2026-10-07-001",
-      "createdAt": "2026-10-07T11:27:52.587Z",
-      "buildVersion": "0.32.4-mockdriver",
+      "createdAt": "2026-10-07T13:01:30.849Z",
+      "buildVersion": "0.32.5-mockdriver",
       "fixturePromptId": "canary-prompt-01",
       "responseWordCount": 55,
       "grades": {
@@ -35,8 +35,8 @@
     },
     {
       "id": "rc-2026-10-07-002",
-      "createdAt": "2026-10-07T11:27:52.588Z",
-      "buildVersion": "0.32.4-mockdriver",
+      "createdAt": "2026-10-07T13:01:30.850Z",
+      "buildVersion": "0.32.5-mockdriver",
       "fixturePromptId": "canary-prompt-02",
       "responseWordCount": 55,
       "grades": {
@@ -68,8 +68,8 @@
     },
     {
       "id": "rc-2026-10-07-003",
-      "createdAt": "2026-10-07T11:27:52.588Z",
-      "buildVersion": "0.32.4-mockdriver",
+      "createdAt": "2026-10-07T13:01:30.850Z",
+      "buildVersion": "0.32.5-mockdriver",
       "fixturePromptId": "canary-prompt-03",
       "responseWordCount": 55,
       "grades": {

package/guidance/discovery/README.md

@@ -0,0 +1,22 @@
+# guidance/discovery/
+
+Home for project discovery artefacts: discovery briefs, prototype
+notes, exploratory write-ups, and anything else that belongs to a
+specific DISCOVERY-stage effort rather than the methodology pack
+itself.
+
+Files directly under `guidance/` are the methodology inventory,
+locked by `test/guidance/inventory.test.js` and `test/mcp/resources.test.js`
+and reachable through `rcf://docs/<slug>`. New additions there require a
+coordinated test-code change and a manifest update.
+
+Files here, under `guidance/discovery/<slug>.md`, do NOT need a manifest
+update and are not served through the methodology-doc URIs. They still
+carry the guidance posture (no em-dash, no non-canonical external URLs,
+filename stem is a well-formed slug of lowercase letters, digits and
+hyphens); `test/guidance/discovery-home.test.js` enforces that.
+
+Companion home for engineer-facing docs: `docs/discovery/`.
+
+Issue 322 carved out this subdir so a first-time contributor can land a
+discovery brief without touching the methodology lock.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "rcf-lite",
-  "version": "0.32.4",
+  "version": "0.32.5",
   "type": "module",
   "description": "One-install tooling for the Requirements Confidence Framework (RCF): the unified `rcf` CLI grouped into the five RCF tool groups (discover, define, build, verify, audit) plus a small core set (init, doctor, guidance, mcp), an MCP server, the live tree viewer and the fresh-context adversarial ship-gate verifier. Consumes @stravica-ai/rcf-schemas.",
   "license": "Apache-2.0",

package/releases/releases.yaml

@@ -40,8 +40,16 @@
 # `npm install rcf-lite`.
 
 feedVersion: 1
-latest: "0.32.4"
+latest: "0.32.5"
 releases:
+  - version: "0.32.5"
+    date: "2026-10-07"
+    breaking: false
+    headlines:
+      - "rcf-lite 0.32.5 ships two chain-shape fixes surfaced by Dex on the discovery-viewer-command-page branch (reporter). The dogfood walker in test/rcf-tree.test.js now mirrors the sidecar-ledger carve-out from src/define/ledgers.js by importing the new DEFINE_RELATIVE_DIR constant and ignoring rcf/define/, so the first `pnpm rcf define ledger brief add` on a fresh tree no longer blows up three dogfood assertions (issue 321). A new guidance/discovery/ (and companion docs/discovery/) subdir gives project discovery artefacts a predictable home outside the three locked methodology inventories; a first-time contributor can now land a discovery brief without touching the methodology lock or the pack manifest (issue 322). The 0.32.1 through 0.32.4 fixes carry forward unchanged."
+    minAgentAction: null
+    notesUrl: "https://stravica.ai/docs/rcf/changelog/"
+
   - version: "0.32.4"
     date: "2026-10-07"
     breaking: false

package/src/define/ledgers.js

@@ -55,7 +55,15 @@ export const LEDGER_NAMES = /** @type {const} */ (['brief', 'decisions', 'concer
 
 /** @typedef {(typeof LEDGER_NAMES)[number]} LedgerName */
 
-const RELATIVE_DIR = 'rcf/define';
+/**
+ * Project-root-relative directory the ledgers (and the freeze record) live in.
+ * Exported so any walker that enumerates `rcf/` can mirror the carve-out
+ * without a second hard-coded copy (issue 321).
+ */
+export const DEFINE_RELATIVE_DIR = 'rcf/define';
+
+// Legacy alias kept until all internal references migrate.
+const RELATIVE_DIR = DEFINE_RELATIVE_DIR;
 
 /** Per-ledger config: filename, array key on the body, entry schema. */
 const LEDGER_CONFIG = /** @type {const} */ ({