reorganize-files

Reorganizing files without breaking imports requires an exhaustive reference sweep that updates static imports, string URL paths, CSS url() usage, and metadata references after moving files. It enforces verification via typecheck and stale-segment grep to catch silent path breakage.

Refactoring a messy public directory safely requires an approval-gated workflow that proposes a coherent target structure based on filename signals before any moves occur. It then applies an atomic edit pass to update configuration path embeddings and verify correctness.

Updating CSS url() references and JSON-LD metadata paths after moving assets requires a comprehensive reference sweep across all path-based pointers. This includes static bundler imports, sitemap entries, and OG tags to ensure no old path segments remain post-move.

Yes, reorganizing loose feature area files without manual updates is possible using an inventory-driven approach that collects all files and applies an atomic edit pass. It automatically updates configuration-embedded paths and test fixtures, finishing with typecheck verification.

The main limitation of automated file path updates is the risk of missing silent breakage in complex metadata, OG tags, or sitemap entries if the reference sweep is not exhaustive. Stale-segment grep is required post-move to ensure no old path segments remain hidden in config embeddings.