stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 2 Releases Wiki Activity

Preserve deployment evidence navigation scope

Browse Source
This commit is contained in:
master
2026-03-10 13:35:00 +02:00
parent 1fe3f489f1
commit b302a5a3d6
4 changed files with 185 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

47
docs/implplan/SPRINT_20260310_025_FE_releases_deployment_evidence_scope_preservation.md Normal file
View File

@@ -0,0 +1,47 @@
# Sprint 20260310-025 - FE Releases Deployment Evidence Scope Preservation
## Topic & Scope
- Preserve active tenant/region/environment/time-window scope through deployment-detail evidence and replay actions so release operators do not fall into stale evidence context after drilling into a deployment.
- Tighten the existing live releases deployment Playwright harness so this class of scope regression fails explicitly in future scratch iterations.
- Working directory: `src/Web/StellaOps.Web`.
- Allowed coordination edits: `docs/implplan/SPRINT_20260310_025_FE_releases_deployment_evidence_scope_preservation.md`.
- Expected evidence: focused Angular scope tests and a live releases deployment Playwright run with scoped evidence/replay links.
## Dependencies & Concurrency
- Depends on the authenticated local stack being reachable through `https://stella-ops.local`.
- Safe parallelism: avoid unrelated search or topology edits while this release-detail iteration is in progress.
## Documentation Prerequisites
- `AGENTS.md`
- `docs/qa/feature-checks/FLOW.md`
- `docs/implplan/SPRINT_20260308_026_FE_live_releases_deployments_route_and_action_repair.md`
## Delivery Tracker
### FE-DEPLOY-SCOPE-001 - Preserve scoped evidence and replay handoffs
Status: DONE
Dependency: none
Owners: QA, Developer, Architect
Task description:
- Update deployment-detail navigation so back-navigation, replay verify, evidence workspace, and proof-chain links all preserve the active shell scope instead of falling back to stale global context.
- Add focused regression tests and harden the live Playwright check so scope drift becomes a failing result.
Completion criteria:
- [x] Deployment detail evidence and proof links merge active query scope.
- [x] `returnTo` emitted by deployment detail preserves the active context query parameters.
- [x] Live releases deployment Playwright evidence/replay checks fail on scope drift and pass on the fixed stack.
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-03-10 | Sprint created after the live releases deployment sweep showed deployment evidence and proof-chain actions reopening under `eu-west/eu-stage/7d` instead of the active `us-east/stage` scope. | Developer |
| 2026-03-10 | Added focused deployment-detail scope regressions (`2/2` passing), rebuilt the web shell, synced the live bundle, and reran the Playwright releases deployment sweep cleanly with scoped replay/evidence/proof URLs and no remaining scope issues. | Developer |
## Decisions & Risks
- Decision: preserve scope at the deployment-detail source by emitting scoped `returnTo` URLs and merged query params rather than relying on downstream evidence pages to guess the active context.
- Risk: similar release-detail surfaces may still encode incomplete `returnTo` state.
- Mitigation: strengthen each live action harness to assert scoped downstream URLs, not just page reachability.
## Next Checkpoints
- Run focused deployment-detail scope tests.
- Rerun the live releases deployment Playwright check and commit the fix.