You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ea2e855
Browse filesBrowse the repository at this point in the historyBrowse files
feat(diagnostics): record probes for the whole session, export them together
Validation had to be driven by hand: open a screen, arm a probe, remember a
save button, then export. That is the wrong default while the car is the
instrument. Evidence is collected on a drive, when nobody should be operating
a screen, and the most decision-relevant result — a probe that heard nothing
— is the one a driver is least likely to think worth saving.
The guidance listener and a new session-long signal recorder now arm when the
application starts, and the export writes every probe artifact itself. One
"Export to USB" carries the guidance trace with its transaction census, the
signal statistics for the whole session, and the recorded trip summaries.
NavGuidanceRecorder owns the trace at process scope, so the probe screen is a
window onto it rather than its owner and closing it no longer ends a capture.
Arming is deliberately not parked-gated: it registers a read-only listener
with no UI, and refusing because the car was moving when the app started
would lose the drive the evidence is being collected on.
Trip summaries travel because trips.json never left the car, so a wrong
distance could only be reported second-hand. Distance over duration gives the
average speed the integration believed in, which is what the speed-unit
question turns on.
Cost: one binder registration, and two 1 Hz ticks reading volatiles and
vehicle properties — the cadence the recording service already uses. Both
recorders keep constant memory; the trace ring is bounded and nothing is
written to disk until an export asks. The artifact pool grew from eight files
to twelve because an export now writes three of them.
Stable arms nothing, writes nothing, and contains none of these classes.
Refs: CP-040
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
0 commit comments