wi event has no 'correction' eventType, so corrections land under whatever type each author picks

wi event rejects eventType "correction" (400, not in the canonical vocabulary), so a correction has to be filed under some other type and the type chosen varies by author. Measured 2026-09-12, two agents, same night, same wall, two DIFFERENT substitutes: coder-terra-cc used 'note' for T59-VERSION-CORRECTION-20260912; pmmaster-evolutiva-cc used 'decision' for a retraction on VENUS-350. So corrections are already scattered across at least two event types, which is worse than one consistently wrong type - a later reader scanning for corrections by type finds nothing, and cannot even learn the convention by example. This matters now because OPS-246 is expected to produce a run of version corrections across several projects: gitpush.sh absorbs a hand-set version as the BASE and increments, so every pre-push version an agent has stated may need correcting on its row. Ask: add 'correction' to the canonical eventType vocabulary. Additive only - no existing type changes meaning, no migration of past events, and the existing 'note'/'decision' uses stay valid. Acceptance is that wi event <ref> correction "body" exits 0 and the type round-trips through wi events. Deliberately NOT part of OPS-246 itself: that row is a conventions fix about where a version number is read from, this is a tracker vocabulary gap that outlives it. Registry names coder-basquetwi-cc as the wi CLI maintainer and that agent does not resolve (see OPS-243), so this is routed to the registry backup.