Remove the registry UI release flag after rollout acceptance

🤖 Generated by the Agentic Engineer

Goal

Remove the short-lived registry-ui OpenFeature release gate once the reference registry has completed its first production rollout and acceptance proof.

Why

The default-off gate makes the first deployment reversible, but leaving a release flag in place after the rollout is understood creates permanent configuration and test surface without an operational purpose.

Delivery

Controller PR #150 is merged and published as signed v1.12.0. The first Platform trial (#3475) is accepted. Child devantler-tech/platform#4342 tracks adoption of the standard workspace release through PR #4343.

The signed v1.12.0 rollout is accepted in production: Platform PR #4343 actually merged, and fresh discovery, Safari queries, persistent appearance and immutable workload readback pass. The detailed protected deployment and live acceptance proof is recorded below. Runtime source/provider adoption remains separate roadmap work.

Acceptance criteria

The hosted registry renders discovered DataProduct descriptors successfully.
The independently deployed harbour product can be opened and queried through the registry and directly.
The OpenFeature provider, REGISTRY_UI_ENABLED configuration, Helm value, and both-state release tests are removed.
The registry UI becomes the normal supported behavior without weakening the iframe sandbox or security headers.
Documentation and deployment values describe the post-rollout behavior.

chore: agent-claim #13 nonce=62e0e3cbfaab97d680c103af50f33b17

🤖 Generated by the Agentic Engineer

Delivered v1.12.0 on the Data products workspace. Controller PR #150 merged as ff7ddcf264f8ce4813ccdb6675a45b4d1e6d1b78; Platform PR #4343 actually merged as 6147f32e51f76dceb8a7bd4566bcb1d2e0b15898.

Production acceptance passed after merge:

Fresh authenticated discovery renders Harbour as Ready. Actual Safari opens the sandboxed explorer, loads both stations and filters Nordhavn to one observation: 16.8 °C and 14.2 PSU. The independent public API returns the same row and its OpenAPI contract loads.
Dark persists after reload. Fresh Light/Dark changes in the in-app browser synchronize the embedded product while retaining the selected station and result. The normal narrow layout displays the observation as a readable row with labelled values.
The live chart and every running image match the independently signature-verified v1.12.0 digests. Both components have two Ready replicas. The obsolete UI environment switch is absent; the approved optional appearance contract, authentication, sandbox and existing isolation boundaries remain intact. Anonymous registry requests still redirect to sign-in.
The protected deployment, required checks and queue-membership guard passed. Fresh Flux readback is current-generation Ready and SourceVerified, and its applied artifact matches the protected publisher's verified receipt for the actual merged main revision. The canonical read-only Platform health check passes.

The workspace is now standard supported behavior; its temporary installation gate is retired. Harbour remains explicitly labelled synthetic sample data. Actual source adoption and provider negotiation/transfer are separate roadmap work, including controller #126; this acceptance makes no claim that those paths are delivered.

Navigation Menu

Repository navigation

Remove the registry UI release flag after rollout acceptance #13

Goal

Why

Delivery

Acceptance criteria

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Remove the registry UI release flag after rollout acceptance #13

Description

Goal

Why

Delivery

Acceptance criteria

Activity

devantler commented on Oct 1, 2026

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions