rcf-lite 0.31.0 → 0.32.1

package/CHANGELOG.md

@@ -6,6 +6,37 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 
 ## [Unreleased]
 
+## [0.32.1] - 2026-10-06
+
+0.32.1 ships two fixes merged since 0.32.0 (merge b6292f5) on top of the layout baseline chore. The viewer's Readiness tab now agrees with the CLI on D3 shapes:pathsResolve, and the D5 crosscut:operationalConcerns trigger reads the structured ac.scope field in addition to the legacy "[deployed]" marker. breaking: false; no behavioural changes on verbs consumers run in CI; fixes only. minAgentAction: null; the managed agent-instructions block hash did not move.
+
+### Fixed
+
+- **Viewer Readiness tab D3 shapes:pathsResolve now agrees with the CLI (issue 307, w-2026-10-06-dave-026).** The viewer's render path (`src/view/index.js` `renderModelToPage`) called `computeReadiness` without the `resolvedPaths` pre-walk, so D3 shapes:pathsResolve false-failed on TAC interface `path:` tokens that resolve on disk and the Readiness tab disagreed with the CLI and freeze. Hit on ai-baseline define/kickoff: CLI reported D3 4/4 passing while the viewer tab showed D3 shapes:pathsResolve failing on four TAC interface paths. Fix: thread `resolvedPaths` through the viewer compute via the same `resolveInterfacePaths` seam the CLI (PR 304, issue 302) and freeze use. The viewer compute now runs the resolve walk against `projectRoot` before `computeReadiness` and passes the resulting `resolvedPaths` set to the compute. The pure gate reads it unchanged. Additive: `renderModelToPage` also returns the computed readiness so a regression test can assert the viewer's check state without parsing HTML. Regression test in `test/view/readiness-paths-resolve-307.test.js` seeds a TAC interface whose `path:` token points at a real file and asserts the viewer compute reports D3 ok; the negative control flips the path to a missing file and asserts D3 fails with the shapes:pathsResolve finding.
+
+- **D5 crosscut:operationalConcerns trigger reads structured `ac.scope` (issue 306, w-2026-10-06-dave-031).** `computeOperationalConcernsCheck` in `src/query/gates.js` looked only for a literal `[deployed]` marker in AC description text, so trees that carry scope as the schema-canonical field `scope: "deployed"` (like ai-baseline, with 23 deployed-scope ACs and `TAD.operationalConcerns` absent) silently passed 0/0 and the gate never fired. Fix: the trigger now also reads `ac.scope === "deployed"`; a deployed-scope AC on either form must find a non-empty `TAD.operationalConcerns`. Legacy `[deployed]` markers are unchanged. Regression fixtures in `test/query/gates.test.js` cover the ai-baseline shape (structured `ac.scope` with empty `operationalConcerns` fails) and a negative control (non-deployed-scope ACs with empty `operationalConcerns` pass).
+
+## [0.32.0] - 2026-10-06
+
+0.32.0 ships four readiness and viewer fixes merged since 0.31.0 (merge ec9464db) as one release. D6 consistency:orphanInterfaces now accepts the schema-canonical object-shape REQ.deliveredBy (issue 301), D3 shapes:pathsResolve inside rcf define freeze pre-resolves TAC interface path tokens the way readiness does (issue 302), the deploy-cloudflare-workers blueprint reworded AC-12113-2 so D6 consistency:unsatisfiable stops reading "absent" as a field name (PR 300), the viewer's SSE tree-update resync preserves the active tab for every main tab including Readiness (issue 297), and the audit view header keeps the tabs visible under long project names and prefers prd.productName (issue 295). minAgentAction: null; the managed agent-instructions block hash did not move.
+
+
+### Fixed
+
+- **D6 consistency:orphanInterfaces now accepts the schema-canonical object-shape REQ.deliveredBy (issue 301, w-2026-10-06-dave-020).** `collectReachedInterfaces` in `src/query/gates.js` previously accepted only array-shape `deliveredBy` and dropped the `{tacId, adrId?, field?}` object form that `@stravica-ai/rcf-schemas` 0.6.3 defines as canonical. Every schema-conforming REQ (including every blueprint-contributed REQ) therefore had its `deliveredBy` silently skipped by the orphanInterfaces reach-walk, and interfaces on blueprint TACs with no AC ownerRef read as orphans. Hit on ai-baseline define/kickoff (115/173 failing on nine applied blueprints). Fix: the walk now also handles the object form, routing `field: interfaces[<name>]` to a single interface via `parseOwnerRefInterfaceField` and a bare `tacId` to every interface on the named TAC (the "delivered by this TAC" meaning carried over from the array-shape bare pointer). Legacy array-shape pointers are unchanged. Regression fixtures in `test/query/gates.test.js` cover the object-shape interface pointer, the bare-tacId object form, and the legacy array shape.
+
+- **D3 shapes:pathsResolve inside `rcf define freeze` now pre-resolves TAC interface `path:` tokens the way `rcf define readiness` does (issue 302, w-2026-10-06-dave-022).** `src/cli/freeze.js` called `computeReadiness` without `resolvedPaths`, so the D3 gate fell back to an empty set and false-failed every repo-relative `path:` token the engineer named on a TAC interface description, even when the file existed on disk and the readiness CLI (which pre-resolves via `resolveInterfacePaths` in `src/cli/readiness.js`) passed D3 4/4. Hit on ai-baseline define/kickoff: readiness green on D3, freeze refused with four shapes:pathsResolve findings. Fix: lifted `resolveInterfacePaths` out of `src/cli/readiness.js` into `src/define/interface-paths.js` so freeze can share it. Freeze now runs the resolve walk against `projectRoot` before `computeReadiness` and passes the resulting `resolvedPaths` set to the compute. The pure gate reads it unchanged. Regression test in `test/cli/freeze.test.js` seeds a TAC interface whose `path:` token points at a real file and asserts freeze succeeds, then flips to a missing path and asserts freeze refuses with exit 4 and surfaces the shapes:pathsResolve finding.
+
+- **Blueprint deploy-cloudflare-workers: AC-12113-2 reworded so D6 consistency:unsatisfiable stops reading "absent" as a field name.** The description parenthetical "Cloudflare's runtime treats the absent field as the default asset-lookup-first shape" tripped extractThenFieldTokens pattern 2 (`<name> field`) which captured "absent" and no recordShape defines that field. Reworded to "treats a missing run_worker_first as the default asset-lookup-first shape"; meaning preserved, the field reference now names the real WranglerAssetsBlock field. Hit on ai-baseline define/kickoff.
+
+- **Viewer: SSE tree-update preserves the active tab for every main tab, Readiness included (issue 297, w-2026-10-06-dave-003).** `resyncTabsAfterSwap` in `src/view/live-client.js` hard-coded a five-entry TABS array (`overview`, `requirements`, `architecture`, `build`, `product-map`) that omitted `readiness`. When Readiness was the active tab and an SSE tree-update swapped `#rcf-live-content` innerHTML (which happens about every 30s since issue 236 writes a heartbeat into `rcf/manifest.json`), the resync `indexOf` returned -1, fell back to Overview, unhid `#tab-overview` and never visited `#tab-readiness`, so both panels were visible. The viewer's standalone context still recovered a tick later when `rcfPage.init()` re-resolved the hash, but WESPA's admin SPA embed (`iframe /rcf-viewer/?embed=1&theme=...`, no hash) saw the Readiness tab silently switch to Overview. The parallel array was removed: the tab list is now derived from the server-rendered `nav.tabs` itself (every `[role="tab"][data-tab]` present at swap time) so a future tab added to the renderer cannot be forgotten by live-client. The overview fallback stays for a genuinely unknown or missing selection. AC-18001-8, CN-778. Issue 236 (heartbeat into git-tracked manifest.json) is unchanged.
+- **Chain: live-client resync responsibility named on TAC-4127-readiness-view.** The TAC previously named `src/view/html-page.js` (now `src/view/page-init.js`) as the owner of the viewer-side tab list but did not name the live-client's post-swap resync. Added a responsibility bullet so a future reader finds both ends of the chain from one node. The TAC's substantive behaviour is unchanged.
+- **Audit view header: tabs always visible under long project names (issue 295).** Dex (WSD) reported on the WESPA project (`manifest.projectName` = `WESPA - WSD Enterprise Semantic Platform for Analytics`, 54 chars) that the sixth main tab (Build) was clipped at 1440 and 1920 and the Find button in `.tools` sat on top of it. The .bar is `max-width: 1280px` with flex children `.brand`, `.product`, `[role=tablist]`, `.tools`; the pre-fix tablist carried `flex: 1 1 auto; min-width: 0; overflow-x: auto` so it was free to shrink below its intrinsic width while `.product` did not yield. The fix moves the shrink budget onto `.product` (via `min-width: 0` on both the flex item and on `.product .name`, so `text-overflow: ellipsis` triggers inside the flex container) and pins `nav.tabs` and `.tools` to `flex-shrink: 0` so the six tabs and the tools group hold their intrinsic widths. `.product .name` now also carries `title="<full projectName>"` so the ellipsis is reversible on hover; the attribute is HTML-escaped on the same path as the inner text. The fix holds in embed and non-embed, light and dark, with the 0.31.0 theme control present. `src/view/style.css`, `src/view/html-page.js`; US-202 gains AC-202-4 (layout rules) and AC-202-5 (title attribute); TS-004 gains the matching passing TCs; CN-017 and CN-771 updated to implement the new ACs; FBS-004 `acIds` updated.
+
+### Changed
+
+- **Audit view header: project display name prefers `prd.productName` (issue 295).** Pre-fix the header read `manifest.projectName`, then fell back to `prd.productName` and `prd.productTitle`. `rcf define update MANIFEST` is not addressable (the manifest has no id in the family grammar), so `manifest.projectName` was a one-shot init value and the only way to rename the audit chrome without re-initialising was a hand edit of `manifest.json`. `prd.productName` is editable via `rcf define update PRD-001 --set productName=<value>`; preferring it in the header makes the display name lite-native without touching the manifest, which keeps owning ids and paths. `src/view/html-page.js` `resolveProductHeader`; US-202 gains AC-202-6; TS-004 gains the matching passing TCs; CN-017 updated. Follow-up for Dave: a lite-native `rcf define update MANIFEST --set projectName=<value>` (Part 2 cut a from the brief) is a separate, larger change (manifest is not a family id; the update verb would grow a MANIFEST special-case alongside the one `rcf define read` already carries) and is NOT shipped here.
+
 ## [0.31.0] - 2026-10-05
 
 0.31.0 ships three themes from rcf-lite PRs 291, 292 and 293. The viewer gains a standalone Light | Dark | Auto theme control (ADR-4137), readable FIND and LookupModal hover and focus states in dark, and a WCAG 2.1 AA contrast audit test that blocks a merge dropping any colour pair below the floor in either theme. DEFINE step 3 rulings R1 to R8 and R13 land, with every tree-wide readiness check evaluated before any scope short-circuit through one shared helper (ADR-4138). And `--id` write-backs are idempotent: `rcf define ledger <name> add --id` and `rcf define create <kind> --id` treat a same-id replay with identical content as a no-op. Breaking under the pre-1.0 convention for three reasons: `rcf define create <kind> --id` and `rcf define ledger <name> add --id` now exit 3 on same-id-different-content; the readiness envelope for a scope-empty stage with a failing tree-wide check is `failing` (or `acknowledged` when acked at the current hash on a warn-with-ack stage), not `notApplicable`; and `shapes:draftSettled` is tree-wide, so a `[draft]` marker outside the D3 scope now fails the check. The managed agent-instructions block did not change, so no agent re-init is needed (minAgentAction null).

package/blueprints/delivery-ci-workflows/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog
 
+## Unreleased
+
+- adds ownerRef on AC-6102-1 (interfaces[entry-point CLI]), AC-6103-1 (interfaces[gate-descriptor]), AC-6108-1 (interfaces[aggregate-report-schema]), AC-6111-1 (interfaces[entry-point CLI]), AC-6111-2 (interfaces[workflow-shape]), AC-6121-2 (interfaces[release-mode]), AC-6122-1 (interfaces[entry-point CLI]) and AC-6123-1 (interfaces[entry-point CLI]) so TAC-701 gate-descriptor and entry-point CLI, TAC-703 aggregate-report-schema, TAC-704 workflow-shape and entry-point CLI, TAC-705 release-mode and entry-point CLI, and TAC-706 entry-point CLI have delivering AC owners (D6 consistency:orphanInterfaces).
+
+
 ## 2.3.5 - 2026-09-11
 
 probe-utils.writeReport no longer promotes an all-accountBoundSkipped row set to PASS via a separate override; aggregate() already returns PASS for a pure-skip set on its own and returns WARN when any WARN row is present, so an all-skipped array carrying a WARN row is no longer silently promoted. Anatomy suite tracks the strengthened shared helper.

package/blueprints/delivery-ci-workflows/contributions/user-stories/delivery-ci-workflows-us-6102.json

@@ -17,7 +17,11 @@
       "then": "the aggregate report's `runner.entryPoint` field records a project-relative path to a `.js` or `.mjs` file that exists at that path in the tree",
       "testable": true,
       "scope": "runtime",
-      "disposition": "fixed"
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-701-delivery-ci-workflows-gate-runner",
+        "field": "interfaces[entry-point CLI]"
+      }
     },
     {
       "id": "AC-6102-2",

package/blueprints/delivery-ci-workflows/contributions/user-stories/delivery-ci-workflows-us-6103.json

@@ -17,7 +17,11 @@
       "then": "the file exists, its `gate` field is `validate`, its `command` field names the `rcf define validate` invocation, its `exitCode` field records the underlying process exit code, and its `stdout` and `stderr` fields carry the captured streams",
       "testable": true,
       "scope": "runtime",
-      "disposition": "template"
+      "disposition": "template",
+      "ownerRef": {
+        "tacId": "TAC-701-delivery-ci-workflows-gate-runner",
+        "field": "interfaces[gate-descriptor]"
+      }
     },
     {
       "id": "AC-6103-2",

package/blueprints/delivery-ci-workflows/contributions/user-stories/delivery-ci-workflows-us-6108.json

@@ -17,7 +17,11 @@
       "then": "the aggregate report's `gates[]` array contains a `coverage-strict` entry with `outcome: missing`, its `reason` field carries a non-empty string, and the aggregate `verdict` is `failed`",
       "testable": true,
       "scope": "runtime",
-      "disposition": "template"
+      "disposition": "template",
+      "ownerRef": {
+        "tacId": "TAC-703-delivery-ci-workflows-aggregate-report",
+        "field": "interfaces[aggregate-report-schema]"
+      }
     },
     {
       "id": "AC-6108-2",

package/blueprints/delivery-ci-workflows/contributions/user-stories/delivery-ci-workflows-us-6111.json

@@ -17,7 +17,11 @@
       "then": "the materialiser reads the file at the documented path and treats its `workflowShape` as authoritative",
       "testable": true,
       "scope": "runtime",
-      "disposition": "template"
+      "disposition": "template",
+      "ownerRef": {
+        "tacId": "TAC-704-delivery-ci-workflows-workflow-materialiser",
+        "field": "interfaces[entry-point CLI]"
+      }
     },
     {
       "id": "AC-6111-2",
@@ -27,7 +31,11 @@
       "then": "the materialiser processes the recognised fields (including the substitution-surface trio) and ignores the unknown fields without failing the boot-check",
       "testable": true,
       "scope": "runtime",
-      "disposition": "template"
+      "disposition": "template",
+      "ownerRef": {
+        "tacId": "TAC-704-delivery-ci-workflows-workflow-materialiser",
+        "field": "interfaces[workflow-shape]"
+      }
     },
     {
       "id": "AC-6111-3",

package/blueprints/delivery-ci-workflows/contributions/user-stories/delivery-ci-workflows-us-6121.json

@@ -27,7 +27,11 @@
       "then": "the release workflow creates the release entity, runs the artefact-publish step, uploads the published artefact to the release entity, and records the just-published version identifier in the aggregate report",
       "testable": true,
       "scope": "runtime",
-      "disposition": "template"
+      "disposition": "template",
+      "ownerRef": {
+        "tacId": "TAC-705-delivery-ci-workflows-release-workflow",
+        "field": "interfaces[release-mode]"
+      }
     },
     {
       "id": "AC-6121-3",

package/blueprints/delivery-ci-workflows/contributions/user-stories/delivery-ci-workflows-us-6122.json

@@ -17,7 +17,11 @@
       "then": "the release workflow dispatches the promote workflow with `versionId` set to the just-published version identifier and waits on the promote workflow's outcome",
       "testable": true,
       "scope": "runtime",
-      "disposition": "template"
+      "disposition": "template",
+      "ownerRef": {
+        "tacId": "TAC-705-delivery-ci-workflows-release-workflow",
+        "field": "interfaces[entry-point CLI]"
+      }
     },
     {
       "id": "AC-6122-2",

package/blueprints/delivery-ci-workflows/contributions/user-stories/delivery-ci-workflows-us-6123.json

@@ -17,7 +17,11 @@
       "then": "a `scheduled-audit` workflow file lands at the provider's workflow path, its trigger set names a cron schedule, and its command line invokes the Node gate-runner entry point with the required check set writing to the distinct report path",
       "testable": true,
       "scope": "runtime",
-      "disposition": "template"
+      "disposition": "template",
+      "ownerRef": {
+        "tacId": "TAC-706-delivery-ci-workflows-scheduled-audit",
+        "field": "interfaces[entry-point CLI]"
+      }
     },
     {
       "id": "AC-6123-2",

package/blueprints/deploy-cloudflare-workers/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog
 
+## Unreleased
+
+- adds ownerRef on AC-12103-1 (interfaces[workerIdentity]) and AC-12110-1 (interfaces[probeUrl]) so the preview URL resolver's workerIdentity and probeUrl interfaces have delivering AC owners (D6 consistency:orphanInterfaces).
+
+
 ## 1.3.2 (register patch, 2026-09-10)
 
 - Register: neutral wording on the ADR-1306 consequences field (closes F-1); no capability change.

package/blueprints/deploy-cloudflare-workers/contributions/user-stories/deploy-cloudflare-workers-us-12103.json

@@ -17,7 +17,11 @@
       "then": "both responses carry the `versionSha` field of V's build provenance in the health-probe body, and the two responses agree on that field",
       "testable": true,
       "scope": "deployed",
-      "disposition": "template"
+      "disposition": "template",
+      "ownerRef": {
+        "tacId": "TAC-1303-deploy-cloudflare-workers-preview-url-resolver",
+        "field": "interfaces[workerIdentity]"
+      }
     },
     {
       "id": "AC-12103-2",

package/blueprints/deploy-cloudflare-workers/contributions/user-stories/deploy-cloudflare-workers-us-12110.json

@@ -17,7 +17,11 @@
       "then": "at least one HTTP request to the production URL's `/healthz` completes within the sixty-second window; the request carries no `Authorization` header that would bypass a production auth layer; the retry count for any single probe does not exceed six",
       "testable": true,
       "scope": "deployed",
-      "disposition": "template"
+      "disposition": "template",
+      "ownerRef": {
+        "tacId": "TAC-1303-deploy-cloudflare-workers-preview-url-resolver",
+        "field": "interfaces[probeUrl]"
+      }
     },
     {
       "id": "AC-12110-2",

package/blueprints/deploy-cloudflare-workers/contributions/user-stories/deploy-cloudflare-workers-us-12113.json

@@ -21,7 +21,7 @@
     },
     {
       "id": "AC-12113-2",
-      "description": "Given the operator answers run-worker-first with true alongside a non-empty assets-directory, when the manifest is generated, then the [assets] block carries run_worker_first = true. Given the operator answers run-worker-first with false or leaves it unanswered, when the manifest is generated, then the [assets] block does NOT carry a run_worker_first key (Cloudflare's runtime treats the absent field as the default asset-lookup-first shape). Anchored to TAC-1302; probed by assets-manifest-scan.mjs with anchorAcId AC-12113-1 (the same module surfaces both facets of the shape).",
+      "description": "Given the operator answers run-worker-first with true alongside a non-empty assets-directory, when the manifest is generated, then the [assets] block carries run_worker_first = true. Given the operator answers run-worker-first with false or leaves it unanswered, when the manifest is generated, then the [assets] block does NOT carry a run_worker_first key (Cloudflare's runtime treats a missing run_worker_first as the default asset-lookup-first shape). Anchored to TAC-1302; probed by assets-manifest-scan.mjs with anchorAcId AC-12113-1 (the same module surfaces both facets of the shape).",
       "given": "an applied fixture whose operator answered assets-directory = ./dist and run-worker-first = true",
       "when": "the probe module parses the fixture wrangler.toml",
       "then": "the parsed [assets] table carries run_worker_first equal to true; when the fixture is switched with SIMULATE_EMPTY_ASSETS=true the run_worker_first field is absent (the whole [assets] block is absent) and the probe still returns verdict pass because the bare-Worker shape is legal",

package/blueprints/email-smtp-resend/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog
 
+## Unreleased
+
+- adds ownerRef on AC-4106-1 (interfaces[smtpClient]), AC-4104-2 (interfaces[auditSink]) and AC-4105-1 (interfaces[verifierClock]) so TAC-401 smtpClient and TAC-402 auditSink and verifierClock have delivering AC owners (D6 consistency:orphanInterfaces).
+
+
 ## 1.1.7 - 2026-09-11
 
 unverified-sender-refusal AC-4102-1 and AC-4102-2 rows are de-claimed to conformanceOnly. The refusal is driven by the local catch-all SMTP fixture (fixture-as-engine) and carries no Resend-returned message id, so the identifier half of the strict-evidence contract is not satisfied here. The live real-account-resend-send row (AC-4101-2) is unchanged.

package/blueprints/email-smtp-resend/contributions/user-stories/email-smtp-resend-us-4104.json

@@ -27,7 +27,11 @@
       "then": "the response status is 401, the response body is empty, the handler invocation counter is unchanged, and the audit sink observes exactly one `webhookVerificationFailed` event",
       "testable": true,
       "scope": "runtime",
-      "disposition": "fixed"
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-402-email-smtp-resend-webhook-verifier",
+        "field": "interfaces[auditSink]"
+      }
     },
     {
       "id": "AC-4104-3",

package/blueprints/email-smtp-resend/contributions/user-stories/email-smtp-resend-us-4105.json

@@ -17,7 +17,11 @@
       "then": "the response status is 401, the response body is empty, the handler invocation counter is unchanged, and the audit sink observes exactly one `webhookReplayStale` event",
       "testable": true,
       "scope": "runtime",
-      "disposition": "template"
+      "disposition": "template",
+      "ownerRef": {
+        "tacId": "TAC-402-email-smtp-resend-webhook-verifier",
+        "field": "interfaces[verifierClock]"
+      }
     },
     {
       "id": "AC-4105-2",

package/blueprints/email-smtp-resend/contributions/user-stories/email-smtp-resend-us-4106.json

@@ -17,7 +17,11 @@
       "then": "the scan returns exactly one module and that module is the adapter module",
       "testable": true,
       "scope": "runtime",
-      "disposition": "fixed"
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-401-email-smtp-resend-send-adapter",
+        "field": "interfaces[smtpClient]"
+      }
     },
     {
       "id": "AC-4106-2",

package/blueprints/observability-probe-endpoints/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog
 
+## Unreleased
+
+- adds ownerRef on AC-14104-1 (interfaces[listenerFactory]) so the listener-topology's listenerFactory interface has a delivering AC owner (D6 consistency:orphanInterfaces).
+
+
 ## 1.2.5 - 2026-09-11
 
 Anatomy suite tracks the strengthened shared helper (WARN-only shortcut removed, log objects and content lists no longer identifiers, retained anchor existence check). No probe changes required.

package/blueprints/observability-probe-endpoints/contributions/user-stories/observability-probe-endpoints-us-14104.json

@@ -17,7 +17,11 @@
       "then": "a GET against `/live` on port 9091 returns 200, a GET against `/live` on the user-traffic port returns 404 (or the project's default not-found response), and a GET against `/ready` on the user-traffic port returns 404",
       "testable": true,
       "scope": "runtime",
-      "disposition": "template"
+      "disposition": "template",
+      "ownerRef": {
+        "tacId": "TAC-1503-observability-probe-endpoints-listener-topology",
+        "field": "interfaces[listenerFactory]"
+      }
     },
     {
       "id": "AC-14104-2",

package/fixtures/canary-manifest.json

@@ -1,9 +1,9 @@
 {
   "registerCanary": [
     {
-      "id": "rc-2026-10-05-001",
-      "createdAt": "2026-10-05T15:28:27.972Z",
-      "buildVersion": "0.31.0-mockdriver",
+      "id": "rc-2026-10-06-001",
+      "createdAt": "2026-10-06T18:28:43.472Z",
+      "buildVersion": "0.32.1-mockdriver",
       "fixturePromptId": "canary-prompt-01",
       "responseWordCount": 55,
       "grades": {
@@ -34,9 +34,9 @@
       "shipDespiteFailReason": "mock canary driver used; no real subagent was dispatched. This record verifies canary infrastructure only, not the register itself."
     },
     {
-      "id": "rc-2026-10-05-002",
-      "createdAt": "2026-10-05T15:28:27.972Z",
-      "buildVersion": "0.31.0-mockdriver",
+      "id": "rc-2026-10-06-002",
+      "createdAt": "2026-10-06T18:28:43.473Z",
+      "buildVersion": "0.32.1-mockdriver",
       "fixturePromptId": "canary-prompt-02",
       "responseWordCount": 55,
       "grades": {
@@ -67,9 +67,9 @@
       "shipDespiteFailReason": "mock canary driver used; no real subagent was dispatched. This record verifies canary infrastructure only, not the register itself."
     },
     {
-      "id": "rc-2026-10-05-003",
-      "createdAt": "2026-10-05T15:28:27.972Z",
-      "buildVersion": "0.31.0-mockdriver",
+      "id": "rc-2026-10-06-003",
+      "createdAt": "2026-10-06T18:28:43.473Z",
+      "buildVersion": "0.32.1-mockdriver",
       "fixturePromptId": "canary-prompt-03",
       "responseWordCount": 55,
       "grades": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "rcf-lite",
-  "version": "0.31.0",
+  "version": "0.32.1",
   "type": "module",
   "description": "One-install tooling for the Requirements Confidence Framework (RCF): the unified `rcf` CLI grouped into the five RCF tool groups (discover, define, build, verify, audit) plus a small core set (init, doctor, guidance, mcp), an MCP server, the live tree viewer and the fresh-context adversarial ship-gate verifier. Consumes @stravica-ai/rcf-schemas.",
   "license": "Apache-2.0",

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

@@ -6,11 +6,13 @@
   "implementsAcIds": [
     "AC-202-1",
     "AC-202-2",
-    "AC-202-3"
+    "AC-202-3",
+    "AC-202-5",
+    "AC-202-6"
   ],
   "dependencies": [],
   "version": "0.1.0",
   "status": "draft",
   "createdAt": "2026-07-10T11:15:32.956Z",
-  "updatedAt": "2026-07-10T11:15:32.956Z"
+  "updatedAt": "2026-10-06T10:24:19.149Z"
 }

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

@@ -4,11 +4,12 @@
   "title": "SearchButton hover/focus/active + three-state theme control styling (AA contrast in both themes)",
   "description": "Baz 2026-10-04 (w-2026-10-04-dave-001): the FIND SearchButton hover previously fell back to a hard-coded light grey (`var(--sv-surface-hover, #f0f3f8)`) because `--sv-surface-hover` was never declared, which painted dark ink on a light grey in dark mode. The hover + focus-visible + active states now use `--sv-active` with the `--sv-control` border and the `--sv-focus` outline so the pair stays above WCAG AA in both themes (AC-205-9). The three-state theme control (`.rcf-theme`, `.rcf-theme-btn`) sits right of the SearchButton in `.tools`; `aria-pressed=\"true\"` uses `--sv-button` / `--sv-onbutton`, hover and focus-visible use `--sv-active`, and the group is hidden under `html[data-embed=\"1\"]`.",
   "implementsAcIds": [
+    "AC-202-4",
     "AC-205-9"
   ],
   "dependencies": [],
   "version": "0.1.0",
   "status": "draft",
   "createdAt": "2026-10-05T09:59:33Z",
-  "updatedAt": "2026-10-05T09:59:33Z"
+  "updatedAt": "2026-10-06T10:24:19.675Z"
 }

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

@@ -0,0 +1,14 @@
+{
+  "cnId": "CN-778",
+  "path": "src/view/live-client.js#resyncTabsAfterSwap",
+  "title": "SSE tree-update tab resync derives the tab list from the rendered nav.tabs (SSOT)",
+  "description": "After the SSE tree-update swaps `#rcf-live-content` innerHTML, the newly-inserted panels carry the Phase 3.6 server-rendered default (one visible, the rest hidden). resyncTabsAfterSwap reads every [role=\"tab\"][data-tab] under the surviving `nav.tabs`, finds the aria-selected button, and aligns `#tab-<name>` visibility so exactly the active tab is visible. The tab list is derived from the DOM rather than a parallel array in this file: before issue 297 the parallel array omitted 'readiness' and a swap while Readiness was active fell back to Overview with both panels visible. The overview fallback is kept only for a genuinely unknown or missing selection. Pairs with CN-744 and CN-745 (which this file also hosts) and with page-init.js's activateTab for the non-swap routing path (AC-18001-8).",
+  "implementsAcIds": [
+    "AC-18001-8"
+  ],
+  "dependencies": [],
+  "version": "0.1.0",
+  "status": "draft",
+  "createdAt": "2026-10-06T12:00:00Z",
+  "updatedAt": "2026-10-06T12:00:00Z"
+}

package/rcf/fbs/fbs-004.json

@@ -9,6 +9,9 @@
     "AC-202-1",
     "AC-202-2",
     "AC-202-3",
+    "AC-202-4",
+    "AC-202-5",
+    "AC-202-6",
     "AC-203-1",
     "AC-203-2"
   ],
@@ -30,7 +33,7 @@
   "domain": "view",
   "notes": "The page is generated fresh each run; no cached prior state lingers between regenerations.",
   "createdAt": "2026-06-25T00:00:00Z",
-  "updatedAt": "2026-07-02T10:22:43Z",
+  "updatedAt": "2026-10-06T10:24:20.204Z",
   "buildOrder": 4,
   "executionStatus": "complete",
   "dependsOnFbsIds": [

package/rcf/fbs/fbs-201.json

@@ -1,6 +1,6 @@
 {
   "createdAt": "2026-10-01T18:00:00Z",
-  "updatedAt": "2026-10-01T18:00:00Z",
+  "updatedAt": "2026-10-06T12:00:00Z",
   "acIds": [
     "AC-18001-1",
     "AC-18001-2",
@@ -9,6 +9,7 @@
     "AC-18001-5",
     "AC-18001-6",
     "AC-18001-7",
+    "AC-18001-8",
     "AC-18101-1",
     "AC-18101-2",
     "AC-18101-3"

package/rcf/tacs/tac-4127-readiness-view.json

@@ -1,6 +1,6 @@
 {
   "createdAt": "2026-10-01T18:00:00Z",
-  "updatedAt": "2026-10-01T18:00:00Z",
+  "updatedAt": "2026-10-06T12:00:00Z",
   "tacId": "TAC-4127-readiness-view",
   "prdId": "PRD-001",
   "tadId": "TAD-001",
@@ -15,7 +15,8 @@
     "src/view/components/findings-list.js: findingsList({ heading, count, items }) returns `<div class=\"rcf-findings-list\"><h4>{heading} <span class=\"rcf-findings-list__count\">{count}</span></h4><ul>...<li><a href={anchor}>{id}</a>: {why}</li>...</ul></div>` with ids capped at 20 and a `... N more suppressed` line beyond.",
     "src/view/components/diff.js: diff(before, after) returns a two-column rendering of two document bodies for the delta list; criterion-level before-and-after is deferred per ADR-4127.",
     "src/view/html-page.js: Readiness button and tabpanel are the first entries; the former Overview button and panel are relabelled PRD; the data-tab=overview and id=tab-overview identifiers are preserved so existing hash anchors still resolve; the inline-script TABS array gains 'readiness' as the first entry (default active tab) and keeps the existing four entries in order.",
-    "src/view/index.js: renderModelToPage loads the freeze record, ledgers, test pointers and profile text once, invokes computeReadiness via the pure src/query/ seam, and threads the result into the model so renderPage and renderContent carry one computed object; the SSE tree-update broadcast rewalks and recomputes on every change under rcf/."
+    "src/view/index.js: renderModelToPage loads the freeze record, ledgers, test pointers and profile text once, invokes computeReadiness via the pure src/query/ seam, and threads the result into the model so renderPage and renderContent carry one computed object; the SSE tree-update broadcast rewalks and recomputes on every change under rcf/.",
+    "src/view/live-client.js: resyncTabsAfterSwap derives the list of tabs from the server-rendered nav.tabs (every [role=tab][data-tab] under it) rather than carrying a parallel array. The SSE swap re-emits every panel with the Phase 3.6 hidden-by-default layout; the resync reads the aria-selected button from the surviving header and makes exactly that panel visible for every tab the server rendered, Readiness included (AC-18001-8). The overview fallback stays for the genuinely-unknown-or-missing selection case."
   ],
   "internalStructure": "readiness.js is a sequence of eleven small block builders calling the three shared components; each block consumes exactly one top-level field of the readiness result so a wire-level JSON diff ties to a visible block. The register ordering is picked once at the top via pickRegister (same helper the CLI uses) and threaded down. Hash anchors are built with the same `#<docId>` convention the existing tabs use so blocker-id links open the right tab and expand the right <details> through the existing resolveHash routine.",
   "interfaces": [

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

@@ -1,11 +1,14 @@
 {
   "createdAt": "2026-07-29T12:57:18.038Z",
-  "updatedAt": "2026-07-29T13:35:14.688Z",
+  "updatedAt": "2026-10-06T10:12:36.226Z",
   "purpose": "Verify documents render as readable curated fields with working inter-document links. AC-202-1 is pending: its static-files-no-server clause predates the Phase 3.8 server-only view (see test-suites/PENDING.md).",
   "testLevel": "unit",
   "acIds": [
     "AC-202-2",
-    "AC-202-3"
+    "AC-202-3",
+    "AC-202-4",
+    "AC-202-5",
+    "AC-202-6"
   ],
   "id": "TS-004",
   "usId": "US-202",
@@ -38,6 +41,83 @@
       "description": "the view serves from a local server process and never writes files to disk",
       "status": "pending",
       "testPointer": "test/view/cli.test.js::rcf audit view never writes any files to disk (regression against static mode)"
+    },
+    {
+      "id": "TC-004-tabs-cannot-shrink",
+      "acId": "AC-202-4",
+      "description": "style.css nav.tabs has flex-shrink: 0 and no min-width: 0, so the tablist never clips the Build tab under a long project name",
+      "status": "passing",
+      "testPointer": "test/view/shell-header-layout.test.js::AC-202-4: nav.tabs cannot shrink below its intrinsic width"
+    },
+    {
+      "id": "TC-004-tools-cannot-shrink",
+      "acId": "AC-202-4",
+      "description": "style.css .tools has flex-shrink: 0 so the Find button and theme control never shrink into the tablist",
+      "status": "passing",
+      "testPointer": "test/view/shell-header-layout.test.js::AC-202-4: .tools cannot shrink below its intrinsic width"
+    },
+    {
+      "id": "TC-004-product-yields-first",
+      "acId": "AC-202-4",
+      "description": "style.css .product has min-width: 0 so it yields to the tablist and tools before clipping anything",
+      "status": "passing",
+      "testPointer": "test/view/shell-header-layout.test.js::AC-202-4: .product yields first via min-width:0"
+    },
+    {
+      "id": "TC-004-name-min-width-zero",
+      "acId": "AC-202-4",
+      "description": "style.css .product .name has min-width: 0 so text-overflow: ellipsis triggers inside the flex .product",
+      "status": "passing",
+      "testPointer": "test/view/shell-header-layout.test.js::AC-202-4: .product .name has min-width:0 so the ellipsis triggers"
+    },
+    {
+      "id": "TC-004-name-title-attribute",
+      "acId": "AC-202-5",
+      "description": "renderPage emits a title=\"<full name>\" attribute on .product .name so hover reveals the whole name under ellipsis",
+      "status": "passing",
+      "testPointer": "test/view/shell-header-layout.test.js::AC-202-5: renderPage emits title=\"<full name>\" on .product .name"
+    },
+    {
+      "id": "TC-004-name-title-escaped",
+      "acId": "AC-202-5",
+      "description": "the title attribute shares the escapeHtml path with the inner text so a projectName of \"<script>\" renders as title=\"&lt;script&gt;\"",
+      "status": "passing",
+      "testPointer": "test/view/shell-header-layout.test.js::AC-202-5: the title attribute is HTML-escaped alongside the body"
+    },
+    {
+      "id": "TC-004-name-title-absent-on-collapse",
+      "acId": "AC-202-5",
+      "description": "no title attribute is emitted when the product block collapses (no projectName)",
+      "status": "passing",
+      "testPointer": "test/view/shell-header-layout.test.js::AC-202-5: no title attribute when the product block collapses"
+    },
+    {
+      "id": "TC-004-prd-productname-wins",
+      "acId": "AC-202-6",
+      "description": "resolveProductHeader prefers prd.productName over manifest.projectName when both are set",
+      "status": "passing",
+      "testPointer": "test/view/product-name-precedence.test.js::AC-202-6: prd.productName wins over manifest.projectName when both are set"
+    },
+    {
+      "id": "TC-004-manifest-fallback",
+      "acId": "AC-202-6",
+      "description": "resolveProductHeader falls back to manifest.projectName when the PRD carries no productName",
+      "status": "passing",
+      "testPointer": "test/view/product-name-precedence.test.js::AC-202-6: manifest.projectName is the first fallback when PRD has no productName"
+    },
+    {
+      "id": "TC-004-prd-producttitle-fallback",
+      "acId": "AC-202-6",
+      "description": "resolveProductHeader falls back to prd.productTitle when neither productName nor manifest is set",
+      "status": "passing",
+      "testPointer": "test/view/product-name-precedence.test.js::AC-202-6: prd.productTitle is the last fallback (brief-stage trees without productName or manifest)"
+    },
+    {
+      "id": "TC-004-render-reflects-precedence",
+      "acId": "AC-202-6",
+      "description": "the renderPage DOM reflects the flipped precedence; the manifest value does not reach the header slice when prd.productName is set",
+      "status": "passing",
+      "testPointer": "test/view/product-name-precedence.test.js::AC-202-6: renderPage reflects the flipped precedence in the DOM"
     }
   ],
   "status": "draft"

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

@@ -1,7 +1,7 @@
 {
   "createdAt": "2026-10-01T18:00:00Z",
-  "updatedAt": "2026-10-01T18:00:00Z",
-  "purpose": "Cover US-18001 (Readiness as tab 1 and the PRD rename) and US-18101 (shared pill, findings-list and diff components). Shares the readiness fixture builders with TS-222 so the tab and the CLI assertions ride the same shapes.",
+  "updatedAt": "2026-10-06T12:00:00Z",
+  "purpose": "Cover US-18001 (Readiness as tab 1 and the PRD rename, plus the live-client resync SSOT guard added for issue 297) and US-18101 (shared pill, findings-list and diff components). Shares the readiness fixture builders with TS-222 so the tab and the CLI assertions ride the same shapes.",
   "testLevel": "unit",
   "acIds": [
     "AC-18001-1",
@@ -11,6 +11,7 @@
     "AC-18001-5",
     "AC-18001-6",
     "AC-18001-7",
+    "AC-18001-8",
     "AC-18101-1",
     "AC-18101-2",
     "AC-18101-3"
@@ -88,6 +89,27 @@
       "description": "No existing Product Map or Requirements test expectation changes; only the Readiness-specific additions land.",
       "status": "pending",
       "testPointer": "test/view/readiness-tab.test.js::readiness tab: AC-18101-3 existing Product Map and Requirements tests retain their expectations"
+    },
+    {
+      "id": "TC-223-swap-preserves-readiness",
+      "acId": "AC-18001-8",
+      "description": "resyncTabsAfterSwap keeps tab-readiness as the sole visible panel when Readiness is aria-selected and the swap left tab-overview visible (the Phase 3.6 server default). Pins issue 297: before the fix, the hard-coded TABS list in live-client.js omitted 'readiness', indexOf returned -1, selected fell back to overview, and both tab-readiness and tab-overview went visible.",
+      "status": "passing",
+      "testPointer": "test/view/live-client.test.js::AC-18001-8 resyncTabsAfterSwap keeps Readiness visible on the embed-no-hash default (issue 297)"
+    },
+    {
+      "id": "TC-223-swap-ssot-every-tab",
+      "acId": "AC-18001-8",
+      "description": "resyncTabsAfterSwap honours every nav.tabs [role=tab][data-tab] the server rendered as the SSOT for the tab list. Iterating the six main tabs with each as aria-selected and the swap-default visible panel set to tab-overview, exactly the aria-selected tab's panel is visible after resync. Guards against future drift: a seventh tab added to the renderer survives a swap without an edit on live-client.",
+      "status": "passing",
+      "testPointer": "test/view/live-client.test.js::AC-18001-8 resyncTabsAfterSwap preserves every tab the DOM renders (SSOT invariant)"
+    },
+    {
+      "id": "TC-223-swap-product-map-regression",
+      "acId": "AC-18001-8",
+      "description": "resyncTabsAfterSwap preserves product-map as the sole visible panel through a swap. Guards the one tab that the pre-issue-297 TABS list did include, so the SSOT rewrite does not regress the behaviour it previously had right.",
+      "status": "passing",
+      "testPointer": "test/view/live-client.test.js::AC-18001-8 resyncTabsAfterSwap preserves Product Map through a swap (regression guard)"
     }
   ],
   "status": "draft"

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

@@ -44,6 +44,11 @@
       "id": "AC-18001-7",
       "description": "[happy] Given the tab and the CLI --json output for the same tree hash, when compared, then every id rendered on the tab appears in the JSON for that hash.",
       "testable": true
+    },
+    {
+      "id": "AC-18001-8",
+      "description": "[must-not] Given any main tab (readiness, overview, requirements, architecture, build, product-map) is the active tab, when an SSE tree-update swaps #rcf-live-content innerHTML and resyncTabsAfterSwap runs, then exactly one tabpanel is visible and it is the active tab's panel. The live-client derives the tab list from the server-rendered nav.tabs rather than carrying a parallel array that can drift from page-init: every nav.tabs [role=tab][data-tab] present at swap time is honoured. Readiness is covered as issue 297's regression.",
+      "testable": true
     }
   ],
   "tacIds": [
@@ -51,5 +56,5 @@
   ],
   "tags": [],
   "createdAt": "2026-10-01T18:00:00Z",
-  "updatedAt": "2026-10-01T18:00:00Z"
+  "updatedAt": "2026-10-06T12:00:00Z"
 }

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

@@ -33,8 +33,32 @@
       "when": "a document links to another",
       "then": "the link navigates to that document's section",
       "testable": true
+    },
+    {
+      "id": "AC-202-4",
+      "description": "[happy] The audit view header keeps every main tab visible and the .tools group right of them at any viewport the chrome supports: the tablist and .tools cannot shrink below their intrinsic width (flex-shrink: 0) and .product carries the shrink budget via min-width: 0 (both on the flex item and on .product .name) so the project name ellipsizes first.",
+      "given": "the viewer rendered in the standalone (non-embed) shell",
+      "when": "any viewport >= 721px the chrome supports (above the responsive @media that re-rows the tabs under 720px)",
+      "then": "the six main tabs are fully visible and the .tools group sits right of them; .product .name ellipsizes when the project name is longer than its slot and nothing in .tools overlaps a clipped tab",
+      "testable": true
+    },
+    {
+      "id": "AC-202-5",
+      "description": "[happy] The .product .name span carries a title=\"<full name>\" attribute so hovering reveals the whole name when the ellipsis has clipped it; the title is HTML-escaped on the same path as the inner text, and when the product block collapses (no project name on the tree) no title attribute is emitted.",
+      "given": "a project tree with a projectName",
+      "when": "the viewer renders the header",
+      "then": "the .name span has title=\"<the full projectName>\" with the same HTML-escaping as the inner text",
+      "testable": true
+    },
+    {
+      "id": "AC-202-6",
+      "description": "[happy] The header display name prefers prd.productName, then manifest.projectName, then prd.productTitle. A rename via `rcf define update PRD-001 --set productName=...` therefore reaches the audit chrome without touching manifest.projectName (which the chain keeps for ids and paths).",
+      "given": "a tree where both manifest.projectName and prd.productName are set",
+      "when": "resolveProductHeader runs",
+      "then": "the header projectName is prd.productName; when the PRD carries no productName the fallback is manifest.projectName, then prd.productTitle",
+      "testable": true
     }
   ],
   "createdAt": "2026-06-25T00:00:00Z",
-  "updatedAt": "2026-07-29T13:34:38.914Z"
+  "updatedAt": "2026-10-06T10:12:07.288Z"
 }

package/releases/releases.yaml

@@ -40,8 +40,25 @@
 # `npm install rcf-lite`.
 
 feedVersion: 1
-latest: "0.31.0"
+latest: "0.32.1"
 releases:
+  - version: "0.32.1"
+    date: "2026-10-06"
+    breaking: false
+    headlines:
+      - "rcf-lite 0.32.1 fixes two readiness gates that false-paired under schema-canonical content on top of 0.32.0. The viewer's Readiness tab D3 shapes:pathsResolve now agrees with the CLI by pre-resolving TAC interface path tokens through the same resolveInterfacePaths seam (issue 307), and the D5 crosscut:operationalConcerns trigger reads the structured ac.scope field in addition to the legacy '[deployed]' marker so trees that carry scope as a schema field no longer silently pass 0/0 (issue 306)."
+    minAgentAction: null
+    notesUrl: "https://stravica.ai/docs/rcf/changelog/"
+
+  - version: "0.32.0"
+    date: "2026-10-06"
+    breaking: false
+    headlines:
+      - "rcf-lite 0.32.0 fixes two readiness and freeze gates that false-tripped under schema-canonical content: D6 consistency:orphanInterfaces now accepts the object-shape REQ.deliveredBy (issue 301), and D3 shapes:pathsResolve inside rcf define freeze pre-resolves TAC interface path tokens the way readiness does (issue 302). The deploy-cloudflare-workers blueprint reworded AC-12113-2 so D6 consistency:unsatisfiable stops reading 'absent' as a field name (PR 300)."
+      - "Viewer fixes: SSE tree-update resync preserves the active tab for every main tab including Readiness (issue 297), and the audit view header keeps the six tabs visible under long project names and prefers prd.productName (issue 295)."
+    minAgentAction: null
+    notesUrl: "https://stravica.ai/docs/rcf/changelog/"
+
   - version: "0.31.0"
     date: "2026-10-05"
     breaking: true

package/src/cli/freeze.js

@@ -35,6 +35,7 @@ import { checkCodeNodeResolution } from '#core/store';
 import { findProjectRoot } from '../view/index.js';
 import { loadFreezeRecord, saveFreezeRecord } from '../define/freeze-record.js';
 import { loadAllLedgers } from '../define/ledgers.js';
+import { resolveInterfacePaths } from '../define/interface-paths.js';
 import {
   STAGE_ALIASES,
   STAGE_GATES,
@@ -368,6 +369,12 @@ async function runFreeze({
   // freezeableAfterAck check below is the real gate (freeze still
   // exits 4 on an unfrozen tree); the wrap's refusal is informational
   // here as it is on readiness.
+  // Issue 302 (2026-10-06): freeze now pre-resolves the TAC
+  // interface `path:` tokens the way readiness does, so the D3
+  // `shapes:pathsResolve` check inside freeze agrees with the
+  // readiness verdict instead of defaulting to an empty set and
+  // false-failing resolvable paths.
+  const resolvedPaths = await resolveInterfacePaths(projectRoot, tree);
   /** @type {import('../query/readiness.js').ReadinessResult} */
   const readiness = computeReadiness(tree, {
     freeze: freezeForCompute,
@@ -375,6 +382,7 @@ async function runFreeze({
     profileText,
     testPointers,
     validateErrors,
+    resolvedPaths,
   });
   const gated = await runWithAdmissibilityGate({
     tree,

package/src/cli/readiness.js

@@ -16,7 +16,7 @@
 // every other query verb has.
 
 import { parseArgs } from 'node:util';
-import { readFile, stat } from 'node:fs/promises';
+import { readFile } from 'node:fs/promises';
 import { join } from 'node:path';
 
 import { resolveTestPointers, walkTree } from '#core/store';
@@ -30,9 +30,9 @@ import {
   STAGE_ORDER,
   STAGE_SHORT_NAMES,
   ackable,
-  extractInterfacePathTokens,
   stagePolicy,
 } from '../query/gates.js';
+import { resolveInterfacePaths } from '../define/interface-paths.js';
 import {
   computeReadiness,
   countLitmusReadersAtHash,
@@ -129,42 +129,6 @@ const STATE_LABEL = {
   notApplicable: 'notApplicable',
 };
 
-/**
- * ADR-4131 (0.30.0 PR 5): walk the tree's TAC interfaces, extract the
- * `path:` tokens the engineer named, resolve each one against
- * `projectRoot` on disk, and return the set of tokens that resolve.
- * `shapes:pathsResolve` reads the set from the stage context and
- * decides the D3 bite without I/O. The compute is pure; this helper is
- * the one place I/O happens for the check.
- *
- * @param {string} projectRoot
- * @param {import('#core/store/walker.js').TreeModel} tree
- * @returns {Promise<Set<string>>}
- */
-async function resolveInterfacePaths(projectRoot, tree) {
-  const resolved = new Set();
-  /** @type {Set<string>} */
-  const candidates = new Set();
-  for (const tac of tree.tacs ?? []) {
-    for (const iface of tac.interfaces ?? []) {
-      const desc = typeof iface?.description === 'string' ? iface.description : '';
-      for (const token of extractInterfacePathTokens(desc)) {
-        candidates.add(token);
-      }
-    }
-  }
-  await Promise.all([...candidates].map(async (token) => {
-    try {
-      await stat(join(projectRoot, token));
-      resolved.add(token);
-    } catch {
-      // Missing path stays out of the set; the gate decides whether
-      // `authoredAt: D3` lets it through.
-    }
-  }));
-  return resolved;
-}
-
 /**
  * Read `rcf/.identity/profile.md` when it exists; return null on
  * ENOENT. Any other read error surfaces as null so the profile

package/src/define/interface-paths.js

@@ -0,0 +1,47 @@
+// Shared define-time helper: resolve the `path:` tokens an engineer
+// named on TAC interfaces against the project root on disk. The pure
+// D3 `shapes:pathsResolve` check reads the resulting set from the
+// stage context; this is the one place I/O happens for the check.
+//
+// Lifted out of `src/cli/readiness.js` in issue 302 (2026-10-06) so
+// the freeze CLI can pre-resolve the same tokens and D3 agrees with
+// readiness instead of false-failing from an empty fallback set.
+// ADR-4131 (0.30.0 PR 5) still names readiness as the origin.
+
+import { stat } from 'node:fs/promises';
+import { join } from 'node:path';
+
+import { extractInterfacePathTokens } from '../query/gates.js';
+
+/**
+ * Walk the tree's TAC interfaces, extract the `path:` tokens the
+ * engineer named, resolve each one against `projectRoot` on disk, and
+ * return the set of tokens that resolve.
+ *
+ * @param {string} projectRoot
+ * @param {import('#core/store/walker.js').TreeModel} tree
+ * @returns {Promise<Set<string>>}
+ */
+export async function resolveInterfacePaths(projectRoot, tree) {
+  const resolved = new Set();
+  /** @type {Set<string>} */
+  const candidates = new Set();
+  for (const tac of tree.tacs ?? []) {
+    for (const iface of tac.interfaces ?? []) {
+      const desc = typeof iface?.description === 'string' ? iface.description : '';
+      for (const token of extractInterfacePathTokens(desc)) {
+        candidates.add(token);
+      }
+    }
+  }
+  await Promise.all([...candidates].map(async (token) => {
+    try {
+      await stat(join(projectRoot, token));
+      resolved.add(token);
+    } catch {
+      // Missing path stays out of the set; the gate decides whether
+      // `authoredAt: D3` lets it through.
+    }
+  }));
+  return resolved;
+}

package/src/query/gates.js

@@ -1582,7 +1582,15 @@ function computeSecurityArchitectureCheck(ctx) {
 function computeOperationalConcernsCheck(ctx) {
   const tree = ctx.tree;
   const tad = /** @type {any} */ (tree.tad ?? {});
-  const hasDeployedAc = (tree.userStories ?? []).some((us) => (us.acceptanceCriteria ?? []).some((ac) => typeof ac?.description === 'string' && ac.description.includes('[deployed]')));
+  // Issue 306 (2026-10-06): schemas carry AC scope as the structured
+  // field `scope: "deployed"`; the legacy `[deployed]` description
+  // marker (R13 2026-10-05) is kept so older trees still trigger. A
+  // deployed-scope AC on either form must find a non-empty
+  // TAD.operationalConcerns.
+  const hasDeployedAc = (tree.userStories ?? []).some((us) => (us.acceptanceCriteria ?? []).some((ac) => {
+    if (ac?.scope === 'deployed') return true;
+    return typeof ac?.description === 'string' && ac.description.includes('[deployed]');
+  }));
   const opFail = [];
   if (hasDeployedAc) {
     const oc = tad.operationalConcerns;
@@ -2064,10 +2072,24 @@ function extractThenFieldTokens(thenClause) {
 /**
  * Collect every interface the tree "reaches" from an AC `ownerRef` or
  * a REQ `deliveredBy` (REQ-174 companion field). The result is a Set
- * of `<tacId>:<name>` keys. A `deliveredBy` on a REQ can take two
- * shapes: an array of `TAC-nnnn:<name>` pointer strings, or an array
- * of plain TAC ids ("delivered by this TAC"); the second shape reaches
- * every interface on the named TAC.
+ * of `<tacId>:<name>` keys.
+ *
+ * REQ `deliveredBy` takes two canonical shapes, both accepted here:
+ *   1. The schema-canonical object form `{tacId, adrId?, field?}`
+ *      (`@stravica-ai/rcf-schemas` 0.6.3 `$defs.deliveredBy`). When
+ *      `tacId` is present:
+ *        - `field: interfaces[<name>]` reaches `{tacId}:{name}` (one
+ *          interface), via `parseOwnerRefInterfaceField`.
+ *        - any other `field`, or no `field`, reaches every interface
+ *          on the named TAC (the "delivered by this TAC" meaning).
+ *      An `adrId`-only deliveredBy does not reach any TAC interface.
+ *   2. A legacy array of pointer strings: `TAC-nnnn:<name>` reaches
+ *      one interface, a bare `TAC-nnnn` reaches every interface on
+ *      that TAC.
+ *
+ * Issue 301 (2026-10-06): the array-only guard dropped every
+ * schema-canonical object deliveredBy and false-positived every
+ * blueprint TAC interface.
  *
  * @param {import('#core/store/walker.js').TreeModel} tree
  * @returns {Set<string>}
@@ -2085,19 +2107,40 @@ function collectReachedInterfaces(tree) {
       out.add(`${ref.tacId}:${name}`);
     }
   }
-  // REQ deliveredBy (optional field; shapes above).
+  // REQ deliveredBy. Both shapes documented above.
   for (const req of tree.requirements ?? []) {
     const deliveredBy = /** @type {any} */ (req)?.deliveredBy;
-    if (!Array.isArray(deliveredBy)) continue;
-    for (const entry of deliveredBy) {
-      if (typeof entry !== 'string' || entry.length === 0) continue;
-      const m = entry.match(/^(TAC-[A-Za-z0-9-]+):(.+)$/);
-      if (m) {
-        out.add(`${m[1]}:${m[2]}`);
+    if (deliveredBy == null) continue;
+    if (Array.isArray(deliveredBy)) {
+      for (const entry of deliveredBy) {
+        if (typeof entry !== 'string' || entry.length === 0) continue;
+        const m = entry.match(/^(TAC-[A-Za-z0-9-]+):(.+)$/);
+        if (m) {
+          out.add(`${m[1]}:${m[2]}`);
+          continue;
+        }
+        // Plain TAC id: every interface on that TAC is reached.
+        const tac = (tree.tacs ?? []).find((t) => t?.tacId === entry);
+        if (!tac) continue;
+        for (const iface of tac.interfaces ?? []) {
+          if (typeof iface?.name === 'string') out.add(`${tac.tacId}:${iface.name}`);
+        }
+      }
+      continue;
+    }
+    if (typeof deliveredBy === 'object') {
+      const tacId = /** @type {any} */ (deliveredBy).tacId;
+      if (typeof tacId !== 'string' || tacId.length === 0) continue;
+      const field = /** @type {any} */ (deliveredBy).field;
+      const name = parseOwnerRefInterfaceField(field);
+      if (name) {
+        out.add(`${tacId}:${name}`);
         continue;
       }
-      // Plain TAC id: every interface on that TAC is reached.
-      const tac = (tree.tacs ?? []).find((t) => t?.tacId === entry);
+      // No field, or a field that does not name an interface: reach
+      // every interface on the named TAC (the "delivered by this TAC"
+      // meaning carried over from the array-shape bare TAC pointer).
+      const tac = (tree.tacs ?? []).find((t) => t?.tacId === tacId);
       if (!tac) continue;
       for (const iface of tac.interfaces ?? []) {
         if (typeof iface?.name === 'string') out.add(`${tac.tacId}:${iface.name}`);

package/src/view/html-page.js

@@ -843,21 +843,33 @@ function buildSpecFilterText(fbs) {
 }
 
 /**
- * Viewer UI refresh PR 2 (shell polish, Baz 2026-10-02; decision 17):
- * the one-bar header carries the project name only. The project name
- * is sourced from `manifest.projectName`, then `prd.productName`,
- * then `prd.productTitle` (the PRD title the brief names). Decision 17
- * is explicit: project name prominent after the icon mark, tool name
- * out of the bar, no technology chip. When the tree exposes no
- * project name, the whole product block collapses and the brand icon
- * stands on its own (silent empty state; CSS `.product:empty { display:none; }`).
+ * Viewer UI refresh PR 2 (shell polish, Baz 2026-10-02; decision 17)
+ * with the issue-295 flip (w-2026-10-06-dave-001): the one-bar header
+ * carries the project name only, sourced from `prd.productName` first
+ * (the human-readable name an owner edits via `rcf define update
+ * PRD-001 --set productName=...`), then `manifest.projectName` (the
+ * init-time value kept for ids / paths), then `prd.productTitle` (the
+ * PRD title the brief names). Decision 17 remains: project name
+ * prominent after the icon mark, tool name out of the bar, no
+ * technology chip. When the tree exposes no project name, the whole
+ * product block collapses and the brand icon stands on its own
+ * (silent empty state; CSS `.product:empty { display:none; }`).
+ *
+ * The precedence flip is a lite-native cut (US-202, Part 2 cut b):
+ * `rcf define update MANIFEST` is not addressable in the current CLI,
+ * so before this change manifest.projectName was a one-shot init value
+ * and the only way to rename the audit surface was a hand edit of
+ * manifest.json. prd.productName is already updatable via `rcf define
+ * update PRD-001 --set productName=...`; preferring it in the header
+ * means the display name is lite-native without touching the manifest
+ * (ids and paths are untouched).
  *
  * @param {import('./tree-model.js').BuiltTreeModel} model
  * @returns {{ projectName: string | null }}
  */
 export function resolveProductHeader(model) {
-  const projectName = model.manifest?.projectName
-    ?? model.prd?.productName
+  const projectName = model.prd?.productName
+    ?? model.manifest?.projectName
     ?? model.prd?.productTitle
     ?? null;
   return { projectName };
@@ -870,7 +882,13 @@ function renderProductBlock(header) {
     // empty state (brief) survives screen-reader output too.
     return '<div class="product"></div>';
   }
-  return `<div class="product"><span class="name">${escapeHtml(header.projectName)}</span>
+  // w-2026-10-06-dave-001 (issue 295): .product .name clips its text
+  // with text-overflow:ellipsis so a long project name yields rather
+  // than pushing the tablist off the bar; the title attribute carries
+  // the full name so hover reveals it. Both the title and the body go
+  // through escapeHtml so the attribute is safe against injection.
+  const safe = escapeHtml(header.projectName);
+  return `<div class="product"><span class="name" title="${safe}">${safe}</span>
         <span class="sub">review surface</span></div>`;
 }
 

package/src/view/index.js

@@ -12,6 +12,7 @@ import { resolveTestPointers, walkTree } from '#core/store';
 import { computeReadiness } from '../query/readiness.js';
 import { computeQuestions } from '../query/questions.js';
 import { loadFreezeRecord } from '../define/freeze-record.js';
+import { resolveInterfacePaths } from '../define/interface-paths.js';
 import { loadAllLedgers } from '../define/ledgers.js';
 import { renderContent, renderPage } from './html-page.js';
 import { renderProductMapGrouping } from './product-map.js';
@@ -77,11 +78,18 @@ export async function renderModelToPage({ projectRoot }) {
   // Load the readiness inputs once per rewalk; the viewer is pure
   // (never recomputes readiness). Failures load as `null` so the tab
   // still renders when a tree is partial.
-  const [freezeRecord, ledgers, testPointers, profileText] = await Promise.all([
+  const [freezeRecord, ledgers, testPointers, profileText, resolvedPaths] = await Promise.all([
     loadFreezeRecord({ projectRoot }).catch(() => null),
     loadAllLedgers({ projectRoot }).catch(() => ({})),
     resolveTestPointers({ projectRoot, tree }).catch(() => undefined),
     readProfileText(projectRoot),
+    // Issue 307 (2026-10-06): run the same TAC-interface path
+    // resolver the CLI and freeze run so the viewer's D3
+    // `shapes:pathsResolve` check reads the resolved set from the
+    // same seam. Before this, the viewer called computeReadiness
+    // without `resolvedPaths`, D3 false-failed on paths that resolve
+    // on disk, and the Readiness tab disagreed with the CLI.
+    resolveInterfacePaths(projectRoot, tree).catch(() => undefined),
   ]);
 
   let readiness = null;
@@ -93,6 +101,7 @@ export async function renderModelToPage({ projectRoot }) {
       profileText,
       testPointers,
       validateErrors: errors,
+      resolvedPaths,
     });
   } catch (err) {
     // A malformed tree should not block the viewer; the Readiness tab
@@ -149,7 +158,12 @@ export async function renderModelToPage({ projectRoot }) {
   // list is extended before the version pin bump). One row per doc id
   // plus one row per AC under each US.
   const indexJson = serialiseViewIndex(model);
-  return { fullPageHtml, contentHtml, errors, tree, pmPartials, indexJson };
+  // Issue 307 (2026-10-06): expose the computed readiness alongside
+  // the rendered HTML so tests can assert the viewer's D3
+  // shapes:pathsResolve agrees with the CLI without parsing HTML. The
+  // viewer HTML is still the operator-facing surface; this field is
+  // additive and consumed by test code only.
+  return { fullPageHtml, contentHtml, errors, tree, pmPartials, indexJson, readiness };
 }
 
 /**

package/src/view/live-client.js

@@ -507,19 +507,27 @@
   // the panels back in line with the aria-selected button and re-run
   // Mermaid in the visible one.
   function resyncTabsAfterSwap(doc, win) {
-    // Phase 3.8 tabs; Phase 3.9 added product-map. Product Map MUST be
-    // in this list so an SSE swap while it is the active tab keeps the
-    // panel visible; without it, resolveActiveTab falls back to
-    // overview and the freshly-swapped pm listeners have already been
-    // rewired by the rcfPage.init() call below.
-    var TABS = ['overview', 'requirements', 'architecture', 'build', 'product-map'];
-    // Scope to the top-level nav.tabs to avoid matching pm-group-btn
+    // Issue 297 (w-2026-10-06-dave-003, AC-18001-8): the authoritative
+    // tab list is the server-rendered nav.tabs itself, not a parallel
+    // array that can drift. Earlier the list was hand-copied here and
+    // omitted 'readiness' (added as tab 1 in US-18001); a Readiness
+    // SSE swap fell back to Overview and both panels went visible.
+    // Deriving from the DOM means a future tab cannot be forgotten
+    // the same way. Scope to nav.tabs to avoid matching pm-group-btn
     // nodes (they also carry role="tab").
+    var buttons = doc.querySelectorAll('nav.tabs [role="tab"][data-tab]');
+    var names = [];
+    for (var b = 0; b < buttons.length; b += 1) {
+      var n = buttons[b].getAttribute ? buttons[b].getAttribute('data-tab') : null;
+      if (n) names.push(n);
+    }
     var selectedBtn = doc.querySelector('nav.tabs [role="tab"][aria-selected="true"]');
     var selected = selectedBtn && selectedBtn.getAttribute ? selectedBtn.getAttribute('data-tab') : null;
-    if (!selected || TABS.indexOf(selected) === -1) selected = 'overview';
-    for (var i = 0; i < TABS.length; i += 1) {
-      var name = TABS[i];
+    if (!selected || names.indexOf(selected) === -1) {
+      selected = names.indexOf('overview') !== -1 ? 'overview' : (names[0] || 'overview');
+    }
+    for (var i = 0; i < names.length; i += 1) {
+      var name = names[i];
       var panel = doc.getElementById('tab-' + name);
       if (!panel) continue;
       if (name === selected) panel.removeAttribute('hidden');

package/src/view/style.css

@@ -236,6 +236,10 @@ header.app-header .bar {
   color: var(--sv-ink);
   overflow: hidden;
   text-overflow: ellipsis;
+  /* w-2026-10-06-dave-001 (issue 295): .product is a flex container; the
+     ellipsis only triggers when its child is itself free to shrink below
+     intrinsic. min-width:0 unlocks that. */
+  min-width: 0;
 }
 
 .product .sub {
@@ -248,8 +252,12 @@ nav.tabs {
   display: flex;
   gap: 0.25rem;
   margin-left: 1rem;
-  flex: 1 1 auto;
-  min-width: 0;
+  /* w-2026-10-06-dave-001 (issue 295): the tablist grows to fill the
+     bar but never shrinks below its intrinsic width (flex-shrink:0),
+     so every main tab stays visible and the Find button in .tools
+     never sits on top of a clipped tab. .product carries the shrink
+     budget via its own min-width:0 and the ellipsis on .product .name. */
+  flex: 1 0 auto;
   overflow-x: auto;
   -webkit-overflow-scrolling: touch;
 }