Repository navigation
Make publisher review available on the platform #4852
Description
🤖 Generated by the Agentic Engineer
Problem
The platform's existing product UI host runs Data Product Controller v2.7.0 without publisher review enabled. Authors cannot use the released local report workspace on that host.
Outcome
Authors can reach publisher review through the existing product UI host, inspect a local report from the same verified release, and move between the enabled workspaces without losing their selected theme.
Acceptance
- Adopt the signed Data Product Controller release containing the entry-point and shared-theme fixes, pinning its image digest and matching signed chart across the existing components.
- Enable publisher review on the independent UI host only, preserving the separate product UI permissions, existing routing, credential stripping and network restrictions.
- Render and validate both supported platform overlays; retain rollout regressions and exact-version verification. Require the expected public navigation, offline publisher page and its assets; refuse missing assets, unsafe response policies and routes left available after withdrawal.
- Merge through the normal production queue and verify the applied artifact, current-generation readiness and immutable runtime images.
- Exercise the public workspace entry, a saved composition report, Light/Dark appearance and navigation cleanup in a real browser.
Part of devantler-tech/khoist#205. Independent-author adoption and retirement of its temporary release gate remain open; this is deployment availability, not an adoption claim.
Planning: Medium priority removes a confirmed access gap in the Ready publisher-adoption workflow. Low effort covers existing artifact pins, one host opt-in, deployment tests and user-path verification. Standard service class. Prerequisites #4853 and devantler-tech/khoist#381 are closed; the signed v2.9.1 image and matching chart are published and verified at source commit df0dd85b5fb0545c5943a7011bffd7a0ad07ac77. The maintainer waives WIP limits for this round.
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Start date
Target date
Effort
Projects
- Status
Activity
chore: agent-claim #4852 nonce=463d5d1cc4b0938011d5ec2fb8955247
chore: agent-claim #4852 nonce=d5e854f2abf815f6e6ea00ba026deee4
chore: agent-claim #4852 nonce=11aa5a24afa6e8bb3eb31a1ab0920625
chore: agent-claim #4852 nonce=ed0d9b487e45caad7d7b3d3a1ba8c0c8
chore: agent-claim #4852 nonce=8175ef4c5679e45b1be68326aa5b90ad
chore: agent-claim #4852 nonce=cc06c2713f1d5a151d289468d298acf8
devantler commentedon Oct 14, 2026
Deployment acceptance is complete through #4871, merged at exact head
4554218868ff3f684a41fa9c1e621f556291a547as7ab2b25430c48bea9c8b2ac221e47d65a414821e. The normal merge-group deployment run 38534447247, including deploy job 115760299728 and its required-check aggregation, succeeded. The accepted job contains the applied artifact digest; the live Source and reconciliation roots agree on that artifact and are Ready for their current generations. The matching pinned chart is Ready, and the running image identities match signed Data Product Controller v2.9.1 digestsha256:d82b984165bc71844c323f752f474f80a7a7f7a78972a5e1171d9f814cb9bb34. Publisher review is enabled only on the independent UI host.The public root exposes both workspaces. I generated a saved v2 composition report from the shipped three-product example using the verified v2.9.1 source
df0dd85b5fb0545c5943a7011bffd7a0ad07ac77, whose release tag and commit signature were read back. In the real public browser, selecting that local file was accepted as complete and metadata-valid with three products, one source, three documents, zero findings and the composition requirement. The consumer preview showed both named producer inputs and their declared protocol/version requirements while retaining unobserved readiness.Light and Dark choices survived workspace navigation and real browser Back. Returning withdrew the report and preview/export surface, showing “No report loaded.” Browser warning/error logs were empty. Public response policy is no-store, denies network connections and frames, and retains nosniff/no-referrer. The accepted rollout retains the tested overlay, asset, policy and withdrawal regressions; no live feature toggle or cluster mutation was used for this verification.
This closes deployment availability only. Independent-author adoption and release-gate retirement remain on devantler-tech/khoist#205; this synthetic report is not their evidence. The separate retained-portal recovery remains open.
chore: agent-claim #4852 nonce=a795b8abd72c8727bbc3ccd42c36b4e2