# Neon profile sync active override report

- date: 2026-05-25
- repo: davisdiehl/lilarcade
- pull request: #514
- merge commit: 1505ab8758093d3220e558b8ff6982f31fd36504
- Amplify job: 692
- evidence role pattern: current_target

## Catch

The local Neon profile sync gate could pass while the checked-in durable
current-target profile still described an older approved candidate.

The app source had one active durable override:

- `monkberry-moon-delight-tab-chord-008-to-016-preservation-candidate`
- expected `chord: 0.16`

But the synced static profile still referenced:

- `monkberry-moon-delight-tab-chord-minus-01-approved-candidate`
- expected `chord: 0.18`

That meant a reviewer or agent could run a green profile-sync check and still
carry stale current-target proof evidence.

## Fix

LilArcade PR #514 changed `scripts/syncNeonRiddleProfiles.mjs` so the
`neon-step-sequencer-durable-current-target` profile is generated from the
active durable override file instead of blindly copying the pack sample.

The synced profile now records:

- `override_id`: `monkberry-moon-delight-tab-chord-008-to-016-preservation-candidate`
- `generated_from_active_durable_override`: `monkberry-moon-delight-tab-chord-008-to-016-preservation-candidate`
- `active_durable_override_count`: `1`
- expected `chord: 0.16`

## Validation

Local checks passed:

- `npm run proof:sequencer:check-profiles`
- `node --test scripts/__tests__/syncNeonRiddleProfiles.test.mjs scripts/__tests__/neonDurableCurrentTargetProof.test.mjs`
- `npm test`
- `npm run build`
- local Riddle Proof Playwright current-target run

GitHub CI passed on PR #514.

Amplify job `692` deployed commit `1505ab8758093d3220e558b8ff6982f31fd36504`.

The post-deploy current-target proof passed against:

`https://main.dlwavl00q582x.amplifyapp.com/games/drum-sequencer?song=monkberry-moon-delight-tab&mix=profile&view=trainer&instrument=chord`

Key deployed evidence:

- status: `passed`
- HTTP status: `200`
- selected song matched
- mix profile matched
- contract level for `chord` matched `0.16`
- profile level for `chord` matched `0.16`
- visible UI token matched `0.16X`
- peak: `0.7768`
- RMS: `0.1116`
- clipping: `false`
- fatal console count: `0`

## Boundary

This proves the deployed current target and checked-in profile agree with the
active durable override. It does not prove subjective mix taste.