rcf-lite 0.18.0 → 0.20.0

package/blueprints/observability-logging/contributions/tacs/tac-1602-observability-logging-redaction-boundary.json

@@ -0,0 +1,27 @@
+{
+  "tacId": "TAC-1602-observability-logging-redaction-boundary",
+  "prdId": "PRD-001",
+  "tadId": "TAD-001",
+  "version": "1.0.0",
+  "status": "approved",
+  "name": "Redaction boundary",
+  "purpose": "Owns the redaction pass every emission passes through before the line lands on the sink. Encapsulates the category vocabulary from ADR-1603 (recommended defaults plus elicited additions) and the field-name matching rule; a payload field whose name or path label matches a category is replaced with the literal string [REDACTED:<category>] in the SERIALISED line, never in the caller's original object.",
+  "responsibilities": [
+    "Apply the redaction rule on a deep-cloned copy of the emission payload so the caller's original object is not mutated (AC-15103-1).",
+    "Accept elicited additional category names at boot (kebab or dotted-namespace grammar) and apply them alongside the recommended defaults (AC-15103-2).",
+    "Refuse construction when an elicited category name fails the accepted grammar (AC-15108-1)."
+  ],
+  "internalStructure": "One module exporting createRedactionBoundary({ categories }) -> { redact(payload) -> payload }. Categories is a Set of strings; matching walks payload keys (dot-path in nested objects) and replaces the value on the returned clone when the key equals or ends in a category name. The clone is a structuredClone unless the payload includes non-cloneable values, in which case the boundary falls back to a JSON round-trip clone with the serialisation-refused fold from TAC-1601.",
+  "interfaces": [
+    {
+      "name": "createRedactionBoundary",
+      "kind": "factory",
+      "description": "createRedactionBoundary({ categories: string[] }) -> { redact(payload: object): object }. Called once at boot from the logger factory; the factory holds the returned redact function and applies it on every emission."
+    }
+  ],
+  "dependencies": [],
+  "tradeoffs": "Redaction runs at the serialisation boundary and therefore only redacts fields the payload declares under a category-named key. Free-text redaction in the message string (an email pasted into a warning message) is out of scope for v1: the mechanism reach is field-level, not text-level. A project that needs text-level redaction wires a project-side wrapper around the logger call sites; the blueprint's guide names this gap.",
+  "notes": "",
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

package/blueprints/observability-logging/contributions/user-stories/observability-logging-us-15101.json

@@ -0,0 +1,34 @@
+{
+  "usId": "observability-logging-US-15101",
+  "prdId": "PRD-001",
+  "reqId": "observability-logging-REQ-001",
+  "version": "1.0.0",
+  "status": "approved",
+  "title": "Every log emission lands as one JSON object per line on stdout with the ratified minimum field set",
+  "asA": "operator running the application and consuming its stdout through a log ingestion pipeline",
+  "iWant": "every log emission to arrive as one JSON object on one line, carrying the shared minimum field set the pipeline expects",
+  "soThat": "the ingestion pipeline parses every line without special cases and no emission escapes as unstructured text",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-15101-1",
+      "description": "A log emission at any level from any call site produces exactly one line on stdout, that line parses as valid JSON, and the parsed object carries every field of the shared minimum set: message, level, timestamp, correlationId, environment, serviceName, serviceVersion.",
+      "given": "a running application with the logger factory constructed and an ambient correlation context",
+      "when": "any call site emits at any level",
+      "then": "one stdout line results, JSON.parse succeeds, and the object has all seven minimum fields present with the correct types",
+      "testable": true,
+      "scope": "runtime"
+    },
+    {
+      "id": "AC-15101-2",
+      "description": "A log emission whose payload contains a non-JSON-representable value (a BigInt, a function reference, a circular object) is caught at the boundary, dropped with one stderr notice naming the offending field, and the calling code path returns as if the emission had succeeded; the service does not crash.",
+      "given": "a running application and a caller passing a BigInt or a circular object as part of a log payload",
+      "when": "the emission is attempted",
+      "then": "stdout carries no line for this emission, stderr carries one notice naming the offending field, and the caller's next line of code executes without throwing",
+      "testable": true,
+      "scope": "runtime"
+    }
+  ],
+  "tacIds": ["TAC-1601-observability-logging-logger-factory"],
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

package/blueprints/observability-logging/contributions/user-stories/observability-logging-us-15102.json

@@ -0,0 +1,43 @@
+{
+  "usId": "observability-logging-US-15102",
+  "prdId": "PRD-001",
+  "reqId": "observability-logging-REQ-002",
+  "version": "1.0.0",
+  "status": "approved",
+  "title": "A correlation identifier read from the inbound request header rides every log line and every outbound request until the request ends",
+  "asA": "operator debugging a request path that spans multiple services",
+  "iWant": "the correlation identifier from the inbound request to appear on every log line the application emits during the request AND on every outbound request the application initiates within the same context",
+  "soThat": "log search returns the whole chain of a logical request across services from one string query",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-15102-1",
+      "description": "A request arriving with the elicited correlation header (default X-Correlation-Id per ADR-1602) causes every log line emitted during the handler and its callees to carry correlationId equal to the header value; a request arriving without the header causes the application to mint a v4 UUID and the same value appears on every log line for the request.",
+      "given": "a running application with the correlation header configured and an inbound request",
+      "when": "the request is processed (with or without the header set)",
+      "then": "every log line emitted during the request carries the same correlationId value; header value wins when present; a v4 UUID is minted otherwise",
+      "testable": true,
+      "scope": "runtime"
+    },
+    {
+      "id": "AC-15102-2",
+      "description": "An outbound HTTP request initiated from within a request-scoped handler carries the ambient correlationId as the same elicited header name.",
+      "given": "an inbound request handler that issues an outbound HTTP call",
+      "when": "the outbound request is sent",
+      "then": "the outbound request headers include the correlation header with the ambient value",
+      "testable": true,
+      "scope": "runtime"
+    },
+    {
+      "id": "AC-15102-3",
+      "description": "A log emission with no ambient correlation context (boot line, scheduled task, background worker startup) carries correlationId equal to null; the field is present.",
+      "given": "a running application with no ambient request context",
+      "when": "a boot-time or background emission occurs",
+      "then": "the line carries correlationId: null",
+      "testable": true,
+      "scope": "runtime"
+    }
+  ],
+  "tacIds": ["TAC-1601-observability-logging-logger-factory"],
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

package/blueprints/observability-logging/contributions/user-stories/observability-logging-us-15103.json

@@ -0,0 +1,34 @@
+{
+  "usId": "observability-logging-US-15103",
+  "prdId": "PRD-001",
+  "reqId": "observability-logging-REQ-003",
+  "version": "1.0.0",
+  "status": "approved",
+  "title": "Fields named or path-labelled with a PII category are redacted at the boundary regardless of call-site discipline",
+  "asA": "operator concerned that PII leaks through logs",
+  "iWant": "the emission boundary to redact fields with named PII categories automatically",
+  "soThat": "a rogue caller that forgets to redact does not leak PII to the log destination",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-15103-1",
+      "description": "A log payload containing a field named or path-tagged with any of the recommended-default categories (credential, pii.email, pii.name, pii.address, token, bearer) is replaced with the literal string [REDACTED:<category>] in the emitted line; the caller's original object is not mutated (a subsequent read of the same object still shows the original value).",
+      "given": "an emission at any level whose payload includes a field tagged as pii.email",
+      "when": "the emission passes through the boundary",
+      "then": "the stdout line's field value equals [REDACTED:pii.email] and the caller-side object still holds the original address",
+      "testable": true,
+      "scope": "runtime"
+    },
+    {
+      "id": "AC-15103-2",
+      "description": "A project may add its own redaction categories at apply through the ADR-1603 elicited-additions parameter; a new category name (kebab or dotted-namespace) is accepted and applied by the boundary in the same round.",
+      "given": "a project that elicited an additional category ssn on ADR-1603",
+      "when": "an emission includes a field tagged ssn",
+      "then": "the stdout line's field value equals [REDACTED:ssn]",
+      "testable": true,
+      "scope": "runtime"
+    }
+  ],
+  "tacIds": ["TAC-1602-observability-logging-redaction-boundary"],
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

package/blueprints/observability-logging/contributions/user-stories/observability-logging-us-15104.json

@@ -0,0 +1,25 @@
+{
+  "usId": "observability-logging-US-15104",
+  "prdId": "PRD-001",
+  "reqId": "observability-logging-REQ-004",
+  "version": "1.0.0",
+  "status": "approved",
+  "title": "Emissions below the operator-elicited minimum level are dropped before serialisation",
+  "asA": "operator sizing log volume for a production environment",
+  "iWant": "emissions below the minimum level to be dropped without serialising them",
+  "soThat": "log volume matches the operator's chosen signal budget and the level filter is honoured line-by-line",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-15104-1",
+      "description": "With the elicited minimum level set to info, an emission at trace or debug produces no stdout line; an emission at info, warn, error or fatal produces one stdout line each.",
+      "given": "a running application with minimum level set to info",
+      "when": "one emission is issued at each of the six levels",
+      "then": "the stdout line count equals 4 (info, warn, error, fatal), and no line at trace or debug appears",
+      "testable": true,
+      "scope": "runtime"
+    }
+  ],
+  "tacIds": ["TAC-1601-observability-logging-logger-factory"],
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

package/blueprints/observability-logging/contributions/user-stories/observability-logging-us-15105.json

@@ -0,0 +1,34 @@
+{
+  "usId": "observability-logging-US-15105",
+  "prdId": "PRD-001",
+  "reqId": "observability-logging-REQ-005",
+  "version": "1.0.0",
+  "status": "approved",
+  "title": "Every log line reflects the operator-elicited environment, serviceName and serviceVersion",
+  "asA": "operator debugging in a shared log destination",
+  "iWant": "every log line to carry the environment, serviceName and serviceVersion the operator set at boot",
+  "soThat": "log queries partition by those three fields without prose parsing on the message string",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-15105-1",
+      "description": "The logger factory refuses to construct when environment, serviceName or serviceVersion is missing or blank; construction failure throws with a message naming the missing field.",
+      "given": "an application booting with one of the three fields absent",
+      "when": "the logger factory is constructed",
+      "then": "the construction throws, the error message names the missing field, and the process exits before any emission is possible",
+      "testable": true,
+      "scope": "runtime"
+    },
+    {
+      "id": "AC-15105-2",
+      "description": "Every emitted line carries environment, serviceName and serviceVersion at fixed field names and equal to the values the operator supplied at boot.",
+      "given": "a running application constructed with the three fields set",
+      "when": "any emission is issued",
+      "then": "the stdout line's three fields equal the operator-supplied values verbatim",
+      "testable": true,
+      "scope": "runtime"
+    }
+  ],
+  "tacIds": ["TAC-1601-observability-logging-logger-factory"],
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

package/blueprints/observability-logging/contributions/user-stories/observability-logging-us-15106.json

@@ -0,0 +1,25 @@
+{
+  "usId": "observability-logging-US-15106",
+  "prdId": "PRD-001",
+  "reqId": "observability-logging-REQ-004",
+  "version": "1.0.0",
+  "status": "approved",
+  "title": "The logger factory refuses to construct with an unknown level string",
+  "asA": "operator wiring the logger factory at boot with a mis-configured minimum level",
+  "iWant": "the factory to refuse construction with a message naming the unknown level and the accepted vocabulary",
+  "soThat": "a typo in the environment variable is caught at boot rather than silently dropping every emission",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-15106-1",
+      "description": "The factory refuses to construct when the elicited minimum level is not one of the recommended-default vocabulary (trace, debug, info, warn, error, fatal); the thrown error names the offending value and lists the accepted set.",
+      "given": "an application booting with minimum level set to 'verbose'",
+      "when": "the factory is constructed",
+      "then": "the construction throws with a message naming 'verbose' as the offending value and listing the accepted vocabulary",
+      "testable": true,
+      "scope": "runtime"
+    }
+  ],
+  "tacIds": ["TAC-1601-observability-logging-logger-factory"],
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

package/blueprints/observability-logging/contributions/user-stories/observability-logging-us-15107.json

@@ -0,0 +1,25 @@
+{
+  "usId": "observability-logging-US-15107",
+  "prdId": "PRD-001",
+  "reqId": "observability-logging-REQ-001",
+  "version": "1.0.0",
+  "status": "approved",
+  "title": "A test double captures emitted lines for assertion without touching stdout",
+  "asA": "test author verifying that the application emits the expected log lines during a test",
+  "iWant": "a test double the factory produces that captures emitted lines in memory instead of writing to stdout",
+  "soThat": "assertions on log emissions do not depend on stdout capture and do not pollute test output",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-15107-1",
+      "description": "The blueprint's guide names an in-memory capture mode of the factory contract that returns an ordered array of the emitted structured objects; the capture mode is a documented API of TAC-1601 and can be constructed in a test without any stdout redirection.",
+      "given": "a test that constructs the factory in capture mode",
+      "when": "the code under test emits any number of log lines",
+      "then": "the returned array contains one entry per emission with the same object shape the runtime writes to stdout, and stdout carries no line",
+      "testable": true,
+      "scope": "runtime"
+    }
+  ],
+  "tacIds": ["TAC-1601-observability-logging-logger-factory"],
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

package/blueprints/observability-logging/contributions/user-stories/observability-logging-us-15108.json

@@ -0,0 +1,25 @@
+{
+  "usId": "observability-logging-US-15108",
+  "prdId": "PRD-001",
+  "reqId": "observability-logging-REQ-003",
+  "version": "1.0.0",
+  "status": "approved",
+  "title": "A redaction category unknown to the boundary is refused at configuration time rather than silently ignored",
+  "asA": "operator elicited into ADR-1603 with a mis-spelled additional category name",
+  "iWant": "the factory to refuse the redaction category at configuration time with a message naming the offending value",
+  "soThat": "a typo in an added category does not silently disable redaction for that field pattern",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-15108-1",
+      "description": "The factory's redaction configuration accepts kebab-cased or dotted-namespace category names (matching the ADR-1603 recommended-default shape) and refuses any other shape with a message naming the offending value and the accepted grammar.",
+      "given": "an application configured with a redaction categories list including 'PII Email' (space, mixed case)",
+      "when": "the factory is constructed",
+      "then": "construction throws with a message naming 'PII Email' as the offending value",
+      "testable": true,
+      "scope": "runtime"
+    }
+  ],
+  "tacIds": ["TAC-1602-observability-logging-redaction-boundary"],
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

package/blueprints/observability-logging/docs/topics.md

@@ -0,0 +1,21 @@
+# observability-logging: coordination vocabulary
+
+## Global topics
+
+| Topic | Owning ADR | Meaning | Composition note |
+|---|---|---|---|
+| `logging` | `ADR-1601-observability-logging-line-shape` | Structured single-line JSON emission contract with the shared minimum field set. | Shelf-canonical claim from v1.0.0. A composing blueprint that ships a different logging contract (structured multi-line, per-service special format, non-JSON) conflicts by design; the operator resolves at project level via `rcf define blueprint supersede logging --incoming <source>`. A library-registered logging provider (wsd-logging, acme-log-emit) is preferred over this shelf provider by the companion-suggestion mechanism. |
+
+## Deliberately unclaimed topics
+
+- `logRedaction` (text-level redaction of the `message` string). Named here so a future companion blueprint can claim it cleanly; this blueprint's redaction is field-name granularity per ADR-1603.
+- `logTransport` (the transport downstream of stdout). Owned by the surrounding platform; a future blueprint may claim it if the shelf ever ships one.
+- `logMetricsBridge` (emitting log-derived metrics). Named here so a future `metrics-store` companion can claim it cleanly.
+
+## Shelf id band and suffix block
+
+| Blueprint | US band | ADR/TAC suffix block | Status | Global topics |
+|---|---|---|---|---|
+| observability-logging | 15101-15899 | 16xx | shipped v1.0.0 | `logging` |
+
+The shelf-wide band registry lives in `packages/rcf-lite/docs/blueprint-authoring.md` section 5.

package/blueprints/observability-logging/guide/observability-logging.md

@@ -0,0 +1,36 @@
+# Guide: observability-logging (v1.0.0)
+
+## What it is
+
+A shipped, org-neutral logging contract for a rcf-lite project. Every log emission lands as one JSON object per line on stdout with a shared field set the applying operator's ingestion pipeline can consume without a per-service parser. Correlation identifiers propagate through the request-scoped context and reflect on outbound requests. A field-name redaction boundary keeps PII out of emitted lines by rule, not by hope. The operator elicits the correlation header name, the redaction category additions and the minimum level per environment at apply.
+
+## What it deliberately is not
+
+- Not a log transport. The blueprint ships to stdout; the applying platform pipes it into whatever ingestion service the operator chose. Elastic Common Schema, Loki, Datadog and Splunk all consume one JSON object per line without a per-blueprint adapter.
+- Not a metrics or tracing surface. Metrics belong to a future `metrics-store` companion; tracing belongs to a distributed-tracing companion. This blueprint contributes neither.
+- Not a text-level PII scrubber. Redaction is field-name granularity per ADR-1603; a PII value concatenated into the `message` string is not caught.
+
+## When to reach for it
+
+- Any project that has not yet applied a logging companion. Applying this blueprint gives a working structured emission surface without registering a library.
+- Any project whose applied service blueprints (application-api-rest, application-spa) declare `suggestedCompanions: ["logging"]` and no more specific library provides the role.
+
+## When it does not fit
+
+- A project standing on an organisation with a shipped logging library (`wsd-logging`, `acme-log-emit`) that provides the `logging` role. Register the library and the companion-suggestion mechanism resolves to the library's provider over this shelf fallback.
+- A project that needs multi-line stack trace emission for a legacy consumer. This blueprint ships single-line JSON only; a project-level `logging` topic supersede lets the project author a different contract.
+
+## What a good outcome looks like
+
+- One JSON object per line on stdout, correlation identifier threaded across services, PII fields redacted at the boundary, level filter honoured per environment, in-memory capture mode used in tests. `rcf define validate` clean; log ingestion pipeline queries partition cleanly by environment, serviceName and serviceVersion.
+
+## The operator decisions that remain open
+
+- **The inbound correlation header name** (ADR-1602). Recommended default `X-Correlation-Id`; elicited alternative per project. Set the value the surrounding platform's proxy or client tooling already stamps.
+- **The redaction categories additions** (ADR-1603). Recommended defaults cover the six common cases; a project with a domain-specific field (ssn, iban, jwt) adds it at apply.
+- **The minimum log level per environment** (ADR-1604). Recommended vocabulary is trace / debug / info / warn / error / fatal; elicited minimum per environment. Production is typically info; development is typically debug or trace.
+- **The log transport downstream of stdout.** Out of scope for this blueprint; the surrounding platform's pipe wires ingestion.
+
+## Cost-honesty
+
+Applying this blueprint adds five REQs, eight USs, two TACs and four ADRs to the project's chain. The runtime cost is one factory per boot plus one redaction pass per emission. There is no runtime dependency added to the project's `package.json`; the factory is authored against the applying project's own runtime. The main hidden cost is the discipline of routing every emission through the factory: the guide's `Known mechanism-reach gaps` section names the class and the project-side workarounds.

package/fixtures/canary-manifest.json

@@ -2,8 +2,8 @@
   "registerCanary": [
     {
       "id": "rc-2026-09-04-001",
-      "createdAt": "2026-09-04T12:13:52.789Z",
-      "buildVersion": "0.18.0-mockdriver",
+      "createdAt": "2026-09-04T17:57:54.464Z",
+      "buildVersion": "0.20.0-mockdriver",
       "fixturePromptId": "canary-prompt-01",
       "responseWordCount": 55,
       "grades": {
@@ -35,8 +35,8 @@
     },
     {
       "id": "rc-2026-09-04-002",
-      "createdAt": "2026-09-04T12:13:52.790Z",
-      "buildVersion": "0.18.0-mockdriver",
+      "createdAt": "2026-09-04T17:57:54.465Z",
+      "buildVersion": "0.20.0-mockdriver",
       "fixturePromptId": "canary-prompt-02",
       "responseWordCount": 55,
       "grades": {
@@ -68,8 +68,8 @@
     },
     {
       "id": "rc-2026-09-04-003",
-      "createdAt": "2026-09-04T12:13:52.790Z",
-      "buildVersion": "0.18.0-mockdriver",
+      "createdAt": "2026-09-04T17:57:54.465Z",
+      "buildVersion": "0.20.0-mockdriver",
       "fixturePromptId": "canary-prompt-03",
       "responseWordCount": 55,
       "grades": {

package/guidance/harness-template.md

@@ -65,6 +65,14 @@ non-technical; the method must be invisible in what they read.
   Library-qualified names like `wsd:auth-oauth2`, the ids each apply
   stamps, and the exact CLI lines belong in files and in `rcf`
   output, not in the conversation.
+- Companion suggestions. When you apply a service blueprint that
+  declares suggested companions, tell the operator the resolved
+  companion set in plain language, name what each companion
+  contributes, and offer the apply command. Do not apply a companion
+  without the operator's explicit go. Where a registered library
+  provides a role, prefer the library over the shelf provider in
+  your suggestion, and say so. The mechanism is suggestion, never
+  compulsion.
 
 Before / after - the same first status after project setup:
 

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

@@ -1 +1 @@
-1db0aeb320810137f642e7dcdc7e8ffb4b43c9d050383ae3c9d10d10de0dd690
+129f4018f526ececaef7ae5bea19ecd72be03a957e2cf2ee3323e85f117f6cba

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

@@ -52,6 +52,14 @@ non-technical; the method must be invisible in what they read.
   Library-qualified names like `wsd:auth-oauth2`, the ids each apply
   stamps, and the exact CLI lines belong in files and in `rcf`
   output, not in the conversation.
+- Companion suggestions. When you apply a service blueprint that
+  declares suggested companions, tell the operator the resolved
+  companion set in plain language, name what each companion
+  contributes, and offer the apply command. Do not apply a companion
+  without the operator's explicit go. Where a registered library
+  provides a role, prefer the library over the shelf provider in
+  your suggestion, and say so. The mechanism is suggestion, never
+  compulsion.
 
 Before / after - the same first status after project setup:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "rcf-lite",
-  "version": "0.18.0",
+  "version": "0.20.0",
   "type": "module",
   "description": "One-install tooling for the Requirements Confidence Framework (RCF): the unified `rcf` CLI grouped into the five RCF tool groups (discover, define, build, verify, audit) plus a small core set (init, doctor, guidance, mcp), an MCP server, the live tree viewer and the fresh-context adversarial ship-gate verifier. Consumes @stravica-ai/rcf-schemas.",
   "license": "Apache-2.0",
@@ -60,7 +60,7 @@
     "#admissibility": "./src/admissibility/index.js"
   },
   "dependencies": {
-    "@stravica-ai/rcf-schemas": "0.5.1",
+    "@stravica-ai/rcf-schemas": "0.6.0",
     "ajv": "^8.20.0",
     "ajv-formats": "^3.0.1"
   },

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

@@ -0,0 +1,14 @@
+{
+  "cnId": "CN-077",
+  "path": "../../blueprints/observability-logging/blueprint.json",
+  "title": "observability-logging v1.0.0 shipped blueprint metadata (providesRoles logging, ADR-1601 global topic logging)",
+  "description": "Anchored by the core companions train (w-2026-09-03-dave-030, d-2026-09-04-022); see the spec at projects/rcf-lite-wsd/specs/rcf-lite-core-companions-spec-2026-09-04.md for the full trace.",
+  "implementsAcIds": [
+    "AC-1301-1"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

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

@@ -0,0 +1,15 @@
+{
+  "cnId": "CN-078",
+  "path": "../../blueprints/observability-logging/README.md",
+  "title": "observability-logging blueprint tree (README, guide, docs/topics.md, assets, contributions/) applies clean into a fresh fixture",
+  "description": "Anchored by the core companions train (w-2026-09-03-dave-030, d-2026-09-04-022); see the spec at projects/rcf-lite-wsd/specs/rcf-lite-core-companions-spec-2026-09-04.md for the full trace.",
+  "implementsAcIds": [
+    "AC-1301-2",
+    "AC-1301-3"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

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

@@ -0,0 +1,14 @@
+{
+  "cnId": "CN-079",
+  "path": "../../blueprints/application-error-handling/blueprint.json",
+  "title": "application-error-handling v1.0.0 shipped blueprint metadata (providesRoles errorHandling, ADR-1701 global topic errorHandling)",
+  "description": "Anchored by the core companions train (w-2026-09-03-dave-030, d-2026-09-04-022); see the spec at projects/rcf-lite-wsd/specs/rcf-lite-core-companions-spec-2026-09-04.md for the full trace.",
+  "implementsAcIds": [
+    "AC-1302-1"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

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

@@ -0,0 +1,15 @@
+{
+  "cnId": "CN-080",
+  "path": "../../blueprints/application-error-handling/README.md",
+  "title": "application-error-handling blueprint tree applies clean and docs/topics.md distinguishes errorHandling from errorEnvelope",
+  "description": "Anchored by the core companions train (w-2026-09-03-dave-030, d-2026-09-04-022); see the spec at projects/rcf-lite-wsd/specs/rcf-lite-core-companions-spec-2026-09-04.md for the full trace.",
+  "implementsAcIds": [
+    "AC-1302-2",
+    "AC-1302-3"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

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

@@ -0,0 +1,15 @@
+{
+  "cnId": "CN-081",
+  "path": "src/blueprint/loader.js#validateProvidesRoles",
+  "title": "Loader accepts providesRoles[] with lower camelCase shape validation",
+  "description": "Anchored by the core companions train (w-2026-09-03-dave-030, d-2026-09-04-022); see the spec at projects/rcf-lite-wsd/specs/rcf-lite-core-companions-spec-2026-09-04.md for the full trace.",
+  "implementsAcIds": [
+    "AC-1401-1",
+    "AC-1401-2"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

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

@@ -0,0 +1,15 @@
+{
+  "cnId": "CN-082",
+  "path": "src/blueprint/loader.js#validateSuggestedCompanions",
+  "title": "Loader accepts suggestedCompanions[] with role/reason shape validation, em-dash and emoji refusal on the reason string",
+  "description": "Anchored by the core companions train (w-2026-09-03-dave-030, d-2026-09-04-022); see the spec at projects/rcf-lite-wsd/specs/rcf-lite-core-companions-spec-2026-09-04.md for the full trace.",
+  "implementsAcIds": [
+    "AC-1401-1",
+    "AC-1401-2"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

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

@@ -0,0 +1,14 @@
+{
+  "cnId": "CN-083",
+  "path": "src/blueprint/loader.js#validateProvidesRolesPairedAdrs",
+  "title": "Loader refuses providesRoles without a paired scope:global ADR carrying the topic string equal to the role name",
+  "description": "Anchored by the core companions train (w-2026-09-03-dave-030, d-2026-09-04-022); see the spec at projects/rcf-lite-wsd/specs/rcf-lite-core-companions-spec-2026-09-04.md for the full trace.",
+  "implementsAcIds": [
+    "AC-1401-3"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

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

@@ -0,0 +1,15 @@
+{
+  "cnId": "CN-084",
+  "path": "src/cli/blueprint.js#main",
+  "title": "rcf define blueprint add: --no-companion-suggestions, --companion selectors preflighted, post-apply resolved suggestion block printed",
+  "description": "Anchored by the core companions train (w-2026-09-03-dave-030, d-2026-09-04-022); see the spec at projects/rcf-lite-wsd/specs/rcf-lite-core-companions-spec-2026-09-04.md for the full trace.",
+  "implementsAcIds": [
+    "AC-1402-1",
+    "AC-1402-2"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

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

@@ -0,0 +1,14 @@
+{
+  "cnId": "CN-085",
+  "path": "src/blueprint/companions.js#setCompanionPin",
+  "title": "companions.js: setCompanionPin lazily creates rcf/companions.json (schemaVersion 1, current pin per role, pinnedAt ISO-8601) and prints the pin-transition line on overwrite",
+  "description": "Anchored by the core companions train (w-2026-09-03-dave-030, d-2026-09-04-022); see the spec at projects/rcf-lite-wsd/specs/rcf-lite-core-companions-spec-2026-09-04.md for the full trace.",
+  "implementsAcIds": [
+    "AC-1402-3"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

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

@@ -0,0 +1,16 @@
+{
+  "cnId": "CN-086",
+  "path": "src/cli/blueprint.js#handleCompanionsVerb",
+  "title": "rcf define blueprint companions <slug>|set|unset sub-verbs: text output with origin annotations, --json envelope",
+  "description": "Anchored by the core companions train (w-2026-09-03-dave-030, d-2026-09-04-022); see the spec at projects/rcf-lite-wsd/specs/rcf-lite-core-companions-spec-2026-09-04.md for the full trace.",
+  "implementsAcIds": [
+    "AC-1403-1",
+    "AC-1403-2",
+    "AC-1403-3"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}

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

@@ -0,0 +1,14 @@
+{
+  "cnId": "CN-087",
+  "path": "src/blueprint/companions.js#resolveCompanionRole",
+  "title": "companions.js: deterministic tier ladder resolver (applied > pinned > registered library > core shelf) with per-origin notes",
+  "description": "Anchored by the core companions train (w-2026-09-03-dave-030, d-2026-09-04-022); see the spec at projects/rcf-lite-wsd/specs/rcf-lite-core-companions-spec-2026-09-04.md for the full trace.",
+  "implementsAcIds": [
+    "AC-1404-1"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-09-04T12:20:00Z",
+  "updatedAt": "2026-09-04T12:20:00Z"
+}