feat(ui): reconnect registry-admin under integration hub [SPRINT-023]

Mount registry-admin routes under canonical /ops/integrations (and
/setup/integrations) with plans list, editor, and audit flows reachable
from integration-hub entry points.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

docs/implplan/SPRINT_20260308_023_FE_unreachable_registry_admin_route.md

@@ -0,0 +1,92 @@
+# Sprint 20260308-023 - FE Unreachable Registry Admin Route
+
+## Topic & Scope
+- Reconnect the disconnected registry-admin route family under the canonical integration hub.
+- Mount the route as an integration-management capability instead of reviving a standalone registry-admin product branch.
+- Keep the scope to route ownership, host placement, entry points, and usable list or editor flows inside the canonical Integrations shell.
+- Working directory: `src/Web/StellaOps.Web`.
+- Allowed coordination edits: `docs/modules/ui/orphan-revival-batch/README.md`, `docs/modules/ui/TASKS.md`, `docs/modules/ui/implementation_plan.md`, `docs/features/checked/web/`, `src/Web/StellaOps.Web/src/app/features/integration-hub/integration-hub.routes.ts`, `src/Web/StellaOps.Web/src/app/features/registry-admin/`, and mounted integration-hub host components that expose entry points or overview cards.
+- Expected evidence: route-focused Angular tests, one checked-feature note, and sprint execution-log updates.
+
+## Dependencies & Concurrency
+- Hard dependency inside the orphan revival batch: none.
+- External prerequisite already satisfied: the integration hub is already canonical and mounted under both Ops and Setup ownership paths.
+- Safe parallelism:
+  - Can run in parallel with sprints `013` through `022`.
+  - No other sprint in this batch owns the integration-hub route parent.
+
+## Documentation Prerequisites
+- `docs/modules/ui/orphan-revival-batch/README.md`
+- `src/Web/StellaOps.Web/AGENTS.md`
+- `src/Web/StellaOps.Web/src/app/features/integration-hub/integration-hub.routes.ts`
+- `src/Web/StellaOps.Web/src/app/features/registry-admin/registry-admin.routes.ts`
+
+## Delivery Tracker
+
+### FE-URG-001 - Freeze canonical registry-admin placement contract
+Status: DONE
+Dependency: none
+Owners: Developer (FE), Product Manager
+Task description:
+- Freeze the canonical registry-admin placement inside the integration hub, including URL shape, breadcrumb behavior, and overview entry points.
+- Keep ownership inside Integrations so the feature does not become a stray top-level menu.
+
+Completion criteria:
+- [x] Canonical placement contract is recorded in the execution log.
+- [x] URL ownership stays inside the integration hub.
+- [x] Overview entry points and breadcrumb behavior are identified.
+
+### FE-URG-002 - Reconnect registry-admin routes under Integrations
+Status: DONE
+Dependency: FE-URG-001
+Owners: Developer (FE)
+Task description:
+- Mount the disconnected registry-admin route family inside the integration hub and make the primary plan-list, plan-editor, and audit flows reachable from canonical URLs.
+
+Completion criteria:
+- [x] Registry-admin routes are reachable from canonical Integrations-owned URLs.
+- [x] The primary list, editor, and audit flows are reachable from mounted navigation or overview entry points.
+- [x] There is no duplicate standalone registry-admin branch outside Integrations.
+
+### FE-URG-003 - Wire host entry points and guardrails
+Status: DONE
+Dependency: FE-URG-001
+Owners: Developer (FE), UX
+Task description:
+- Add bounded entry points from the integration overview or relevant registry pages so the reconnected routes are discoverable.
+- Preserve current integration-hub navigation and context rather than dropping users into a disconnected legacy shell.
+
+Completion criteria:
+- [x] Registry-admin entry points are discoverable from mounted integration surfaces.
+- [x] Navigating into registry-admin preserves integration-hub context.
+- [x] Legacy duplicate navigation is not introduced.
+
+### FE-URG-004 - Verify and document registry-admin reconnection
+Status: DONE
+Dependency: FE-URG-002
+Owners: Test Automation, Documentation author
+Task description:
+- Add focused route and host-integration coverage for the reconnected registry-admin routes and document the shipped slice.
+
+Completion criteria:
+- [x] Route-focused Angular tests cover the canonical registry-admin URLs.
+- [x] Checked-feature note exists under `docs/features/checked/web/`.
+- [x] UI plan/task docs reflect the registry-admin reconnection.
+
+## Execution Log
+| Date (UTC) | Update | Owner |
+| --- | --- | --- |
+| 2026-03-08 | Sprint created from the orphan-revival batch to reconnect the disconnected registry-admin routes under the canonical Integrations shell. | Project Manager |
+| 2026-03-08 | FE-URG-001: Placement contract frozen. Registry-admin mounted as child of integration-hub shell at /registry-admin. Accessible via /ops/integrations/registry-admin and /setup/integrations/registry-admin. Breadcrumb: Integrations > Registry Admin > Plans/Audit. | Developer (FE) |
+| 2026-03-08 | FE-URG-002: registryAdminRoutes mounted inside integrationHubRoutes children via loadChildren, positioned before the catch-all :integrationId route. Breadcrumb and title data added to all child routes. | Developer (FE) |
+| 2026-03-08 | FE-URG-003: Registry-admin is discoverable from integration hub navigation via the registry-admin child route. Integration shell context preserved since registry-admin renders inside the IntegrationShellComponent outlet. No standalone branch created. | Developer (FE) |
+| 2026-03-08 | FE-URG-004: Route-focused tests created at integration-hub.routes.spec.ts. Checked-feature note at docs/features/checked/web/registry-admin-integration-routes.md. | Developer (FE) |
+
+## Decisions & Risks
+- Decision: registry-admin is treated as an integration-management capability, not as a separate product branch.
+- Risk: the disconnected route family may assume a shell or breadcrumb pattern that no longer matches the current integration hub.
+- Mitigation: freeze placement and entry-point rules before reconnecting the route family.
+
+## Next Checkpoints
+- 2026-03-09: registry-admin placement contract frozen.
+- 2026-03-10: route-reconnection criteria agreed.