Make registry-admin audit route self-identifying

This commit is contained in:
master
2026-03-11 19:09:46 +02:00
parent 6afd8f951e
commit 8eec0a9dee
5 changed files with 308 additions and 0 deletions

View File

@@ -0,0 +1,68 @@
# Sprint 20260311_008 - FE Live Registry Admin Audit Route Identity
## Topic & Scope
- Prove whether the `registry-admin` audit tab failure is a real route break or a weak post-navigation page identity.
- Keep the fix inside the web workspace by making the audit child route render explicit audit-specific content after navigation.
- Add focused regression coverage and rerun the live changed-surfaces sweep on `https://stella-ops.local`.
- Working directory: `src/Web/StellaOps.Web`.
- Expected evidence: root-cause notes, focused Angular spec, rebuilt web bundle, live Playwright pass for the registry-admin audit action.
## Dependencies & Concurrency
- Depends on the live compose stack being healthy and reachable.
- Safe parallelism: limited to `src/Web/StellaOps.Web` plus this sprint file.
## Documentation Prerequisites
- `AGENTS.md`
- `docs/qa/feature-checks/FLOW.md`
## Delivery Tracker
### FE-REGISTRY-AUDIT-001 - Root-cause the audit-tab live failure
Status: DONE
Dependency: none
Owners: QA, 3rd line support
Task description:
- Reproduce the failing `audit-tab` action from the live changed-surfaces sweep and determine whether the click fails, the route fails, or the target route lacks truthful audit-specific content.
Completion criteria:
- [x] Live authenticated Playwright proves whether `/ops/integrations/registry-admin/audit` is reached.
- [x] Root cause is recorded with concrete evidence.
### FE-REGISTRY-AUDIT-002 - Make the audit route self-identifying
Status: DONE
Dependency: FE-REGISTRY-AUDIT-001
Owners: Product Manager, Architect, Developer
Task description:
- Update the registry-admin audit child view so the audit route renders an explicit title/description/count summary. The target page must clearly indicate that the user is in the audit trail, not just inside the generic registry shell.
Completion criteria:
- [x] The audit child view renders an audit-specific heading.
- [x] The audit state remains clear in loading, empty, and populated cases.
- [x] Focused component tests cover the visible route identity.
### FE-REGISTRY-AUDIT-003 - Reverify the live registry-admin action flow
Status: DONE
Dependency: FE-REGISTRY-AUDIT-002
Owners: QA
Task description:
- Rebuild the web bundle, sync it into the live stack, and rerun the changed-surfaces or focused registry-admin Playwright flow to confirm the audit tab now produces truthful post-navigation evidence.
Completion criteria:
- [x] Web build passes.
- [x] Live Playwright confirms the audit tab lands on `/registry-admin/audit`.
- [x] Live Playwright confirms the page exposes audit-specific visible text.
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-03-11 | Sprint created after the changed-surfaces sweep flagged the registry-admin audit tab. | QA |
| 2026-03-11 | Authenticated Playwright repro proved the click navigates correctly to `/ops/integrations/registry-admin/audit`; the real defect is that the target child view exposes no audit-specific heading, so the route is not self-identifying. | QA / 3rd line support |
| 2026-03-11 | Added explicit audit title/summary content to `PlanAuditComponent`, covered it with focused Angular specs (`2/2` across the registry-admin shell and audit view), rebuilt the web bundle, synced it into `compose_console-dist`, restarted `stellaops-router-gateway`, and passed the focused live Playwright proof in `live-registry-admin-audit-check.mjs` with `actionOk=true` and zero runtime errors. | Product / Architect / Developer / QA |
## Decisions & Risks
- Decision: treat this as a product defect, not a harness change. The audit route is real, but without audit-specific visible identity the user cannot reliably confirm the navigation succeeded.
- Risk: only checking URL would hide regressions where the shell changes but the intended audit view does not become obvious to the user.
- Decision: use a focused live Playwright check for this slice instead of re-running the full changed-surfaces matrix after every small route-identity fix. That preserves truthful verification while staying within the low-churn runtime budget.
## Next Checkpoints
- Move to the next live route/action defect from the changed-surfaces and broader action sweeps after committing this registry-admin repair.