@fluid-app/fluid-cli-theme-dev 0.1.48 → 0.1.50

package/README.md

@@ -39,11 +39,20 @@ The dev server will:
 
 For a pulled theme, a newly created dev theme is a server-side reference clone
 of the pulled source. It preserves theme content and DAM/ImageKit references,
-so initial dev startup does not reseed every asset from the working copy.
-Once the CLI has seen that dev theme, later startups compare local files to the
-pull shadow and send only that local diff instead of downloading the complete
-remote resource index. A newer source pull, changed ImageKit manifest, or web
-editor write invalidates the shortcut and falls back to the remote comparison.
+so initial dev startup does not reseed every asset from the working copy. The
+CLI keeps a compact local index of the development theme's acknowledged
+checksums and version. Later startups validate that version, compare local files
+to the cached dev state, and send only the actual changes without downloading
+the complete remote resource index. A web-editor write, changed ImageKit
+manifest, missing or malformed cache, or interrupted write invalidates the
+shortcut and falls back to the full remote comparison. Set
+`FLUID_THEME_DEV_DISABLE_SHADOW_SYNC=1` to force that comparison as an emergency
+rollback.
+
+Theme paths that differ only by letter case are refused before pull, push, or
+dev writes. Windows separators are normalized before comparison. Default macOS
+and Windows filesystems cannot preserve both resources, so continuing would
+replace one path and delete the other.
 
 | Flag                       | Default     | Description                               |
 | -------------------------- | ----------- | ----------------------------------------- |