rcf-lite 0.8.0 → 0.9.0

package/CHANGELOG.md

@@ -4,6 +4,47 @@ All notable changes to this project are documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). Pre-1.0, breaking changes are signalled by a minor version bump.
 
+## [0.9.0] - 2026-08-25
+
+The blueprint-mechanism release. Ships Phase 1 blueprint composition (standards + selective retrieval), Phase 3.5 conflict-resolution verbs, the 0.4.4 prefix-family id grammar seam, and the first content packages built on the mechanism: SPA (v1.0.0 through v1.3.0 including the styled-under-CSP and deployment-gate cures), auth (v1.0.0 magic-link + opaque cookie sessions), persistence (v1.0.0 SQLite-first store), ci-pipeline (v1.0.0), observability (v1.0.0), and REST (16 REQ / 20 US / 117 AC doc set). Consumes `@stravica-ai/rcf-schemas@0.4.5` (exact pin, additive-only from 0.4.3 through 0.4.5).
+
+### Added (release cycle roll-up)
+
+Detailed entries below cover the Phase 3.5 verbs (PR #90). The following merges since 0.8.0 also ship in this release and are not itemised further here; each landed with its own tests, docs, and (where applicable) fbs / us / adr chain:
+
+- **PR #83 Phase 1 blueprint mechanism.** Blueprint composition, standards ruleset wiring, selective retrieval. Foundation for every `blueprint/*-v1.0.0` PR that follows.
+- **PR #84 walker + loader for the 0.4.4 prefix-family id grammar (w-2026-08-19-001).** Teaches the store walker and loader the widened id shapes admitted by `@stravica-ai/rcf-schemas@0.4.4` so prefix-family ids (e.g. `FBS-004-user-login`, `US-1002`, four-digit TS / TC ids) round-trip through the graph without silent detachment.
+- **PR #86 SPA blueprint content package (w-2026-08-19-001).** First content package on the blueprint mechanism.
+- **PR #87 Phase 1 blueprint mechanism, eight post-review nits.**
+- **PR #88 blueprint ownership fix (w-2026-08-19-005).** Ownership checks consult the authoritative manifest record, not string grammar.
+- **PR #89 REST blueprint content package (w-2026-08-19-005, d-2026-08-19-007).** 16 REQ / 20 US (117 AC) / 6 TAC / 8 ADR doc set with OpenAPI skeleton, auth-class reference, samples, guide, topics vocabulary.
+- **PR #91 blueprint authoring documentation.** Standard, walkthrough, checklist, plus their registration in the links manifest.
+- **PR #92 pre-handover fix batch.** Three CLI paper-cuts, doc fixes, agent-block nudges.
+- **PR #93 auth blueprint v1.0.0.** Passwordless magic-link plus opaque cookie sessions.
+- **PR #94 persistence blueprint v1.0.0.** SQLite-first store with a forward-only migration runner.
+- **PR #95 ci-pipeline blueprint v1.0.0.**
+- **PR #96 observability blueprint v1.0.0.** Two-endpoint HTTP health probes, public status page, notification-outcome sink.
+- **PR #97 SPA blueprint v1.1.0.** Icon and token mechanism-reach cure.
+- **PR #98 SPA blueprint v1.2.0.** Styled-under-shipped-CSP mechanism-reach cure, plus the `noInlineStyleBlocks` invariant on the rcf-lite side.
+- **PR #99 SPA blueprint v1.3.0 (w-2026-08-24-006).** External-dep provisioning, core-flow E2E deployment-gate class cure, plus the rcf-lite placeholder-shape detector.
+
+### Added (blueprint conflict-resolution verbs, w-2026-08-19-008)
+
+- **`src/blueprint/resolutions.js`.** Pure helpers on top of the new `manifest.resolutions[]` seam (rcf-schemas 0.4.5): `nextResolutionId(manifest, now)` mints monotonic `res-YYYY-MM-DD-NNN` ids; `matchingResolution(manifest, { topic, incoming, existing })` returns the resolution record that resolves a specific globalAdrTopic conflict pair, matching on kind + topic + both `{slug, adrId}` pairs listed in `supersedes[]` (superset OK, subset not).
+- **`src/blueprint/supersede.js` + `rcf blueprint supersede <topic>` verb.** Scaffolds a project-level ADR at `rcf/adrs/adr-NNN-<topic>.json` (well-formed against `adr.schema.json`, editable stubs) that supersedes every applied blueprint's scope:global ADR on the topic, and appends a `manifest.resolutions[]` record so the detector honours the resolution on subsequent `rcf blueprint add` runs. Refuses when the topic has fewer than two applied scope:global ADRs, when the manifest is missing prd or tad, and when a file already exists at the scaffolded ADR path. Optional `--reason` operator note; whitespace-only reasons are refused at the writer edge.
+- **`rcf blueprint add --resolve <topic>=project:<ADR-id>` flag.** Repeatable per conflicted topic. Records a `manifest.resolutions[]` entry in-memory BEFORE conflict detection runs, so a freshly declared resolution is honoured; the record then persists via the manifest write alongside the applied-blueprint update. Refuses declarations whose topic does not match a scope:global ADR on the incoming blueprint, whose topic has no matching applied blueprint, whose `resolvedByAdrId` is mis-shaped, or whose `--reason` is whitespace-only.
+- **`src/blueprint/conflicts.js` reshape.** `detectGlobalAdrConflicts` accepts an optional manifest and honours matching resolutions. `renderConflictReport` now leads each conflict block with per-side `blueprint <slug>: <title> — <decision>` headers (falls back to `<id> at <path>` when the tree did not carry the ADR body), footers ids + paths under `refs:`, and names four honest resolution paths (adopt-incoming, keep-existing, supersede via project ADR, declare-on-add via `--resolve`) with the actual conflicting blueprint slugs already substituted — no `<slug>` placeholders. New `conflictReportJson(conflicts)` returns the same shape as a machine-readable object for agent-driven composition.
+- **`src/blueprint/apply.js` enrichment.** ADR title + one-sentence decision are pulled off `tree.byId` for the existing side and threaded onto the conflict record so the renderer's per-side headers render cleanly.
+- **`src/blueprint/diff.js` + `rcf blueprint diff <topic>` verb.** Read-only side-by-side view of every applied blueprint's scope:global ADR on a topic: id, path, title, status, decision.
+- **`src/cli/blueprint.js` wiring.** New verbs `supersede`, `diff`; new flags `--resolve` (repeatable), `--reason`, `--json` on `add`.
+- **`src/blueprint/index.js` re-exports** the new APIs: `nextResolutionId`, `matchingResolution`, `supersedeBlueprintTopic`, `diffBlueprintTopic`, `renderDiff`, `conflictReportJson`, `detectCrossBlueprintClaims`.
+- **New tests.** `test/blueprint/resolutions.test.js` (10), `test/blueprint/supersede.test.js` (5), `test/blueprint/coresidence.test.js` (3 — the SPA + REST co-residence money paths via supersede-first, declare-on-add, and honour-idempotency), `test/blueprint/diff.test.js` (4), plus 5 new cases on `test/blueprint/cli.test.js` (--resolve success + reshape refuse, --json refuse + apply, supersede verb, diff verb, --resolve validation) and 2 updated cases on `test/blueprint/conflicts.test.js` (reshape assertions).
+- **`fbs-017` + `us-1002` prose refresh (residual fold-in).** `fbs/fbs-017.json` approach + notes now name the manifest-record ownership model (Phase 3.5 rewrite of the earlier grammar narrative) and the Phase 3.5 verbs; `user-stories/us-1002.json` AC-1002-3 now describes the reshaped four-honest-paths message rather than the pre-Phase-3.5 three-path placeholder prose. `test/view/fixtures/phase-3-6-static.html` regenerated to match.
+
+### Changed
+
+- **`packages/rcf-lite/package.json`** dependency `@stravica-ai/rcf-schemas` bumped `0.4.4 -> 0.4.5` (exact pin, per the umbrella exact-pin doctrine). 0.4.5 is an additive-only patch adding `manifest.resolutions[]`.
+
 ## [0.8.0] - 2026-08-12 (on `slug-train/0.8.0`, PR pending)
 
 ### Added (Car 4, verify updates per requirements doc)

package/bin/rcf.js

@@ -36,6 +36,9 @@ import { main as uiBaselineMain } from '../src/cli/ui-baseline.js';
 import { main as uiClassifyMain } from '../src/cli/ui-classify.js';
 import { main as designMain } from '../src/cli/design.js';
 import { main as browserVerifyMain } from '../src/cli/browser-verify.js';
+// Blueprint mechanism (Phase 1, w-2026-08-18-016).
+import { main as blueprintMain } from '../src/cli/blueprint.js';
+import { main as standardsMain } from '../src/cli/standards.js';
 import { main as updateMain } from '../src/cli/update.js';
 import { main as validateMain } from '../src/cli/validate.js';
 import { main as viewMain } from '../src/cli/view.js';
@@ -76,6 +79,9 @@ export const SUBCOMMANDS = {
   'ui-baseline': uiBaselineMain,
   design: designMain,
   'browser-verify': browserVerifyMain,
+  // Blueprint mechanism (Phase 1, w-2026-08-18-016).
+  blueprint: blueprintMain,
+  standards: standardsMain,
   // Track C+D (elicitation-and-playbook-hardening-0.7.0) verbs.
   'req-classify': reqClassifyMain,
   'req-baseline': reqBaselineMain,

package/fixtures/canary-manifest.json

@@ -1,9 +1,9 @@
 {
   "registerCanary": [
     {
-      "id": "rc-2026-08-12-001",
-      "createdAt": "2026-08-12T16:39:41.040Z",
-      "buildVersion": "0.8.0-mockdriver",
+      "id": "rc-2026-08-25-001",
+      "createdAt": "2026-08-25T14:47:32.185Z",
+      "buildVersion": "0.9.0-mockdriver",
       "fixturePromptId": "canary-prompt-01",
       "responseWordCount": 55,
       "grades": {
@@ -34,9 +34,9 @@
       "shipDespiteFailReason": "mock canary driver used; no real subagent was dispatched. This record verifies canary infrastructure only, not the register itself."
     },
     {
-      "id": "rc-2026-08-12-002",
-      "createdAt": "2026-08-12T16:39:41.041Z",
-      "buildVersion": "0.8.0-mockdriver",
+      "id": "rc-2026-08-25-002",
+      "createdAt": "2026-08-25T14:47:32.185Z",
+      "buildVersion": "0.9.0-mockdriver",
       "fixturePromptId": "canary-prompt-02",
       "responseWordCount": 55,
       "grades": {
@@ -67,9 +67,9 @@
       "shipDespiteFailReason": "mock canary driver used; no real subagent was dispatched. This record verifies canary infrastructure only, not the register itself."
     },
     {
-      "id": "rc-2026-08-12-003",
-      "createdAt": "2026-08-12T16:39:41.041Z",
-      "buildVersion": "0.8.0-mockdriver",
+      "id": "rc-2026-08-25-003",
+      "createdAt": "2026-08-25T14:47:32.185Z",
+      "buildVersion": "0.9.0-mockdriver",
       "fixturePromptId": "canary-prompt-03",
       "responseWordCount": 55,
       "grades": {

package/guidance/harness-template.md

@@ -42,6 +42,17 @@ non-technical; the method must be invisible in what they read.
   not ask the operator to look it up for you.
 - Never re-ask a granted permission. Track what the operator has
   authorised and act on it. Asking again reads as not listening.
+- Do not announce work you are about to do; do it, then report.
+  "I'll now run coverage and check the tree" burns a turn. Run the
+  check, report the outcome. Announce only when the work needs
+  authorisation you do not already have, or when it will take long
+  enough that silence would look like a stall.
+- When the operator asks whether something works, answer with
+  evidence. Run the check, cite the command and the output. "Yes,
+  the health endpoint returns 200 - `curl -sS localhost:8080/health`
+  -> `{ok:true}`" is the shape. Never answer from memory of what
+  should be true; the method exists to make that class of answer
+  impossible.
 - Tone: it is in hand. The operator steers; you drive. Confident
   without hedging, and plainly honest when something is genuinely
   blocked or ambiguous.

package/guidance/managed/agent-instructions-block.hash

@@ -1 +1 @@
-24d596ffef22c1f55fdad901ce424e443caade9cd44e8d659f17f14f1ef1ac47
+7f5e3c3bd4c2c6c4bc7d98d77f7d715c7c43278a39e5ecfd0e85ed8d64e199f5

package/guidance/managed/agent-instructions-block.md

@@ -29,6 +29,17 @@ non-technical; the method must be invisible in what they read.
   not ask the operator to look it up for you.
 - Never re-ask a granted permission. Track what the operator has
   authorised and act on it. Asking again reads as not listening.
+- Do not announce work you are about to do; do it, then report.
+  "I'll now run coverage and check the tree" burns a turn. Run the
+  check, report the outcome. Announce only when the work needs
+  authorisation you do not already have, or when it will take long
+  enough that silence would look like a stall.
+- When the operator asks whether something works, answer with
+  evidence. Run the check, cite the command and the output. "Yes,
+  the health endpoint returns 200 - `curl -sS localhost:8080/health`
+  -> `{ok:true}`" is the shape. Never answer from memory of what
+  should be true; the method exists to make that class of answer
+  impossible.
 - Tone: it is in hand. The operator steers; you drive. Confident
   without hedging, and plainly honest when something is genuinely
   blocked or ambiguous.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "rcf-lite",
-  "version": "0.8.0",
+  "version": "0.9.0",
   "type": "module",
   "description": "One-install tooling for the Requirements Confidence Framework (RCF): the unified `rcf` CLI (init, view, validate, build, verify, finalise and 25+ more verbs), an MCP server, the live tree viewer and the fresh-context adversarial ship-gate verifier. Consumes @stravica-ai/rcf-schemas.",
   "license": "Apache-2.0",
@@ -58,7 +58,7 @@
     "#admissibility": "./src/admissibility/index.js"
   },
   "dependencies": {
-    "@stravica-ai/rcf-schemas": "0.4.3",
+    "@stravica-ai/rcf-schemas": "0.4.5",
     "ajv": "^8.20.0",
     "ajv-formats": "^3.0.1"
   },

package/rcf/adrs/adr-010.json

@@ -0,0 +1,30 @@
+{
+  "adrId": "ADR-010",
+  "prdId": "PRD-001",
+  "tadId": "TAD-001",
+  "version": "1.0.0",
+  "status": "accepted",
+  "title": "Blueprint conflict-topic vocabulary is a free-label lookup key (camelCase canonical on shipped blueprints)",
+  "context": "Round-1 of Phase 3.5 (w-2026-08-19-008) gate-tightened the topic vocabulary at the supersede writer by requiring topics to be kebab slugs; the SHIPPED SPA and REST blueprints declare their scope:global ADR topics in camelCase (authModel, errorEnvelope, clientRouting, theming, clientState, apiVersioning, logging), so following the reshaped conflict message's option 3 exactly as printed exited 2 with 'not a valid kebab slug' on every shipped topic. The 0.4.5 manifest schema is silent on topic character class (minLength: 1) and the schema docs cite errorEnvelope as an example. Gate-tightening past the schema is a first-class defect on this estate.",
+  "decision": "The blueprint conflict-topic vocabulary is a FREE LABEL — a lookup key used by the conflict detector (exact-match between an incoming ADR's declared topic and each applied ADR's declared topic) and by the resolution record (verbatim on manifest.resolutions[].topic). No character-class constraint beyond the schema's own minLength: 1 plus a writer-edge whitespace-only refuse. The shipped blueprint packs are canonical: their topics MUST be camelCase kebab-free single-word or camelCase identifiers (authModel, errorEnvelope, clientRouting, ...); new shipped blueprints follow the same convention. When a topic string must be projected into an id grammar that does require a kebab slug (specifically the scaffolded project-ADR id tail, whose grammar is `^ADR-\\d{3,}(-[a-z0-9]+(?:-[a-z0-9]+)*)?$`), the writer kebab-ifies at the projection edge (`authModel` -> `ADR-NNN-auth-model`) and never at the vocabulary edge.",
+  "consequences": "The reshaped conflict message's option 3 executes verbatim from the refused-add state against the shipped SPA + REST blueprints. Topic strings on manifest.resolutions[].topic remain byte-identical to the topic strings on the applied blueprint's ADR.contributions[].topic, so exact-match lookup is trivial to reason about. Kebab-ification is confined to the project-ADR id tail; the same topic string may appear verbatim in the manifest and kebab-cased inside an ADR id in the same tree without conflict. Blueprint authors who ship non-camelCase topics (kebab-case, snake_case) still validate against the schema; the exact-match detector still functions; only the ADR id tail projection changes.",
+  "alternativesConsidered": [
+    {
+      "name": "Enforce kebab-slug topics at the writer edge",
+      "summary": "Reject any topic string that is not `[a-z][a-z0-9]*(?:-[a-z0-9]+)*` at supersede and add --resolve.",
+      "reasonNotChosen": "Gate-tightens past the manifest schema (which is minLength: 1 with no character constraint), incompatible with the shipped SPA + REST blueprints' camelCase topic vocabulary, and made option 3 unexecutable as printed against the shipped packs."
+    },
+    {
+      "name": "Retroactively kebab-case the shipped blueprint packs' topics",
+      "summary": "Change SPA + REST blueprints to declare kebab topics (auth-model, error-envelope, ...); consumers migrate.",
+      "reasonNotChosen": "The blueprint packs are canonical content the mechanism serves; the mechanism does not get to dictate the packs' vocabulary. camelCase is a legitimate identifier shape (the schema examples confirm it)."
+    },
+    {
+      "name": "Normalise topics at the detector",
+      "summary": "Fold both sides to a canonical form (kebab or lowercased-strip-nonalnum) before comparing.",
+      "reasonNotChosen": "Introduces vocabulary drift (two different topic strings comparing equal) and makes the operator's mental model of what matches what harder, not easier. Exact-match on the free label is the least surprising rule."
+    }
+  ],
+  "createdAt": "2026-08-19T15:45:00.000Z",
+  "updatedAt": "2026-08-19T15:45:00.000Z"
+}

package/rcf/code-nodes/cn-058.json

@@ -0,0 +1,18 @@
+{
+  "cnId": "CN-058",
+  "path": "src/blueprint/apply.js#applyBlueprint",
+  "title": "Blueprint apply orchestrator",
+  "description": "Loads a blueprint from a source directory, runs the conflict-detection pass BEFORE any file write, stamps contribution ids into the blueprint's namespace, copies contribution files into the tree, and appends a validated entry to manifest.blueprints[]. Idempotent on same-slug + same-version re-apply. From Phase 3.5 (w-2026-08-19-008) also composes any operator --resolve declarations into manifest.resolutions[] BEFORE detection so the resolution is honoured this run and persists alongside the applied-blueprint update, wires the singular --reason onto every generated declaration (whitespace-only refused at the writer edge), and dedupes duplicate --resolve topics within a single add (first-wins) surfacing a warning to the caller.",
+  "implementsAcIds": [
+    "AC-1001-1",
+    "AC-1001-4",
+    "AC-1002-2",
+    "AC-1002-6",
+    "AC-1002-7"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-08-19T00:00:00Z",
+  "updatedAt": "2026-08-19T00:00:00Z"
+}

package/rcf/code-nodes/cn-059.json

@@ -0,0 +1,14 @@
+{
+  "cnId": "CN-059",
+  "path": "src/blueprint/list.js#listBlueprints",
+  "title": "Blueprint list projection",
+  "description": "Reads manifest.blueprints[] and returns rows in appliedAt order.",
+  "implementsAcIds": [
+    "AC-1001-2"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-08-19T00:00:00Z",
+  "updatedAt": "2026-08-19T00:00:00Z"
+}

package/rcf/code-nodes/cn-060.json

@@ -0,0 +1,14 @@
+{
+  "cnId": "CN-060",
+  "path": "src/blueprint/remove.js#removeBlueprint",
+  "title": "Blueprint remove with referring-doc guard",
+  "description": "Refuses when any project-authored doc references a contribution id; otherwise unlinks contribution files and rewrites the manifest.",
+  "implementsAcIds": [
+    "AC-1001-3"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-08-19T00:00:00Z",
+  "updatedAt": "2026-08-19T00:00:00Z"
+}

package/rcf/code-nodes/cn-061.json

@@ -0,0 +1,14 @@
+{
+  "cnId": "CN-061",
+  "path": "src/cli/blueprint.js#main",
+  "title": "rcf blueprint CLI dispatcher",
+  "description": "Wires the blueprint verb family into the unified rcf bin; dispatches add|list|remove.",
+  "implementsAcIds": [
+    "AC-1001-5"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-08-19T00:00:00Z",
+  "updatedAt": "2026-08-19T00:00:00Z"
+}

package/rcf/code-nodes/cn-062.json

@@ -0,0 +1,14 @@
+{
+  "cnId": "CN-062",
+  "path": "src/blueprint/namespace.js#stampId",
+  "title": "Blueprint id namespacing (prefix + suffix families)",
+  "description": "Stamps a doc id with a blueprint slug according to family: prefix for REQ/US/PRD/BS/TAD/TS, suffix for ADR/TAC/FBS/CN.",
+  "implementsAcIds": [
+    "AC-1002-1"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-08-19T00:00:00Z",
+  "updatedAt": "2026-08-19T00:00:00Z"
+}

package/rcf/code-nodes/cn-063.json

@@ -0,0 +1,15 @@
+{
+  "cnId": "CN-063",
+  "path": "src/blueprint/conflicts.js#detectGlobalAdrConflicts",
+  "title": "scope:global ADR conflict detection",
+  "description": "Detects two applied blueprints each contributing a scope:global ADR on the same topic; returns Conflict records.",
+  "implementsAcIds": [
+    "AC-1002-2",
+    "AC-1002-4"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-08-19T00:00:00Z",
+  "updatedAt": "2026-08-19T00:00:00Z"
+}

package/rcf/code-nodes/cn-064.json

@@ -0,0 +1,15 @@
+{
+  "cnId": "CN-064",
+  "path": "src/blueprint/conflicts.js#renderConflictReport",
+  "title": "Conflict-presentation report writer",
+  "description": "Renders a Conflict[] list into an operator-facing block with per-side `blueprint <slug>: <title> — <decision>` headers (Phase 3.5 reshape; falls back to `<id> at <path>` when the tree did not carry the ADR body), a refs footer, and four honest resolution paths with actual conflicting blueprint slugs substituted. Symmetric enrichment: BOTH sides (incoming from the blueprint's ADR file on disk, existing from the walker's tree) are decorated with title + one-sentence decision before rendering. A parallel `conflictReportJson(conflicts)` returns the same shape as a JSON object with per-conflict `resolutions[]` triples for agent-driven composition.",
+  "implementsAcIds": [
+    "AC-1002-3",
+    "AC-1002-8"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-08-19T00:00:00Z",
+  "updatedAt": "2026-08-19T00:00:00Z"
+}

package/rcf/code-nodes/cn-065.json

@@ -0,0 +1,16 @@
+{
+  "cnId": "CN-065",
+  "path": "src/blueprint/standards.js#registerStandardsPack",
+  "title": "Standards ingestion (reference-by-default + out-of-root copy)",
+  "description": "Detects whether the source lives inside the project root; references-in-place when yes, copies into rcf/standards/<slug>/ when no; writes the manifest.standards[] entry.",
+  "implementsAcIds": [
+    "AC-1003-1",
+    "AC-1003-2",
+    "AC-1003-3"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-08-19T00:00:00Z",
+  "updatedAt": "2026-08-19T00:00:00Z"
+}

package/rcf/code-nodes/cn-066.json

@@ -0,0 +1,14 @@
+{
+  "cnId": "CN-066",
+  "path": "src/cli/standards.js#main",
+  "title": "rcf standards CLI dispatcher",
+  "description": "Wires the standards verb family into the unified rcf bin; dispatches add|list.",
+  "implementsAcIds": [
+    "AC-1003-4"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-08-19T00:00:00Z",
+  "updatedAt": "2026-08-19T00:00:00Z"
+}

package/rcf/code-nodes/cn-067.json

@@ -0,0 +1,15 @@
+{
+  "cnId": "CN-067",
+  "path": "src/build/standards-selector.js#selectStandards",
+  "title": "Deterministic tag-scoring standards selector",
+  "description": "Reads FBS work text against manifest standards tags and returns the deterministic subset of relevant slugs.",
+  "implementsAcIds": [
+    "AC-1004-1",
+    "AC-1004-4"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-08-19T00:00:00Z",
+  "updatedAt": "2026-08-19T00:00:00Z"
+}

package/rcf/code-nodes/cn-068.json

@@ -0,0 +1,15 @@
+{
+  "cnId": "CN-068",
+  "path": "src/build/bundle.js#assembleBundle",
+  "title": "Bundle assembler standardIds host (0.4.4)",
+  "description": "Bundle assembler branch that hosts operator-authored contextRequirements.standardIds override + agentic selection, and renders the standards payload alongside TACs/ADRs.",
+  "implementsAcIds": [
+    "AC-1004-2",
+    "AC-1004-3"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-08-19T00:00:00Z",
+  "updatedAt": "2026-08-19T00:00:00Z"
+}

package/rcf/code-nodes/cn-069.json

@@ -0,0 +1,16 @@
+{
+  "cnId": "CN-069",
+  "path": "src/blueprint/supersede.js#supersedeBlueprintTopic",
+  "title": "Project-ADR supersession scaffolder (conflict-pair second side)",
+  "description": "Scaffolds a project-level ADR under rcf/adrs/adr-NNN-<kebab-topic>.json that supersedes the CONFLICT PAIR on the topic (one currently-applied blueprint's scope:global ADR + one incoming blueprint's scope:global ADR — Baz ruling, w-2026-08-19-008 round 3), and appends a matching manifest.resolutions[] record so the conflict detector honours the resolution when the operator re-runs `rcf blueprint add <incoming source>`. The verb accepts an optional `--incoming <source>` argument (required when applied count on the topic is < 2; informational when >= 2): the verb loads the incoming blueprint from disk, finds its scope:global ADR on the topic, stamps the id into the incoming blueprint's namespace, and uses that {slug, adrId} as the second side of supersedes[]. This lets option 3 as printed by the reshaped conflict message execute VERBATIM from the refused-add state — no --resolve prep, no menu-copy weakening. Topic is a LOOKUP KEY (see ADR-010): any string that exact-matches an applied ADR's declared topic is accepted (schema minLength:1, whitespace-only refused at the writer edge; camelCase, snake_case and kebab-case all pass). The scaffolded ADR id derives its slug tail by kebab-ifying the topic (`authModel` -> `ADR-NNN-auth-model`) so the ADR grammar's `[a-z0-9](-[a-z0-9]+)*` tail is satisfied. Every rcfError message returned by this module is prefix-free (no `blueprint supersede: ` in the message body); the CLI edge prepends the single `[error] blueprint supersede: ` line. Refuses when the manifest is missing prd or tad, when applied+incoming count on the topic is < 2, and when a file already exists at the scaffolded ADR path.",
+  "implementsAcIds": [
+    "AC-1002-5",
+    "AC-1002-9",
+    "AC-1002-10"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-08-19T14:35:00.000Z",
+  "updatedAt": "2026-08-19T14:35:00.000Z"
+}

package/rcf/fbs/fbs-016.json

@@ -0,0 +1,39 @@
+{
+  "fbsId": "FBS-016",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 16,
+  "executionStatus": "notStarted",
+  "title": "Blueprint verb family (add, list, remove, upgrade) with manifest.blueprints[] writes",
+  "summary": "Introduce the `rcf blueprint <verb>` verb family and its manifest-writing path. Adds `src/blueprint/` module (loader, applier, contribution-writer) and `src/cli/blueprint.js` (parseArgs, dispatch, HELP block). Adds `blueprint` to the top-level SUBCOMMANDS map on `bin/rcf.js` and to the `TOP_LEVEL` block on `src/cli/help.js` so `rcf --help` advertises it. Every apply writes an entry to `manifest.blueprints[]` per the 0.4.4 schema (slug, version, appliedAt, source, namespace, contributions[]). `add` is idempotent on a clean re-apply; `remove` refuses when any project-authored doc references a contribution id.",
+  "approach": "One dispatcher, one loader, one applier, one writer. bin/rcf.js gains `blueprint: blueprintMain` on SUBCOMMANDS; src/cli/blueprint.js parses `add|list|remove|upgrade` and dispatches to src/blueprint/ handlers. Blueprint loading is a small package-metadata reader (slug, version, ADR contributions with optional scope, doc contributions manifest); Phase 1 keeps the resolver `file://` and `link:` only, with the registry/git-ref shape captured in the source string so the schema forward-compat holds. Contribution writing goes through the existing store writer paths so a blueprint apply produces the same doc files a hand-created doc would. Removal is a manifest patch + contribution-path unlink; the referring-doc check reuses the existing tree walker to enumerate every string field for id occurrences.",
+  "deliverables": [
+    "src/cli/blueprint.js: parseArgs + HELP + main() dispatching add/list/remove/upgrade",
+    "src/blueprint/index.js: barrel re-exporting apply, list, remove, upgrade, loadBlueprint, detectGlobalAdrConflicts",
+    "src/blueprint/apply.js: apply(tree, blueprint, opts) — idempotency + conflict detection + contribution writes + manifest update",
+    "src/blueprint/loader.js: loadBlueprint(source) — reads a blueprint's metadata (slug, version, ADR contributions with scope, doc contributions)",
+    "src/blueprint/remove.js: remove(tree, slug, opts) — referring-doc scan + manifest patch + file unlinks",
+    "src/blueprint/list.js: list(tree) — reads manifest.blueprints[] and returns rows",
+    "bin/rcf.js: `blueprint: blueprintMain` on SUBCOMMANDS",
+    "src/cli/help.js: `blueprint <verb>` on the TOP_LEVEL block, `help blueprint` prints the blueprint HELP",
+    "test/blueprint/apply.test.js, list.test.js, remove.test.js, cli.test.js — behaviour tests keyed to AC-1001-1..5"
+  ],
+  "acIds": [
+    "AC-1001-1",
+    "AC-1001-2",
+    "AC-1001-3",
+    "AC-1001-4",
+    "AC-1001-5"
+  ],
+  "contextRequirements": {
+    "tacIds": [],
+    "adrIds": []
+  },
+  "dependsOnFbsIds": [],
+  "domain": "cli",
+  "estimatedSize": "medium",
+  "riskLevel": "low",
+  "notes": "Landing car of Phase 1 blueprint mechanism (w-2026-08-18-016, design-brief.md v2 §Composition model). Written against @stravica-ai/rcf-schemas 0.4.4 (blueprints[] host schema); dev pin to feature/blueprint-additive-0.4.4 on the schemas repo carries until the Baz 2FA publish flips the pin to registry-resolved 0.4.4.",
+  "createdAt": "2026-08-18T22:56:02.353Z",
+  "updatedAt": "2026-08-18T22:56:02.353Z"
+}

package/rcf/fbs/fbs-017.json

@@ -0,0 +1,40 @@
+{
+  "fbsId": "FBS-017",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 17,
+  "executionStatus": "notStarted",
+  "title": "Namespaced blueprint ids and scope:global ADR conflict surfacing",
+  "summary": "Blueprint-contributed docs are namespaced by the blueprint's slug: REQ/US/PRD/BS/TAD/TS via the 0.4.4 slug PREFIX (e.g. `spa-REQ-001`), and ADR/TAC/FBS/CN via the 0.4.3 kebab SUFFIX (e.g. `ADR-005-rest-versioning`). `rcf blueprint add` runs a conflict-detection pass BEFORE writing anything: two blueprints both contributing an ADR tagged `scope: global` on the same topic exit non-zero with both sides printed and four honest resolution paths named (adopt-incoming, keep-existing, supersede via project ADR, declare-on-add via `--resolve`). Non-global TACs, ADRs, REQs, USs and FBSes namespace cleanly and cannot topic-conflict; cross-blueprint id claims (an incoming id already recorded on another applied blueprint) are refused via the authoritative manifest record, not string grammar.",
+  "approach": "Namespacing is enforced at the loader: contribution ids are stamped with the blueprint slug at load time; a contribution whose declared id already carries a namespace is trusted verbatim (author declaration is the truth for what that blueprint owns; the earlier grammar-veto of legitimate slug-tail ids like `ADR-201-spa-theme` under blueprint `spa` was retired in w-2026-08-19-005). Ownership of a written contribution is answered by the manifest's `appliedBlueprintRecord.contributions[]` list — the authoritative record — not by re-parsing the id string. Conflict detection reads the applied `blueprints[]` and the applying blueprint's contributions, and scores collisions along two axes: `scope: global` ADR topic collision (two applied ADRs both tagged `scope: global` with a matching `topic` field), and cross-blueprint ownership (an incoming id whose manifest record is on a DIFFERENT applied blueprint's contribution list — the class the record consultation catches once grammar stopped being a trust surface). Presentation: per-conflict block leads with both ADR titles and their one-sentence decisions, ids and paths as a footer, and four honest resolution paths with actual blueprint slugs filled in — no placeholders. A `--json` output shape is available for agent-driven composition. Phase 3.5 (w-2026-08-19-008) added the `supersede` and `diff` verbs plus the `--resolve` add-time flag, backed by `manifest.resolutions[]` on the 0.4.5 schema; both blueprint ADRs may now co-reside on disk as superseded history alongside a project-level ADR that supersedes them.",
+  "deliverables": [
+    "src/blueprint/namespace.js: pure functions that stamp/verify contribution namespacing for all doc kinds",
+    "src/blueprint/conflicts.js: detectGlobalAdrConflicts(appliedBlueprints, incomingContributions) returning zero-or-more Conflict records",
+    "Updates to src/blueprint/apply.js: conflict pass runs BEFORE any file write; non-empty conflict list short-circuits with a printed report + non-zero exit",
+    "test/blueprint/namespace.test.js: prefix/suffix stamping tests keyed to AC-1002-1",
+    "test/blueprint/conflicts.test.js: global-ADR conflict cases keyed to AC-1002-2 / AC-1002-3, non-conflict cases for AC-1002-4"
+  ],
+  "acIds": [
+    "AC-1002-1",
+    "AC-1002-2",
+    "AC-1002-3",
+    "AC-1002-4",
+    "AC-1002-5",
+    "AC-1002-6",
+    "AC-1002-7",
+    "AC-1002-8",
+    "AC-1002-9",
+    "AC-1002-10"
+  ],
+  "contextRequirements": {
+    "tacIds": [],
+    "adrIds": []
+  },
+  "dependsOnFbsIds": ["FBS-016"],
+  "domain": "cli",
+  "estimatedSize": "medium",
+  "riskLevel": "medium",
+  "notes": "Prototype-unknown #1 (design-brief.md v2 §Depth for v1) — conflict-presentation ergonomics settled here as first pass; Phase 3 (REST blueprint) exposed the ergonomic friction against the real SPA+REST conflict; Phase 3.5 (w-2026-08-19-008) reshaped the message and added the supersede / diff / --resolve verbs plus the `manifest.resolutions[]` seam (rcf-schemas 0.4.5). Ownership-via-manifest-record rewrite landed separately in w-2026-08-19-005.",
+  "createdAt": "2026-08-18T22:56:02.353Z",
+  "updatedAt": "2026-08-18T22:56:02.353Z"
+}

package/rcf/fbs/fbs-018.json

@@ -0,0 +1,34 @@
+{
+  "fbsId": "FBS-018",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 18,
+  "executionStatus": "notStarted",
+  "title": "Standards ingestion: rcf standards add + reference-by-default",
+  "summary": "Introduce a `rcf standards <verb>` verb family (`add`, `list`) that registers standards packs on the project manifest. Reference-by-default when the source lives inside the project root; copy into `rcf/standards/<slug>/` only when the source lives outside. Manifest registration is authoritative; every add writes a `manifest.standards[]` entry per the 0.4.4 `standardsPackRecord` schema.",
+  "approach": "One dispatcher, one applier. src/cli/standards.js parses `add|list`; src/blueprint/standards.js resolves whether the source is inside or outside the project root (via node:path.relative + startsWith), copies when needed, and writes the manifest entry. Copy path is fs.cp recursive with a per-run overwrite guard (idempotent re-adds refuse to re-copy unless `--refresh` is passed; Phase 1 keeps to add-only + idempotent read, `refresh` verb deferred to Phase 3).",
+  "deliverables": [
+    "src/cli/standards.js: parseArgs + HELP + main() for add/list",
+    "src/blueprint/standards.js: registerStandardsPack(root, opts) — in-root vs out-of-root detection + optional copy + manifest.standards[] write",
+    "bin/rcf.js: `standards: standardsMain` on SUBCOMMANDS",
+    "src/cli/help.js: `standards <verb>` on the TOP_LEVEL block",
+    "test/blueprint/standards.test.js: in-root reference / out-of-root copy / idempotency cases keyed to AC-1003-1..4"
+  ],
+  "acIds": [
+    "AC-1003-1",
+    "AC-1003-2",
+    "AC-1003-3",
+    "AC-1003-4"
+  ],
+  "contextRequirements": {
+    "tacIds": [],
+    "adrIds": []
+  },
+  "dependsOnFbsIds": [],
+  "domain": "cli",
+  "estimatedSize": "small",
+  "riskLevel": "low",
+  "notes": "Reference-by-default is ratified decision 2 (design-brief.md v2). Copy path targets rcf/standards/<slug>/ (ratified decision 3).",
+  "createdAt": "2026-08-18T22:56:02.353Z",
+  "updatedAt": "2026-08-18T22:56:02.353Z"
+}

package/rcf/fbs/fbs-019.json

@@ -0,0 +1,33 @@
+{
+  "fbsId": "FBS-019",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 19,
+  "executionStatus": "notStarted",
+  "title": "Selective retrieval at bundle assembly (contextRequirements.standardIds)",
+  "summary": "Extend `src/build/bundle.js#assembleBundle` so its `context` section reads `contextRequirements.standardIds`. When the FBS carries an operator-authored `standardIds` array, that array is honoured verbatim. Otherwise a deterministic tag-scoring selector reads the FBS work text (title + summary + approach + notes + AC descriptions) against `manifest.standards[]` (tags + slug + summary) and returns the subset of slugs whose tags occur in the work text. The bundle's context.standardIds carries the selection; the standards' summaries render into the standards payload alongside TACs and ADRs.",
+  "approach": "The selector is a pure function in src/build/standards-selector.js — no wall clock, no random source, no network. Scoring is deterministic tag-hit counting with lowercase-normalised substring match; ties break by manifest order (standards[] is authored). The bundle assembler prefers operator-authored `contextRequirements.standardIds` when present (design principle 5 override path) and calls the selector otherwise. Empty selection is legitimate and never blocks. Phase 1 keeps the selector local and heuristic; the design brief allows a small model call, but adding an LLM dependency to a pure projection is out of scope for the mechanism landing — the heuristic satisfies the ACs and the seam is where a smarter selector plugs in.",
+  "deliverables": [
+    "src/build/standards-selector.js: selectStandards(fbs, standards) — deterministic tag-hit scoring returning the ordered subset of slugs",
+    "src/build/bundle.js: contextRequirements.standardIds hosts operator override or selector output; standards payload rendered into context alongside tacs/adrs",
+    "test/build/standards-selector.test.js: deterministic-selection cases keyed to AC-1004-1, AC-1004-3, AC-1004-4",
+    "test/build/bundle-standards.test.js: bundle-shape cases (default + override) keyed to AC-1004-1, AC-1004-2"
+  ],
+  "acIds": [
+    "AC-1004-1",
+    "AC-1004-2",
+    "AC-1004-3",
+    "AC-1004-4"
+  ],
+  "contextRequirements": {
+    "tacIds": [],
+    "adrIds": []
+  },
+  "dependsOnFbsIds": ["FBS-018"],
+  "domain": "build",
+  "estimatedSize": "small",
+  "riskLevel": "low",
+  "notes": "Ratified decision 4 (agentic at bundle-assembly time, operator override supported). Heuristic-tag selector satisfies the deterministic ACs; a smarter selector plugs into the same seam without touching the bundle assembler.",
+  "createdAt": "2026-08-18T22:56:02.353Z",
+  "updatedAt": "2026-08-18T22:56:02.353Z"
+}

package/rcf/requirements/req-010.json

@@ -0,0 +1,20 @@
+{
+  "createdAt": "2026-08-18T22:54:27.031Z",
+  "updatedAt": "2026-08-18T22:57:45.660Z",
+  "description": "The framework provides a Blueprint mechanism the operator uses to compose blueprint packages (specifications + assets, not code) onto a project tree at any point in its life. Composition is many blueprints per project. Blueprint-contributed docs are namespaced by the blueprint's slug so multiple blueprints cannot collide on ids. Standards packs register at rcf init (or later via rcf standards add), reference-by-default, copied to rcf/standards/<slug>/ only when the source lives outside the project root. Manifest registration is authoritative. Selective retrieval populates fbs.contextRequirements.standardIds at bundle-assembly time by analysing the FBS work text against the standards tag vocabulary; operator override is supported by authoring the array on the FBS. scope:global ADR contributions surface as blocking conflicts at rcf blueprint add time.",
+  "reqId": "REQ-010",
+  "prdId": "PRD-001",
+  "title": "Blueprint library mechanism (composition, standards, selective retrieval)",
+  "category": "functional",
+  "domain": "cli",
+  "priority": "must",
+  "version": "0.1.0",
+  "status": "draft",
+  "shapeClassification": {
+    "shapes": [
+      "none"
+    ],
+    "reason": "keyword-scan",
+    "classifiedAt": "2026-08-18T22:54:27.048Z"
+  }
+}