archivist-duplication-auditor

To audit duplicate code without modifying files, compare inventory implementations for behavior drift across date/time handling and validation. The auditor writes a formal report under docs/code-audits/reports/, identifying duplicates while avoiding automatic edits to preserve intentional design.

Behavior drift occurs when copied logic diverges over time. It is identified by reading inventory files and comparing implementations across areas like DTO mapping, lifecycle actions, and API error mapping to detect near-duplicated logic that has functionally diverged from the original pattern.

Generate a code audit report by running the auditor against your target project. It compares repeated UI and component patterns, writes findings to docs/code-audits/reports/, and suggests lightweight remediation mitigations without applying automatic migrations or edits to the source.

No, the duplication auditor does not apply automatic fixes or migrations. It keeps remediation suggestions lightweight, producing a structured report documenting findings while preserving intentional design by avoiding automatic edits to the codebase.

Yes, you can audit custom field handling and list/query helpers for near-duplicate logic. The auditor specifically targets these areas, alongside validation and date/time handling, reading inventory to compare implementations and report any behavior drift.