# Neon Batch Patch Plan Identity Catch

The local Neon ratchet batch found a handoff ambiguity between two different proof roles.

The approved-candidate step produced a new durable patch plan for `chord 0.18 -> 0.08`, but the existing durable current-target proof was still verifying the already-active source override at `chord 0.18`. Before the fix, both used the same override id:

`monkberry-moon-delight-tab-chord-minus-01-approved-candidate`

That made a planned future patch and the current active target look like the same durable edit even though their mixer levels differed.

## Fix

LilArcade PR #505 changed durable patch-plan ids to include absolute `from-to` mixer levels, so the new planned patch becomes:

`monkberry-moon-delight-tab-chord-018-to-008-approved-candidate`

The ratchet batch now also compares the planned patch with active current-target proof results. If the same id appears with different levels, the batch fails with `planned_override_id_collision`. If the planned patch is not applied yet, the batch records `planned_override_not_applied_yet` as a non-finding handoff.

## Final Receipt

The final focused local batch passed with:

- approved candidate: `chord -0.10`
- planned durable override: `chord 0.08`
- active current-target override: `chord 0.18`
- plan comparison: `planned_override_not_applied_yet`
- current-target findings: `0`
- clipping: `false`
- low level: `false`

## Boundary

This proves the patch handoff identity and current-target semantics are no longer ambiguous. It does not prove the proposed mix is subjectively better.