Refactor & Safety Pass

You are performing a guarded refactoring operation. Follow every section in order — do not skip the pre-check or post-check.

Pre-Refactor Checklist

Before touching any code:

1. Identify all consumers — grep for imports and usages of the target across the entire project.
2. Check test coverage — find test files that cover the target (matching file names, import paths, or direct references).
3. Note public API surface — list every exported type, function, component, or constant from the target.
4. Assess blast radius — count how many files will change. If >20 files, warn the user and confirm before proceeding.

During Refactor — Safety Rules

• Preserve all public exports, or update every consumer that depends on them.
• Update barrel files (index.ts, index.js) when moving or renaming exports.
• Maintain backward-compatible type signatures unless the user explicitly intends a breaking change.
• Keep git commits atomic: one logical change per commit.
• If renaming: grep the entire project for string references — test IDs, route names, analytics events, config keys, comments.

Refactor Patterns

Rename

• Find-and-replace across the entire project, including strings, comments, and test IDs.
• Check dynamic references (string interpolation, object key access).

Extract function / component

• Move to the appropriate directory following existing project conventions.
• Export from the new location, update the original to import from it.
• Update barrel files if the project uses them.

Move file

• Update all import paths that reference the old location.
• Update barrel exports.
• Check for relative path breakage in nearby files.
• Delete the old file — do not leave a copy behind.

Change signature

• Update all call sites to match the new signature.
• Update type definitions.
• Update tests that call the function or component.

Inline

• Verify the abstraction has a single usage (or very few) before inlining.
• Remove the now-dead abstraction after inlining.
• Remove its export from barrel files.

Post-Refactor Verification

After completing the refactor:

1. Grep for old name/path — should return zero hits. If any remain, update them.
2. Check for orphaned files — if a new file was created, confirm the old file was deleted (unless intentionally keeping both).
3. Check for dead exports — things still exported but no longer imported anywhere.
4. Verify tests reference valid targets — test imports and assertions should point to the new name/path.