TASK-004A: Diagnostics State and Timeline
AI Execution Profile
- Model class:
Balanced - Reasoning effort:
Medium
Scope
- extend canonical app state with structured diagnostics timeline models
- add bounded retention behavior for recent diagnostics
- define any minimal operational counter or snapshot models needed by later sub-tasks
- add application-level helpers or services for publishing diagnostics if needed
- keep the new state usable by UI and tests without introducing hidden view-only models
Copy/Paste Prompt
text
Implement only TASK-004A: Diagnostics State and Timeline.
Read first:
- docs/specs/SLICE-004-operational-maturity.md
- docs/adrs/ADR-001-use-central-app-state-store.md
- docs/adrs/ADR-004-use-one-operational-maturity-slice-before-specialized-modules.md
- docs/tasks/slice-004/TASK-004A-diagnostics-state-and-timeline.md
Goal:
- Add the canonical diagnostics timeline and operational state primitives needed for the operational maturity slice.
Scope:
- Extend AppState with structured diagnostics timeline models.
- Keep diagnostics history bounded and deterministic.
- Add minimal counter or snapshot models that later tasks can project in the UI.
- Add application-level publishing helpers only if they simplify later workflow changes.
Do not:
- Build or redesign XAML yet
- Implement simulator profile loading yet
- Change run summary persistence yet
Important:
- Diagnostics timeline must live in canonical AppState
- Avoid hidden UI-only caches
- Keep the shape simple enough for later tests and projections