— 06 UI CURRENT INTEGRATION / NO FALSE GREEN

Scope note: no production UI deploy was performed in any prior macro and none is performed here. The web source repo is not present on this workstation nor inside the VPS read allowlist, so UI source coherence was assessed from the deployed s174 bundle (client + server chunks) and live behaviour, not from repo source.

What the deployed UI binds to:

• The pivot/registries pages call /api/registry/* and /api/registries-pivot/* . The registries-pivot endpoints are pg-backed (rpQuery over v_count_integrity / v_registries_pivot_* ) and return 200 with real PG truth, including count_integrity_verdict and pivot_backed/pivot_missing — i.e. the UI already has access to invariant/reliability truth from the current views.
• Stale/drift references found: the /knowledge/registries page calls /api/registries/index, which is not mounted (404) — see doc 03. This is the one concrete client/server drift.
• No direct v1/v2 raw-object references hide pollution: /api/registry/counts does expose the raw polluted total (2,122,910) rather than the clean managed count. This is a raw-vs-clean honesty gap in one endpoint, surfaced here, not hidden. Recommend the registries/composition UI present managed (clean) vs raw side by side.

False-green control: the central rule is encoded in v_rp_production_ui_no_false_green_guard — ui_production_ready is true only when real_break_routes = 0 (no SERVER_ERROR and no real ROUTE_MISSING). Current read-back: BLOCKED_REAL_API_BREAKS_PRESENT_DO_NOT_CLAIM_READY (3 real breaks, 12 healthy). So the DB itself refuses to certify the UI ready while matrix/pivot-query/registries-index are broken. The page returning HTTP 200 is therefore not sufficient to claim readiness — the guard and the smoke harness both gate on the API truth, not the page shell.

Post-fix expectation: once the operator applies the handler swaps (matrix, pivot-query) and the registries/index rebuild, the guard flips to GREEN_OK_TO_CLAIM_READY and the smoke harness returns PASS. Until then, the UI must be treated as NOT production-ready.

Secondary UI-adjacent observation: homepage SSR fetch of /items/pages returns 403 Forbidden (page renders via fallback). This is a Directus collection/field permission matter, separate from the RP API breaks; flagged for follow-up, not addressed here to avoid broad auth/permission mutation.