rcf-lite 0.17.0 → 0.18.0

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-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,18 @@
 # `npm install rcf-lite`.
 
 feedVersion: 1
-latest: "0.17.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

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';

package/src/blueprint/remove-resolution.js

@@ -0,0 +1,104 @@
+// `rcf define blueprint remove-resolution <adr-id>` implementation.
+//
+// Removes a single entry from `manifest.resolutions[]` (and NOTHING
+// else). The `<adr-id>` argument is matched against the entry's
+// `resolvedByAdrId` field, which is how the doctor's probe-path-owner
+// check (spec section 9) and the four-path resolution card (spec
+// section 4) name the resolution to the operator.
+//
+// Behaviours (spec amendment A2, ratified 2026-09-04):
+//   - Removes the resolutions[] entry whose `resolvedByAdrId` equals
+//     the argument; leaves every other manifest section untouched. The
+//     project-level ADR file at `rcf/adrs/<adr-id>.json` is NOT
+//     deleted: an operator who wants to keep the ruling ADR as
+//     historical context after the redundant resolution goes away has
+//     that path open; an operator who wants the ADR gone can rm it
+//     themselves.
+//   - Refuses exit 2 when the argument is not a resolution entry on
+//     this manifest. Two flavours count as "not a resolution entry":
+//     the id is malformed (fails the ADR-\d{3,}(-<kebab-tail>)? grammar),
+//     or the id is well-formed but names no ADR anywhere on the
+//     tree AND is not present under any resolutions[] entry.
+//   - Idempotent on a second run: when the id is a well-formed ADR
+//     id that names an ADR present on the tree (the ruling ADR that
+//     the resolution had pointed at) but is not (any longer) present
+//     under any resolutions[] entry, the module returns
+//     `{ removed: false, alreadyAbsent: true }` and the CLI edge
+//     prints "nothing to remove" and exits 0. The distinction is:
+//     the ruling ADR still exists on disk, so the operator is running
+//     the SAME operation a second time, not typing a bogus id.
+//
+// The verb never touches project ADR files, blueprint records, or any
+// other manifest section. That keeps the scope narrow enough that the
+// operator can reason about the write without reading the module.
+
+import { isRcfError, rcfError } from '../core/errors/index.js';
+import { updateManifest } from './manifest-writer.js';
+
+const ADR_ID_PATTERN = /^ADR-\d{3,}(?:-[a-z0-9]+(?:-[a-z0-9]+)*)?$/;
+
+/**
+ * @typedef {object} RemoveResolutionResult
+ * @property {boolean} removed
+ * @property {boolean} [alreadyAbsent]
+ * @property {string}  resolvedByAdrId
+ * @property {string}  [resolutionId]
+ * @property {string}  [topic]
+ */
+
+/**
+ * @param {object} args
+ * @param {string} args.projectRoot
+ * @param {import('#core/store/walker.js').TreeModel} args.tree
+ * @param {string} args.resolvedByAdrId
+ * @param {boolean} [args.dryRun]
+ * @returns {Promise<RemoveResolutionResult | import('../core/errors/index.js').RcfError>}
+ */
+export async function removeResolution({ projectRoot, tree, resolvedByAdrId, dryRun = false }) {
+  if (typeof resolvedByAdrId !== 'string' || resolvedByAdrId.trim().length === 0) {
+    return rcfError({ kind: 'usage', message: `<adr-id> is required (e.g. rcf define blueprint remove-resolution ADR-011-health-probes).` });
+  }
+  if (!ADR_ID_PATTERN.test(resolvedByAdrId)) {
+    return rcfError({ kind: 'usage', message: `'${resolvedByAdrId}' is not a well-formed ADR id (grammar: ADR-\\d{3,}(-<kebab-tail>)?).` });
+  }
+  const manifest = tree.manifest ?? {};
+  const resolutions = Array.isArray(manifest.resolutions) ? manifest.resolutions : [];
+  const index = resolutions.findIndex((r) => r?.resolvedByAdrId === resolvedByAdrId);
+  if (index === -1) {
+    // Not on resolutions[]. Two branches:
+    //   - the ruling ADR file exists on the tree: idempotent no-op
+    //     (this is a re-run of the same operation).
+    //   - no ADR by that id anywhere: refuse. The operator has typed
+    //     an id that this project has no record of, either as a
+    //     resolution entry or as a project ADR.
+    const adrPresent = tree.byId instanceof Map && tree.byId.has(resolvedByAdrId);
+    if (adrPresent) {
+      return { removed: false, alreadyAbsent: true, resolvedByAdrId };
+    }
+    return rcfError({
+      kind: 'usage',
+      message: `'${resolvedByAdrId}' is not a resolution entry on this manifest (no resolutions[] record names it as resolvedByAdrId, and no ADR by that id exists on the project tree).`,
+    });
+  }
+  const target = resolutions[index];
+  const result = await updateManifest({
+    projectRoot,
+    manifest,
+    mutate: (next) => {
+      const list = Array.isArray(next.resolutions) ? next.resolutions : [];
+      list.splice(index, 1);
+      // Drop the field entirely when empty so the manifest shape stays
+      // as compact as it was before any resolution was ever recorded.
+      if (list.length === 0) delete next.resolutions;
+      else next.resolutions = list;
+    },
+    dryRun,
+  });
+  if (isRcfError(result)) return result;
+  return {
+    removed: true,
+    resolvedByAdrId,
+    resolutionId: typeof target?.id === 'string' ? target.id : undefined,
+    topic: typeof target?.topic === 'string' ? target.topic : undefined,
+  };
+}

package/src/cli/blueprint.js

@@ -20,6 +20,7 @@ import {
   groupRowsByCategory,
   listBlueprints,
   removeBlueprint,
+  removeResolution,
   renderDiff,
   resolveBlueprintSource,
   supersedeBlueprintTopic,
@@ -66,6 +67,20 @@ Verbs:
   diff <topic>           Side-by-side view of every applied blueprint's
                          scope:global ADR on <topic>: id, path, title,
                          status, decision. Read-only.
+  remove-resolution <adr-id>
+                         Remove a single manifest.resolutions[] entry by
+                         its resolvedByAdrId (the id the doctor's
+                         probe-path-owner check names when a historical
+                         resolution has become redundant after a
+                         blueprint upgrade). Writes nothing else: the
+                         project-level ADR file at rcf/adrs/<adr-id>.json
+                         is left in place as historical context. Refuses
+                         exit 2 when <adr-id> is malformed or names no
+                         ADR on the project tree. Idempotent on re-run:
+                         when <adr-id> is a well-formed ADR id that
+                         names an ADR present on the tree but is no
+                         longer on any resolutions[] entry, prints
+                         "nothing to remove" and exits 0.
   library <verb>         Manage external blueprint libraries. Sub-verbs:
                          add, list, remove, refresh. See
                          'rcf define blueprint library --help' for the
@@ -364,6 +379,32 @@ export async function main(argv, deps = {}) {
     return 0;
   }
 
+  if (verb === 'remove-resolution') {
+    if (rest.length === 0) {
+      stderr.write('[error] blueprint remove-resolution: missing <adr-id>\n');
+      return 2;
+    }
+    const adrId = rest[0];
+    const result = await removeResolution({
+      projectRoot, tree, resolvedByAdrId: adrId,
+      dryRun: parsed.values['dry-run'] === true,
+    });
+    if (isRcfError(result)) {
+      stderr.write(`[error] blueprint remove-resolution: ${result.message}\n`);
+      return 2;
+    }
+    if (result.alreadyAbsent) {
+      if (!parsed.values.quiet) stdout.write(`[blueprint] nothing to remove: '${adrId}' is not on manifest.resolutions[].\n`);
+      return 0;
+    }
+    if (!parsed.values.quiet) {
+      const topicSuffix = result.topic ? ` (topic '${result.topic}')` : '';
+      const idSuffix = result.resolutionId ? `; dropped resolution ${result.resolutionId}` : '';
+      stdout.write(`[blueprint] removed resolution for '${adrId}'${topicSuffix}${idSuffix}.\n`);
+    }
+    return 0;
+  }
+
   stderr.write(`[error] blueprint: unknown verb '${verb}'\n`);
   stderr.write(HELP);
   return 2;

package/src/cli/doctor.js

@@ -76,6 +76,7 @@ const KNOWN_CHECKS = /** @type {const} */ ([
   'browser-present',
   'playwright-mcp-reachable',
   'playwright-mcp-redundant',
+  'probe-path-owner',
 ]);
 
 /** The four Playwright-related checks doctor runs conditionally for
@@ -102,7 +103,7 @@ Options:
                             Values: agent-instructions, gitignore,
                                     knowledge, identity, playwright-present,
                                     browser-present, playwright-mcp-reachable,
-                                    playwright-mcp-redundant.
+                                    playwright-mcp-redundant, probe-path-owner.
   --json                    Emit machine-readable envelope: { ok, drift, writes, notices }.
   --quiet                   Only summary line + first 3 drift items.
   --force                   Accept a legacy-markers --fix on hand-edited
@@ -247,6 +248,11 @@ export async function main(argv, deps = {}) {
       // API-only project even under an explicit --check ask.
       if (!ctx.browserFacing) continue;
       result = await runPlaywrightMcpRedundantCheck(ctx);
+    } else if (check === 'probe-path-owner') {
+      // Fires whenever more than one applied blueprint teaches probe paths.
+      // Runs on every project (not gated on browser-facing). Spec:
+      // projects/rcf-lite-wsd/specs/rcf-lite-probe-path-alignment-spec-2026-09-04.md section 9.
+      result = await runProbePathOwnerCheck(ctx);
     } else continue;
     for (const d of result.drift) drift.push({ check, ...d });
     for (const w of result.writes) writes.push(w);
@@ -705,6 +711,75 @@ async function runPlaywrightMcpRedundantCheck(ctx) {
   return { drift, writes: [] };
 }
 
+/* ------------------------------------------------------------------ */
+/* Check: probe-path-owner (probe-path alignment spec section 9)      */
+/* ------------------------------------------------------------------ */
+
+/**
+ * Fires when more than one applied blueprint teaches probe paths. Reads
+ * `rcf/manifest.json` for the applied-blueprint records; counts how many
+ * carry a scope:global ADR on `healthProbes` (the shelf-wide probe-path
+ * ownership topic). More than one is drift: names the blueprints and the
+ * remedy line naming the one that would have to drop its opinion.
+ *
+ * Also names any resolutions[] entry the alignment removed as redundant
+ * (a project that applied essentials v1.x + probe-endpoints v1.0.0 and
+ * resolved the two topics via supersede will have a resolution entry
+ * pointing at both blueprint ADRs; after re-applying to essentials v2.0.0
+ * the essentials side no longer claims the topic and the resolution is
+ * redundant historical context the operator can remove).
+ */
+async function runProbePathOwnerCheck(ctx) {
+  const drift = [];
+  const manifestPath = join(ctx.projectRoot, 'rcf', 'manifest.json');
+  let manifest = null;
+  try {
+    manifest = JSON.parse(await readFile(manifestPath, 'utf8'));
+  } catch { return { drift, writes: [] }; }
+  const applied = Array.isArray(manifest?.blueprints) ? manifest.blueprints : [];
+  const claimants = { healthProbes: [], readinessSemantics: [] };
+  for (const b of applied) {
+    for (const c of b?.contributions ?? []) {
+      if (c?.kind === 'adr' && c?.scope === 'global' && (c.topic === 'healthProbes' || c.topic === 'readinessSemantics')) {
+        claimants[c.topic].push({ slug: b.slug, adrId: c.id });
+      }
+    }
+  }
+  for (const topic of ['healthProbes', 'readinessSemantics']) {
+    if (claimants[topic].length > 1) {
+      const slugs = claimants[topic].map((x) => x.slug).join(', ');
+      const owner = claimants[topic].find((x) => x.slug === 'observability-probe-endpoints');
+      const remedy = owner
+        ? `${claimants[topic].filter((x) => x.slug !== 'observability-probe-endpoints').map((x) => x.slug).join(', ')} would have to drop its scope:global claim on ${topic} (observability-probe-endpoints is the shelf canonical owner from probe-endpoints v1.0.0)`
+        : `one of ${slugs} would have to drop its scope:global claim on ${topic}`;
+      drift.push({
+        item: `multiple-${topic}-owners`,
+        file: 'rcf/manifest.json',
+        message: `more than one applied blueprint teaches probe paths on topic '${topic}': ${slugs}. ${remedy}. Spec: projects/rcf-lite-wsd/specs/rcf-lite-probe-path-alignment-spec-2026-09-04.md section 9.`,
+        refusedByFix: true,
+      });
+    }
+  }
+  // Redundant resolutions: a resolutions[] entry that names both
+  // `healthProbes` or `readinessSemantics` where the current claimant
+  // count is 1 (or 0) is redundant historical context.
+  const resolutions = Array.isArray(manifest?.resolutions) ? manifest.resolutions : [];
+  for (const r of resolutions) {
+    if (r?.topic === 'healthProbes' || r?.topic === 'readinessSemantics') {
+      if (claimants[r.topic].length <= 1) {
+        drift.push({
+          item: `redundant-${r.topic}-resolution`,
+          file: 'rcf/manifest.json',
+          message: `resolution '${r?.resolvedByAdrId ?? '(unnamed)'}' on topic '${r.topic}' is now redundant historical context: only ${claimants[r.topic].length} applied blueprint claims the topic after the probe-path alignment. Consider \`rcf define blueprint remove-resolution ${r?.resolvedByAdrId ?? '<id>'}\` or leave the resolution ADR as historical.`,
+          refusedByFix: true,
+        });
+      }
+    }
+  }
+  return { drift, writes: [] };
+}
+
+
 /**
  * Default reader for the project-root .mcp.json body. Returns the parsed
  * object, or null on missing / unparseable (doctor treats an unparseable