CH-006: Establish the first M-001 event-priority evidence door

[flemming-n-larsen]

Acceptance brief

Plan item: M-143 under M-001 — wanted: yes.

Criterion resolution:

• EVT-001: retired by IDR-005; no handler-order behavior is claimed because the named classic robot does not observe handler order.
• EVT-015: verifies. EventPriorityConformanceTest runs the bridge-owned two-phase priority probe against read-only sample.Target on classic and Tank Royale. The probe first raises scan priority and requires a scan callback inside onHitWall, then lowers scan priority and requires that the same blocked-window callback is absent.

What merge binds: IDR-005's narrow event-priority boundary, EVT-015 as the successor criterion, and M-143 complete. It supersedes the accepted meaning of EVT-001; no unmerged base is authorized or required.

Evidence on commit e509d7997151c135cf33ec5f176536736a64746:

• ./gradlew :robocode-api:test --rerun-tasks — pass.
• ./gradlew :conformance-test:test -PtankRoyaleBotApiVersion=1.2.0 --rerun-tasks — 13 tests pass with the matched local Tank Royale API/runner pair.
• clue validate --forbid-changes — pass.
• Tier 3 completed with two unrelated pre-existing bridge-only watch-list filesystem errors (AD.CodaFirst_1.1, ag.Gir_0.99); no M-001 event-dispatch failure.
• Mandatory agentic review pass 3 — clean; EVT-015 resolves as verifies.

Documentation impact: updated CAP-001 criteria, design, overview, IDR index, plan bookkeeping, and the identity ledger; the transient CH-006 workspace was digested and removed.