rcf-lite 0.16.0 → 0.18.0

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

@@ -0,0 +1,12 @@
+{
+  "cnId": "CN-073",
+  "path": "src/cli/init.js#runPlaywrightMcpPass",
+  "title": "Init's Playwright MCP pass + probeClaudeCodeMcp seam + redundant-entry check",
+  "description": "runPlaywrightMcpPass in src/cli/init.js implements the four-branch decision tree: project-scope Playwright signature detected -> left alone; probe found at any scope in Claude Code -> left alone; probe none -> write distinctly-named playwright-rcf entry; probe inconclusive -> write with the 'could not probe' notice. --no-playwright-mcp suppresses the write step entirely; the probe still runs so the print-out remains honest. probeClaudeCodeMcp in src/setup/playwright-checks.js shells out to `claude mcp list` (5s timeout) plus `claude mcp get <name>` for the scope; parseClaudeMcpListOutput and parseClaudeMcpGetScope carry the parsing logic. Doctor's playwright-mcp-redundant check (runPlaywrightMcpRedundantCheck in src/cli/doctor.js) fires only on browser-facing projects when both project and user scopes carry a Playwright signature; --fix does not repair the drift (deliberate operator choice per spec 4.5).",
+  "implementsAcIds": ["AC-1104-1", "AC-1104-2", "AC-1104-3", "AC-1104-4", "AC-1104-5"],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-09-03T17:00:00Z",
+  "updatedAt": "2026-09-03T17:00:00Z"
+}

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

@@ -0,0 +1,19 @@
+{
+  "cnId": "CN-074",
+  "path": "test/blueprint/probe-path-alignment.test.js",
+  "title": "Three-way probe-path compose test (nine assertions across essentials v2.0.0, probe-endpoints v1.1.0, api-rest v2.0.0)",
+  "description": "The compose test file covers the nine assertions ratified in spec section 7 as document-level mechanism invariants over the shipped blueprint contributions and the applied rcf/ tree. Six static-named permutation tests for assertion 1 (the AC-1201-1 test pointer resolves to the first permutation), then one assertion each for one-owner-per-topic in the manifest, no-literal-path in the applied tree with Historical-ADR skip, bare compose defaults + optional startup + loadBalancer /health, essentials-alone required-config + PROBE_INTERFACE_PATHS_MISSING, auth-exempt-list agreement, TAC path-required-no-default, startup binding when enabled, and no dual handler registration. Runs in one process under the shipped node --test runner.",
+  "implementsAcIds": [
+    "AC-1201-1",
+    "AC-1201-2",
+    "AC-1202-1",
+    "AC-1203-1",
+    "AC-1203-2",
+    "AC-1203-3"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-09-04T00:00:00Z",
+  "updatedAt": "2026-09-04T00:00:00Z"
+}

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

@@ -0,0 +1,15 @@
+{
+  "cnId": "CN-075",
+  "path": "src/cli/doctor.js#runProbePathOwnerCheck",
+  "title": "probe-path-owner doctor check",
+  "description": "Reads rcf/manifest.json, counts scope:global claimants on healthProbes and readinessSemantics; drift on more than one claimant per topic (names the applied blueprints and the remedy line naming the one that would have to drop its opinion, spec section 9). Also flags redundant historical resolutions[] entries on either topic when the current claimant count is <= 1 (a project that resolved the v1.x designed-in conflicts and re-applied to essentials v2.0.0 sees the resolution flagged as redundant, with the rcf define blueprint remove-resolution hint). Added to KNOWN_CHECKS; help text lists the new check. Not gated on browser-facing.",
+  "implementsAcIds": [
+    "AC-1203-2",
+    "AC-1203-3"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-09-04T00:00:00Z",
+  "updatedAt": "2026-09-04T00:00:00Z"
+}

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

@@ -0,0 +1,14 @@
+{
+  "cnId": "CN-076",
+  "path": "src/blueprint/remove-resolution.js#removeResolution",
+  "title": "`rcf define blueprint remove-resolution` verb implementation",
+  "description": "removeResolution({ projectRoot, tree, resolvedByAdrId }) matches the argument against tree.manifest.resolutions[].resolvedByAdrId and drops the single matching entry via updateManifest (validates + tmp-write + rename); no other section of the manifest is touched, and the project-level ADR file at rcf/adrs/<adr-id>.json is left in place as historical context. Refuses with a usage rcfError (mapped to exit 2 at the CLI edge) when the id is malformed against ^ADR-\\d{3,}(-<kebab-tail>)?$ or when it is well-formed but names no ADR on tree.byId and is not on resolutions[]. When the id is well-formed and names an ADR present on the tree but is not on resolutions[], returns `{ removed: false, alreadyAbsent: true }` so the CLI edge prints the 'nothing to remove' line and exits 0 (the second-pass idempotency semantics ratified in spec A2). The verb is dispatched from src/cli/blueprint.js's main() and advertised in the HELP block; the doctor's probe-path-owner check names it verbatim as the remedy line for a redundant historical resolution.",
+  "implementsAcIds": [
+    "AC-1204-1"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-09-04T00:00:00Z",
+  "updatedAt": "2026-09-04T00:00:00Z"
+}

package/rcf/fbs/fbs-020.json

@@ -0,0 +1,18 @@
+{
+  "fbsId": "FBS-020",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 20,
+  "executionStatus": "verified",
+  "title": "Verify pins the Playwright MCP version",
+  "summary": "Extend packages/rcf-lite/src/verify/engine/launcher.js with an exported PLAYWRIGHT_MCP_VERSION constant and a playwrightMcpConfig(version) composer; DEFAULT_MCP_CONFIG composes @playwright/mcp@<version> not @latest. Extend the CLI (src/verify/cli/run.js) with a --playwright-mcp-version override, a loud stderr override notice, and preflight-print of the pinned default. Stamp the effective pin on report.run.runStats.playwrightMcpVersion.",
+  "acIds": ["AC-1101-1","AC-1101-2","AC-1101-3","AC-1101-4"],
+  "dependsOnFbsIds": [],
+  "contextRequirements": { "tacIds": [], "adrIds": [] },
+  "domain": "verify",
+  "estimatedSize": "small",
+  "riskLevel": "low",
+  "notes": "Landed in the ratified 2026-09-03 e2e-contract train. Covers US-1101 on REQ-011.",
+  "createdAt": "2026-09-03T17:00:00Z",
+  "updatedAt": "2026-09-03T17:00:00Z"
+}

package/rcf/fbs/fbs-021.json

@@ -0,0 +1,18 @@
+{
+  "fbsId": "FBS-021",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 21,
+  "executionStatus": "verified",
+  "title": "Blueprints amend for e2e as a declared test level",
+  "summary": "Bump application-spa to 1.4.0, add top-level browserSurface object, add US-1134 (icon) and US-1135 (auth) as new browser-facing acceptance criteria, and ship assets/tc-templates/e2e.md as the paste-in template. Bump delivery-ci-workflows to 2.2.0, add US-6124 with AC-6124-1 for the elicited e2e check, add the illustrative e2e job in pull-request-checks.yml, and add the alternate-provider notes for the e2e job. Prove the applied SPA v1.4.0 manifest validates against rcf-schemas 0.5.1 with no browserSurface field on the applied blueprint record.",
+  "acIds": ["AC-1102-1","AC-1102-2","AC-1102-3","AC-1102-4","AC-1102-5"],
+  "dependsOnFbsIds": [],
+  "contextRequirements": { "tacIds": [], "adrIds": [] },
+  "domain": "verify",
+  "estimatedSize": "small",
+  "riskLevel": "low",
+  "notes": "Landed in the ratified 2026-09-03 e2e-contract train. Covers US-1102 on REQ-011.",
+  "createdAt": "2026-09-03T17:00:00Z",
+  "updatedAt": "2026-09-03T17:00:00Z"
+}

package/rcf/fbs/fbs-022.json

@@ -0,0 +1,18 @@
+{
+  "fbsId": "FBS-022",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 22,
+  "executionStatus": "verified",
+  "title": "Doctor: playwright-present, browser-present, playwright-mcp-reachable, playwright-mcp-redundant",
+  "summary": "Declare @playwright/mcp and playwright as optional peer dependencies. Add src/setup/playwright-checks.js with the four checks and the loadBrowserFacingSources projection over manifest.blueprints. Wire the four checks into src/cli/doctor.js: run the three probes iff at least one applied blueprint declares a browserSurface OR the operator explicitly asks by --check; print the skip line otherwise; playwright-mcp-redundant fires only on browser-facing projects.",
+  "acIds": ["AC-1103-1","AC-1103-2","AC-1103-3","AC-1103-4"],
+  "dependsOnFbsIds": [],
+  "contextRequirements": { "tacIds": [], "adrIds": [] },
+  "domain": "verify",
+  "estimatedSize": "small",
+  "riskLevel": "low",
+  "notes": "Landed in the ratified 2026-09-03 e2e-contract train. Covers US-1103 on REQ-011.",
+  "createdAt": "2026-09-03T17:00:00Z",
+  "updatedAt": "2026-09-03T17:00:00Z"
+}

package/rcf/fbs/fbs-023.json

@@ -0,0 +1,18 @@
+{
+  "fbsId": "FBS-023",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 23,
+  "executionStatus": "verified",
+  "title": "Init: Playwright MCP entry only when no scope-visible entry exists",
+  "summary": "Add a --no-playwright-mcp flag. After the rcf mcp entry write, detect a project-scope Playwright signature (any args string matching /^@playwright\/mcp(@|$)/) and leave it alone if present. Otherwise probe the harness (claude mcp list + claude mcp get <name>) and, on 'none' or 'inconclusive', write a distinctly named playwright-rcf project-scope entry. --no-playwright-mcp suppresses the write step entirely; the probe still runs so the print-out remains honest.",
+  "acIds": ["AC-1104-1","AC-1104-2","AC-1104-3","AC-1104-4","AC-1104-5"],
+  "dependsOnFbsIds": [],
+  "contextRequirements": { "tacIds": [], "adrIds": [] },
+  "domain": "verify",
+  "estimatedSize": "small",
+  "riskLevel": "low",
+  "notes": "Landed in the ratified 2026-09-03 e2e-contract train. Covers US-1104 on REQ-011.",
+  "createdAt": "2026-09-03T17:00:00Z",
+  "updatedAt": "2026-09-03T17:00:00Z"
+}

package/rcf/fbs/fbs-024.json

@@ -0,0 +1,24 @@
+{
+  "fbsId": "FBS-024",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 24,
+  "executionStatus": "verified",
+  "title": "Three-way compose test asserting no globalAdrTopic conflict on healthProbes or readinessSemantics across every ordering",
+  "summary": "Add packages/rcf-lite/test/blueprint/probe-path-alignment.test.js: six per-permutation tests (assertion 1) covering AC-1201-1 and one applied-manifest walker (assertion 2) covering AC-1201-2. Uses the shipped applyBlueprint + walkTree + initProject seams; runs in one process under the shipped node --test runner.",
+  "acIds": [
+    "AC-1201-1",
+    "AC-1201-2"
+  ],
+  "dependsOnFbsIds": [],
+  "contextRequirements": {
+    "tacIds": [],
+    "adrIds": []
+  },
+  "domain": "blueprints",
+  "estimatedSize": "small",
+  "riskLevel": "low",
+  "notes": "Part of the ratified 2026-09-04 probe-path alignment train (w-2026-09-03-dave-021). Covers US-1201 on REQ-012.",
+  "createdAt": "2026-09-04T00:00:00Z",
+  "updatedAt": "2026-09-04T00:00:00Z"
+}

package/rcf/fbs/fbs-025.json

@@ -0,0 +1,25 @@
+{
+  "fbsId": "FBS-025",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 25,
+  "executionStatus": "verified",
+  "title": "Compose test assertion 3: greppable no-literal-path invariant on the applied rcf/ tree",
+  "summary": "Add the assertion 3 block to packages/rcf-lite/test/blueprint/probe-path-alignment.test.js: applies the three amended blueprints, walks the resulting rcf/ tree, greps for the five literal probe-path strings, and skips ADR contribution files whose title begins \"Historical:\" (per spec section 4) or whose adrId names probe-secrecy (context-only ADR).",
+  "acIds": [
+    "AC-1202-1"
+  ],
+  "dependsOnFbsIds": [
+    "FBS-024"
+  ],
+  "contextRequirements": {
+    "tacIds": [],
+    "adrIds": []
+  },
+  "domain": "blueprints",
+  "estimatedSize": "small",
+  "riskLevel": "low",
+  "notes": "Part of the ratified 2026-09-04 probe-path alignment train (w-2026-09-03-dave-021). Covers US-1202 on REQ-012.",
+  "createdAt": "2026-09-04T00:00:00Z",
+  "updatedAt": "2026-09-04T00:00:00Z"
+}

package/rcf/fbs/fbs-026.json

@@ -0,0 +1,27 @@
+{
+  "fbsId": "FBS-026",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 26,
+  "executionStatus": "verified",
+  "title": "Compose test assertions 4-9 covering the per-blueprint ratified alignment facts and the probe-path-owner doctor check",
+  "summary": "Add the assertion 4-9 block to packages/rcf-lite/test/blueprint/probe-path-alignment.test.js covering probe-endpoints optional startup + composing section (assertion 4, 8), essentials PROBE_INTERFACE_PATHS_MISSING refuse-boot + no-shipped-default TACs + no-dual-handler (assertions 5, 7, 9), api-rest deferral of the probe paths and auth-exempt-list binding (assertion 6). Add the probe-path-owner check to KNOWN_CHECKS in packages/rcf-lite/src/cli/doctor.js with the runProbePathOwnerCheck implementation reading manifest.blueprints[].contributions[] for scope:global topic multi-claim drift and manifest.resolutions[] for redundant resolutions on healthProbes/readinessSemantics after the alignment.",
+  "acIds": [
+    "AC-1203-1",
+    "AC-1203-2",
+    "AC-1203-3"
+  ],
+  "dependsOnFbsIds": [
+    "FBS-025"
+  ],
+  "contextRequirements": {
+    "tacIds": [],
+    "adrIds": []
+  },
+  "domain": "blueprints",
+  "estimatedSize": "medium",
+  "riskLevel": "low",
+  "notes": "Part of the ratified 2026-09-04 probe-path alignment train (w-2026-09-03-dave-021). Covers US-1203 on REQ-012.",
+  "createdAt": "2026-09-04T00:00:00Z",
+  "updatedAt": "2026-09-04T00:00:00Z"
+}

package/rcf/fbs/fbs-027.json

@@ -0,0 +1,25 @@
+{
+  "fbsId": "FBS-027",
+  "prdId": "PRD-001",
+  "bsId": "BS-001",
+  "buildOrder": 27,
+  "executionStatus": "verified",
+  "title": "`rcf define blueprint remove-resolution <adr-id>` verb (drops one manifest.resolutions[] entry; idempotent; refuses exit 2 on malformed or unknown id)",
+  "summary": "Add packages/rcf-lite/src/blueprint/remove-resolution.js implementing removeResolution({ projectRoot, tree, resolvedByAdrId }) with the three ratified behaviours (remove + idempotent + refuse), export it from packages/rcf-lite/src/blueprint/index.js, wire the `remove-resolution` verb into packages/rcf-lite/src/cli/blueprint.js's HELP block and dispatch, and cover the surface with packages/rcf-lite/test/blueprint/remove-resolution.test.js (module) and remove-resolution cases appended to packages/rcf-lite/test/blueprint/cli.test.js (CLI edge). No changes to the doctor hint text (it names the verb already); no changes to project ADR files (the verb is scoped to manifest.resolutions[]).",
+  "acIds": [
+    "AC-1204-1"
+  ],
+  "dependsOnFbsIds": [
+    "FBS-026"
+  ],
+  "contextRequirements": {
+    "tacIds": [],
+    "adrIds": []
+  },
+  "domain": "blueprints",
+  "estimatedSize": "small",
+  "riskLevel": "low",
+  "notes": "Part of the ratified 2026-09-04 probe-path alignment train (w-2026-09-03-dave-021). Covers US-1204 on REQ-012. Spec amendment A2, added under the envelope 2026-09-04 after gate d-2026-09-04-016 finding 1 (the doctor and spec section 9 named the verb before it existed).",
+  "createdAt": "2026-09-04T00:00:00Z",
+  "updatedAt": "2026-09-04T00:00:00Z"
+}

package/rcf/prd.json

@@ -18,7 +18,8 @@
     "SDD build loop: assemble an implementation prompt from a build specification and mark it done on merge",
     "Local stdio MCP surface exposing query, CRUD, view and build to AI tooling",
     "Validation of every document against the published schema package at every boundary",
-    "Deploy-aware, runtime-honest build guidance: a documented local preview as the default build outcome, an early deploy-target question that constrains the stack, and runtime-provenance labels on verification claims"
+    "Deploy-aware, runtime-honest build guidance: a documented local preview as the default build outcome, an early deploy-target question that constrains the stack, and runtime-provenance labels on verification claims",
+    "End-to-end verification contract: version-pinned Playwright MCP in verify, e2e as a declared test level in the chain (application-spa browserSurface and delivery-ci-workflows e2e CI job), doctor checks for browser-facing projects, and init that writes a Playwright MCP entry only when no scope-visible entry exists"
   ],
   "outOfScope": [
     "The schema package itself, which is the separately published rcf-schemas contract",
@@ -43,5 +44,5 @@
     "MCP transport is local stdio only"
   ],
   "createdAt": "2026-06-25T00:00:00Z",
-  "updatedAt": "2026-07-20T17:56:57.237Z"
+  "updatedAt": "2026-09-03T16:56:00Z"
 }

package/rcf/requirements/req-011.json

@@ -0,0 +1,22 @@
+{
+  "reqId": "REQ-011",
+  "prdId": "PRD-001",
+  "title": "e2e verification contract: pinned Playwright MCP, declared e2e test level, doctor and init behaviour",
+  "description": "The rcf-lite verify pass provisions a version-pinned Playwright MCP server instead of @latest, prints the effective pin in preflight, and honours an emergency override. The rcf method exposes e2e as a declared test level: the application-spa blueprint declares a browserSurface, contributes browser-facing acceptance criteria, and cross-links a test-case template to the browser-verify TAC; the delivery-ci-workflows blueprint materialises a distinct e2e CI job when an applied blueprint declares a browserSurface. rcf doctor gains playwright-present, browser-present, playwright-mcp-reachable, and playwright-mcp-redundant checks for browser-facing projects; non-browser projects skip the three with one reason line. rcf init writes a Playwright MCP entry only when a project-scope signature is absent and a user-scope harness probe cannot prove one exists; otherwise it leaves the wiring alone or writes the distinctly named playwright-rcf fallback. All four parts observe the ratified 2026-09-03 e2e contract at projects/rcf-lite-wsd/specs/rcf-lite-e2e-contract-spec-2026-09-03.md.",
+  "category": "functional",
+  "domain": "verify",
+  "priority": "must",
+  "rationale": "Verify is the ship gate. A silent runtime change in the browser MCP on the next verify run is the reproducibility hole Baz named on 2026-09-03. Pinning the MCP closes it. Formalising e2e as a declared test level gives browser-facing projects a first-class contract instead of relying on the verify browser stage as a proxy for coverage. Doctor and init together make Playwright the operator's decision, not rcf-lite's ambient inheritance.",
+  "tags": [
+    "verify",
+    "playwright-mcp",
+    "e2e",
+    "blueprint-library",
+    "doctor",
+    "init"
+  ],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-09-03T16:56:00Z",
+  "updatedAt": "2026-09-03T16:56:00Z"
+}

package/rcf/requirements/req-012.json

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

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

@@ -0,0 +1,66 @@
+{
+  "id": "TS-030",
+  "usId": "US-1101",
+  "title": "Verify pins the Playwright MCP version, prints it in preflight, honours the override",
+  "purpose": "Cover the four ACs on US-1101: the pinned constant + composed default MCP config, the preflight stderr line, the override notice + non-semver refusal, and the default pin lands on the report as runStats.playwrightMcpVersion.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-1101-1",
+    "AC-1101-2",
+    "AC-1101-3",
+    "AC-1101-4"
+  ],
+  "testCases": [
+    {
+      "id": "TC-030-pin-constant-exported",
+      "acId": "AC-1101-1",
+      "description": "PLAYWRIGHT_MCP_VERSION is exported as a semver string, not @latest",
+      "testPointer": "test/verify/engine/launcher.test.js::PLAYWRIGHT_MCP_VERSION is exported as a semver string and is NOT @latest",
+      "status": "pending",
+      "scope": "library"
+    },
+    {
+      "id": "TC-030-default-config-uses-pin",
+      "acId": "AC-1101-1",
+      "description": "DEFAULT_MCP_CONFIG.args composes @playwright/mcp with the pinned version and never @latest",
+      "testPointer": "test/verify/engine/launcher.test.js::DEFAULT_MCP_CONFIG composes @playwright/mcp with the pinned version (never @latest)",
+      "status": "pending",
+      "scope": "library"
+    },
+    {
+      "id": "TC-030-preflight-line",
+      "acId": "AC-1101-2",
+      "description": "rcf verify run prints one preflight line naming the effective @playwright/mcp pin on stderr",
+      "testPointer": "test/verify/cli/run.test.js::run: preflight prints the pinned Playwright MCP version to stderr",
+      "status": "pending",
+      "scope": "runtime"
+    },
+    {
+      "id": "TC-030-override-notice",
+      "acId": "AC-1101-3",
+      "description": "--playwright-mcp-version fires the loud stderr override notice and records the effective pin on the report",
+      "testPointer": "test/verify/cli/run.test.js::run: --playwright-mcp-version fires the loud override notice AND lands on the report",
+      "status": "pending",
+      "scope": "runtime"
+    },
+    {
+      "id": "TC-030-override-non-semver-refused",
+      "acId": "AC-1101-3",
+      "description": "--playwright-mcp-version with a non-semver value refuses exit 2 with the spec-named message",
+      "testPointer": "test/verify/cli/run.test.js::run: --playwright-mcp-version with a non-semver value refuses exit 2 with the spec-named message",
+      "status": "pending",
+      "scope": "runtime"
+    },
+    {
+      "id": "TC-030-default-pin-on-report",
+      "acId": "AC-1101-4",
+      "description": "Even with no override the report records the default pin as runStats.playwrightMcpVersion",
+      "testPointer": "test/verify/cli/run.test.js::run: default pin lands on the report as runStats.playwrightMcpVersion even with no override",
+      "status": "pending",
+      "scope": "runtime"
+    }
+  ],
+  "status": "draft",
+  "createdAt": "2026-09-03T18:30:50Z",
+  "updatedAt": "2026-09-03T18:30:50Z"
+}

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

@@ -0,0 +1,59 @@
+{
+  "id": "TS-031",
+  "usId": "US-1102",
+  "title": "application-spa v1.4.0 declares browserSurface, delivery-ci-workflows v2.2.0 documents the e2e job",
+  "purpose": "Cover the five ACs on US-1102: SPA blueprint at 1.4.0 with browserSurface.declared, the two new e2e user stories plus the e2e.md template, delivery-ci-workflows v2.2.0 US-6124 binding the four e2e-job points, the illustrative GHA workflow + per-provider notes, and the applied manifest validating with no browserSurface on the applied record.",
+  "testLevel": "contract",
+  "acIds": [
+    "AC-1102-1",
+    "AC-1102-2",
+    "AC-1102-3",
+    "AC-1102-4",
+    "AC-1102-5"
+  ],
+  "testCases": [
+    {
+      "id": "TC-031-spa-version-and-flag",
+      "acId": "AC-1102-1",
+      "description": "SPA blueprint.json is at version 1.4.0 and browserSurface.declared is true",
+      "testPointer": "test/blueprint/apply-spa-v1-4-0-schema.test.js::AC-1102-5: apply application-spa v1.4.0 -> manifest still validates + no browserSurface on the applied record",
+      "status": "pending",
+      "scope": "library"
+    },
+    {
+      "id": "TC-031-spa-us-and-template",
+      "acId": "AC-1102-2",
+      "description": "SPA contributes US-1134 and US-1135 as browser-facing e2e stories, and ships assets/tc-templates/e2e.md naming the browser-verify driver seam",
+      "testPointer": "test/blueprint/e2e-contract-blueprint-facts.test.js::AC-1102-2: application-spa ships US-1134 and US-1135 as browser-facing (scope: deployed) e2e stories, plus the e2e.md template",
+      "status": "pending",
+      "scope": "library"
+    },
+    {
+      "id": "TC-031-ci-us-6124",
+      "acId": "AC-1102-3",
+      "description": "delivery-ci-workflows v2.2.0 contributes US-6124 whose AC-6124-1 names the four e2e-job points",
+      "testPointer": "test/blueprint/e2e-contract-blueprint-facts.test.js::AC-1102-3: delivery-ci-workflows v2.2.0 US-6124 binds an AC naming the four e2e-job points",
+      "status": "pending",
+      "scope": "library"
+    },
+    {
+      "id": "TC-031-illustrative-workflow-and-notes",
+      "acId": "AC-1102-4",
+      "description": "Illustrative GHA pull-request-checks.yml carries the e2e job block and notes.md translates it per provider",
+      "testPointer": "test/blueprint/e2e-contract-blueprint-facts.test.js::AC-1102-4: illustrative GHA pull-request-checks.yml carries the e2e job and notes.md translates the four points per provider",
+      "status": "pending",
+      "scope": "library"
+    },
+    {
+      "id": "TC-031-manifest-validates",
+      "acId": "AC-1102-5",
+      "description": "Applying SPA v1.4.0 produces a manifest that still validates against rcf-schemas 0.5.1 and the applied record carries no browserSurface field",
+      "testPointer": "test/blueprint/apply-spa-v1-4-0-schema.test.js::AC-1102-5: apply application-spa v1.4.0 -> manifest still validates + no browserSurface on the applied record",
+      "status": "pending",
+      "scope": "runtime"
+    }
+  ],
+  "status": "draft",
+  "createdAt": "2026-09-03T18:30:50Z",
+  "updatedAt": "2026-09-03T18:30:50Z"
+}

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

@@ -0,0 +1,50 @@
+{
+  "id": "TS-032",
+  "usId": "US-1103",
+  "title": "rcf doctor Playwright + browser checks on browser-facing projects",
+  "purpose": "Cover the four ACs on US-1103: peer-dependency declaration for @playwright/mcp and playwright as optional peers, the three doctor checks reporting fix lines on a browser-facing project, the skip line on an API-only project, and the --check override running one of the three checks on demand.",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-1103-1",
+    "AC-1103-2",
+    "AC-1103-3",
+    "AC-1103-4"
+  ],
+  "testCases": [
+    {
+      "id": "TC-032-peer-deps-optional",
+      "acId": "AC-1103-1",
+      "description": "packages/rcf-lite/package.json declares @playwright/mcp and playwright as optional peer dependencies",
+      "testPointer": "test/pkg/peer-deps-playwright.test.js::AC-1103-1: @playwright/mcp and playwright are declared as optional peer dependencies",
+      "status": "pending",
+      "scope": "library"
+    },
+    {
+      "id": "TC-032-fix-lines",
+      "acId": "AC-1103-2",
+      "description": "A browser-facing project with the three items missing reports all three fix lines exactly per the spec",
+      "testPointer": "test/cli/doctor-playwright.test.js::doctor: browser-facing project with everything missing reports all three fix lines",
+      "status": "pending",
+      "scope": "runtime"
+    },
+    {
+      "id": "TC-032-skip-line",
+      "acId": "AC-1103-3",
+      "description": "An API-only project prints the skip line and does not run the three checks",
+      "testPointer": "test/cli/doctor-playwright.test.js::doctor: API-only project prints the skip line and does NOT run the three checks",
+      "status": "pending",
+      "scope": "runtime"
+    },
+    {
+      "id": "TC-032-check-override",
+      "acId": "AC-1103-4",
+      "description": "--check playwright-present on an API-only project overrides the skip and runs the check",
+      "testPointer": "test/cli/doctor-playwright.test.js::doctor --check playwright-present on an API-only project runs the check anyway (spec 3.5)",
+      "status": "pending",
+      "scope": "runtime"
+    }
+  ],
+  "status": "draft",
+  "createdAt": "2026-09-03T18:30:50Z",
+  "updatedAt": "2026-09-03T18:30:50Z"
+}

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

@@ -0,0 +1,83 @@
+{
+  "id": "TS-033",
+  "usId": "US-1104",
+  "title": "rcf init Playwright MCP entry write only when no scope-visible entry exists",
+  "purpose": "Cover the five ACs on US-1104: signature-based project-scope detection leaves a pre-existing entry alone, the injected probe drives the four downstream branches (none/found/inconclusive/CLI-absent), the distinct 'playwright-rcf' entry has the exact shape, --no-playwright-mcp suppresses the write, and doctor's redundant-entry probe fires only on browser-facing projects.",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-1104-1",
+    "AC-1104-2",
+    "AC-1104-3",
+    "AC-1104-4",
+    "AC-1104-5"
+  ],
+  "testCases": [
+    {
+      "id": "TC-033-project-scope-signature-left-alone",
+      "acId": "AC-1104-1",
+      "description": "A pre-existing project-scope Playwright signature leaves .mcp.json untouched and prints the 'left alone' line",
+      "testPointer": "test/cli/init-playwright.test.js::init: existing project-scope Playwright signature -> left alone (spec 4.1)",
+      "status": "pending",
+      "scope": "runtime"
+    },
+    {
+      "id": "TC-033-probe-none-writes-distinct",
+      "acId": "AC-1104-2",
+      "description": "Probe returning 'none' drives the distinct playwright-rcf project-scope write branch",
+      "testPointer": "test/cli/init-playwright.test.js::init: fresh project + probe=none -> writes distinctly named playwright-rcf entry",
+      "status": "pending",
+      "scope": "library"
+    },
+    {
+      "id": "TC-033-probe-found-leaves-alone",
+      "acId": "AC-1104-2",
+      "description": "Probe returning 'found' at user scope leaves .mcp.json alone with the 'already registered ... in Claude Code' line",
+      "testPointer": "test/cli/init-playwright.test.js::init: probe=found at user scope -> left alone; no project entry written (spec 4.2)",
+      "status": "pending",
+      "scope": "library"
+    },
+    {
+      "id": "TC-033-probe-inconclusive-writes-with-notice",
+      "acId": "AC-1104-2",
+      "description": "Probe returning 'inconclusive' writes the distinct entry and prints the could-not-probe notice (covers both CLI-absent and unparseable branches via the injected probe result)",
+      "testPointer": "test/cli/init-playwright.test.js::init: probe=inconclusive -> writes playwright-rcf entry AND prints the could-not-probe notice (spec 4.3)",
+      "status": "pending",
+      "scope": "library"
+    },
+    {
+      "id": "TC-033-distinct-entry-shape",
+      "acId": "AC-1104-3",
+      "description": "The written playwright-rcf entry equals { type:'stdio', command:'npx', args:['-y', '@playwright/mcp@<version>'], env:{} }",
+      "testPointer": "test/cli/init-playwright.test.js::init: fresh project + probe=none -> writes distinctly named playwright-rcf entry",
+      "status": "pending",
+      "scope": "runtime"
+    },
+    {
+      "id": "TC-033-no-playwright-mcp-suppresses-write",
+      "acId": "AC-1104-4",
+      "description": "--no-playwright-mcp suppresses the write; the probe still runs but no Playwright entry is created",
+      "testPointer": "test/cli/init-playwright.test.js::init --no-playwright-mcp: probe still runs, but no Playwright entry is written",
+      "status": "pending",
+      "scope": "runtime"
+    },
+    {
+      "id": "TC-033-redundant-fires-browser-facing",
+      "acId": "AC-1104-5",
+      "description": "playwright-mcp-redundant fires when project + user both declare Playwright on a browser-facing project",
+      "testPointer": "test/cli/doctor-playwright.test.js::doctor: playwright-mcp-redundant fires when project + user both declare Playwright (browser-facing only)",
+      "status": "pending",
+      "scope": "runtime"
+    },
+    {
+      "id": "TC-033-redundant-quiet-on-api-only",
+      "acId": "AC-1104-5",
+      "description": "playwright-mcp-redundant does NOT fire on an API-only project",
+      "testPointer": "test/cli/doctor-playwright.test.js::doctor: playwright-mcp-redundant does NOT fire on an API-only project (spec 4.5)",
+      "status": "pending",
+      "scope": "runtime"
+    }
+  ],
+  "status": "draft",
+  "createdAt": "2026-09-03T18:30:50Z",
+  "updatedAt": "2026-09-03T18:30:50Z"
+}

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

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