fix(09): revise plans based on checker feedback
- 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.
This commit is contained in:
@@ -14,14 +14,14 @@ autonomous: true
|
||||
|
||||
must_haves:
|
||||
truths:
|
||||
- "Template file changes trigger Pebble cache invalidation"
|
||||
- "Page/layout/partial modifications reflect immediately in browser"
|
||||
- "Hot reload only active in development mode"
|
||||
- "File watcher uses OS-native WatchService (not polling)"
|
||||
- "Cache invalidation is targeted (not full cache clear)"
|
||||
- "Developer edits template file, browser refresh shows changes without server restart"
|
||||
- "Page/layout/partial modifications reflect immediately after save"
|
||||
- "Hot reload only active when DEV_MODE environment variable is true"
|
||||
- "File system changes detected efficiently without CPU overhead"
|
||||
- "Only changed template is reloaded, not the entire cache"
|
||||
artifacts:
|
||||
- path: "summercms/src/hot/FileWatcher.scala"
|
||||
provides: "File change detection using WatchService"
|
||||
provides: "File change detection"
|
||||
contains: "class FileWatcher"
|
||||
- path: "summercms/src/hot/HotReloadService.scala"
|
||||
provides: "Reload orchestration service"
|
||||
@@ -500,12 +500,11 @@ After all tasks complete:
|
||||
|
||||
<success_criteria>
|
||||
- Hot reload only active when DEV_MODE=true and HOT_RELOAD=true
|
||||
- FileWatcher uses OS-native WatchService (not polling)
|
||||
- Template changes invalidate specific template cache entry
|
||||
- Page changes also trigger router rebuild
|
||||
- Changes reflect immediately without JVM restart
|
||||
- Template file saved -> changes visible on next browser refresh (no restart)
|
||||
- Targeted invalidation: only changed template reloaded, not all templates
|
||||
- Page changes also trigger router rebuild for URL changes
|
||||
- Production mode uses full caching for performance
|
||||
- Event debouncing prevents rapid reload spam
|
||||
- Event debouncing prevents rapid reload spam during fast typing
|
||||
</success_criteria>
|
||||
|
||||
<output>
|
||||
|
||||
Reference in New Issue
Block a user