Repair live releases deployment detail flows
This commit is contained in:
@@ -0,0 +1,69 @@
|
||||
# Sprint 20260308-026 - FE Live Releases Deployments Route And Action Repair
|
||||
|
||||
## Topic & Scope
|
||||
- Repair the canonical `/releases/deployments` subtree so deployment detail routes render under the Releases shell instead of falling through to unrelated fallback content.
|
||||
- Remove or replace dead actions inside the currently mounted deployment history/detail surfaces so visible UI affordances are either functional or explicitly not presented.
|
||||
- Keep the repair inside the active Web shell and document the live contract boundary while the legacy deployment API remains unavailable.
|
||||
- Working directory: `src/Web/StellaOps.Web`.
|
||||
- Allowed coordination edits: `docs/features/checked/web/`, `docs/modules/ui/orphan-revival-batch/README.md`, `docs/modules/ui/TASKS.md`, `src/Web/StellaOps.Web/src/app/routes/releases.routes.ts`, `src/Web/StellaOps.Web/src/app/features/deployments/`, `src/Web/StellaOps.Web/scripts/`.
|
||||
- Expected evidence: targeted Angular coverage, rebuilt web bundle synced to the compose frontdoor volume, and live Playwright verification against `https://stella-ops.local`.
|
||||
|
||||
## Dependencies & Concurrency
|
||||
- Depends on the current Releases shell remaining canonical for deployment history under `/releases`.
|
||||
- Safe parallelism: avoid unrelated search, package, and setup areas; keep edits limited to the releases route tree and `features/deployments`.
|
||||
|
||||
## Documentation Prerequisites
|
||||
- `src/Web/StellaOps.Web/AGENTS.md`
|
||||
- `docs/modules/platform/architecture-overview.md`
|
||||
- `docs/technical/architecture/console-admin-rbac.md`
|
||||
- `docs/technical/architecture/console-branding.md`
|
||||
- `docs/modules/ui/orphan-revival-batch/README.md`
|
||||
- `docs/features/checked/web/deployment-monitoring-ui.md`
|
||||
- `docs/features/checked/web/deployment-detail-with-workflow-dag-visualization.md`
|
||||
|
||||
## Delivery Tracker
|
||||
|
||||
### FE-LIVE-DEP-001 - Reconnect canonical Releases deployment detail routing
|
||||
Status: DONE
|
||||
Dependency: none
|
||||
Owners: Developer (FE), QA
|
||||
Task description:
|
||||
- Mount the full deployments route tree under `/releases/deployments` so detail URLs resolve inside the canonical Releases shell.
|
||||
- Verify that the deployment list no longer links to unreachable routes or invalid release-version URLs.
|
||||
|
||||
Completion criteria:
|
||||
- [x] `/releases/deployments/:deploymentId` renders the deployment detail workspace instead of fallback content.
|
||||
- [x] Deployment list actions do not point at non-existent `/releases/:version` routes.
|
||||
- [x] Route-focused regression coverage exists for the canonical Releases mount.
|
||||
|
||||
### FE-LIVE-DEP-002 - Make deployment detail actions functional or remove them
|
||||
Status: DONE
|
||||
Dependency: FE-LIVE-DEP-001
|
||||
Owners: Developer (FE), Product Manager
|
||||
Task description:
|
||||
- Replace console-log-only deployment detail actions with real operator flows where safe, and remove misleading actions where no live contract exists yet.
|
||||
- Keep the detail workspace internally consistent in the canonical `/releases` host even while the legacy deployment API remains unavailable.
|
||||
|
||||
Completion criteria:
|
||||
- [x] Visible deployment detail actions either navigate/download/copy successfully or are no longer shown.
|
||||
- [x] Legacy `/deployments` path assumptions are removed from the mounted detail workspace.
|
||||
- [x] Checked-feature documentation records the repaired live contract and any intentionally deferred capability.
|
||||
|
||||
## Execution Log
|
||||
| Date (UTC) | Update | Owner |
|
||||
| --- | --- | --- |
|
||||
| 2026-03-08 | Sprint created after live Playwright found `/releases/deployments/:deploymentId` falling through to fallback content and the deployment list generating dead release links. | Developer (FE) |
|
||||
| 2026-03-08 | Re-mounted `/releases/deployments` as the full lazy route tree, removed dead release-version anchors from the list surface, and added route/list regression coverage. | Developer (FE) |
|
||||
| 2026-03-08 | Replaced console-log-only detail actions with real evidence-tab, replay, proof-chain, artifact, and log flows; removed rollback from the mounted UI because the live deployment operate API is still absent. | Developer (FE) |
|
||||
| 2026-03-08 | Verified targeted Angular coverage (`15/15`), rebuilt the web bundle, synced `dist/stellaops-web/browser` into `compose_console-dist`, and passed the live Playwright regression script `scripts/live-releases-deployments-check.mjs` against `https://stella-ops.local`. | QA |
|
||||
|
||||
## Decisions & Risks
|
||||
- Decision: keep the current deployment detail workspace as a bounded, read-only `/releases/deployments/:deploymentId` surface because the Releases shell still owns deployment history, but avoid implying live operate/rollback contracts that the backend does not currently provide.
|
||||
- Risk: the legacy deployment HTTP API (`/api/v1/release-orchestrator/deployments`) is currently unavailable in the live stack, so this sprint must avoid binding visible routes to dead backend contracts.
|
||||
- Mitigation: repair route ownership first, then keep the detail page honest about which actions are available in the current canonical host.
|
||||
- Decision: `Open Evidence` now focuses the local evidence tab, while evidence/proof-chain hand-offs route to canonical `/evidence/capsules` and `/evidence/proofs` entry points instead of fabricating a capsule-detail deep link that may not exist in live data.
|
||||
- Decision: the evidence workspace and proof-chain links preserve `returnTo` so operators can jump back to the deployment detail route without losing the canonical Releases host.
|
||||
|
||||
## Next Checkpoints
|
||||
- 2026-03-08: route tree reconnected and live detail render verified.
|
||||
- 2026-03-08: detail actions rechecked with Playwright after bundle sync.
|
||||
Reference in New Issue
Block a user