fix(audit): make detector-ID collisions visible (display + load-time warning)

[ProtocolWarden]

What

The durable upstream half of the detector-ID collision saga (#48 was the first half).

#48 un-masked the count when two detectors share an id — but the displayed finding still showed only the first-registered detector's title. So a .console/task.md violation surfaced as:

[R2] README first H1 does not match repo name

…which silently misdirected a consumer: the reviewer saw a nonsensical "README H1" failure on a CLI PR, classified it ci_misconfigured_check, escalated to a human, and the goal lane stalled for hours chasing a phantom README issue. (Diagnosing it required running the exact custodian, the real boundary artifact, and invoking the .console detector directly.)

Fix — make the collision visible at both points (non-breaking)

• audit_kit/result.py → collision_note(pattern): a marker rendered for any merged (collided) pattern, naming the colliding collision_sources and warning that the title may not match the finding — read the samples. Used by both finding renderers (cli/audit.py, cli/multi.py).

  [MED] [R2] README first H1 does not match repo name — 1 finding(s)  [⚠ DETECTOR-ID COLLISION across: builtin, custom — the title above is only the first-registered detector's; the real finding may be a different one, see samples]
        .console/task.md missing ## Objective
  

• cli/runner.py → _warn_detector_id_collisions(detectors): logs a WARNING at load time for every id registered by more than one detector, listing each source's description — so the collision is fixable at the source (rename the custom detector) instead of discovered the hard way.

No detector ids are renamed — the builtin readme R1/R2 vs reconcile R1/R2 families and custom-plugin ids keep working; the collision is just no longer silent.

Tests

3 new tests (collision marker on/off; load-time warning fires per duplicate and not for unique ids). 1128 existing tests pass; ruff check src + ty clean.

Companion: ProtocolWarden/OperationsCenter#384 renames that repo's colliding .console detectors to OC1/OC2. This upstream fix ensures any repo's future collision is loud, not silent.

🤖 Generated with Claude Code