TASK-003A: Recipe Catalog Contracts and Validation Model
AI Execution Profile
- Model class:
Budget or Balanced - Reasoning effort:
Low to Medium
Scope
- add the application-facing recipe catalog abstraction
- define any minimal recipe catalog entry or validation result models needed by this slice
- keep canonical loaded recipe behavior compatible with existing app state and guards
- define validation responsibilities clearly without adding file I/O yet
Copy/Paste Prompt
text
Implement only TASK-003A: Recipe Catalog Contracts and Validation Model.
Read first:
- docs/specs/SLICE-003-json-recipe-file-management.md
- docs/adrs/ADR-001-use-central-app-state-store.md
- docs/adrs/ADR-003-use-json-recipe-catalog-before-in-app-editor.md
- docs/tasks/slice-003/TASK-003A-recipe-catalog-contracts-and-validation-model.md
Goal:
- Add the application-facing contracts and minimal validation models for file-backed recipe management.
Scope:
- Add a recipe catalog abstraction in the application layer.
- Define the minimal models needed to represent available recipes and validation outcomes.
- Preserve existing canonical loaded recipe semantics in AppState and command guards.
Do not:
- Implement file access yet
- Implement startup scanning yet
- Build UI yet
Important:
- Keep file access out of the presentation layer
- Do not invent duplicate runtime recipe models if existing Recipe/ScanPoint contracts already fit