# 4-duplicated

Pins the **stale / duplicated** taxonomy edge → `dedupe` exact-edit kind →
derived `auto` tier (dedupe is non-destructive + reversible). The `canonical_ref`
points at the surviving copy, `docs/setup.md`.

**Scanner signal exercised:** `stale_name_location` (on `docs/setup-legacy.md`,
"legacy" in the name).

**KNOWN GAP — surface for human review:** the scanner has *no* dedicated
duplication signal; it cannot detect that `setup-legacy.md` is byte-for-byte
identical to `setup.md`. This case therefore rides a *co-occurring*
`stale_name_location` signal as the deterministic trigger, while the *duplicated*
classification itself is the model's judgment (the two files being identical). The
canonical `docs/setup.md` is present in `input/` and correctly stays a cleared,
zero-signal shortlist entry. This is the one case where the intended subtype is not
backed by a matching scanner signal.