ahmido
0a1ecf99c9
Applied diagnostic surface contract rules to Audit Log inspect modal and Support Diagnostics action context, consolidating raw diagnostic data into safe modals according to Spec 374. Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #445
46 lines
2.8 KiB
Markdown
46 lines
2.8 KiB
Markdown
# Requirements Checklist: Spec 374 - Diagnostic Entry Point and Support Diagnostics Consolidation v1
|
|
|
|
**Purpose**: Validate preparation readiness for Spec 374 before implementation.
|
|
**Created**: 2026-06-12
|
|
**Feature**: `specs/374-diagnostic-entry-point-support-diagnostics-consolidation/spec.md`
|
|
|
|
## Spec Quality
|
|
|
|
- [x] CHK001 The selected candidate is directly provided by the user and aligned with current repo truth.
|
|
- [x] CHK002 The completed-spec guardrail excludes Spec 373 as a refresh target and treats it as context.
|
|
- [x] CHK003 The spec states the concrete operator workflow: start diagnostics from Environment Dashboard and distinguish Support Diagnostics from Repair Diagnostics.
|
|
- [x] CHK004 The spec defines the smallest enterprise-capable slice and rejects a diagnostic hub.
|
|
- [x] CHK005 Functional requirements are testable and avoid implementation-only wording where product behavior is enough.
|
|
- [x] CHK006 Out-of-scope boundaries are explicit for provider, permission, evidence, system, OperationRun, customer/auditor, and bloat-guard work.
|
|
- [x] CHK007 Risks, assumptions, and non-blocking open questions are recorded.
|
|
|
|
## Constitution And Guardrails
|
|
|
|
- [x] CHK008 UI Surface Impact is completed and does not conflict with no-impact handling.
|
|
- [x] CHK009 UI/Productization Coverage classifies the dashboard, support modal, repair diagnostics page, and deferred destinations.
|
|
- [x] CHK010 Cross-cutting shared pattern reuse names existing builders/helpers/actions before any new local work.
|
|
- [x] CHK011 OperationRun UX impact states no new start/completion behavior and limits usage to existing links.
|
|
- [x] CHK012 Provider boundary treatment keeps provider/permission diagnostics out of repair diagnostics.
|
|
- [x] CHK013 Proportionality review states no new persisted truth, abstraction, enum/state family, or diagnostic framework.
|
|
- [x] CHK014 RBAC and destructive-action safety requirements are explicit for existing repair actions.
|
|
- [x] CHK015 Test governance names the narrowest proving lanes and fixture cost controls.
|
|
|
|
## Task Readiness
|
|
|
|
- [x] CHK016 `tasks.md` includes repo-truth and source-audit tasks before runtime edits.
|
|
- [x] CHK017 `tasks.md` includes tests before implementation for dashboard entry, repair diagnostics, and support modal behavior.
|
|
- [x] CHK018 `tasks.md` includes browser smoke and screenshot tasks for reachable surfaces.
|
|
- [x] CHK019 `tasks.md` includes final validation and artifact close-out tasks.
|
|
- [x] CHK020 `tasks.md` includes explicit non-goals to prevent scope creep.
|
|
|
|
## Preparation Outcome
|
|
|
|
- [x] CHK021 Candidate Selection Gate result: pass.
|
|
- [x] CHK022 Spec Readiness Gate result: pass for preparation.
|
|
- [x] CHK023 Review outcome class: acceptable-special-case.
|
|
- [x] CHK024 Workflow outcome: keep.
|
|
|
|
## Notes
|
|
|
|
This checklist validates preparation only. It does not claim runtime implementation, browser smoke, or test execution.
|