Deduplicate

Single goal: remove duplicated knowledge by placing one canonical implementation and having every consumer use it.

Do not broaden into general cleanup, renaming, layout rewrites, or smell hunting. If something is not duplication (or forced by a correct dedupe), leave it alone.

Core Rules

• Preserve behavior, public APIs, and data formats unless the user authorizes a change.
• Deduplicate knowledge that will drift, not coincidental structural similarity.
• Prefer a little intentional duplication over a wrong abstraction. Extract only when the copies share one stable concept, name, and change reason.
• Reuse an existing home for the concept when one exists. Do not invent a competing utils / helpers / shared dump.
• Keep edits reviewable: one duplication cluster (or tightly related cluster) per pass when the scope is large.
• Preserve unrelated user changes.

Establish Scope

• Targeted: only the named file, directory, module, feature, or duplication cluster. Follow references outside the target for understanding; change them only when required to wire the shared source.
• Full codebase: search first-party code for duplication hotspots. Exclude generated files, vendored code, build output, caches, lockfiles, snapshots, and migrations unless they are the stated problem.