frontend-refactor-worker

Automating frontend file moves requires coordinating directory changes with consistent import path updates and symbol renames across modules. This workflow propagates changes to configuration files like vite.config.ts and AGENTS.md to maintain codebase integrity during refactoring.

Validating frontend refactors involves running sequential checks for type-check, lint, unit tests, and build steps. This process enforces safety safeguards against broken deployments by verifying that file moves, import updates, and symbol renames pass end-to-end validation.

Renaming symbols during frontend refactoring can preserve dual-name exports by applying consistent propagation rules across modules. This workflow handles symbol renames while maintaining backward compatibility for existing import statements throughout the codebase.

Updating configuration files like vite.config.ts and AGENTS.md is supported as part of a feature refactor. The workflow applies targeted config file updates alongside file moves, import path changes, and symbol renames to ensure all references remain consistent.

Large frontend codebases require consistent propagation of changes across interconnected modules and configuration files. This workflow centralizes coordinated refactor tasks—moving files, updating imports, and renaming symbols—while running comprehensive validation to catch cross-module breakages.

Validation checks for import updates and file moves include sequential type-check, lint, unit tests, and build verification. These end-to-end safeguards prevent broken deployments by ensuring all coordinated refactor changes pass before integration.