ops/platform-setup/* must render their intended platform-setup pages without rewriting the browser URL to setup/topology/*.
Explicit drill-ins into the broader topology product may still link to /setup/topology/* when the destination has no canonical ops/platform-setup equivalent.
trust-signing stays a redirect into Setup > Trust & Signing; it is not owned by Platform Setup.
promotion-paths, workflows-gates, gate-profiles, release-templates and policy-bindings (heading “Feed Policy”) have no owner read and no editor. Each opens with a reference notice: the page does not read, store or apply settings for the tenant, and nothing on it is selected for an environment or enforced by a promotion gate.
They render no fixed profiles, freshness SLAs, workflow rows or template rows, and no define, edit or select controls. Release Orchestrator has no named gate-profile, release-template or workflow-catalog model. The approval-policy gate, one of the four promotion gates Release Orchestrator registers, reads the approval policies and the policy pack bound to the target environment (Gate policies); when no approval policy matches or no pack is bound, it uses the approval mode or pack set in Release Orchestrator service configuration.
The release-templates page links to release creation as Create Release Version, with no template identity. The reference pages do not link to the workflow inventory, the topology promotion graph (it renders gate profiles and approval counts derived from the environment type) or Defaults & Guardrails (it renders fixed impact rows). The Platform Setup home quick link for policy-bindings is titled Feed Policy, matching the page heading.
promotion-paths, workflows-gates and gate-profiles end with an owner-editor block for the approval-policy gate: Open Approval Policies (/releases/policies) for a session holding release.policy.read, and Open Gate policies (/ops/policy/packs, where environment policy bindings are edited) for a session holding policy:read. Each entry states the change grant (release.policy.manage, release.policy-bindings.write, each together with its read grant, which the owner endpoints require on every route); an entry the session cannot open names the missing scope and is not linked. Grants are the session’s own scopes; admin does not imply them. The former Open Gate Policies link to the unguarded /ops/policy/baselines mount is gone. No platform-setup route mounts or redirects to these editors.
The route at policy-bindings has the tab title and breadcrumb Feed Policy, matching the page.
Regression controls: platform-setup-reference-pages.spec.ts and platform-setup-feed-policy-page.component.spec.ts fail on reintroduced fixed rows, editing controls, default/enforcement copy or template selection; platform-setup-policy-editors.component.spec.ts covers the grant matrix of the owner-editor block and platform-setup.routes.spec.ts the Feed Policy title and the absence of editor aliases.
