rcf-lite 0.16.0 → 0.18.0

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/user-stories/us-1101.json

@@ -0,0 +1,51 @@
+{
+  "usId": "US-1101",
+  "prdId": "PRD-001",
+  "reqId": "REQ-011",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "Verify pins the Playwright MCP version and prints it in preflight",
+  "asA": "operator running rcf verify as the ship gate",
+  "iWant": "the verify launcher to provision a version-pinned @playwright/mcp instead of @latest, print the effective pin in preflight, record it in the report, and honour an emergency override with a loud stderr notice",
+  "soThat": "a newly published Playwright MCP release cannot become a silent runtime change on the next verify run, and every report artefact carries the exact browser tooling version the pass ran against",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-1101-1",
+      "description": "packages/rcf-lite/src/verify/engine/launcher.js exports a PLAYWRIGHT_MCP_VERSION constant, and DEFAULT_MCP_CONFIG.args composes @playwright/mcp@<PLAYWRIGHT_MCP_VERSION> instead of @playwright/mcp@latest.",
+      "given": "the rcf-lite source at HEAD",
+      "when": "the launcher module is imported",
+      "then": "PLAYWRIGHT_MCP_VERSION resolves to a semver string and DEFAULT_MCP_CONFIG.mcpServers.playwright.args contains the exact-pinned @playwright/mcp@<version> token, with no @latest anywhere in the module",
+      "testable": true,
+      "scope": "library"
+    },
+    {
+      "id": "AC-1101-2",
+      "description": "rcf verify run prints one preflight line naming the effective @playwright/mcp pin on stderr; the line is not suppressed by --quiet.",
+      "given": "a browser-facing fixture project and a stubbed verify launcher",
+      "when": "rcf verify run is invoked with valid required flags",
+      "then": "stderr contains one line matching /^Playwright MCP: pinned to @playwright\\/mcp@/ carrying the effective pin",
+      "testable": true,
+      "scope": "runtime"
+    },
+    {
+      "id": "AC-1101-3",
+      "description": "rcf verify run --playwright-mcp-version <semver> overrides the pinned constant for one run, prints a loud stderr override notice, and records the effective pin on the report as runStats.playwrightMcpVersion. A non-semver value refuses with exit 2.",
+      "given": "the same fixture, run with --playwright-mcp-version 0.0.99",
+      "when": "the run completes",
+      "then": "stderr carries one line matching /^Playwright MCP: OVERRIDE @playwright\\/mcp@0\\.0\\.99/, the report's run.runStats.playwrightMcpVersion equals 0.0.99, and rerunning with --playwright-mcp-version notasemver exits 2 with a semver-shape error",
+      "testable": true,
+      "scope": "runtime"
+    },
+    {
+      "id": "AC-1101-4",
+      "description": "Even when no override fires, the report records the effective (default) pin as run.runStats.playwrightMcpVersion so a report re-render tells the operator what browser tooling the pass ran against.",
+      "given": "a completed verify run with no override",
+      "when": "the report JSON is inspected",
+      "then": "report.run.runStats.playwrightMcpVersion equals PLAYWRIGHT_MCP_VERSION",
+      "testable": true,
+      "scope": "runtime"
+    }
+  ],
+  "createdAt": "2026-09-03T16:56:00Z",
+  "updatedAt": "2026-09-03T16:56:00Z"
+}

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

@@ -0,0 +1,60 @@
+{
+  "usId": "US-1102",
+  "prdId": "PRD-001",
+  "reqId": "REQ-011",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "Application-spa declares browserSurface and delivery-ci-workflows materialises an e2e CI job",
+  "asA": "operator applying the application-spa and delivery-ci-workflows blueprints",
+  "iWant": "the SPA blueprint's manifest to declare a browserSurface field, its browser-facing acceptance criteria and e2e test-case template to ship, and the delivery-ci-workflows materialiser to wire a distinct e2e CI job when at least one applied blueprint carries a browserSurface",
+  "soThat": "e2e is a first-class declared test level in the chain, and browser-facing projects get a distinct pull-request-checks e2e job while API-only projects keep the existing workflow shape verbatim",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-1102-1",
+      "description": "blueprints/application-spa/blueprint.json is at version 1.4.0 and carries a top-level browserSurface object with declared: true; the object also carries routes[] and themes[] as reference hint arrays.",
+      "given": "the SPA blueprint at HEAD",
+      "when": "blueprint.json is inspected",
+      "then": "version equals 1.4.0 and .browserSurface.declared is true",
+      "testable": true,
+      "scope": "library"
+    },
+    {
+      "id": "AC-1102-2",
+      "description": "The SPA blueprint contributes two new browser-facing acceptance criteria in the 1101 to 1899 band (existing 1131 and 1132 are already occupied by unrelated 1.3.x contributions): US-1134 binds an e2e AC on application-spa-REQ-011 (iconography), US-1135 binds an e2e AC on application-spa-REQ-009 (user arrival and auth surfaces); a paste-in assets/tc-templates/e2e.md test-case template ships and names the browser-verify TAC as its driver seam.",
+      "given": "the SPA blueprint at HEAD",
+      "when": "blueprints/application-spa/contributions/user-stories/ and blueprints/application-spa/assets/tc-templates/ are inspected",
+      "then": "application-spa-us-1134.json and application-spa-us-1135.json exist, each binds one AC whose scope is deployed and whose description names an e2e observable at a rendered browser surface; assets/tc-templates/e2e.md exists and references TAC-208",
+      "testable": true,
+      "scope": "library"
+    },
+    {
+      "id": "AC-1102-3",
+      "description": "blueprints/delivery-ci-workflows/blueprint.json is at version 2.2.0 and contributes a new US-6124 whose AC binds the elicited e2e check to a distinct e2e CI job that runs project testLevel: e2e cases against a local preview or --parity-env runtime, uploads browser artefacts, and reports a distinct row in the aggregate pipeline report.",
+      "given": "the delivery-ci-workflows blueprint at HEAD",
+      "when": "blueprint.json and contributions/user-stories/delivery-ci-workflows-us-6124.json are inspected",
+      "then": "version equals 2.2.0 and the US-6124 record binds an AC-6124-1 whose description names the four points above",
+      "testable": true,
+      "scope": "library"
+    },
+    {
+      "id": "AC-1102-4",
+      "description": "The illustrative GHA workflow at blueprints/delivery-ci-workflows/assets/ci-provider-examples/github-actions/pull-request-checks.yml carries a documented e2e job, and the alternate-provider notes file at ../notes.md carries one line per provider translating the same four points.",
+      "given": "the delivery-ci-workflows blueprint at HEAD",
+      "when": "the illustrative workflow file is inspected",
+      "then": "the workflow declares an e2e job as an example, and notes.md contains one line per provider (GitLab CI, CircleCI, Buildkite, Jenkins) naming the four points",
+      "testable": true,
+      "scope": "library"
+    },
+    {
+      "id": "AC-1102-5",
+      "description": "Applying application-spa v1.4.0 to a scratch project produces a manifest that still validates against rcf-schemas 0.5.1; the applied blueprint record carries no new field, and doctor and the delivery-ci-workflows materialiser both read browserSurface from the applied record's source blueprint.json via the existing manifest.blueprints[].source reference.",
+      "given": "a scratch project created by rcf init with application-spa v1.4.0 applied",
+      "when": "the resulting rcf/manifest.json is validated against the shipped schemas",
+      "then": "validation passes and no browserSurface key appears on the applied blueprint record itself",
+      "testable": true,
+      "scope": "runtime"
+    }
+  ],
+  "createdAt": "2026-09-03T16:56:00Z",
+  "updatedAt": "2026-09-03T16:56:00Z"
+}

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

@@ -0,0 +1,51 @@
+{
+  "usId": "US-1103",
+  "prdId": "PRD-001",
+  "reqId": "REQ-011",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "rcf doctor checks Playwright and a browser on browser-facing projects and skips them otherwise",
+  "asA": "operator running rcf doctor on either a browser-facing or an API-only project",
+  "iWant": "doctor to run playwright-present, browser-present, and playwright-mcp-reachable checks when at least one applied blueprint declares a browserSurface, and to skip all three with one printed reason line otherwise",
+  "soThat": "browser-facing projects surface missing Playwright, missing browser, or an unreachable @playwright/mcp with actionable fix lines, while API-only projects are not asked to install a browser stack they will never use",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-1103-1",
+      "description": "packages/rcf-lite/package.json declares @playwright/mcp and playwright as optional peer dependencies (peerDependenciesMeta.<pkg>.optional: true). npm and pnpm do not fail install when the peers are absent.",
+      "given": "packages/rcf-lite at HEAD",
+      "when": "package.json is inspected",
+      "then": ".peerDependencies['@playwright/mcp'] and .peerDependencies.playwright are declared and .peerDependenciesMeta.<pkg>.optional is true for both",
+      "testable": true,
+      "scope": "library"
+    },
+    {
+      "id": "AC-1103-2",
+      "description": "On a browser-facing fixture project (application-spa v1.4.0 applied), rcf doctor runs playwright-present, browser-present, and playwright-mcp-reachable; each check emits at most one fix line naming the exact remedy per the spec's fix-line table.",
+      "given": "a browser-facing fixture with no @playwright/mcp installed",
+      "when": "rcf doctor is run",
+      "then": "the three checks appear in the drift output and their fix lines match the spec's fix-line strings",
+      "testable": true,
+      "scope": "runtime"
+    },
+    {
+      "id": "AC-1103-3",
+      "description": "On an API-only fixture project (application-api-rest applied, no browser-facing blueprint), rcf doctor prints one line naming the three skipped checks and their skip reason. The line is not suppressed by --quiet.",
+      "given": "an API-only fixture project",
+      "when": "rcf doctor is run",
+      "then": "stdout contains exactly one line 'rcf doctor: skipping playwright-present, browser-present, playwright-mcp-reachable (no applied blueprint declares a browser surface).'",
+      "testable": true,
+      "scope": "runtime"
+    },
+    {
+      "id": "AC-1103-4",
+      "description": "The three checks are legal values of --check <check>[,check]; passing one explicitly on a non-browser project overrides the skip and runs it.",
+      "given": "an API-only fixture project",
+      "when": "rcf doctor --check playwright-present is run",
+      "then": "the playwright-present check runs and reports its result rather than being skipped",
+      "testable": true,
+      "scope": "runtime"
+    }
+  ],
+  "createdAt": "2026-09-03T16:56:00Z",
+  "updatedAt": "2026-09-03T16:56:00Z"
+}

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

@@ -0,0 +1,60 @@
+{
+  "usId": "US-1104",
+  "prdId": "PRD-001",
+  "reqId": "REQ-011",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "rcf init writes a Playwright MCP entry only when no scope-visible entry exists",
+  "asA": "operator running rcf init on a project with or without an ambient Playwright MCP entry",
+  "iWant": "init to detect a project-scope Playwright signature by command-tail matching, probe user scope via claude mcp list where the Claude Code harness is on PATH, write a distinctly named playwright-rcf project-scope entry only when it cannot prove any Playwright entry exists at any scope, and honour --no-playwright-mcp",
+  "soThat": "an operator with a user-scope Playwright MCP entry in Claude Code keeps it (init never shadows it) and an operator with none gets a working project-scope entry that shadows nothing at any scope by naming convention",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-1104-1",
+      "description": "When the project-scope .mcp.json carries a Playwright signature (any entry key whose args contain a string matching /^@playwright\\/mcp(@|$)/), rcf init writes no Playwright entry and prints the 'left alone' line naming the key.",
+      "given": "a fixture project with a pre-existing mcpServers entry whose args include @playwright/mcp",
+      "when": "rcf init is run",
+      "then": "the .mcp.json keys are unchanged and stdout carries the line 'Playwright MCP: already registered in .mcp.json under key '<name>' at project scope, left alone.'",
+      "testable": true,
+      "scope": "runtime"
+    },
+    {
+      "id": "AC-1104-2",
+      "description": "When the project-scope .mcp.json carries no Playwright signature, init probes the harness via an injectable seam (default: claude mcp list; 5 second timeout; text output parsed for the signature). Probe results 'entry found at user scope', 'no entry anywhere', 'CLI absent or non-zero', and 'output unparseable' each drive the correct downstream branch.",
+      "given": "a fixture project and a stubbed probe returning each of the four probe results in turn",
+      "when": "rcf init runs against each probe result",
+      "then": "'entry found' leaves .mcp.json untouched and prints the 'already registered at <scope> scope in Claude Code' line; 'no entry anywhere' writes the distinct playwright-rcf project-scope entry; both 'CLI absent or non-zero' and 'output unparseable' treat the probe as inconclusive and write the distinct playwright-rcf entry with the 'could not probe' notice",
+      "testable": true,
+      "scope": "library"
+    },
+    {
+      "id": "AC-1104-3",
+      "description": "The playwright-rcf entry, when written, has key 'playwright-rcf' distinct from 'playwright', command 'npx', args ['-y', '@playwright/mcp@<PLAYWRIGHT_MCP_VERSION>'] and empty env.",
+      "given": "a fixture project with no ambient Playwright entry anywhere",
+      "when": "rcf init runs with the probe stubbed inconclusive",
+      "then": ".mcp.json.mcpServers['playwright-rcf'] equals { type: 'stdio', command: 'npx', args: ['-y', '@playwright/mcp@<version>'], env: {} }",
+      "testable": true,
+      "scope": "runtime"
+    },
+    {
+      "id": "AC-1104-4",
+      "description": "rcf init --no-playwright-mcp suppresses the write step for the Playwright entry entirely; the probe still runs so the print-out remains honest, but no .mcp.json Playwright entry is created and no existing one is touched.",
+      "given": "a fixture project with no ambient Playwright entry anywhere",
+      "when": "rcf init --no-playwright-mcp is run",
+      "then": ".mcp.json.mcpServers contains no key matching a Playwright signature",
+      "testable": true,
+      "scope": "runtime"
+    },
+    {
+      "id": "AC-1104-5",
+      "description": "rcf doctor's playwright-mcp-redundant check fires only on browser-facing projects; when the project-scope .mcp.json carries a Playwright signature AND the probe reports a Playwright signature at user scope, doctor reports drift with the removal line naming --no-playwright-mcp and the hand-edit path. --fix does not repair this drift.",
+      "given": "a browser-facing fixture with a project-scope playwright entry and a stubbed probe reporting user-scope",
+      "when": "rcf doctor is run",
+      "then": "the drift output contains one 'playwright-mcp-redundant' entry naming the two remedies and no --fix action is applied",
+      "testable": true,
+      "scope": "runtime"
+    }
+  ],
+  "createdAt": "2026-09-03T16:56:00Z",
+  "updatedAt": "2026-09-03T16:56:00Z"
+}

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

@@ -0,0 +1,34 @@
+{
+  "usId": "US-1201",
+  "prdId": "PRD-001",
+  "reqId": "REQ-012",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "observability-essentials + observability-probe-endpoints + application-api-rest compose cleanly in every ordering with no globalAdrTopic conflict on healthProbes or readinessSemantics",
+  "asA": "operator applying the three post-alignment observability + api-rest blueprints on one project in any order",
+  "iWant": "the three amended blueprints (essentials v2.0.0, probe-endpoints v1.1.0, api-rest v2.0.0) to apply cleanly in every ordering, with observability-probe-endpoints as the sole scope:global claimant of healthProbes and readinessSemantics in the resulting manifest",
+  "soThat": "a project that reaches for all three shipped blueprints inherits a single-owner probe-path surface without an operator-side supersede ADR or a manifest-editing follow-up",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-1201-1",
+      "description": "Applying the three blueprints in every ordering (six permutations) into a freshly initialised project tree succeeds with no `globalAdrTopic` conflict on `healthProbes` or `readinessSemantics`; the resulting `rcf/manifest.json` carries all three blueprint records.",
+      "given": "a freshly initialised rcf-lite project tree and the three shipped blueprints at essentials v2.0.0, probe-endpoints v1.1.0, api-rest v2.0.0",
+      "when": "for each of the six permutations of the three blueprints, applyBlueprint runs three times in that order against a fresh project tree",
+      "then": "no ordering returns a `globalAdrTopic` conflict on healthProbes or readinessSemantics, and every ordering ends with manifest.blueprints containing observability-essentials, observability-probe-endpoints, and application-api-rest",
+      "testable": true,
+      "scope": "library"
+    },
+    {
+      "id": "AC-1201-2",
+      "description": "In the applied manifest, exactly one blueprint declares `scope: global` with `topic: healthProbes` (observability-probe-endpoints ADR-1501) and exactly one declares `scope: global` with `topic: readinessSemantics` (observability-probe-endpoints ADR-1502); zero from essentials, zero from api-rest.",
+      "given": "a project with all three amended blueprints applied",
+      "when": "manifest.blueprints[].contributions[] is walked for scope:global ADRs on the two topics",
+      "then": "the claimant list for healthProbes equals [\"observability-probe-endpoints\"] and the claimant list for readinessSemantics equals [\"observability-probe-endpoints\"]",
+      "testable": true,
+      "scope": "library"
+    }
+  ],
+  "tacIds": [],
+  "createdAt": "2026-09-04T00:00:00Z",
+  "updatedAt": "2026-09-04T00:00:00Z"
+}

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

@@ -0,0 +1,25 @@
+{
+  "usId": "US-1202",
+  "prdId": "PRD-001",
+  "reqId": "REQ-012",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "The applied tree carries no literal probe path (/healthz, /readyz, /healthz/*) outside observability-probe-endpoints prose",
+  "asA": "operator or reviewer grepping an applied project tree for literal probe paths after re-applying the three amended blueprints",
+  "iWant": "zero matches for /healthz, /readyz, /healthz/live, /healthz/ready or /healthz/startup in the applied `rcf/` tree, so the shelf ships one probe-path opinion (the resolved one) and no rogue literals",
+  "soThat": "a project that composes the three shipped blueprints never inherits a stale literal path binding that disagrees with the resolved probe path set",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-1202-1",
+      "description": "Grepping the applied `rcf/` tree of a project that has re-applied observability-essentials v2.0.0 + observability-probe-endpoints v1.1.0 + application-api-rest v2.0.0 for the strings `/healthz/live`, `/healthz/ready`, `/healthz/startup`, `/healthz`, and `/readyz` returns zero matches across all contribution JSON files.",
+      "given": "a project with all three amended blueprints applied",
+      "when": "the applied `rcf/` tree is grepped for the five literal probe-path strings above",
+      "then": "the match count is zero (matches remain only in the source blueprint READMEs and guides for observability-probe-endpoints, never in the applied contribution JSON)",
+      "testable": true,
+      "scope": "library"
+    }
+  ],
+  "tacIds": [],
+  "createdAt": "2026-09-04T00:00:00Z",
+  "updatedAt": "2026-09-04T00:00:00Z"
+}

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

@@ -0,0 +1,43 @@
+{
+  "usId": "US-1203",
+  "prdId": "PRD-001",
+  "reqId": "REQ-012",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "Each amended blueprint carries the ratified alignment facts: probe-endpoints optional startup + composing section; essentials path-neutral REQs/TACs and PROBE_INTERFACE_PATHS_MISSING; api-rest defers all probe paths",
+  "asA": "reviewer walking the three amended blueprint source directories after the alignment lands",
+  "iWant": "each blueprint to carry the shape the spec ratified: observability-probe-endpoints v1.1.0 adds the optional startup path and a composing section; observability-essentials v2.0.0 restates REQ-001/002 and TAC-801/802 path-neutral and names the PROBE_INTERFACE_PATHS_MISSING boot refusal; application-api-rest v2.0.0 defers probe paths to the resolved set with a matching AC on the auth-exempt list and a startup AC that consumes the optional path",
+  "soThat": "a downstream project (or a gate reviewer walking the shelf) reads the ratified alignment off the source blueprints directly, without needing to reconstruct the intent from the spec",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-1203-1",
+      "description": "observability-probe-endpoints/blueprint.json declares version 1.1.0. US-14102 carries a new AC-14102-4 naming the three-path resolution (/live, /ready, /startup) and the startup handler when `probeInterface.options.kubernetes.startup.enabled: true`. US-14107 carries a new AC-14107-4 naming the three-entry auth-exempt list when startup is enabled. ADR-1503 decision text names the startup.enabled flag, the same body shape, and the fused topology by default. `guide/observability-probe-endpoints.md` carries a \"Composing with observability-essentials and application-api-rest\" section naming the deferral pattern and the compose test at `packages/rcf-lite/test/blueprint/probe-path-alignment.test.js` as the ratified truth.",
+      "given": "the shipped observability-probe-endpoints blueprint source directory at HEAD",
+      "when": "blueprint.json, US-14102, US-14107, ADR-1503, and the guide are read",
+      "then": "blueprint.json version equals 1.1.0; AC-14102-4 and AC-14107-4 exist and name the startup path; ADR-1503 decision names startup.enabled; the guide carries the composing section naming the compose test path",
+      "testable": true,
+      "scope": "library"
+    },
+    {
+      "id": "AC-1203-2",
+      "description": "observability-essentials/blueprint.json declares version 2.0.0; the ADR-801 and ADR-802 contribution entries no longer carry `scope: \"global\"` or `topic`. REQ-001 and REQ-002 restate path-neutral and name `probeInterface.paths.liveness` / `probeInterface.paths.readiness` as the required configuration key. TAC-801 and TAC-802 mark the path as REQUIRED with no shipped default and name the `PROBE_INTERFACE_PATHS_MISSING` stable-coded boot refusal on the responsibilities list. US-7101 gains AC-7101-4 and US-7102 gains AC-7102-4 covering the boot-refusal-on-missing-config semantics. `docs/topics.md` shrinks the global-topics table to `statusPageContract` alone and records `healthProbes` and `readinessSemantics` in a \"Historical global topics (dropped in v2.0.0)\" section.",
+      "given": "the shipped observability-essentials blueprint source directory at HEAD",
+      "when": "blueprint.json, ADR-801, ADR-802, REQ-001, REQ-002, TAC-801, TAC-802, US-7101, US-7102, and docs/topics.md are read",
+      "then": "blueprint.json version equals 2.0.0; ADR-801/802 contribution entries carry no scope or topic field; REQ-001/002 name probeInterface.paths and refuses-boot; TAC-801/802 mark path as REQUIRED and name PROBE_INTERFACE_PATHS_MISSING; AC-7101-4 and AC-7102-4 exist; topics.md carries the Historical global topics section",
+      "testable": true,
+      "scope": "library"
+    },
+    {
+      "id": "AC-1203-3",
+      "description": "application-api-rest/blueprint.json declares version 2.0.0. REQ-006 restates path-neutral naming observability-probe-endpoints as the probe-path owner and probeInterface.paths as the essentials-alone fallback. US-2108 all eight ACs bind to \"the resolved liveness path\", \"the resolved readiness path\", or \"the resolved startup path\"; AC-2108-5 binds the auth-exempt assertion to the resolved probe path set (naming `getExemptPathSet` from TAC-1501). TAC-306 responsibilities restate the three probe surfaces at their resolved paths, drop the literal path strings, and name the auth-exempt consumption of the resolved set. US-2103 versioning-exemption AC no longer carries the literal `/healthz/*` and names the resolved probe paths instead.",
+      "given": "the shipped application-api-rest blueprint source directory at HEAD",
+      "when": "blueprint.json, REQ-006, US-2108 (all eight ACs), TAC-306, and US-2103 are read",
+      "then": "blueprint.json version equals 2.0.0; REQ-006 names probe-endpoints and probeInterface.paths as the two path-resolution sources; every US-2108 AC contains \"resolved\" and none contains a literal /healthz/* prefix; TAC-306 responsibilities name the resolved probe path set and getExemptPathSet or probeInterface.paths; US-2103 no longer contains /healthz/*",
+      "testable": true,
+      "scope": "library"
+    }
+  ],
+  "tacIds": [],
+  "createdAt": "2026-09-04T00:00:00Z",
+  "updatedAt": "2026-09-04T00:00:00Z"
+}

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

@@ -0,0 +1,25 @@
+{
+  "usId": "US-1204",
+  "prdId": "PRD-001",
+  "reqId": "REQ-012",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "Operator running `rcf define blueprint remove-resolution <adr-id>` drops a redundant historical resolutions[] entry cleanly (spec section 9 remedy)",
+  "asA": "operator running `rcf doctor --check probe-path-owner` on a project that upgraded to observability-essentials v2.0.0 + observability-probe-endpoints v1.1.0 and now sees a redundant-<topic>-resolution drift line",
+  "iWant": "the `rcf define blueprint remove-resolution <adr-id>` verb the drift line and section 9 name to actually exist, drop the named manifest.resolutions[] entry (and nothing else), refuse exit 2 when the id is not a resolution entry, and be idempotent on a second run",
+  "soThat": "the section 9 migration remedy printed by the doctor is executable verbatim, and re-running the same command after a successful pass is a no-op rather than a refusal",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-1204-1",
+      "description": "The `rcf define blueprint remove-resolution <adr-id>` verb exists on the blueprint CLI (advertised in `rcf help define blueprint`), matches the `<adr-id>` argument against `manifest.resolutions[].resolvedByAdrId`, and exhibits three ratified behaviours: (a) when an entry matches, drop that entry and only that entry from `manifest.resolutions[]` (every other manifest section byte-identical, and the project-level ADR file at `rcf/adrs/<adr-id>.json` untouched), print one result line naming the id, the topic, and the dropped resolution id, and exit 0; (b) when the `<adr-id>` is a well-formed ADR id that still names an ADR present on the project tree but is no longer on any `resolutions[]` entry, print `[blueprint] nothing to remove: '<adr-id>' is not on manifest.resolutions[]` and exit 0 (idempotent on re-run of the same operation); (c) when the `<adr-id>` is malformed against the ADR id grammar, or is well-formed but names no ADR on the tree and no resolutions[] entry, print `[error] blueprint remove-resolution: ...` on stderr and exit 2.",
+      "given": "a project whose manifest.resolutions[] carries one globalAdrTopic entry on healthProbes with resolvedByAdrId = 'ADR-011-health-probes' and the ADR file present at rcf/adrs/adr-011-health-probes.json",
+      "when": "the operator runs `rcf define blueprint remove-resolution ADR-011-health-probes` once, then a second time, then with 'not-an-adr' and with 'ADR-999-nowhere'",
+      "then": "the first run exits 0 with the removal line and drops the single resolutions[] entry (project-ADR file untouched, every other manifest section byte-identical); the second run exits 0 with the 'nothing to remove' line and does not write; 'not-an-adr' exits 2 with 'is not a well-formed ADR id'; 'ADR-999-nowhere' exits 2 with 'is not a resolution entry on this manifest'; and `rcf help define blueprint` output contains the `remove-resolution <adr-id>` verb block",
+      "testable": true,
+      "scope": "library"
+    }
+  ],
+  "tacIds": [],
+  "createdAt": "2026-09-04T00:00:00Z",
+  "updatedAt": "2026-09-04T00:00:00Z"
+}

package/releases/releases.yaml

@@ -40,8 +40,28 @@
 # `npm install rcf-lite`.
 
 feedVersion: 1
-latest: "0.16.0"
+latest: "0.18.0"
 releases:
+  - version: "0.18.0"
+    date: "2026-09-04"
+    breaking: true
+    headlines:
+      - "The rcf-lite blueprint shelf now names a single owner for probe paths across the observability, API and Kubernetes surfaces, so a project that composes more than one of these blueprints no longer has to reconcile duplicate claims by hand."
+      - "observability-essentials v2.0.0 and application-api-rest v2.0.0 drop their shipped literal /healthz and /readyz path defaults and defer to the resolved path set from observability-probe-endpoints v1.1.0, which also adds an optional Kubernetes /startup path (off by default, on per project via probeInterface.options.kubernetes.startup.enabled)."
+      - "rcf doctor grows a probe-path-owner check that flags a project applying more than one blueprint on the probe-path topic; rcf define blueprint remove-resolution <adr-id> is the paired remedy verb that drops a single manifest resolutions entry. Migration: a project on essentials v1.x alone needs one probeInterface.paths line per environment on re-apply unless it also composes probe-endpoints v1.1.0 or later; a project that applied both essentials v1.x and probe-endpoints v1.0.0 with a superseding project-level ADR will see the new doctor check flag those resolutions as redundant with the remove-resolution verb as the hint."
+    minAgentAction: null
+    notesUrl: "https://stravica.ai/docs/rcf/changelog/"
+
+  - version: "0.17.0"
+    date: "2026-09-04"
+    breaking: false
+    headlines:
+      - "rcf verify now pins the Playwright MCP browser tooling to a specific version, prints the effective pin on preflight and lands it on the run report, and takes a one-run override for emergency use."
+      - "rcf doctor grows four checks for browser-facing projects (Playwright installed, a browser available, the Playwright MCP reachable, and no shadowed duplicate entry), routed by an applied blueprint declaring a browser surface; API-only projects see one skip line."
+      - "rcf init writes a Playwright MCP entry only when no scope-visible one exists; when it cannot prove absence it writes a distinctly named playwright-rcf project-scope entry, and --no-playwright-mcp opts out entirely. application-spa v1.4.0 and delivery-ci-workflows v2.2.0 ship the paired browser stories and the illustrative e2e job as a documentation contract."
+    minAgentAction: null
+    notesUrl: "https://stravica.ai/docs/rcf/changelog/"
+
   - version: "0.16.0"
     date: "2026-09-03"
     breaking: false

package/src/blueprint/index.js

@@ -3,6 +3,7 @@
 export { applyBlueprint } from './apply.js';
 export { listBlueprints, enrichRowsWithCategories, groupRowsByCategory } from './list.js';
 export { removeBlueprint } from './remove.js';
+export { removeResolution } from './remove-resolution.js';
 export { loadBlueprint } from './loader.js';
 export { detectGlobalAdrConflicts, detectCrossBlueprintClaims, renderConflictReport, conflictReportJson } from './conflicts.js';
 export { stampId, parseIdParts, namespaceStyleFor, isNamespacedFor } from './namespace.js';