rcf-lite 0.17.0 → 0.19.0

package/rcf/fbs/fbs-029.json

@@ -0,0 +1,27 @@
+{
+  "fbsId": "FBS-029",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 29,
+  "executionStatus": "verified",
+  "title": "application-error-handling v1.0.0 shelf blueprint (contributions + README + guide + docs/topics.md + assets); errorHandling topic distinct from errorEnvelope",
+  "summary": "Core companions train (w-2026-09-03-dave-030, d-2026-09-04-022). Covers the AC set above end to end through the shipped code paths named on the paired CN implementsAcIds[] and the paired TS testPointer entries under packages/rcf-lite/test/. Runtime provenance: Node 24.14.0 on the repo's dogfood tree; each fixture verified in scratchpad. See the spec at projects/rcf-lite-wsd/specs/rcf-lite-core-companions-spec-2026-09-04.md.",
+  "acIds": [
+    "AC-1302-1",
+    "AC-1302-2",
+    "AC-1302-3"
+  ],
+  "dependsOnFbsIds": [
+    "FBS-028"
+  ],
+  "contextRequirements": {
+    "tacIds": [],
+    "adrIds": []
+  },
+  "domain": "blueprints",
+  "estimatedSize": "small",
+  "riskLevel": "low",
+  "notes": "Part of the core companions train (w-2026-09-03-dave-030, d-2026-09-04-022). One FBS per US on REQ-013/014/015.",
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

package/rcf/fbs/fbs-030.json

@@ -0,0 +1,27 @@
+{
+  "fbsId": "FBS-030",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 30,
+  "executionStatus": "verified",
+  "title": "Loader accepts providesRoles[] and suggestedCompanions[] with shape validation + em-dash / emoji refusal on reason strings + paired-scope:global-ADR gate",
+  "summary": "Core companions train (w-2026-09-03-dave-030, d-2026-09-04-022). Covers the AC set above end to end through the shipped code paths named on the paired CN implementsAcIds[] and the paired TS testPointer entries under packages/rcf-lite/test/. Runtime provenance: Node 24.14.0 on the repo's dogfood tree; each fixture verified in scratchpad. See the spec at projects/rcf-lite-wsd/specs/rcf-lite-core-companions-spec-2026-09-04.md.",
+  "acIds": [
+    "AC-1401-1",
+    "AC-1401-2",
+    "AC-1401-3"
+  ],
+  "dependsOnFbsIds": [
+    "FBS-029"
+  ],
+  "contextRequirements": {
+    "tacIds": [],
+    "adrIds": []
+  },
+  "domain": "blueprints",
+  "estimatedSize": "small",
+  "riskLevel": "low",
+  "notes": "Part of the core companions train (w-2026-09-03-dave-030, d-2026-09-04-022). One FBS per US on REQ-013/014/015.",
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

package/rcf/fbs/fbs-031.json

@@ -0,0 +1,27 @@
+{
+  "fbsId": "FBS-031",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 31,
+  "executionStatus": "verified",
+  "title": "rcf define blueprint add prints resolved companion suggestions after apply; --companion selectors preflight-refuse non-providers; --no-companion-suggestions suppresses both phases; pins land in rcf/companions.json",
+  "summary": "Core companions train (w-2026-09-03-dave-030, d-2026-09-04-022). Covers the AC set above end to end through the shipped code paths named on the paired CN implementsAcIds[] and the paired TS testPointer entries under packages/rcf-lite/test/. Runtime provenance: Node 24.14.0 on the repo's dogfood tree; each fixture verified in scratchpad. See the spec at projects/rcf-lite-wsd/specs/rcf-lite-core-companions-spec-2026-09-04.md.",
+  "acIds": [
+    "AC-1402-1",
+    "AC-1402-2",
+    "AC-1402-3"
+  ],
+  "dependsOnFbsIds": [
+    "FBS-030"
+  ],
+  "contextRequirements": {
+    "tacIds": [],
+    "adrIds": []
+  },
+  "domain": "blueprints",
+  "estimatedSize": "small",
+  "riskLevel": "low",
+  "notes": "Part of the core companions train (w-2026-09-03-dave-030, d-2026-09-04-022). One FBS per US on REQ-013/014/015.",
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

package/rcf/fbs/fbs-032.json

@@ -0,0 +1,27 @@
+{
+  "fbsId": "FBS-032",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 32,
+  "executionStatus": "verified",
+  "title": "rcf define blueprint companions <slug>|set|unset sub-verbs (text output with origin annotations; --json envelope; set/unset round-trip; unset without pin refuses)",
+  "summary": "Core companions train (w-2026-09-03-dave-030, d-2026-09-04-022). Covers the AC set above end to end through the shipped code paths named on the paired CN implementsAcIds[] and the paired TS testPointer entries under packages/rcf-lite/test/. Runtime provenance: Node 24.14.0 on the repo's dogfood tree; each fixture verified in scratchpad. See the spec at projects/rcf-lite-wsd/specs/rcf-lite-core-companions-spec-2026-09-04.md.",
+  "acIds": [
+    "AC-1403-1",
+    "AC-1403-2",
+    "AC-1403-3"
+  ],
+  "dependsOnFbsIds": [
+    "FBS-031"
+  ],
+  "contextRequirements": {
+    "tacIds": [],
+    "adrIds": []
+  },
+  "domain": "blueprints",
+  "estimatedSize": "small",
+  "riskLevel": "low",
+  "notes": "Part of the core companions train (w-2026-09-03-dave-030, d-2026-09-04-022). One FBS per US on REQ-013/014/015.",
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

package/rcf/fbs/fbs-033.json

@@ -0,0 +1,27 @@
+{
+  "fbsId": "FBS-033",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 33,
+  "executionStatus": "verified",
+  "title": "Deterministic tier ladder resolver (applied > pinned > registered library > shelf); two-libraries-one-role refuses exit 3 with three-path resolution message on both add and companions verb; validate refuses unresolvable pin exit 3",
+  "summary": "Core companions train (w-2026-09-03-dave-030, d-2026-09-04-022). Covers the AC set above end to end through the shipped code paths named on the paired CN implementsAcIds[] and the paired TS testPointer entries under packages/rcf-lite/test/. Runtime provenance: Node 24.14.0 on the repo's dogfood tree; each fixture verified in scratchpad. See the spec at projects/rcf-lite-wsd/specs/rcf-lite-core-companions-spec-2026-09-04.md.",
+  "acIds": [
+    "AC-1404-1",
+    "AC-1404-2",
+    "AC-1404-3"
+  ],
+  "dependsOnFbsIds": [
+    "FBS-032"
+  ],
+  "contextRequirements": {
+    "tacIds": [],
+    "adrIds": []
+  },
+  "domain": "blueprints",
+  "estimatedSize": "small",
+  "riskLevel": "low",
+  "notes": "Part of the core companions train (w-2026-09-03-dave-030, d-2026-09-04-022). One FBS per US on REQ-013/014/015.",
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

package/rcf/fbs/fbs-034.json

@@ -0,0 +1,27 @@
+{
+  "fbsId": "FBS-034",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 34,
+  "executionStatus": "verified",
+  "title": "Loader accepts standardsTrace[] + per-ADR recommendedDefault / elicited / standardsTraceClause; refuses missing standardsTraceClause when standardsTrace is declared; no cross-check on clause severity to kind (amendment A2)",
+  "summary": "Core companions train (w-2026-09-03-dave-030, d-2026-09-04-022). Covers the AC set above end to end through the shipped code paths named on the paired CN implementsAcIds[] and the paired TS testPointer entries under packages/rcf-lite/test/. Runtime provenance: Node 24.14.0 on the repo's dogfood tree; each fixture verified in scratchpad. See the spec at projects/rcf-lite-wsd/specs/rcf-lite-core-companions-spec-2026-09-04.md.",
+  "acIds": [
+    "AC-1501-1",
+    "AC-1501-2",
+    "AC-1501-3"
+  ],
+  "dependsOnFbsIds": [
+    "FBS-033"
+  ],
+  "contextRequirements": {
+    "tacIds": [],
+    "adrIds": []
+  },
+  "domain": "blueprints",
+  "estimatedSize": "small",
+  "riskLevel": "low",
+  "notes": "Part of the core companions train (w-2026-09-03-dave-030, d-2026-09-04-022). One FBS per US on REQ-013/014/015.",
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

package/rcf/requirements/req-012.json

@@ -0,0 +1,22 @@
+{
+  "reqId": "REQ-012",
+  "prdId": "PRD-001",
+  "title": "Core shelf: probe-path binding has one owner (observability-probe-endpoints), essentials and api-rest defer",
+  "description": "The shipped observability-essentials, observability-probe-endpoints, and application-api-rest blueprints compose on one project without a `globalAdrTopic` conflict on the `healthProbes` or `readinessSemantics` topics; observability-probe-endpoints is the sole shelf-wide `scope: global` claimant on both topics. observability-essentials v2.0.0 drops those claims and restates its two probe REQs and TACs path-neutral, refusing boot with the stable-coded error `PROBE_INTERFACE_PATHS_MISSING` when `probeInterface.paths.liveness` or `probeInterface.paths.readiness` is absent and probe-endpoints is not composed. application-api-rest v2.0.0 drops the literal `/healthz/live`, `/healthz/ready`, and `/healthz/startup` bindings from REQ-006, US-2108 (all eight ACs), TAC-306 and US-2103, deferring to the resolved probe path set (probe-endpoints Kubernetes profile default `/live` and `/ready`, optional `/startup`; loadBalancer profile `/health`; or project-supplied `probeInterface.paths` in the essentials-alone case). observability-probe-endpoints v1.1.0 adds the optional third Kubernetes-profile path `startup` (default `/startup`), off by default and enabled by `probeInterface.options.kubernetes.startup.enabled: true`, with paired ACs on US-14102 and US-14107 and a composing section in its guide. The three-way alignment is verified by the compose test at `packages/rcf-lite/test/blueprint/probe-path-alignment.test.js` and is the ratified truth for the shelf.",
+  "category": "functional",
+  "domain": "blueprints",
+  "priority": "must",
+  "rationale": "The shipped shelf carried three literal probe-path opinions before this alignment (essentials /healthz + /readyz, probe-endpoints /live + /ready, api-rest /healthz/live + /healthz/ready + /healthz/startup). Composing any two of the three on one project either fired a designed-in `globalAdrTopic` conflict on healthProbes/readinessSemantics or silently shipped three disagreeing probe bindings. WSD-012 mandates /live and /ready, which is the probe-endpoints Kubernetes default; Dex's A4 wsd-service-anatomy binds those two paths as a parameter and required this item as its dependency. Aligning ownership to one blueprint (probe-endpoints) and making the other two defer is the smallest change that closes both the conflict-by-design surface and the silent-disagreement surface without inventing a new composer primitive. Ratified spec: `projects/rcf-lite-wsd/specs/rcf-lite-probe-path-alignment-spec-2026-09-04.md` (sections 1 through 11).",
+  "tags": [
+    "blueprints",
+    "observability",
+    "probe-endpoints",
+    "essentials",
+    "api-rest",
+    "alignment"
+  ],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-09-04T00:00:00Z",
+  "updatedAt": "2026-09-04T00:00:00Z"
+}

package/rcf/requirements/req-013.json

@@ -0,0 +1,22 @@
+{
+  "reqId": "REQ-013",
+  "prdId": "PRD-001",
+  "title": "Core shelf gains two general-enterprise-practice companion blueprints: observability-logging and application-error-handling",
+  "description": "The shipped core shelf carries two new blueprints written to general enterprise practice, not to any one organisation's standards. `observability-logging` v1.0.0 (category `observability`, US band 15101-15899, ADR/TAC suffix block 16xx) contributes REQs, USs, TACs and ADRs for a structured single-line JSON emission surface with a correlation-identifier propagation contract, a redaction boundary anchored to named PII categories, an operator-elicited level vocabulary, and an environment/service-name/service-version stamping contract. Its `providesRoles` field carries `[\"logging\"]` and its ADR-1601 mints the shelf-wide `logging` global topic (transferred from `application-api-rest-ADR-304`, retained there as a superseded record per version-rule discipline). `application-error-handling` v1.0.0 (category `application`, US band 16101-16899, ADR/TAC suffix block 17xx) contributes REQs, USs, TACs and ADRs for the uncaught-exception boundary, the internal error record shape (code, category, message, correlation identifier, cause chain, redacted context), a transient/permanent/unknown classification vocabulary, and error emission delegated through the logging companion. Its `providesRoles` carries `[\"errorHandling\"]` and its ADR-1701 mints the `errorHandling` global topic (distinct from `errorEnvelope`, which stays with `application-api-rest` as the REST wire shape). Both blueprints ship the same anatomy every shipped shelf blueprint teaches: `blueprint.json` + `contributions/` + `README.md` + `guide/<slug>.md` + `docs/topics.md` + `assets/`; every AC is runtime-observable through a stdout capture, a filesystem-write observer, or a stubbed transport.",
+  "category": "functional",
+  "domain": "blueprints",
+  "priority": "must",
+  "rationale": "The core shelf carried no logging or error-handling blueprint before this train; every WSD-facing service blueprint (Dex's `wsd-api-rest`) stated its companion suggestions in prose only, with no core fallback for projects that had not registered the WSD library. Baz on 2026-09-03 during the WSD blueprint round review ratified two decisions in one clause: the core shelf carries a `logging` and an `error-handling` blueprint written to general enterprise practice (not to any one organisation's standards), and a companion-suggestion mechanism (REQ-014) surfaces them at apply time. Shipping the two blueprints as general-enterprise-practice siblings of the WSD library halves means every project falls back to a sensible logging and error-handling contract without adopting a library, and the WSD library becomes a specialisation (adds `standardsTrace[]`, adds WSD-specific ADR clauses) that the mechanism resolves in preference to the core when the library is registered.",
+  "tags": [
+    "blueprints",
+    "observability",
+    "logging",
+    "error-handling",
+    "companions",
+    "shelf"
+  ],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

package/rcf/requirements/req-014.json

@@ -0,0 +1,22 @@
+{
+  "reqId": "REQ-014",
+  "prdId": "PRD-001",
+  "title": "Companion-suggestion mechanism: additive manifest fields, deterministic resolution rule, `rcf define blueprint companions` verb, refusal shapes, project-level pin file, agent-facing paragraph",
+  "description": "The blueprint mechanism gains a suggestion channel that a service blueprint uses to name the companion roles it recommends alongside itself, and the loader resolves each role deterministically. Two additive optional top-level fields land on `blueprint.json`: `providesRoles[]` names the roles a blueprint provides (lower camelCase strings on `^[a-z][a-zA-Z0-9]*$`); a blueprint declaring a role MUST also carry the paired `scope: global` ADR on the topic string the role names (a `logging` role carries a `scope: global, topic: logging` ADR; a `errorHandling` role carries `scope: global, topic: errorHandling`). `suggestedCompanions[]` is a non-empty array of `{role, reason}` objects the service blueprint recommends. The resolution rule walks a deterministic tier ladder for each suggested role: applied provider wins first (already resolved at apply time), then registered library provider (`rcf/blueprint-libraries.json`), then core-shelf provider. A single library candidate wins over the shelf candidate; two library candidates for one role refuses at apply and at `rcf define blueprint companions` with exit 3 and a three-path resolution message (explicit `--companion` selector, project-level pin, or removing one library). A `--companion <role>=<slug>` selector on `rcf define blueprint add` accepts `<libraryPrefix>:<slug>` or a bare shelf slug and writes the choice to `rcf/companions.json`; naming a slug that does not declare the role refuses exit 2. A project-level `rcf/companions.json` (schemaVersion 1, current pin only per amendment A1, no per-apply history, no severity field) records role-to-provider pinnings; `rcf define blueprint companions set|unset` writes and removes pins; the file rides git. `rcf define validate` refuses exit 3 when a pinned role names an unresolvable provider. The apply-time suggestion block prints after `rcf define blueprint add` succeeds and is suppressible with `--no-companion-suggestions`. The three surfaces (apply-time block, `rcf define blueprint companions <slug>` verb, `rcf define blueprint list` annotation for suggested-but-not-applied companions) render the same resolution through a single loader function. A paragraph on the managed agent-instructions block's `How to talk to your operator` section (regenerated via `scripts/gen-managed-artefacts.mjs`) tells the agent to surface resolved companions verbally without picking. The mechanism is suggestion, never compulsion: a blueprint that declares `suggestedCompanions: [\"logging\"]` still applies cleanly with no logging blueprint present. Backward-compatible: a blueprint that does not declare `suggestedCompanions[]` produces an empty resolution and prints no block.",
+  "category": "functional",
+  "domain": "blueprints",
+  "priority": "must",
+  "rationale": "Before this train, service blueprints named their companion suggestions in prose in each README and each guide, and the machine could not act on them: `rcf define blueprint add` could not print a suggestion, `rcf define blueprint list` could not annotate an outstanding one, the agent could not know which library provider to prefer, and the operator had no place to record a project-level choice that outlived any single apply. Baz on 2026-09-03 during the WSD blueprint round review ratified the mechanism in the same clause as the two new core blueprints: the mechanism surfaces the suggestion three ways from one resolution rule, the agent surfaces the resolved companions verbally, and the operator adopts explicitly. Suggestion by role (not by slug) is the load-bearing choice: a service blueprint ships once and works with every library that provides the role; the operator's opt-in to a library IS the choice the resolution rule records.",
+  "tags": [
+    "blueprints",
+    "companions",
+    "provides-roles",
+    "suggested-companions",
+    "resolution",
+    "pin"
+  ],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

package/rcf/requirements/req-015.json

@@ -0,0 +1,21 @@
+{
+  "reqId": "REQ-015",
+  "prdId": "PRD-001",
+  "title": "Standards-derived-blueprint discipline: authoring standard section 8a, additive contribution fields, load-time validation",
+  "description": "The blueprint-authoring standard gains a section 8a that names the standards-derived discipline for any blueprint that composes on an organisational or industry standard: MUST clauses become ACs where the clause binds a testable runtime or artefact behaviour; a MUST that binds an operator choice (choice-shaped) may land as a `recommendedDefault: true` ADR carrying the clause id on `standardsTraceClause`; not-carried rows stay allowed with a named reason (per amendment A2, Baz 2026-09-04T12:20:31Z). SHOULD clauses become recommended ADR defaults (`recommendedDefault: true`) with the elicited-parameter alternative documented in the ADR's consequences. MAY clauses become elicited ADR choices (`elicited: true`) that the applying operator supplies at apply. Three additive optional ADR-contribution fields on `blueprint.json`: `recommendedDefault: true` marks the ADR as a SHOULD (or a choice-shaped MUST); `elicited: true` marks the ADR as taking an operator-supplied value at apply; `standardsTraceClause` records the standard clause identifier verbatim (`WSD-001 clause 3.1`, `RFC 7807 section 3.1`) or the sentinel `\"generic enterprise practice\"` for the neutral shelf blueprints. `recommendedDefault` and `elicited` are mutually independent. One additive blueprint-level field: `standardsTrace[]` is a list of `{id, version}` objects naming the standards the blueprint composes; optional; a blueprint that ships without it is a general-enterprise-practice blueprint by default. Load-time validation: if `standardsTrace[]` is set, every ADR contribution MUST carry a non-null `standardsTraceClause` (refusal shape: `blueprint '<slug>' declares standardsTrace but ADR contribution '<id>' has no standardsTraceClause; every ADR must reference a standard clause or the sentinel 'generic enterprise practice'.`); no cross-check on clause severity to kind mapping (that discipline is prose, not code). The discipline lands the moment a blueprint declares `standardsTrace[]`; zero shelf blueprints declare it today (the two new core blueprints in REQ-013 are general enterprise practice). Dex's WSD library at 0.9.1 already ships standards-trace tables that this discipline formalises.",
+  "category": "functional",
+  "domain": "blueprints",
+  "priority": "must",
+  "rationale": "Dex's WSD library composes on the WSD-001 through WSD-012 standards with clause-level trace tables under `docs/standards-trace.md`. Before this train, the trace lived in prose only, and a library blueprint's ADR could omit any standard reference without the loader noticing. Baz on 2026-09-03 during the WSD blueprint round review ratified the discipline as `really good idea` and made it the shelf standard for any future library or shipped blueprint that composes on named standards. Baz amendment A2 (2026-09-04T12:20:31Z) refined the MUST-to-kind mapping to admit choice-shaped MUSTs as ADRs so the WSD library's 41 MUSTs (27 to AC, 8 to ADR, 8 not-carried per Dex's tables) fit under the discipline without renumbering. The additive fields and load-time validation give machine-checkable adherence without changing any existing blueprint (zero shelf blueprints declare `standardsTrace[]` today).",
+  "tags": [
+    "blueprints",
+    "authoring",
+    "standards",
+    "traceability",
+    "loader"
+  ],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

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

@@ -0,0 +1,32 @@
+{
+  "id": "TS-034",
+  "usId": "US-1201",
+  "title": "Three amended blueprints apply cleanly in every ordering with one-owner-per-topic in the manifest",
+  "purpose": "Cover the two ACs on US-1201: no globalAdrTopic conflict on healthProbes/readinessSemantics during apply in any of the six permutations, and one-and-only-one probe-endpoints scope:global claimant per topic in the resulting manifest.",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-1201-1",
+    "AC-1201-2"
+  ],
+  "testCases": [
+    {
+      "id": "TC-034-permutations-no-globaladr-conflict",
+      "acId": "AC-1201-1",
+      "description": "The first of six orderings (essentials -> probe-endpoints -> api-rest) is exercised here as the resolved test-point representative of the parameterised assertion; the other five permutations run in the same suite file (assertion 1 (apply cleanly in every ordering): ...) and share this AC.",
+      "testPointer": "test/blueprint/probe-path-alignment.test.js::assertion 1 (apply cleanly in every ordering): observability-essentials -> observability-probe-endpoints -> application-api-rest",
+      "status": "pending",
+      "scope": "library"
+    },
+    {
+      "id": "TC-034-one-owner-per-topic",
+      "acId": "AC-1201-2",
+      "description": "After applying all three blueprints into a fresh project tree, exactly one scope:global ADR on healthProbes and one on readinessSemantics are present in the manifest, both owned by observability-probe-endpoints",
+      "testPointer": "test/blueprint/probe-path-alignment.test.js::assertion 2: one owner per topic across the applied manifest",
+      "status": "pending",
+      "scope": "library"
+    }
+  ],
+  "status": "draft",
+  "createdAt": "2026-09-04T00:00:00Z",
+  "updatedAt": "2026-09-04T00:00:00Z"
+}

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

@@ -0,0 +1,23 @@
+{
+  "id": "TS-035",
+  "usId": "US-1202",
+  "title": "Applied tree carries no literal /healthz or /readyz path outside probe-endpoints prose",
+  "purpose": "Cover the one AC on US-1202: greppable proof that /healthz, /readyz, /healthz/live, /healthz/ready and /healthz/startup do not appear in the applied rcf/ contribution JSON tree after re-applying all three amended blueprints.",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-1202-1"
+  ],
+  "testCases": [
+    {
+      "id": "TC-035-no-literal-path-in-applied-tree",
+      "acId": "AC-1202-1",
+      "description": "Applying all three amended blueprints and grepping the applied rcf/ tree for the five literal path strings returns zero matches",
+      "testPointer": "test/blueprint/probe-path-alignment.test.js::assertion 3: no literal probe path outside probe-endpoints prose or Historical ADRs in applied tree",
+      "status": "pending",
+      "scope": "library"
+    }
+  ],
+  "status": "draft",
+  "createdAt": "2026-09-04T00:00:00Z",
+  "updatedAt": "2026-09-04T00:00:00Z"
+}

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

@@ -0,0 +1,65 @@
+{
+  "id": "TS-036",
+  "usId": "US-1203",
+  "title": "Each amended blueprint carries the ratified alignment facts (probe-endpoints, essentials, api-rest)",
+  "purpose": "Cover the three ACs on US-1203: probe-endpoints has the optional startup ACs and composing section; essentials has path-neutral REQs/TACs and boot-refusal ACs; api-rest defers all probe paths to the resolved set.",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-1203-1",
+    "AC-1203-2",
+    "AC-1203-3"
+  ],
+  "testCases": [
+    {
+      "id": "TC-036-probe-endpoints-optional-startup",
+      "acId": "AC-1203-1",
+      "description": "probe-endpoints v1.1.0 declares the optional startup path across ADR-1503, US-14102 AC-14102-4, US-14107 AC-14107-4, and the guide composing section",
+      "testPointer": "test/blueprint/probe-path-alignment.test.js::assertion 4: bare compose default declares /live and /ready; optional /startup; loadBalancer /health",
+      "status": "pending",
+      "scope": "library"
+    },
+    {
+      "id": "TC-036-essentials-path-neutral-and-refusal",
+      "acId": "AC-1203-2",
+      "description": "essentials v2.0.0 restates REQ-001/002 path-neutral, marks TAC-801/802 path as REQUIRED with no default, and adds AC-7101-4/AC-7102-4 for the PROBE_INTERFACE_PATHS_MISSING boot refusal",
+      "testPointer": "test/blueprint/probe-path-alignment.test.js::assertion 5: essentials-alone declares required probeInterface.paths and refuses boot when absent",
+      "status": "pending",
+      "scope": "library"
+    },
+    {
+      "id": "TC-036-essentials-no-shipped-default",
+      "acId": "AC-1203-2",
+      "description": "TAC-801/802 interfaces carry no literal /healthz or /readyz path defaults and mark the path parameter as REQUIRED",
+      "testPointer": "test/blueprint/probe-path-alignment.test.js::assertion 7: essentials-alone shape gates on required probeInterface.paths, TACs carry no shipped default",
+      "status": "pending",
+      "scope": "library"
+    },
+    {
+      "id": "TC-036-essentials-no-dual-handler",
+      "acId": "AC-1203-2",
+      "description": "essentials TAC-801/802 responsibilities name the no-dual-handler semantics when probe-endpoints is composed",
+      "testPointer": "test/blueprint/probe-path-alignment.test.js::assertion 9: essentials TAC-801/802 promise no dual handler registration when probe-endpoints is composed",
+      "status": "pending",
+      "scope": "library"
+    },
+    {
+      "id": "TC-036-api-rest-auth-exempt-list",
+      "acId": "AC-1203-3",
+      "description": "api-rest US-2108 AC-2108-5 binds the auth-exempt assertion to the resolved probe path set naming getExemptPathSet, and TAC-306 responsibilities carry the same binding",
+      "testPointer": "test/blueprint/probe-path-alignment.test.js::assertion 6: api-rest auth-exempt list equals the probe-endpoints resolved path set",
+      "status": "pending",
+      "scope": "library"
+    },
+    {
+      "id": "TC-036-api-rest-startup-consumption",
+      "acId": "AC-1203-3",
+      "description": "api-rest US-2108 AC-2108-4 binds the startup semantics to the resolved startup path and names the startup.enabled flag or probeInterface.paths.startup as the enablement source",
+      "testPointer": "test/blueprint/probe-path-alignment.test.js::assertion 8: startup binding when enabled is declared on probe-endpoints and consumed by api-rest",
+      "status": "pending",
+      "scope": "library"
+    }
+  ],
+  "status": "draft",
+  "createdAt": "2026-09-04T00:00:00Z",
+  "updatedAt": "2026-09-04T00:00:00Z"
+}

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

@@ -0,0 +1,55 @@
+{
+  "id": "TS-037",
+  "usId": "US-1204",
+  "title": "`rcf define blueprint remove-resolution <adr-id>` verb: remove + idempotent + refuse behaviours",
+  "purpose": "Cover the single AC on US-1204: the ratified three-behaviour surface (remove entry, idempotent re-run, refuse-exit-2 on malformed or unknown id) end-to-end through the CLI, plus the help block advertising the verb.",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-1204-1"
+  ],
+  "testCases": [
+    {
+      "id": "TC-037-remove-drops-entry-and-prints-line",
+      "acId": "AC-1204-1",
+      "description": "One resolutions[] entry seeded with resolvedByAdrId 'ADR-011-health-probes'; the verb prints the removal line naming the id, topic 'healthProbes' and resolution id, exits 0, drops the single entry from manifest.resolutions[], and leaves every other manifest section and the ruling ADR file on disk unchanged.",
+      "testPointer": "test/blueprint/cli.test.js::rcf blueprint remove-resolution drops the resolutions[] entry and prints one result line (spec A2)",
+      "status": "pending",
+      "scope": "library"
+    },
+    {
+      "id": "TC-037-idempotent-second-run",
+      "acId": "AC-1204-1",
+      "description": "After a successful remove, a second run of the same command exits 0 and prints the 'nothing to remove' line without writing the manifest.",
+      "testPointer": "test/blueprint/cli.test.js::rcf blueprint remove-resolution is idempotent on re-run when the ruling ADR still exists on the tree",
+      "status": "pending",
+      "scope": "library"
+    },
+    {
+      "id": "TC-037-refuse-malformed-adr-id",
+      "acId": "AC-1204-1",
+      "description": "A malformed id 'not-an-adr' exits 2 with the well-formed-ADR-id error on stderr.",
+      "testPointer": "test/blueprint/cli.test.js::rcf blueprint remove-resolution refuses exit 2 on a malformed <adr-id>",
+      "status": "pending",
+      "scope": "library"
+    },
+    {
+      "id": "TC-037-refuse-unknown-adr-id",
+      "acId": "AC-1204-1",
+      "description": "A well-formed id ('ADR-999-nowhere') that names no ADR on the tree and no resolutions[] entry exits 2 with the 'is not a resolution entry' error on stderr.",
+      "testPointer": "test/blueprint/cli.test.js::rcf blueprint remove-resolution refuses exit 2 when <adr-id> is well-formed but names no ADR anywhere on the tree",
+      "status": "pending",
+      "scope": "library"
+    },
+    {
+      "id": "TC-037-help-lists-verb",
+      "acId": "AC-1204-1",
+      "description": "`rcf help define blueprint` output contains the `remove-resolution <adr-id>` verb block including the idempotent-on-re-run line.",
+      "testPointer": "test/blueprint/cli.test.js::rcf help define blueprint prints the remove-resolution verb",
+      "status": "pending",
+      "scope": "library"
+    }
+  ],
+  "status": "draft",
+  "createdAt": "2026-09-04T00:00:00Z",
+  "updatedAt": "2026-09-04T00:00:00Z"
+}

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

@@ -0,0 +1,41 @@
+{
+  "id": "TS-038",
+  "usId": "US-1301",
+  "title": "observability-logging v1.0.0 ships on the core shelf with the ratified anatomy and applies clean",
+  "purpose": "Cover the three ACs on US-1301: shipped anatomy (blueprint.json + contributions + README + guide + docs/topics.md + assets), clean apply into a fresh fixture, and shelf-canonical logging global topic on ADR-1601 with providesRoles logging.",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-1301-1",
+    "AC-1301-2",
+    "AC-1301-3"
+  ],
+  "testCases": [
+    {
+      "id": "TC-038-blueprint-json-fields",
+      "acId": "AC-1301-1",
+      "description": "blueprints/observability-logging/blueprint.json declares slug, version 1.0.0, category observability, providesRoles [\"logging\"], and includes contributions for REQ-001..005, US-15101..15108, TAC-1601, TAC-1602 and ADR-1601..1604 with ADR-1601 carrying scope global and topic logging.",
+      "testPointer": "test/blueprint/observability-logging-anatomy.test.js::observability-logging: blueprint.json declares the ratified shape (TC-038-blueprint-json-fields)",
+      "status": "pending",
+      "scope": "library"
+    },
+    {
+      "id": "TC-038-clean-apply",
+      "acId": "AC-1301-2",
+      "description": "rcf define blueprint add against a fresh fixture applies observability-logging cleanly (exit 0), records manifest.blueprints[] with slug observability-logging at 1.0.0, and writes rcf/adr/adr-1601-observability-logging-line-shape.json.",
+      "testPointer": "test/blueprint/observability-logging-anatomy.test.js::observability-logging: apply into a fresh fixture succeeds and writes the namespaced contributions (TC-038-clean-apply)",
+      "status": "pending",
+      "scope": "library"
+    },
+    {
+      "id": "TC-038-anatomy-and-topics",
+      "acId": "AC-1301-3",
+      "description": "The blueprint anatomy is complete: README.md carries the Apply block and Known mechanism-reach gaps section; docs/topics.md names the logging global topic string and records the 15101-15899 band with 16xx suffix block; guide/observability-logging.md exists.",
+      "testPointer": "test/blueprint/observability-logging-anatomy.test.js::observability-logging: anatomy files exist with the required sections (TC-038-anatomy-and-topics)",
+      "status": "pending",
+      "scope": "library"
+    }
+  ],
+  "status": "draft",
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

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

@@ -0,0 +1,41 @@
+{
+  "id": "TS-039",
+  "usId": "US-1302",
+  "title": "application-error-handling v1.0.0 ships on the core shelf with providesRoles errorHandling and mints the errorHandling global topic distinct from errorEnvelope",
+  "purpose": "Cover the three ACs on US-1302: shipped anatomy and blueprint.json fields, clean apply into a fresh fixture, and errorHandling vs errorEnvelope topic distinction.",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-1302-1",
+    "AC-1302-2",
+    "AC-1302-3"
+  ],
+  "testCases": [
+    {
+      "id": "TC-039-blueprint-json-fields",
+      "acId": "AC-1302-1",
+      "description": "blueprints/application-error-handling/blueprint.json declares slug, version 1.0.0, category application, providesRoles [\"errorHandling\"], and includes contributions for REQ-001..004, US-16101..16107, TAC-1701, TAC-1702 and ADR-1701..1703 with ADR-1701 carrying scope global and topic errorHandling.",
+      "testPointer": "test/blueprint/application-error-handling-anatomy.test.js::application-error-handling: blueprint.json declares the ratified shape (TC-039-blueprint-json-fields)",
+      "status": "pending",
+      "scope": "library"
+    },
+    {
+      "id": "TC-039-clean-apply",
+      "acId": "AC-1302-2",
+      "description": "rcf define blueprint add applies application-error-handling cleanly into a fresh fixture, records manifest.blueprints[] with the slug at 1.0.0, and writes rcf/adr/adr-1701-application-error-handling-record-shape.json.",
+      "testPointer": "test/blueprint/application-error-handling-anatomy.test.js::application-error-handling: apply into a fresh fixture succeeds and writes the namespaced contributions (TC-039-clean-apply)",
+      "status": "pending",
+      "scope": "library"
+    },
+    {
+      "id": "TC-039-topics-distinct",
+      "acId": "AC-1302-3",
+      "description": "docs/topics.md distinguishes errorHandling from errorEnvelope (errorHandling internal record and boundary; errorEnvelope stays with application-api-rest as REST wire shape) and reserves the 16101-16899 band with 17xx suffix block.",
+      "testPointer": "test/blueprint/application-error-handling-anatomy.test.js::application-error-handling: docs/topics.md distinguishes errorHandling from errorEnvelope (TC-039-topics-distinct)",
+      "status": "pending",
+      "scope": "library"
+    }
+  ],
+  "status": "draft",
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

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

@@ -0,0 +1,57 @@
+{
+  "id": "TS-040",
+  "usId": "US-1401",
+  "title": "Loader accepts providesRoles and suggestedCompanions with shape validation and paired-ADR gate",
+  "purpose": "Cover the three ACs on US-1401: accepted shape (both fields optional and independent), refusal shapes for camelCase pattern / empty reason / em-dash / emoji, paired-scope-global-ADR gate.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-1401-1",
+    "AC-1401-2",
+    "AC-1401-3"
+  ],
+  "testCases": [
+    {
+      "id": "TC-040-loader-accepts-both",
+      "acId": "AC-1401-1",
+      "description": "loadBlueprint against a fixture declaring providesRoles: [\"logging\"] and suggestedCompanions: [{role: \"logging\", reason: \"...\"}] returns the fields on the LoadedBlueprint object; a fixture declaring neither also loads clean.",
+      "testPointer": "test/blueprint/loader-companions.test.js::loader accepts and preserves providesRoles and suggestedCompanions (AC-1401-1)",
+      "status": "pending",
+      "scope": "library"
+    },
+    {
+      "id": "TC-040-refuse-bad-camelcase",
+      "acId": "AC-1401-2",
+      "description": "loadBlueprint refuses a fixture declaring providesRoles: [\"Logging\"] (upper camel) with rcfError kind validation naming providesRoles[0] and the offending value.",
+      "testPointer": "test/blueprint/loader-companions.test.js::loader refuses providesRoles value that fails the lower camelCase pattern (AC-1401-2)",
+      "status": "pending",
+      "scope": "library"
+    },
+    {
+      "id": "TC-040-refuse-empty-reason",
+      "acId": "AC-1401-2",
+      "description": "loadBlueprint refuses a fixture with suggestedCompanions entry whose reason is empty or whitespace-only.",
+      "testPointer": "test/blueprint/loader-companions.test.js::loader refuses suggestedCompanions entry with empty or whitespace-only reason (AC-1401-2)",
+      "status": "pending",
+      "scope": "library"
+    },
+    {
+      "id": "TC-040-refuse-em-dash-and-emoji",
+      "acId": "AC-1401-2",
+      "description": "loadBlueprint refuses a fixture with an em-dash (U+2014) or an emoji in the reason string.",
+      "testPointer": "test/blueprint/loader-companions.test.js::loader refuses em-dash in suggestedCompanions reason (AC-1401-2)",
+      "status": "pending",
+      "scope": "library"
+    },
+    {
+      "id": "TC-040-paired-adr-required",
+      "acId": "AC-1401-3",
+      "description": "loadBlueprint refuses a fixture declaring providesRoles: [\"logging\"] but no scope:global ADR carrying topic 'logging' with the exact paired-ADR refusal message.",
+      "testPointer": "test/blueprint/loader-companions.test.js::loader refuses providesRoles without a paired scope:global ADR on the topic string (AC-1401-3)",
+      "status": "pending",
+      "scope": "library"
+    }
+  ],
+  "status": "draft",
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}