@stravica-ai/rcf-schemas 0.4.5 → 0.5.1

package/CHANGELOG.md

@@ -4,6 +4,51 @@ All notable changes to `@stravica-ai/rcf-schemas` are documented in this file.
 
 The format roughly follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and the project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). Pre-1.0 breaking changes are signalled by a minor bump per semver 0.x convention.
 
+## 0.5.1 - 2026-08-31
+
+Additive patch bump for the external-blueprint-library mechanism landing in `rcf-lite`. Adds one optional field on the applied-blueprint record so a project can durably record which registered library an apply resolved through, without the ownership fact having to be re-derived by string-matching `source`. Every change is additive: every 0.5.0-valid document remains valid, and every existing id continues to validate byte-for-byte.
+
+### Added
+
+- **`manifest.schema.json`**: new optional `libraryPrefix` on `$defs.appliedBlueprintRecord`, referencing `common.$defs.blueprintSlug`. Stamped when an apply resolves through a registered external blueprint library (for example, an apply of `acme:spa` stamps `libraryPrefix: acme`); absent for shelf and path applies. Once stamped, the record's `libraryPrefix` is the ownership fact: the library registry may be renamed, re-pointed, or unregistered without orphaning previously applied records. Written by the library-resolving branch of `rcf blueprint add`; read by `rcf library remove`'s ownership check in preference to `source`-prefix matching.
+- Fixtures (valid): `fixtures/valid/manifest/manifest-013-blueprint-library-prefix.json` (one library-applied blueprint with `libraryPrefix` stamped, alongside a shelf-applied blueprint with no `libraryPrefix`).
+- Fixtures (invalid): `fixtures/invalid/manifest/manifest-022-library-prefix-bad-slug.json` (uppercase `libraryPrefix`, violates the `blueprintSlug` shape).
+- Tests: `libraryPrefix` cases added to `manifest.test.js` covering the happy path (stamped alone, coexists with `namespace` and `contributions`), the shelf/path back-compat case (record without `libraryPrefix` still validates), a mixed library-and-shelf record, the two reject cases (uppercase, leading-hyphen), and a pre-0.5.1 back-compat case that keeps a `blueprints[]` record without `libraryPrefix` valid.
+
+### Notes
+
+- Additive-only: every 0.5.0-valid document remains valid. `additionalProperties: false` on the record is preserved: `libraryPrefix` is the only new permitted property.
+- Canonical `$id` URLs stay at `v0.5.0`, following the patch-release precedent set at 0.2.1, 0.3.1, 0.4.1, 0.4.2, 0.4.3, 0.4.4, and 0.4.5.
+- Version choice: per repo precedent (every additive change since 0.2.0 has bumped as a patch), this bumps `0.5.0 -> 0.5.1`.
+
+## 0.5.0 - 2026-08-28
+
+Minor bump for the `testPointer` conditional-by-status ruling (`w-2026-08-27-dave-001`, Baz ratified 2026-08-27). `testPointer` on a Test Case is now REQUIRED when the TC's `status` is `passing` or `failing`, and OPTIONAL when the TC's `status` is `pending` or `skipped`. This closes the "a passing verdict may point at nothing" hole the 0.4.x shape allowed and moves the durable landing point for the rule out of `rcf-lite`'s local strictness overlay (`w-2026-07-28-005`) into the shared schema, where every consumer inherits it uniformly.
+
+### Changed
+
+- **`test-suite.schema.json`**: `$defs.testCase.testPointer` gains `minLength: 1` (a `testPointer` present at all must be non-empty; empty-string pointers were the same class of dishonest-coverage failure as absent pointers). A new `allOf` clause on `$defs.testCase` conditionally requires `testPointer` when `status` is `passing` or `failing`; other statuses may still omit it. The `additionalProperties: false` guarantee is preserved: nothing new is permitted; only the requiredness on one existing field is tightened for two of the four status values.
+- **Canonical `$id`** URLs bumped from `https://schemas.stravica.io/rcf/v0.4.0/...` to `https://schemas.stravica.io/rcf/v0.5.0/...` on every schema, in lock-step with the bundle version. Matches the precedent set at 0.3.0 and 0.4.0 (patch releases keep the URL pinned; minor releases bump the URL). No consumer in the Stravica org hard-codes the URL literal (org-wide search 2026-08-28 hit only this repo's own files); `rcf-lite`, `rcf-build-lite`, `rcf-tools`, and every persona-run repo load schemas by file path and register with whatever `$id` the file declares.
+- **Documentation URLs bumped in lock-step.** The `docs/*.md` canonical-`$id` references were stale on `v0.3.0` (never bumped at 0.4.0); this release syncs every doc page and the `README.md` code example to `v0.5.0`.
+
+### Added
+
+- **Fixtures (valid)**: `fixtures/valid/test-suite/ts-006-testpointer-conditional.json` (a five-TC suite exercising every branch: passing+pointer, failing+pointer, pending without pointer, skipped without pointer, and pending with a declared-intent pointer).
+- **Fixtures (invalid)**: `fixtures/invalid/test-suite/ts-008-passing-tc-missing-testpointer.json`, `fixtures/invalid/test-suite/ts-009-failing-tc-missing-testpointer.json` (the two directions of the new required rule), `fixtures/invalid/test-suite/ts-010-empty-testpointer.json` (the `minLength: 1` guard against empty-string pointers).
+- **Tests**: `test/test-suite.test.js` gains the conditional-required cases (pending/skipped without pointer still valid; passing/failing without pointer rejected with an error referencing `testPointer`; passing/failing with pointer valid; pending/skipped may still carry a declared pointer; empty-string pointer rejected; mixed-status suite valid). Existing tests that constructed `status: passing` TCs without `testPointer` were updated to include a pointer so they exercise their originally intended assertion (id-slug pattern, scope tags, runtime provenance, and so on) rather than fail on the new rule.
+
+### Migration
+
+- **Pre-0.5.0 docs with only `pending`/`skipped` TCs missing `testPointer`**: remain valid unchanged.
+- **Pre-0.5.0 docs with `passing` or `failing` TCs missing `testPointer`**: were already dishonest coverage claims; validate against 0.5.0 by either (a) adding the real `testPointer` (the honest fix; the pointer is what the TC is asserting exists), or (b) downgrading the TC to `pending` or `skipped` if no executable landed. `rcf-lite`'s pre-0.5.0 strictness overlay already forced this in practice for tools that ran through the CLI; 0.5.0 makes the schema the single source of truth.
+- **`rcf-lite` consumers**: the durable landing was called out in `rcf-lite`'s own overlay comment ("drop this block when that ships"). A follow-up `rcf-lite` release pins `@stravica-ai/rcf-schemas` to `0.5.0` and removes the local overlay so validation is inherited from the schema uniformly.
+
+### Notes
+
+- Pre-1.0 semver convention (repo has followed this since 0.1.0): breaking-in-any-direction schema changes bump minor. This release breaks docs that authored dishonest `passing`/`failing`-without-pointer TCs; hence 0.5.0, not a patch.
+- The rule is expressed as an `allOf` with an `if`/`then` conditional (the same pattern 0.4.2 used for per-kind `testTheatreFinding.tsId` requiredness). Ajv strict mode requires `testPointer` to be redeclared inside `then.properties`; the redeclaration mirrors the outer shape (`type: string, minLength: 1`) and is not an independent constraint.
+- The 0.4.4 `back-compat-freeze.test.js` byte-for-byte pin is on a manifest fixture (`manifest-011-preblueprint-chain-frozen.json`) and is untouched by this release; it continues to pass on 0.5.0.
+
 ## 0.4.5 - 2026-08-19
 
 Additive patch bump for the blueprint conflict-resolution mechanism landing in `rcf-lite` Phase 3.5. Adds the schema seam the `rcf blueprint supersede` and `rcf blueprint add --resolve` verbs key to, so a project can record an operator ruling that resolves a cross-blueprint conflict on a scope:global ADR topic. Every change is additive: every 0.4.4-valid document remains valid, and every existing id continues to validate byte-for-byte.

package/README.md

@@ -46,7 +46,7 @@ io.stravica.rcf:rcf-schemas:0.3.0
 Each schema is fetchable by its canonical `$id`:
 
 ```
-https://schemas.stravica.io/rcf/v0.3.0/<name>.schema.json
+https://schemas.stravica.io/rcf/v0.5.0/<name>.schema.json
 ```
 
 ## Use
@@ -77,7 +77,7 @@ for (const name of names) {
   ajv.addSchema(schema);
 }
 
-const validatePrd = ajv.getSchema('https://schemas.stravica.io/rcf/v0.3.0/prd.schema.json');
+const validatePrd = ajv.getSchema('https://schemas.stravica.io/rcf/v0.5.0/prd.schema.json');
 const ok = validatePrd(myPrdDoc);
 if (!ok) console.error(validatePrd.errors);
 ```

package/docs/adr.md

@@ -4,7 +4,7 @@ Architectural Decision Record. One per decision, one file each. Follows the Nyga
 
 ## Canonical `$id`
 
-`https://schemas.stravica.io/rcf/v0.3.0/adr.schema.json`
+`https://schemas.stravica.io/rcf/v0.5.0/adr.schema.json`
 
 ## Required fields
 

package/docs/build-sequence.md

@@ -4,7 +4,7 @@ Build Sequence. One per project. Pure planning shell. FBS files each carry the m
 
 ## Canonical `$id`
 
-`https://schemas.stravica.io/rcf/v0.3.0/build-sequence.schema.json`
+`https://schemas.stravica.io/rcf/v0.5.0/build-sequence.schema.json`
 
 ## Required fields
 

package/docs/cn.md

@@ -4,7 +4,7 @@ Code Node. One file per node. Bridges the requirements graph to source code: ide
 
 ## Canonical `$id`
 
-`https://schemas.stravica.io/rcf/v0.3.0/cn.schema.json`
+`https://schemas.stravica.io/rcf/v0.5.0/cn.schema.json`
 
 ## Required fields
 

package/docs/common.md

@@ -4,7 +4,7 @@ Shared `$defs` referenced via `$ref` from every other RCF schema. ID patterns, s
 
 ## Canonical `$id`
 
-`https://schemas.stravica.io/rcf/v0.3.0/common.schema.json`
+`https://schemas.stravica.io/rcf/v0.5.0/common.schema.json`
 
 ## What's in `$defs`
 

package/docs/fbs.md

@@ -6,7 +6,7 @@ Structurally, each FBS carries the mandatory `bsId` back-reference plus `buildOr
 
 ## Canonical `$id`
 
-`https://schemas.stravica.io/rcf/v0.3.0/fbs.schema.json`
+`https://schemas.stravica.io/rcf/v0.5.0/fbs.schema.json`
 
 ## Required fields
 

package/docs/manifest.md

@@ -4,7 +4,7 @@ Project manifest. Roots-only shape: declares `prd`, `tad`, `bs`. Children are ow
 
 ## Canonical `$id`
 
-`https://schemas.stravica.io/rcf/v0.3.0/manifest.schema.json`
+`https://schemas.stravica.io/rcf/v0.5.0/manifest.schema.json`
 
 ## Required fields
 

package/docs/prd.md

@@ -4,7 +4,7 @@ Product Requirements Document. One per project. Pure shell document; REQ bodies
 
 ## Canonical `$id`
 
-`https://schemas.stravica.io/rcf/v0.3.0/prd.schema.json`
+`https://schemas.stravica.io/rcf/v0.5.0/prd.schema.json`
 
 ## Required fields
 

package/docs/req.md

@@ -4,7 +4,7 @@ Individual Requirement within a PRD. One file per REQ. Recommended path: `rcf/re
 
 ## Canonical `$id`
 
-`https://schemas.stravica.io/rcf/v0.3.0/req.schema.json`
+`https://schemas.stravica.io/rcf/v0.5.0/req.schema.json`
 
 ## Required fields
 

package/docs/tac.md

@@ -4,7 +4,7 @@ Technical Architecture Component. One file per architectural component. Verbose
 
 ## Canonical `$id`
 
-`https://schemas.stravica.io/rcf/v0.3.0/tac.schema.json`
+`https://schemas.stravica.io/rcf/v0.5.0/tac.schema.json`
 
 ## Required fields
 

package/docs/tad.md

@@ -4,7 +4,7 @@ Master Technical Architecture Document. One per project. Pure shell for cross-cu
 
 ## Canonical `$id`
 
-`https://schemas.stravica.io/rcf/v0.3.0/tad.schema.json`
+`https://schemas.stravica.io/rcf/v0.5.0/tad.schema.json`
 
 ## Required fields
 

package/docs/test-suite.md

@@ -4,7 +4,7 @@ Test Suite. One file per Test Suite. The JSON specification of what Test Cases e
 
 ## Canonical `$id`
 
-`https://schemas.stravica.io/rcf/v0.3.0/test-suite.schema.json`
+`https://schemas.stravica.io/rcf/v0.5.0/test-suite.schema.json`
 
 ## TS-as-JSON: what this schema is for
 
@@ -39,10 +39,14 @@ Each entry in `testCases[]`:
 | `id` | `^TC-\d{3,}-[a-z0-9-]+$` | yes | TC identifier. `TC-<TS-suffix>-<slug>`; slug is a lowercase alphanumeric identifier (hyphens allowed). Slug uniqueness is within-TS, not global. TS-suffix widened to three-digit minimum, unbounded above (0.4.3). |
 | `acId` | `^AC-\d{3,}(-\d+)?$` | yes | Which AC on the parent US this TC verifies. |
 | `description` | string, min 1 | yes | What the TC covers. |
-| `testPointer` | string | no | Pointer to the executable test, `filePath::testName` format. |
+| `testPointer` | string, min 1 | conditional | Pointer to the executable test, `filePath::testName` format. **Required** when `status` is `passing` or `failing` (a passing or failing verdict claims coverage and must point at the test that produced the verdict). **Optional** when `status` is `pending` or `skipped` (no executable test has landed yet, and there is nothing honest to point at). Non-empty when present. Behaviour ratified 2026-08-27; landed in 0.5.0. |
 | `status` | enum | yes | `pending`, `passing`, `failing`, `skipped`. Authored in 0.2.0; derived from real test runs in Phase 6+. |
 | `scope` | `scopeTag` enum | no | `library`, `runtime`, `deployed`, `unclassified`. Optional at schema level (0.4.3). Ruleset-enforcing consumers may require the TC scope to be equal to or wider than the covered AC's scope. |
 
+## What changed in 0.5.0
+
+`testPointer` moved from unconditionally-optional to conditionally-required by `status`. A TC with `status: passing` or `status: failing` MUST carry a non-empty `testPointer`; a TC with `status: pending` or `status: skipped` MAY omit it (and may still declare a planned pointer). The old shape (unconditionally optional) let a TC claim a passing verdict while pointing at nothing, which is dishonest coverage; 0.5.0 makes the schema express what the rcf-lite consumer already enforced as a local overlay (`w-2026-07-28-005`). Consumers on 0.4.x that shipped only `pending`/`skipped` TCs without `testPointer` remain valid; consumers that shipped `passing`/`failing` TCs without `testPointer` need to add pointers or downgrade the verdict.
+
 ## What changed in 0.2.0
 
 The 0.1.0 shape was per-AC (`acId` + `prdId` + `version` + `testCases[given/when/then]`). 0.2.0 makes the suite per-US-and-across-ACs, keeps the TS id in `common.schema.json` (`tsId`), and moves the Given/When/Then verbiage into the TC's `description` (specialised BDD-style step language belongs in the executable test, not the JSON spec).

package/docs/user-story.md

@@ -4,7 +4,7 @@ User Story document. One file per US. Contains Acceptance Criteria inline as `ac
 
 ## Canonical `$id`
 
-`https://schemas.stravica.io/rcf/v0.3.0/user-story.schema.json`
+`https://schemas.stravica.io/rcf/v0.5.0/user-story.schema.json`
 
 ## Required fields
 

package/fixtures/invalid/manifest/manifest-022-library-prefix-bad-slug.json

@@ -0,0 +1,16 @@
+{
+  "version": "2.0.0",
+  "projectName": "Invalid libraryPrefix (uppercase)",
+  "prd": { "id": "PRD-001", "path": "rcf/prd.json" },
+  "tad": { "id": "TAD-001", "path": "rcf/tad.json" },
+  "bs":  { "id": "BS-001",  "path": "rcf/build-sequence.json" },
+  "blueprints": [
+    {
+      "slug": "spa",
+      "version": "1.0.0",
+      "appliedAt": "2026-08-31T10:00:00Z",
+      "source": "acme:spa",
+      "libraryPrefix": "ACME"
+    }
+  ]
+}

package/fixtures/invalid/test-suite/ts-008-passing-tc-missing-testpointer.json

@@ -0,0 +1,19 @@
+{
+  "id": "TS-201",
+  "usId": "US-201",
+  "title": "Passing TC missing required testPointer",
+  "purpose": "0.5.0 requires testPointer on passing TCs; this fixture omits it and must be rejected.",
+  "testLevel": "unit",
+  "acIds": ["AC-201-1"],
+  "testCases": [
+    {
+      "id": "TC-201-passing-no-pointer",
+      "acId": "AC-201-1",
+      "description": "Claims a passing verdict but points at nothing; the conditional-required rule rejects this shape.",
+      "status": "passing"
+    }
+  ],
+  "status": "draft",
+  "createdAt": "2026-08-28T00:00:00Z",
+  "updatedAt": "2026-08-28T00:00:00Z"
+}

package/fixtures/invalid/test-suite/ts-009-failing-tc-missing-testpointer.json

@@ -0,0 +1,19 @@
+{
+  "id": "TS-202",
+  "usId": "US-202",
+  "title": "Failing TC missing required testPointer",
+  "purpose": "0.5.0 requires testPointer on failing TCs; this fixture omits it and must be rejected.",
+  "testLevel": "unit",
+  "acIds": ["AC-202-1"],
+  "testCases": [
+    {
+      "id": "TC-202-failing-no-pointer",
+      "acId": "AC-202-1",
+      "description": "Claims a failing verdict but points at nothing; the conditional-required rule rejects this shape.",
+      "status": "failing"
+    }
+  ],
+  "status": "draft",
+  "createdAt": "2026-08-28T00:00:00Z",
+  "updatedAt": "2026-08-28T00:00:00Z"
+}

package/fixtures/invalid/test-suite/ts-010-empty-testpointer.json

@@ -0,0 +1,20 @@
+{
+  "id": "TS-203",
+  "usId": "US-203",
+  "title": "Empty testPointer is rejected",
+  "purpose": "0.5.0 requires testPointer to be non-empty (minLength 1); an empty string is not a legitimate pointer.",
+  "testLevel": "unit",
+  "acIds": ["AC-203-1"],
+  "testCases": [
+    {
+      "id": "TC-203-empty-pointer",
+      "acId": "AC-203-1",
+      "description": "Empty pointer would let a TC claim coverage while pointing at nothing.",
+      "testPointer": "",
+      "status": "passing"
+    }
+  ],
+  "status": "draft",
+  "createdAt": "2026-08-28T00:00:00Z",
+  "updatedAt": "2026-08-28T00:00:00Z"
+}

package/fixtures/valid/manifest/manifest-013-blueprint-library-prefix.json

@@ -0,0 +1,25 @@
+{
+  "version": "2.0.0",
+  "projectName": "Project applying blueprints through a registered library",
+  "prd": { "id": "PRD-001", "path": "rcf/prd.json" },
+  "tad": { "id": "TAD-001", "path": "rcf/tad.json" },
+  "bs":  { "id": "BS-001",  "path": "rcf/build-sequence.json" },
+  "blueprints": [
+    {
+      "slug": "spa",
+      "version": "1.0.0",
+      "appliedAt": "2026-08-31T10:00:00Z",
+      "source": "acme:spa",
+      "libraryPrefix": "acme",
+      "contributions": [
+        { "id": "spa-REQ-001", "path": "rcf/requirements/spa-req-001.json", "kind": "req" }
+      ]
+    },
+    {
+      "slug": "rest",
+      "version": "1.0.0",
+      "appliedAt": "2026-08-31T10:00:05Z",
+      "source": "rcf/blueprints/rest"
+    }
+  ]
+}

package/fixtures/valid/test-suite/ts-003-runtime-provenance.json

@@ -23,6 +23,7 @@
       "id": "TC-015-non-2xx",
       "acId": "AC-1001-2",
       "description": "non-2xx response surfaces to caller",
+      "testPointer": "test/email-dispatcher.test.ts::non-2xx surfaces",
       "status": "passing",
       "runtimeProvenance": {
         "profile": "mock",

package/fixtures/valid/test-suite/ts-004-widened-tsId.json

@@ -10,6 +10,7 @@
       "id": "TC-1000-startup-loads-config",
       "acId": "AC-1001-1",
       "description": "On boot, the config loader wires and dispatches the first tick.",
+      "testPointer": "test/boot.test.ts::startup loads config",
       "status": "passing",
       "scope": "runtime"
     },
@@ -17,6 +18,7 @@
       "id": "TC-1000-deployed-smoke",
       "acId": "AC-1001-1",
       "description": "On the deployed instance, the first probe fires against a real target.",
+      "testPointer": "test/deploy.smoke.ts::deployed first probe",
       "status": "passing",
       "scope": "deployed"
     }

package/fixtures/valid/test-suite/ts-006-testpointer-conditional.json

@@ -0,0 +1,46 @@
+{
+  "id": "TS-200",
+  "usId": "US-200",
+  "title": "TC testPointer conditional-by-status coverage",
+  "purpose": "Prove the 0.5.0 rule: testPointer is required for passing/failing TCs and optional for pending/skipped TCs.",
+  "testLevel": "unit",
+  "acIds": ["AC-200-1"],
+  "testCases": [
+    {
+      "id": "TC-200-passing-with-pointer",
+      "acId": "AC-200-1",
+      "description": "Passing TC carries the executable pointer.",
+      "testPointer": "test/example.test.js::passing case",
+      "status": "passing"
+    },
+    {
+      "id": "TC-200-failing-with-pointer",
+      "acId": "AC-200-1",
+      "description": "Failing TC still points at the executable that produced the verdict.",
+      "testPointer": "test/example.test.js::failing case",
+      "status": "failing"
+    },
+    {
+      "id": "TC-200-pending-no-pointer",
+      "acId": "AC-200-1",
+      "description": "Pending TC has no landed executable yet, so no pointer.",
+      "status": "pending"
+    },
+    {
+      "id": "TC-200-skipped-no-pointer",
+      "acId": "AC-200-1",
+      "description": "Skipped TC also has no executable to point at.",
+      "status": "skipped"
+    },
+    {
+      "id": "TC-200-pending-with-pointer",
+      "acId": "AC-200-1",
+      "description": "A pending TC may still declare its intended pointer.",
+      "testPointer": "test/example.test.js::planned case",
+      "status": "pending"
+    }
+  ],
+  "status": "approved",
+  "createdAt": "2026-08-28T00:00:00Z",
+  "updatedAt": "2026-08-28T00:00:00Z"
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stravica-ai/rcf-schemas",
-  "version": "0.4.5",
+  "version": "0.5.1",
   "type": "module",
   "description": "JSON Schemas for the Requirements Confidence Framework (RCF). Language-neutral. The contract every RCF tool keys to.",
   "license": "Apache-2.0",
@@ -19,9 +19,6 @@
     "LICENSE",
     "CHANGELOG.md"
   ],
-  "scripts": {
-    "test": "node --test test/*.test.js"
-  },
   "devDependencies": {
     "ajv": "^8.17.1",
     "ajv-formats": "^3.0.1"
@@ -40,5 +37,8 @@
     "json-schema",
     "specifications",
     "traceability"
-  ]
-}
+  ],
+  "scripts": {
+    "test": "node --test test/*.test.js"
+  }
+}

package/schemas/adr.schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "https://schemas.stravica.io/rcf/v0.4.0/adr.schema.json",
+  "$id": "https://schemas.stravica.io/rcf/v0.5.0/adr.schema.json",
   "title": "RCF Architectural Decision Record",
   "description": "Architectural Decision Record. One per decision, one file each. Nygard / MADR convention.",
   "type": "object",
@@ -19,11 +19,11 @@
     "updatedAt"
   ],
   "properties": {
-    "adrId": { "$ref": "https://schemas.stravica.io/rcf/v0.4.0/common.schema.json#/$defs/adrId" },
-    "prdId": { "$ref": "https://schemas.stravica.io/rcf/v0.4.0/common.schema.json#/$defs/prdId" },
-    "tadId": { "$ref": "https://schemas.stravica.io/rcf/v0.4.0/common.schema.json#/$defs/tadId" },
-    "version": { "$ref": "https://schemas.stravica.io/rcf/v0.4.0/common.schema.json#/$defs/version" },
-    "status": { "$ref": "https://schemas.stravica.io/rcf/v0.4.0/common.schema.json#/$defs/adrStatus" },
+    "adrId": { "$ref": "https://schemas.stravica.io/rcf/v0.5.0/common.schema.json#/$defs/adrId" },
+    "prdId": { "$ref": "https://schemas.stravica.io/rcf/v0.5.0/common.schema.json#/$defs/prdId" },
+    "tadId": { "$ref": "https://schemas.stravica.io/rcf/v0.5.0/common.schema.json#/$defs/tadId" },
+    "version": { "$ref": "https://schemas.stravica.io/rcf/v0.5.0/common.schema.json#/$defs/version" },
+    "status": { "$ref": "https://schemas.stravica.io/rcf/v0.5.0/common.schema.json#/$defs/adrStatus" },
 
     "title": { "type": "string", "minLength": 1 },
     "context": { "type": "string", "minLength": 1 },
@@ -34,14 +34,14 @@
       "items": { "$ref": "#/$defs/alternative" }
     },
 
-    "supersededBy": { "$ref": "https://schemas.stravica.io/rcf/v0.4.0/common.schema.json#/$defs/adrId" },
+    "supersededBy": { "$ref": "https://schemas.stravica.io/rcf/v0.5.0/common.schema.json#/$defs/adrId" },
     "relatedAdrs": {
       "type": "array",
-      "items": { "$ref": "https://schemas.stravica.io/rcf/v0.4.0/common.schema.json#/$defs/adrId" }
+      "items": { "$ref": "https://schemas.stravica.io/rcf/v0.5.0/common.schema.json#/$defs/adrId" }
     },
 
-    "createdAt": { "$ref": "https://schemas.stravica.io/rcf/v0.4.0/common.schema.json#/$defs/timestamp" },
-    "updatedAt": { "$ref": "https://schemas.stravica.io/rcf/v0.4.0/common.schema.json#/$defs/timestamp" }
+    "createdAt": { "$ref": "https://schemas.stravica.io/rcf/v0.5.0/common.schema.json#/$defs/timestamp" },
+    "updatedAt": { "$ref": "https://schemas.stravica.io/rcf/v0.5.0/common.schema.json#/$defs/timestamp" }
   },
   "$defs": {
     "alternative": {

package/schemas/build-sequence.schema.json

@@ -1,22 +1,22 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "https://schemas.stravica.io/rcf/v0.4.0/build-sequence.schema.json",
+  "$id": "https://schemas.stravica.io/rcf/v0.5.0/build-sequence.schema.json",
   "title": "RCF Build Sequence",
   "description": "One per project. Pure planning shell. FBSs each carry the mandatory bsId parent reference plus buildOrder; the ordered FBS list is computed by loading every FBS under rcf/fbs/, filtering by bsId, and sorting by buildOrder. Duplicate buildOrder within one BS is a validation error at load time.",
   "type": "object",
   "additionalProperties": false,
   "required": ["bsId", "prdId", "version", "status", "createdAt", "updatedAt"],
   "properties": {
-    "bsId": { "$ref": "https://schemas.stravica.io/rcf/v0.4.0/common.schema.json#/$defs/bsId" },
-    "prdId": { "$ref": "https://schemas.stravica.io/rcf/v0.4.0/common.schema.json#/$defs/prdId" },
-    "version": { "$ref": "https://schemas.stravica.io/rcf/v0.4.0/common.schema.json#/$defs/version" },
-    "status": { "$ref": "https://schemas.stravica.io/rcf/v0.4.0/common.schema.json#/$defs/authoringStatus" },
+    "bsId": { "$ref": "https://schemas.stravica.io/rcf/v0.5.0/common.schema.json#/$defs/bsId" },
+    "prdId": { "$ref": "https://schemas.stravica.io/rcf/v0.5.0/common.schema.json#/$defs/prdId" },
+    "version": { "$ref": "https://schemas.stravica.io/rcf/v0.5.0/common.schema.json#/$defs/version" },
+    "status": { "$ref": "https://schemas.stravica.io/rcf/v0.5.0/common.schema.json#/$defs/authoringStatus" },
     "title": { "type": "string" },
     "buildPhilosophy": { "type": "string" },
     "generationStrategy": {
       "enum": ["verticalSlice", "dependencyFirst", "domainGrouped", "riskFrontLoaded"]
     },
-    "createdAt": { "$ref": "https://schemas.stravica.io/rcf/v0.4.0/common.schema.json#/$defs/timestamp" },
-    "updatedAt": { "$ref": "https://schemas.stravica.io/rcf/v0.4.0/common.schema.json#/$defs/timestamp" }
+    "createdAt": { "$ref": "https://schemas.stravica.io/rcf/v0.5.0/common.schema.json#/$defs/timestamp" },
+    "updatedAt": { "$ref": "https://schemas.stravica.io/rcf/v0.5.0/common.schema.json#/$defs/timestamp" }
   }
 }

package/schemas/cn.schema.json

@@ -1,13 +1,13 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "https://schemas.stravica.io/rcf/v0.4.0/cn.schema.json",
+  "$id": "https://schemas.stravica.io/rcf/v0.5.0/cn.schema.json",
   "title": "RCF Code Node",
   "description": "Code Node document. One file per node. Identity is a working-tree path, optionally #symbol-suffixed; granularity (file vs symbol) is derived from the presence of '#', never stored. Bridges the spec graph to source: implementsAcIds anchors the node into the AC layer, dependencies declares CN-to-CN edges.",
   "type": "object",
   "additionalProperties": false,
   "required": ["cnId", "path", "implementsAcIds", "version", "status", "createdAt", "updatedAt"],
   "properties": {
-    "cnId": { "$ref": "https://schemas.stravica.io/rcf/v0.4.0/common.schema.json#/$defs/cnId" },
+    "cnId": { "$ref": "https://schemas.stravica.io/rcf/v0.5.0/common.schema.json#/$defs/cnId" },
     "path": {
       "type": "string",
       "minLength": 1,
@@ -18,19 +18,19 @@
     "description": { "type": "string" },
     "implementsAcIds": {
       "type": "array",
-      "items": { "$ref": "https://schemas.stravica.io/rcf/v0.4.0/common.schema.json#/$defs/acId" },
+      "items": { "$ref": "https://schemas.stravica.io/rcf/v0.5.0/common.schema.json#/$defs/acId" },
       "minItems": 0,
       "description": "Acceptance criteria this code node satisfies. May be empty: an orphan CN (utilities, glue, wiring) is a legitimate state."
     },
     "dependencies": {
       "type": "array",
-      "items": { "$ref": "https://schemas.stravica.io/rcf/v0.4.0/common.schema.json#/$defs/cnId" },
+      "items": { "$ref": "https://schemas.stravica.io/rcf/v0.5.0/common.schema.json#/$defs/cnId" },
       "minItems": 0,
       "description": "Code nodes this node depends on (CN-to-CN edges). Hand-declared in v1."
     },
-    "version": { "$ref": "https://schemas.stravica.io/rcf/v0.4.0/common.schema.json#/$defs/version" },
-    "status": { "$ref": "https://schemas.stravica.io/rcf/v0.4.0/common.schema.json#/$defs/cnStatus" },
-    "createdAt": { "$ref": "https://schemas.stravica.io/rcf/v0.4.0/common.schema.json#/$defs/timestamp" },
-    "updatedAt": { "$ref": "https://schemas.stravica.io/rcf/v0.4.0/common.schema.json#/$defs/timestamp" }
+    "version": { "$ref": "https://schemas.stravica.io/rcf/v0.5.0/common.schema.json#/$defs/version" },
+    "status": { "$ref": "https://schemas.stravica.io/rcf/v0.5.0/common.schema.json#/$defs/cnStatus" },
+    "createdAt": { "$ref": "https://schemas.stravica.io/rcf/v0.5.0/common.schema.json#/$defs/timestamp" },
+    "updatedAt": { "$ref": "https://schemas.stravica.io/rcf/v0.5.0/common.schema.json#/$defs/timestamp" }
   }
 }

package/schemas/common.schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "https://schemas.stravica.io/rcf/v0.4.0/common.schema.json",
+  "$id": "https://schemas.stravica.io/rcf/v0.5.0/common.schema.json",
   "title": "RCF Shared Definitions",
   "description": "Shared $defs referenced via $ref from every other RCF schema. ID patterns, status enums, version string, timestamp format, and the docRef shape. This file is not a document schema; consumers register it alongside the 11 doc-type schemas at validator init. From 0.4.4 the reqId/usId/prdId/bsId/tadId/tsId patterns accept an optional lowercase kebab-slug prefix (for example, spa-REQ-001) so blueprint mechanisms can contribute namespaced doc ids without colliding with project-authored ids. Existing numeric-only ids remain valid. The adrId/tacId/fbsId/cnId patterns already carry an optional kebab-slug SUFFIX (0.4.3) and are intentionally left untouched: id grammar is mixed across types for tonight (prefix for REQ/US/PRD/BS/TAD/TS; suffix for ADR/TAC/FBS/CN); unifying is a schemas follow-up.",
   "$defs": {