rcf-lite 0.7.1 → 0.9.0

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"
+  }
+}

package/rcf/test-suites/ts-026.json

@@ -0,0 +1,54 @@
+{
+  "id": "TS-026",
+  "usId": "US-1001",
+  "title": "Blueprint verb family",
+  "purpose": "Cover rcf blueprint add/list/remove verb family behaviour and the manifest.blueprints[] write path.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-1001-1",
+    "AC-1001-2",
+    "AC-1001-3",
+    "AC-1001-4",
+    "AC-1001-5"
+  ],
+  "testCases": [
+    {
+      "id": "TC-026-add-writes-manifest",
+      "acId": "AC-1001-1",
+      "description": "add on a clean project writes manifest.blueprints[] and copies namespaced contributions",
+      "testPointer": "test/blueprint/apply.test.js::applyBlueprint: writes an entry to manifest.blueprints[] and copies namespaced contributions (AC-1001-1)",
+      "status": "pending"
+    },
+    {
+      "id": "TC-026-list-in-apply-order",
+      "acId": "AC-1001-2",
+      "description": "list prints applied blueprints in appliedAt order",
+      "testPointer": "test/blueprint/list-remove.test.js::listBlueprints: two applied blueprints render in appliedAt order (AC-1001-2)",
+      "status": "pending"
+    },
+    {
+      "id": "TC-026-remove-refuses-on-referring",
+      "acId": "AC-1001-3",
+      "description": "remove refuses when a project-authored doc references a contribution id",
+      "testPointer": "test/blueprint/list-remove.test.js::removeBlueprint: refuses when a project-authored doc references a contribution id (AC-1001-3)",
+      "status": "pending"
+    },
+    {
+      "id": "TC-026-add-idempotent-reapply",
+      "acId": "AC-1001-4",
+      "description": "re-apply of same slug+version is a no-op",
+      "testPointer": "test/blueprint/apply.test.js::applyBlueprint: idempotent re-apply of the same slug + version returns alreadyApplied and does not rewrite the manifest (AC-1001-4)",
+      "status": "pending"
+    },
+    {
+      "id": "TC-026-help-advertises-blueprint",
+      "acId": "AC-1001-5",
+      "description": "rcf --help advertises blueprint as a top-level command",
+      "testPointer": "test/blueprint/cli.test.js::rcf --help advertises `blueprint` and `standards` as top-level commands (AC-1001-5)",
+      "status": "pending"
+    }
+  ],
+  "status": "draft",
+  "createdAt": "2026-08-19T00:00:00Z",
+  "updatedAt": "2026-08-19T00:00:00Z"
+}

package/rcf/test-suites/ts-027.json

@@ -0,0 +1,115 @@
+{
+  "id": "TS-027",
+  "usId": "US-1002",
+  "title": "Namespacing + scope:global ADR conflict surfacing",
+  "purpose": "Cover blueprint-contributed id namespacing and the scope:global ADR conflict-detection path.",
+  "testLevel": "unit",
+  "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"
+  ],
+  "testCases": [
+    {
+      "id": "TC-027-prefix-namespacing",
+      "acId": "AC-1002-1",
+      "description": "prefix-family ids gain a kebab-slug prefix on stamp",
+      "testPointer": "test/blueprint/namespace.test.js::stampId: bare prefix-family id gains the slug as PREFIX",
+      "status": "pending"
+    },
+    {
+      "id": "TC-027-suffix-namespacing",
+      "acId": "AC-1002-1",
+      "description": "suffix-family ids gain a kebab-slug suffix on stamp",
+      "testPointer": "test/blueprint/namespace.test.js::stampId: bare suffix-family id gains the slug as SUFFIX",
+      "status": "pending"
+    },
+    {
+      "id": "TC-027-global-adr-conflict-surfaced",
+      "acId": "AC-1002-2",
+      "description": "add refuses on scope:global ADR topic collision",
+      "testPointer": "test/blueprint/apply.test.js::applyBlueprint: scope:global ADR conflict across two applied blueprints refuses the second add (AC-1002-2)",
+      "status": "pending"
+    },
+    {
+      "id": "TC-027-conflict-report-shape",
+      "acId": "AC-1002-3",
+      "description": "conflict report leads with per-side title + decision headers and names four honest resolution paths with actual blueprint slugs substituted (Phase 3.5 reshape)",
+      "testPointer": "test/blueprint/conflicts.test.js::renderConflictReport: leads with per-side headers (topic in parens) and names four honest resolution paths (Phase 3.5)",
+      "status": "pending"
+    },
+    {
+      "id": "TC-027-nonglobal-namespaced-no-conflict",
+      "acId": "AC-1002-4",
+      "description": "namespaced non-global TACs do not conflict",
+      "testPointer": "test/blueprint/conflicts.test.js::detectGlobalAdrConflicts: namespaced TACs never conflict (AC-1002-4)",
+      "status": "pending"
+    },
+    {
+      "id": "TC-027-shipped-blueprints-option-3-executable",
+      "acId": "AC-1002-5",
+      "description": "shipped SPA + REST option-3 verbatim-from-refused-state money probe: fresh scaffold; add spa; add rest (refused with the reshaped message); follow option 3 EXACTLY as printed (`rcf blueprint supersede errorEnvelope --incoming <rest>` and `rcf blueprint supersede authModel --incoming <rest>`) with ZERO prep; then re-run `rcf blueprint add <rest>` and verify co-residence + honour",
+      "testPointer": "test/blueprint/cli.test.js::shipped SPA + REST: option 3 executes VERBATIM from the refused-add state (rev-3 P1-1, Baz ruling on the conflict-pair supersede precondition)",
+      "status": "pending"
+    },
+    {
+      "id": "TC-027-add-reason-persists",
+      "acId": "AC-1002-6",
+      "description": "rcf blueprint add --reason attaches the ruling text to every resolutions[] record on that add",
+      "testPointer": "test/blueprint/cli.test.js::rcf blueprint add --reason: reason lands on every resolution record (rev-2 P1-2)",
+      "status": "pending"
+    },
+    {
+      "id": "TC-027-add-reason-whitespace-refused",
+      "acId": "AC-1002-6",
+      "description": "whitespace-only --reason on add refused at the writer edge (exit 2, no record written)",
+      "testPointer": "test/blueprint/cli.test.js::rcf blueprint add --reason: whitespace-only reason is refused at the writer edge (rev-2 P1-2)",
+      "status": "pending"
+    },
+    {
+      "id": "TC-027-add-resolve-dedupes-with-warn",
+      "acId": "AC-1002-7",
+      "description": "duplicate --resolve for the same topic keeps the first declaration, drops the rest, and warns on stderr",
+      "testPointer": "test/blueprint/cli.test.js::rcf blueprint add --resolve: duplicate topic dedupes with a stderr warning; only one record persists (rev-2 P3-b)",
+      "status": "pending"
+    },
+    {
+      "id": "TC-027-add-resolve-error-no-double-prefix",
+      "acId": "AC-1002-7",
+      "description": "--resolve validation error carries the CLI's single '[error] blueprint add: ' prefix — the underlying rcfError message MUST NOT prepend its own 'blueprint add: '",
+      "testPointer": "test/blueprint/cli.test.js::rcf blueprint add --resolve: validation error carries no doubled prefix (rev-2 P3-a)",
+      "status": "pending"
+    },
+    {
+      "id": "TC-027-conflict-enrichment-symmetric",
+      "acId": "AC-1002-8",
+      "description": "conflict rendering + --json shape carry title + one-sentence decision on BOTH sides (incoming read from disk, existing read from tree)",
+      "testPointer": "test/blueprint/cli.test.js::conflict enrichment is symmetric: incoming side carries title + decision read off the blueprint contribution file (rev-2 nit)",
+      "status": "pending"
+    },
+    {
+      "id": "TC-027-topic-free-label-camelcase-verbatim",
+      "acId": "AC-1002-9",
+      "description": "ADR-010 chain-level decision on record: shipped camelCase topics are accepted verbatim on manifest.resolutions[].topic; the ADR id tail is kebab-ified; no rcfError names 'kebab slug' on any non-whitespace topic",
+      "testPointer": "test/blueprint/cli.test.js::shipped SPA + REST: option 3 executes VERBATIM from the refused-add state (rev-3 P1-1, Baz ruling on the conflict-pair supersede precondition)",
+      "status": "pending"
+    },
+    {
+      "id": "TC-027-supersede-no-double-prefix",
+      "acId": "AC-1002-10",
+      "description": "every error path in supersede.js exits at the CLI with exactly one `[error] blueprint supersede: ` prefix; the doubled `blueprint supersede: blueprint supersede:` string never appears",
+      "testPointer": "test/blueprint/cli.test.js::rcf blueprint supersede: every rcfError message lands with exactly one `[error] blueprint supersede:` prefix (rev-3 mechanical P1)",
+      "status": "pending"
+    }
+  ],
+  "status": "draft",
+  "createdAt": "2026-08-19T00:00:00Z",
+  "updatedAt": "2026-08-19T00:00:00Z"
+}

package/rcf/test-suites/ts-028.json

@@ -0,0 +1,46 @@
+{
+  "id": "TS-028",
+  "usId": "US-1003",
+  "title": "Standards ingestion",
+  "purpose": "Cover rcf standards add reference-by-default and out-of-root copy paths.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-1003-1",
+    "AC-1003-2",
+    "AC-1003-3",
+    "AC-1003-4"
+  ],
+  "testCases": [
+    {
+      "id": "TC-028-add-writes-manifest-entry",
+      "acId": "AC-1003-1",
+      "description": "add writes a validated standards[] manifest entry",
+      "testPointer": "test/blueprint/standards.test.js::registerStandardsPack: in-repo source is referenced in place (AC-1003-1, AC-1003-2)",
+      "status": "pending"
+    },
+    {
+      "id": "TC-028-inrepo-referenced-in-place",
+      "acId": "AC-1003-2",
+      "description": "in-repo source is referenced in place, no copy written",
+      "testPointer": "test/blueprint/standards.test.js::registerStandardsPack: in-repo source is referenced in place (AC-1003-1, AC-1003-2)",
+      "status": "pending"
+    },
+    {
+      "id": "TC-028-outofroot-copied-in",
+      "acId": "AC-1003-3",
+      "description": "out-of-root source copied into rcf/standards/<slug>/",
+      "testPointer": "test/blueprint/standards.test.js::registerStandardsPack: out-of-root source is copied into rcf/standards/<slug>/ (AC-1003-3)",
+      "status": "pending"
+    },
+    {
+      "id": "TC-028-manifest-validates",
+      "acId": "AC-1003-4",
+      "description": "manifest with standards[] entries validates against the shipped schema",
+      "testPointer": "test/blueprint/standards.test.js::registerStandardsPack: in-repo source is referenced in place (AC-1003-1, AC-1003-2)",
+      "status": "pending"
+    }
+  ],
+  "status": "draft",
+  "createdAt": "2026-08-19T00:00:00Z",
+  "updatedAt": "2026-08-19T00:00:00Z"
+}

package/rcf/test-suites/ts-029.json

@@ -0,0 +1,46 @@
+{
+  "id": "TS-029",
+  "usId": "US-1004",
+  "title": "Selective retrieval at bundle assembly",
+  "purpose": "Cover the agentic tag-scoring selector and its operator-override path at bundle assembly.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-1004-1",
+    "AC-1004-2",
+    "AC-1004-3",
+    "AC-1004-4"
+  ],
+  "testCases": [
+    {
+      "id": "TC-029-agentic-selection",
+      "acId": "AC-1004-1",
+      "description": "bundle carries agentically-selected standardIds",
+      "testPointer": "test/build/bundle-standards.test.js::bundle: agentic selection picks matching standards from manifest.standards[] (AC-1004-1)",
+      "status": "pending"
+    },
+    {
+      "id": "TC-029-operator-override",
+      "acId": "AC-1004-2",
+      "description": "operator-authored standardIds override the selector",
+      "testPointer": "test/build/bundle-standards.test.js::bundle: operator-authored contextRequirements.standardIds overrides the agentic selection (AC-1004-2)",
+      "status": "pending"
+    },
+    {
+      "id": "TC-029-empty-never-blocks",
+      "acId": "AC-1004-3",
+      "description": "empty selection is legitimate; bundle assembles without blocking",
+      "testPointer": "test/build/bundle-standards.test.js::bundle: empty selection is legitimate and never blocks (AC-1004-3)",
+      "status": "pending"
+    },
+    {
+      "id": "TC-029-deterministic",
+      "acId": "AC-1004-4",
+      "description": "selection is stable per input across repeat invocations",
+      "testPointer": "test/build/standards-selector.test.js::selectStandards: selection is deterministic across repeat invocations (AC-1004-4)",
+      "status": "pending"
+    }
+  ],
+  "status": "draft",
+  "createdAt": "2026-08-19T00:00:00Z",
+  "updatedAt": "2026-08-19T00:00:00Z"
+}

package/rcf/user-stories/us-1001.json

@@ -0,0 +1,56 @@
+{
+  "usId": "US-1001",
+  "prdId": "PRD-001",
+  "reqId": "REQ-010",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "Blueprint verb family: add, list, remove, upgrade",
+  "description": "A `rcf blueprint` verb family provides the primary operator seat for composing blueprints onto a project. Every verb runs against the current tree, is idempotent where the semantics allow, and writes to the manifest's `blueprints[]` registry so the applied set is greppable and mechanical.",
+  "asA": "operator on an RCF project",
+  "iWant": "to add, list, remove and upgrade blueprints against my project tree from a single `rcf blueprint` verb family",
+  "soThat": "composition is a first-class action instead of a one-shot init flag, and I can layer several blueprints across the life of a project without hand-editing the manifest",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-1001-1",
+      "description": "`rcf blueprint add <slug>` on a project with no blueprints applied writes an entry into `manifest.blueprints[]` and prints the applied slug and version",
+      "given": "a validated project tree with no existing `blueprints[]` entries and a resolvable blueprint slug",
+      "when": "`rcf blueprint add <slug>` runs",
+      "then": "the manifest gains one `blueprints[]` entry (slug, version, appliedAt, source, and any contributions[] the blueprint wrote), and stdout names the slug and applied version",
+      "testable": true
+    },
+    {
+      "id": "AC-1001-2",
+      "description": "`rcf blueprint list` prints every applied blueprint (slug, version, appliedAt) in apply order",
+      "given": "a project with one or more blueprints already applied",
+      "when": "`rcf blueprint list` runs",
+      "then": "every applied blueprint prints, one per line, ordered by `appliedAt`, with slug, version and apply timestamp columns",
+      "testable": true
+    },
+    {
+      "id": "AC-1001-3",
+      "description": "`rcf blueprint remove <slug>` removes the manifest entry and refuses when any project-authored doc references a contributed id",
+      "given": "a project with the blueprint applied and no project-authored doc referencing any of the contributions[] ids",
+      "when": "`rcf blueprint remove <slug>` runs",
+      "then": "the `blueprints[]` entry is dropped from the manifest; when a project-authored doc DOES reference a contribution, the verb exits non-zero and prints the referencing id + path without mutating the manifest",
+      "testable": true
+    },
+    {
+      "id": "AC-1001-4",
+      "description": "`rcf blueprint add <slug>` is idempotent: repeating on an already-applied clean slug is a no-op with a friendly message",
+      "given": "a project with `<slug>` already in `blueprints[]`",
+      "when": "`rcf blueprint add <slug>` runs again with no conflicts to surface",
+      "then": "the manifest is not rewritten, exit code is 0, and stdout names the slug as already applied at the applied version",
+      "testable": true
+    },
+    {
+      "id": "AC-1001-5",
+      "description": "`rcf --help` lists `blueprint` alongside the other top-level commands",
+      "given": "the unified `rcf` bin",
+      "when": "`rcf --help` runs",
+      "then": "the top-level usage advertises `blueprint <verb>` as an available command",
+      "testable": true
+    }
+  ],
+  "createdAt": "2026-08-18T22:54:33.194Z",
+  "updatedAt": "2026-08-18T22:54:33.194Z"
+}

package/rcf/user-stories/us-1002.json

@@ -0,0 +1,96 @@
+{
+  "usId": "US-1002",
+  "prdId": "PRD-001",
+  "reqId": "REQ-010",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "Composition, namespaced ids and scope:global ADR conflict surfacing",
+  "description": "Multiple blueprints may be applied to a single project. Blueprint-contributed docs are namespaced by the blueprint's slug so ids cannot collide across blueprints. A blueprint's ADR contributions may be tagged `scope: global`; two applied blueprints each contributing a `scope: global` ADR are a genuine conflict and `rcf blueprint add` surfaces both entries and refuses to write. Conflict-presentation ergonomics are prototype-unknown #1 (design brief); this US covers the first pass.",
+  "asA": "operator on an RCF project",
+  "iWant": "blueprint contributions to compose without id collisions, and for `scope: global` ADR conflicts to be surfaced with both sides visible before anything is written",
+  "soThat": "composition never silently merges incompatible whole-project decisions",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-1002-1",
+      "description": "Blueprint-contributed doc ids are namespaced with the blueprint's slug so composition cannot collide on ids at the id layer",
+      "given": "two blueprints `spa` and `rest` that both contribute a REQ, a US and an ADR",
+      "when": "both are applied to the same project via `rcf blueprint add`",
+      "then": "every contributed id carries the blueprint slug as its prefix (REQ/US: `spa-REQ-001`, `rest-REQ-001`) or as its kebab-suffix (ADR: `ADR-004-spa-theme`, `ADR-005-rest-versioning`); no two contributed ids across the two blueprints match",
+      "testable": true
+    },
+    {
+      "id": "AC-1002-2",
+      "description": "`rcf blueprint add <slug>` refuses when the new blueprint contributes a `scope: global` ADR on a topic already contributed by an applied blueprint",
+      "given": "a project with blueprint `alpha` already applied contributing an ADR tagged `scope: global` on topic `versioning`",
+      "when": "`rcf blueprint add beta` runs and blueprint `beta` also contributes a `scope: global` ADR on `versioning`",
+      "then": "the verb exits non-zero, prints both ADR ids and their file paths, and the manifest is unchanged",
+      "testable": true
+    },
+    {
+      "id": "AC-1002-3",
+      "description": "Conflict output leads with per-side headers (ADR title + one-sentence decision) and names four honest resolution paths with actual blueprint slugs filled in (Phase 3.5 reshape)",
+      "given": "the conflict case above",
+      "when": "the verb prints the conflict",
+      "then": "the output opens with `conflict on topic (<topic>)` and one line per side carrying `blueprint <slug>: <title> — <decision>` (or `<id> at <path>` when the tree did not carry the ADR body), a `refs:` footer with both ids + paths, and four honest resolutions numbered 1-4: adopt-incoming (`rcf blueprint remove <existing-slug>`), keep-existing (do not add the incoming), supersede via a project-level ADR (`rcf blueprint supersede <topic>`), and declare-on-add (`rcf blueprint add <source> --resolve <topic>=project:<ADR-id>`) — all with the actual conflicting blueprint slugs already substituted, no `<slug>` placeholders",
+      "testable": true
+    },
+    {
+      "id": "AC-1002-4",
+      "description": "Non-global TACs, ADRs, REQs, USs and FBSes are namespaced and cannot conflict",
+      "given": "two blueprints each contributing a TAC on the same topic without `scope: global`",
+      "when": "both are applied",
+      "then": "both TACs co-exist under distinct namespaced ids; no conflict is surfaced",
+      "testable": true
+    },
+    {
+      "id": "AC-1002-5",
+      "description": "The supersession record's two sides are the CONFLICT PAIR — one currently-applied blueprint's scope:global ADR on the topic PLUS one incoming (would-be-applied) blueprint's scope:global ADR on the same topic — and the `rcf blueprint supersede` verb accepts the incoming blueprint as the second side. Operator ruling (Baz, w-2026-08-19-008 round 3): option 3 as printed in the reshaped conflict message MUST be executable EXACTLY as printed from the refused-add state, with zero prep. Mechanism (builder judgement against the chain): the reshaped conflict message names option 3 as `rcf blueprint supersede <topic> --incoming <source>`, carrying the very same `<source>` argument the refused add was invoked with; `supersede` loads the incoming blueprint from `--incoming <source>`, finds its scope:global ADR on `<topic>`, stamps its id into the incoming blueprint's namespace, and uses `{slug, adrId}` for the incoming blueprint as the second side of `manifest.resolutions[].supersedes[]`. The scaffolded project ADR file lists both blueprint ADR ids (applied + incoming stamped) under `relatedAdrs[]`; after supersede returns, re-running `rcf blueprint add <source>` succeeds because the detector honours the freshly-recorded resolution. `--incoming <source>` is required when applied count on the topic is < 2 and is silently accepted (informational) when applied count is already >= 2.",
+      "given": "a fresh project with ZERO applied blueprints and the shipped SPA + REST blueprints on disk (both carry scope:global ADRs on camelCase topics `errorEnvelope` and `authModel`)",
+      "when": "the operator runs the flow verbatim as printed: `rcf blueprint add <spa>`; `rcf blueprint add <rest>` (refused with the reshaped four-honest-paths message); then follows option 3 EXACTLY as printed: `rcf blueprint supersede errorEnvelope --incoming <rest>` and `rcf blueprint supersede authModel --incoming <rest>`; then re-runs `rcf blueprint add <rest>`",
+      "then": "each supersede exits 0, scaffolds a project ADR at `rcf/adrs/adr-NNN-<kebab-topic>.json` (topic string verbatim on `manifest.resolutions[].topic`; ADR id tail kebab-ified per ADR-010), and appends a `manifest.resolutions[]` record listing both blueprint ADR ids in `supersedes[]`; the subsequent `rcf blueprint add <rest>` exits 0 (detector honours the resolution) and both blueprint ADR files co-reside on disk with the project supersedes-ADR alongside them",
+      "testable": true
+    },
+    {
+      "id": "AC-1002-6",
+      "description": "`rcf blueprint add --reason <text>` attaches the operator's ruling text to every `manifest.resolutions[]` record minted on that add. Whitespace-only reasons are refused at the writer edge (schema does not enforce a minimum floor on the field itself; the writer's floor is emptiness, not length).",
+      "given": "an incoming blueprint whose apply would collide on one or more topics, resolved via one or more --resolve declarations",
+      "when": "the operator adds `--reason \"...\"` alongside the --resolve flags",
+      "then": "every newly-minted resolutions[] record carries the reason string verbatim; a whitespace-only --reason exits 2 with an error naming the topic and no record is written",
+      "testable": true
+    },
+    {
+      "id": "AC-1002-7",
+      "description": "Duplicate `--resolve` declarations for the same topic within a single `rcf blueprint add` are deduped: the first declaration is kept, subsequent declarations on the same topic are dropped, and a `[warn]` line names each dropped topic on stderr. The add still exits 0 on success; the manifest carries exactly one resolutions[] record per topic.",
+      "given": "an incoming blueprint whose apply would collide on topic X",
+      "when": "the operator passes `--resolve X=project:ADR-A --resolve X=project:ADR-B` on the same command",
+      "then": "the manifest carries exactly one resolutions[] record on topic X with `resolvedByAdrId: ADR-A` (first-wins), and stderr carries a warn line naming X as a duplicate --resolve topic",
+      "testable": true
+    },
+    {
+      "id": "AC-1002-8",
+      "description": "Conflict enrichment is symmetric: the CLI's conflict report and `--json` output both carry `title` + one-sentence `decision` on BOTH sides of a globalAdrTopic conflict — the existing side read from the walker's tree, the incoming side read from the blueprint's ADR file on disk. Round-1 only enriched the existing side, which read asymmetrically against shipped blueprints.",
+      "given": "an incoming blueprint that would collide with an applied blueprint on a scope:global ADR topic, both ADRs carrying a title and a decision",
+      "when": "`rcf blueprint add <source>` refuses with the reshaped message (with or without --json)",
+      "then": "both `incoming` and `existing` sides render `blueprint <slug>: <title> — <decision>` in the terminal output, and `conflicts[].incoming` and `conflicts[].existing` both carry `title` and `decision` in the --json output",
+      "testable": true
+    },
+    {
+      "id": "AC-1002-9",
+      "description": "Chain-level decision (ADR-010): the blueprint conflict-topic vocabulary is a FREE LABEL — a lookup key used by the detector (exact-match between an incoming ADR's topic and each applied ADR's topic) and stored verbatim on `manifest.resolutions[].topic`. No character-class constraint beyond the manifest schema's `minLength: 1` plus a writer-edge whitespace-only refuse. The shipped SPA + REST blueprints declare their scope:global ADR topics in camelCase (authModel, errorEnvelope, clientRouting, theming, clientState, apiVersioning, logging) and that vocabulary is canonical. Kebab-ification is confined to the projection into the ADR-id slug tail (ADR grammar requires kebab), never at the vocabulary edge.",
+      "given": "the shipped SPA + REST blueprint packs on disk (topics: authModel, errorEnvelope, ...)",
+      "when": "supersede and add --resolve run on any of those topics as printed",
+      "then": "the writer accepts the topic verbatim; the manifest.resolutions[].topic value byte-matches the applied ADR's topic; the scaffolded project ADR id carries a kebab-cased tail derived from the topic (`authModel` -> `ADR-NNN-auth-model`); no rcfError references 'kebab slug' or 'valid kebab' on any non-whitespace topic string",
+      "testable": true
+    },
+    {
+      "id": "AC-1002-10",
+      "description": "Error-message prefix discipline on supersede: rcfError messages returned from `src/blueprint/supersede.js` MUST NOT prepend their own `blueprint supersede: ` prefix — the CLI edge already writes `[error] blueprint supersede: ` on every rcfError from the supersede verb. Round-2 caught the same bug on the `add` path; round-3 catches it on the supersede path (six sites: supersede.js:54, :70, :85, :107, :145, :160).",
+      "given": "any error path in `src/blueprint/supersede.js` (missing topic, --reason whitespace-only, sub-2 applied ADRs, missing prd/tad, overwrite guard tripped, ADR write ioFailure)",
+      "when": "`rcf blueprint supersede ...` runs into that error path at the CLI",
+      "then": "the printed stderr line matches `^\\[error\\] blueprint supersede: <message>$` with exactly one `blueprint supersede: ` prefix; the string `blueprint supersede: blueprint supersede:` does not appear anywhere in the output",
+      "testable": true
+    }
+  ],
+  "createdAt": "2026-08-18T22:54:33.194Z",
+  "updatedAt": "2026-08-19T14:30:00.000Z"
+}

package/rcf/user-stories/us-1003.json

@@ -0,0 +1,48 @@
+{
+  "usId": "US-1003",
+  "prdId": "PRD-001",
+  "reqId": "REQ-010",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "Standards ingestion: reference by default, copy only when out of root",
+  "description": "Standards packs are per operator or organisation and register at `rcf init` (or later via `rcf standards add`). Manifest registration is authoritative. In-repo sources are referenced in place. Out-of-root sources are copied into `rcf/standards/<slug>/` so the tree remains portable. Provenance (personal vs corporate) is recorded per pack.",
+  "asA": "operator on an RCF project",
+  "iWant": "to register standards packs against my project tree, referencing in place when the source is already inside the repo and copying into `rcf/standards/<slug>/` only when the source lives outside the project root",
+  "soThat": "duplication inside the repo is not accepted, portability across machines is preserved for external sources, and the manifest is the single source of truth for what standards apply",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-1003-1",
+      "description": "`rcf standards add <path>` writes a manifest entry with the pack's id, slug, sourcePath, tag vocabulary, testsProvidedBy and provenance",
+      "given": "a project with no standards registered and a valid standards folder anywhere on disk",
+      "when": "`rcf standards add <path> --slug wsd-naming --tags naming,conventions --tests-provided-by agent --provenance corporate` runs",
+      "then": "the manifest gains one `standards[]` entry with all named fields populated and validates against the schema",
+      "testable": true
+    },
+    {
+      "id": "AC-1003-2",
+      "description": "In-repo sources are referenced in place; no copy is written",
+      "given": "a standards folder path inside the project root (e.g. `docs/standards/wsd-naming`)",
+      "when": "`rcf standards add` runs against it",
+      "then": "the `sourcePath` records the in-repo path, `copyPath` is absent, and no file is written under `rcf/standards/`",
+      "testable": true
+    },
+    {
+      "id": "AC-1003-3",
+      "description": "Out-of-root sources are mirrored into `rcf/standards/<slug>/` and `copyPath` records the mirror",
+      "given": "a standards folder path outside the project root (an absolute path pointing outside the repo)",
+      "when": "`rcf standards add` runs against it",
+      "then": "the source is copied into `rcf/standards/<slug>/`, the manifest entry records the original `sourcePath` and the in-tree `copyPath`, and re-running the verb is idempotent (no double copy)",
+      "testable": true
+    },
+    {
+      "id": "AC-1003-4",
+      "description": "The manifest.standards[] entry validates against the shipped schema (@stravica-ai/rcf-schemas standardsPackRecord)",
+      "given": "a manifest with one or more standards[] entries",
+      "when": "`rcf validate` runs",
+      "then": "the manifest validates without errors under the shipped schema",
+      "testable": true
+    }
+  ],
+  "createdAt": "2026-08-18T22:54:33.194Z",
+  "updatedAt": "2026-08-18T22:54:33.194Z"
+}

package/rcf/user-stories/us-1004.json

@@ -0,0 +1,48 @@
+{
+  "usId": "US-1004",
+  "prdId": "PRD-001",
+  "reqId": "REQ-010",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "Selective retrieval at bundle assembly (contextRequirements.standardIds)",
+  "description": "The build-context bundle assembler runs a deterministic selector during FBS bundle assembly that reads the FBS work text plus the standards manifest (tags, titles, and short summaries) and returns the subset of standard slugs relevant to the FBS. The selected slugs populate `contextRequirements.standardIds` for that bundle only. Operator override is supported by authoring the array on the FBS.",
+  "asA": "operator on an RCF project with standards registered",
+  "iWant": "the bundle assembler to select relevant standards per FBS automatically, and to honour my override when I author the array on the FBS itself",
+  "soThat": "the default path does not require operator authoring and the override path exists when the agentic selection needs correcting",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-1004-1",
+      "description": "The bundle for an FBS with no operator-authored standardIds carries the agentically-selected subset",
+      "given": "a project with two standards packs (`wsd-naming` tagged `naming`, `security-baseline` tagged `security`) and an FBS whose summary names `security`",
+      "when": "the bundle assembler runs for that FBS with no operator-authored `standardIds`",
+      "then": "the bundle's `context` section carries `standardIds` including `security-baseline` and the pack's rendered summary in the standards payload",
+      "testable": true
+    },
+    {
+      "id": "AC-1004-2",
+      "description": "Operator-authored `contextRequirements.standardIds` on the FBS overrides the agentic selection",
+      "given": "the same project and FBS as AC-1004-1, but with `contextRequirements.standardIds: ['wsd-naming']` authored on the FBS",
+      "when": "the bundle assembler runs",
+      "then": "the bundle's `context.standardIds` matches the operator-authored value byte-for-byte; the agentic selection is not invoked",
+      "testable": true
+    },
+    {
+      "id": "AC-1004-3",
+      "description": "The assembler never blocks on an empty selection",
+      "given": "a project with no standards registered, or an FBS whose work text matches no standard",
+      "when": "the bundle assembler runs",
+      "then": "the bundle assembles with `context.standardIds` empty (or absent) and no standards payload; the assembler does not error",
+      "testable": true
+    },
+    {
+      "id": "AC-1004-4",
+      "description": "Selection is stable per input (deterministic tag-scoring; no wall-clock or random source)",
+      "given": "an FBS work text and a standards manifest, both fixed",
+      "when": "the selector is invoked twice",
+      "then": "the two returned selections are equal (same slugs, same order)",
+      "testable": true
+    }
+  ],
+  "createdAt": "2026-08-18T22:54:33.194Z",
+  "updatedAt": "2026-08-18T22:54:33.194Z"
+}