- Plan 02: Added key_link clarifying CmsPageService.render populates
PageRenderContext.components before template rendering. Updated
Task 2/3 actions to emphasize component initialization flow.
- Plan 03: Split into 03 (storage + library core) and 03b (image
processing + routes) to reduce scope from 9 files to 7+4 files.
Estimated context reduced from ~65% to ~45% each.
- Plan 03b: New plan for ImageProcessor and MediaRoutes. Added
specific curl command with -F flags and expected JSON response.
- Plan 05: Added plugin integration test (MenuPluginIntegrationSpec)
demonstrating custom menu item type registration, resolution, and
template rendering per CONT-09 requirement.
- Plan 06: Reframed must_haves truths from implementation details
to user-observable outcomes (e.g., 'Developer edits template file,
browser refresh shows changes without server restart')
- Roadmap: Updated Phase 9 from 6 to 7 plans.
Phase 02: Plugin System
- 3 plans in 3 waves (sequential)
- 02-01: Plugin discovery and manifest parsing
- 02-02: Lifecycle management and dependency resolution
- 02-03: Extension API with type-safe plugin-to-plugin communication
- Ready for execution
- Updated 01-02-PLAN.md Task 3 to NOT run migrations on startup
- Updated must_haves truth: 'run via ZIO effect when invoked' (not 'on startup')
- Updated verification/success_criteria to reflect manual migration
- Updated ROADMAP success criteria #3 to match CONTEXT.md decision
Per CONTEXT.md line 22-23: migrations run manually via CLI command
