TASK-004D: Simulator Profiles and Configuration
AI Execution Profile
- Model class:
Balanced - Reasoning effort:
Medium
Scope
- add the application and infrastructure contracts needed for named simulator profiles
- load available profiles from configuration at startup
- expose current and available profile state through canonical app state
- allow safe operator selection of profiles for future operations
- emit diagnostics entries when profile changes occur
Copy/Paste Prompt
text
Implement only TASK-004D: Simulator Profiles and Configuration.
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-004D-simulator-profiles-and-configuration.md
Goal:
- Replace scattered simulator constants with named configuration-backed profiles that operators can select safely.
Scope:
- Add profile contracts and configuration loading.
- Load named profiles at startup and expose them through AppState.
- Allow profile selection only for future operations, not mid-run mutation of active work.
- Apply selected profile behavior through existing simulator abstractions where practical.
- Emit diagnostics entries for profile changes.
Do not:
- Add hot reload or a profile editor
- Bypass the existing application boundaries
- Couple profile loading directly to XAML
Important:
- Keep configuration loading deterministic
- Prefer a small believable parameter set over a giant options object