# v2.69 engine-switch speed evidence

- Added a dedicated `GS: x knots` pilot-log line immediately after each engine started/stopped line.
- Preserves existing `Engine N: Started/Stopped` wording for server/analyser compatibility.
- Supports DB-backed single-engine taxi detection without adding client-side scoring.

# v2.68 submit verification and map centre fix

## Changed
- Explicit PIREP submit no longer clears purely because a POST completed.
- A non-auth/non-session uncertain submit response now triggers an immediate JetVA logbook verification for the current flight.
- If the matching official JetVA PIREP is found, the client records that PIREP ID and runs the normal successful clear/reset path.
- If the matching official JetVA PIREP is not found, the client keeps the existing local resend protection.
- Option C live map aircraft follow now recentres on the aircraft marker after each active tracking update, removing the old route-box centre offset behaviour while tracking.

## Not changed
- No BlueSky/kACARS changes.
- No server/API changes.
- No database/schema changes.
- No scoring/profile changes.
- No route/FL lock changes.

# v2.68 submit clear return fix

- Client submit flow no longer treats a completed non-auth HTTP 500 wrapper response as an automatic local-failed resend case.
- If the explicit Send PIREP POST completed and was not auth/session/network failure, Jet Track locks as filed and runs the existing UI clear path.
- This prevents stale local resend queue entries when JetVA/phpVMS has already created and accepted the PIREP but the wrapper confirmation response is non-2xx.
- No scoring, server liveupdate, route/FL lock, evidence capture, resolver, or BlueSky logic changed.

# v2.67 reset/log cleanup
- Full post-filing and post-resend reset now clears the completed session, stale route/FL/DEP/ARR, filed badge, parked/right-side panel, PFD/status values, aircraft marker, flown path, route line and map markers.
- No-bid refresh after filing now returns to a clean idle/no-booked-flight state instead of leaving the previous completed flight visible.
- Pilot-facing excessive_vertical_speed_spike spam is compressed to one summary line containing max VS and sample count.
- Display-only negative zero values such as VS: -0 fpm and Bank: -0° are clamped to 0.
- Positive landing-rate values are labelled as possible bounce/positive contact evidence without changing raw evidence or normal landing-rate capture.
- No scoring, BlueSky/kACARS, database schema, resolver, reverse-thrust, Route/FL locking, SimBrief, engine detection, PIREP filing, auth/security, or logbook de-dupe changes.

# v2.66 route/FL lock input fix
- Fixed Option C overlay Route and Flight Level boxes still accepting typed input after Start Tracking.
- Lock state is now pushed to the overlay immediately when tracking starts or the session is sealed.
- Overlay Route/FL controls become disabled/read-only once the session Route/FL values are authoritative.
- Flight Level overlay input now accepts digits only; alphabetic and other non-numeric characters are stripped before posting to C#.
- No scoring, resolver, BlueSky, server endpoint, database, PIREP submission, or logbook logic changes.

# v2.66 cursor/input fix
- Fixed Route overlay textarea cursor jumping to the far right while typing.
- Fixed Flight Level overlay field being reformatted/re-written while the pilot is typing.
- The active Route/FL editor is no longer overwritten by overlay sync until the field is locked or focus leaves the field.
- Removed immediate overlay re-sync from Route/FL keystroke handlers to prevent feedback-loop input jitter.
- No scoring, resolver, BlueSky, database, server endpoint, PIREP submission, or logbook de-dupe changes.

# v2.66
- Route and Flight Level are editable until Start Tracking; SimBrief can prefill but is not required.
- Start Tracking locks the current Route and Flight Level as authoritative session values for the tracked flight/evidence/PIREP context.
- Locked Route/Flight Level values cannot be overwritten by later UI edits, SimBrief refresh, schedule reload, or post-start changes.
- Parked/final pilot-facing IAS/TAS/GS display now clamps negative near-zero noise to 0.
- Removed Actual Max Altitude from the flight-open/header block; final summary output remains.
- Added display-only compression for repeated post-landing flap-change lines; scoring/evidence remains intact.
- No scoring architecture, resolver, BlueSky, database, server endpoint, PIREP submission, or logbook de-dupe changes.
- Note: uploaded client source contains no JetTrack-side G-force landing display/report path, so there is no client-side G-force code change in this package.

# v2.65
- Fixed local-only completed PIREP persistence/resend state when server filing is not confirmed.
- Fixed logbook merge so unsent local flights are not hidden by loose same-day server matches.
- Fixed Send Selected to JetVA button flow: it refreshes JetVA before resend and gives feedback instead of silently doing nothing.
- Muted unreliable speedbrake armed/raw diagnostic spam while preserving actual speedbrake deployment evidence.
- Overspeed evidence now sends both the log event and explicit JetTrack boolean evidence for server scoring.

# Jet Track v2.63

- PIREP filed confirmation OK now triggers the completed-flight UI reset.
- Debrief / PIREP page closes after OK once the reset has completed.
- Retains v2.62 map/state reset, reverse-thrust correction, resolver security, and final snapshot cleanup.
- No resolver, scoring, BlueSky, PIREP count, database, or server endpoint changes.

# Jet Track v2.62

- Reverse thrust stop logging now uses the first sustained stow transition speed, not a delayed low-speed/stopped value.
- Reverse restart noise after rollout stop is locked out once a stop is logged.
- Airborne snapshots suppress irrelevant parking-brake released lines.
- Final approach snapshot now prefers a configured final sample so flap/gear events do not appear inside the snapshot block.
- Approach/final phase logging is held behind descent evidence when descent exists.
- Successful PIREP submit now clears the completed session, route/map/log state immediately on server success before the confirmation popup.
- Option C map reset clears route, aircraft, flown track, and JetVA overlay text/selection.
- v2.61 secured resolver, no-hardcoded-airport, speedbrake raw proof, and pushback cleanup retained.

## v2.66 resend reset fix
- Fixed local logbook resend flow so, when the resent local PIREP belongs to the current completed session, the same post-submit cleanup runs after the success dialog.
- This clears the active flight context, resets the live map/tracking UI, creates a fresh recorder, and closes the logbook window after successful resend.
- Older/local historical resend rows do not reset an unrelated current session.
