TASK-003: Implement JSON Recipe File Management

• Status: Ready
• Date: 2026-04-16
• Spec: SLICE-003: JSON Recipe File Management
• ADRs: ADR-001: Use Central App State Store, ADR-003: Use JSON Recipe Catalog Before In-App Editor

Objective

Replace seeded-only recipe loading with a realistic file-backed JSON recipe catalog while keeping recipe selection, load behavior, and diagnostics predictable.

Scope

• add an application-facing recipe catalog abstraction
• implement a configurable folder-backed JSON recipe catalog in infrastructure
• scan recipes on startup
• allow explicit operator refresh of available recipes
• load validated file-backed recipes into canonical app state
• add diagnostics for missing folders, invalid JSON, and validation failures
• add tests for scanning, validation, refresh, and load behavior

Non-Scope

• recipe editing UI
• writing recipes back to disk
• schema migration/version upgrade behavior
• hot reload or file watching

AI Tool Guidance

Do not hand this whole task to one AI chat.

Use the smaller task pack for implementation:

1. TASK-003A: Recipe Catalog Contracts and Validation Model
2. TASK-003B: JSON Recipe Catalog Infrastructure
3. TASK-003C: Startup Scan and Refresh Integration
4. TASK-003D: Operator UI and Selection Flow
5. TASK-003E: Tests and Sample Recipe Assets

The recommended order, cost guidance, and copy/paste prompts are documented in SLICE-003 Task Pack.

Acceptance Criteria Mapping

The implementation must satisfy all acceptance criteria from SLICE-003.