rcf-lite 0.32.3 → 0.32.5

package/CHANGELOG.md

@@ -6,6 +6,23 @@ 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.
+
+### Fixed
+
+- **D6 consistency:unsatisfiable stops reading English stop words out of prose `fields:` lists and `<name> field` phrases (issue 319, w-2026-10-07-dave-003).** `extractThenFieldTokens` in `src/query/gates.js` now shares a broader English stop-word set (`STOP_PATTERN_23`: the, a, an, and, or, of, to, in, on, for, with, by, from, at, as, is, are, be, this, that, these, those, it, its, not, no, all, any, each, per, via, into, than, then, when, which, who, whom, where, while) across patterns 2 and 3, and reuses pattern 4's file-extension skip (md, json, jsonl, ...) and two-character path-context lookbehind on both branches. Pattern 3 additionally walks a comma-separated identifier list after `fields:` so a prose field list such as `required fields: userID, email, createdAt` yields every token it names (one for each missing field), not only the first after the colon. The AC-130-1 WESPA then-clause (sentence-ending `fields: the ...`) is silent on the gate; the AC-060-3 shape (`required fields: userID, email`) is retained and now surfaces every real missing field, not only the first. Pattern 1 is untouched; pattern 4 keeps its 0.32.3 behaviour; the issue 311 and issue 315 fixtures stay green. Regression fixtures in `test/query/gates.test.js` cover a negative control on the AC-130-1 shape, a positive control that both `userID` and `createdAt` fire, and a pattern 2 file-extension / path-context control.
+
 ## [0.32.3] - 2026-10-07
 
 0.32.3 is a hotfix for the 0.32.2 D6 consistency:unsatisfiable regression discovered by Barry on ai-on-record (define/kickoff, head 974b4c1) and second-sourced by Dex on WESPA (26 green-to-red findings in three classes, 2026-10-06 20:05Z). The regression came from pattern 4 of `extractThenFieldTokens` in `src/query/gates.js`, added in PR 313 as part of the issue 311 fix. breaking: false; the 0.32.1 and 0.32.2 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-07T10:44:10.684Z",
-      "buildVersion": "0.32.3-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-07T10:44:10.684Z",
-      "buildVersion": "0.32.3-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-07T10:44:10.684Z",
-      "buildVersion": "0.32.3-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.3",
+  "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,24 @@
 # `npm install rcf-lite`.
 
 feedVersion: 1
-latest: "0.32.3"
+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
+    headlines:
+      - "rcf-lite 0.32.4 is the stop-word follow-up to 0.32.3 after Dex's second-consumer check of PR 318 on WESPA (issue 319). Patterns 2 and 3 of extractThenFieldTokens (prose `<name> field` and `fields: <name>`) now share a broader English stop-word set and reuse pattern 4's file-extension and path-context skips, so the AC-130-1 WESPA then-clause `declares NO join-shaped fields: the earlier jurisdiction ...` stops reading `the` as a record field. Pattern 3 additionally walks a comma-separated list after `fields:` so a real prose field list such as `required fields: userID, email, createdAt` yields every token it names. The 0.32.1, 0.32.2 and 0.32.3 fixes carry forward unchanged."
+    minAgentAction: null
+    notesUrl: "https://stravica.ai/docs/rcf/changelog/"
+
   - version: "0.32.3"
     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} */ ({

package/src/query/gates.js

@@ -2065,6 +2065,26 @@ const PATTERN_4_FILE_EXTENSION_SKIP = new Set([
   'mp4', 'mov', 'log',
 ]);
 
+// English stop-word skip for patterns 2 and 3 (prose field lists).
+// Issue 319 (0.32.4): 0.32.3 moved pattern 4's stop-word skip onto the
+// dot-notation branch but left the pattern 2/3 regex (`<name> field`
+// and `field: <name>` prose) with no stop-word filter at all, so a
+// then-clause like `declares NO join-shaped fields: the earlier
+// jurisdiction ...` fed `the` to the extractor as a field name. The
+// list below is the superset the issue brief named: subject/object
+// stop words, articles, prepositions, demonstratives, auxiliaries and
+// WH-words that have ever been observed sitting next to `field` or
+// after `fields:` in a plain English sentence. Patterns 2 and 3 skip a
+// token drawn from this set unconditionally; pattern 4 keeps its own
+// small stop-word guard as belt-and-braces behind the shape-name gate.
+const STOP_PATTERN_23 = new Set([
+  'the', 'a', 'an', 'and', 'or', 'of', 'to', 'in', 'on', 'for', 'with',
+  'by', 'from', 'at', 'as', 'is', 'are', 'be', 'this', 'that', 'these',
+  'those', 'it', 'its', 'not', 'no', 'all', 'any', 'each', 'per', 'via',
+  'into', 'than', 'then', 'when', 'which', 'who', 'whom', 'where',
+  'while',
+]);
+
 /**
  * Pull field tokens out of a `then` clause. A field token is a word
  * that follows a verb like `set`, `write`, `include`, `return`,
@@ -2099,22 +2119,56 @@ function extractThenFieldTokens(thenClause, shapeNames = new Set()) {
   const text = stripQuotedSubstrings(thenClause);
   /** @type {Set<string>} */
   const tokens = new Set();
+  // Pattern 4's local stop set is the small guard it has carried since
+  // 0.32.3; the broader pattern 2/3 list lives at module scope as
+  // STOP_PATTERN_23 (issue 319).
   const STOP = new Set(['the', 'a', 'an', 'this', 'that', 'its', 'our', 'their', 'any', 'no', 'some', 'each', 'every', 'another']);
 
-  // Pattern 2 (preserved): `<name> field` (adjective-form naming). The
-  // backtick around the name is optional; the stop-word skip keeps
-  // "the field", "a field" and "its field" from tripping the check.
+  // Pattern 2 (narrowed, issue 319): `<name> field` (adjective-form
+  // naming). The backtick around the name is optional. 0.32.3 and
+  // earlier only skipped a short set of articles and demonstratives,
+  // and never skipped file-extension tokens or path-context contexts
+  // on this branch. Pattern 2 now shares the broader STOP_PATTERN_23
+  // list and reuses pattern 4's file-extension and path-context
+  // skips so a prose phrase like `report.json field` or `/path/x
+  // field` does not read a filename stem or path fragment as a
+  // record field.
   for (const m of text.matchAll(/`?\b([A-Za-z_][A-Za-z0-9_]*)`?\s+field\b/g)) {
     const token = m[1];
     if (!token) continue;
-    if (STOP.has(token.toLowerCase())) continue;
+    if (STOP_PATTERN_23.has(token.toLowerCase())) continue;
+    if (PATTERN_4_FILE_EXTENSION_SKIP.has(token.toLowerCase())) continue;
+    const start = m.index ?? 0;
+    const beforeHead = text.slice(Math.max(0, start - 2), start);
+    if (/\//.test(beforeHead)) continue;
     tokens.add(token);
   }
-  // Pattern 3 (preserved): `field: <name>` or `field = <name>`
-  // (schema-like notation inside a then clause). The name's backtick
-  // is optional.
-  for (const m of text.matchAll(/\bfields?\s*[:=]\s*`?([A-Za-z_][A-Za-z0-9_]*)`?/g)) {
-    if (m[1]) tokens.add(m[1]);
+  // Pattern 3 (narrowed, issue 319): `fields: <name>` or `fields =
+  // <name>` (schema-like notation inside a then clause). Walks a
+  // comma-separated list after the colon so prose like `required
+  // fields: userID, email, createdAt` yields all three candidates,
+  // not just the first. Three skips apply to every candidate:
+  //   - STOP_PATTERN_23 (English stop words such as `the` from
+  //     `declares NO join-shaped fields: the earlier jurisdiction
+  //     ...`, the AC-130-1 WESPA shape in issue 319);
+  //   - PATTERN_4_FILE_EXTENSION_SKIP (file-extension tokens such
+  //     as `md`, `json`, `yaml`);
+  //   - path context (two characters before `fields:` contain `/`),
+  //     mirroring pattern 4's path-context guard so a prose line
+  //     inside a path reference does not read as a field list.
+  for (const m of text.matchAll(/\bfields?\s*[:=]\s*(`?[A-Za-z_][A-Za-z0-9_]*`?(?:\s*,\s*`?[A-Za-z_][A-Za-z0-9_]*`?)*)/g)) {
+    const start = m.index ?? 0;
+    const beforeHead = text.slice(Math.max(0, start - 2), start);
+    if (/\//.test(beforeHead)) continue;
+    const list = m[1];
+    if (!list) continue;
+    for (const raw of list.split(/\s*,\s*/)) {
+      const name = raw.replace(/^`/, '').replace(/`$/, '');
+      if (!name) continue;
+      if (STOP_PATTERN_23.has(name.toLowerCase())) continue;
+      if (PATTERN_4_FILE_EXTENSION_SKIP.has(name.toLowerCase())) continue;
+      tokens.add(name);
+    }
   }
   // Pattern 4 (narrowed, issue 315): `<ShapeName>.<fieldName>` dot
   // notation. Shape names are PascalCase. 0.32.2 emitted a field