Description
Record shapes vary by client version and a whole record type can disappear between releases with no error. A decoder that quietly produces nothing looks identical to a quiet day, which is the failure mode this project most needs to not have.
Acceptance Criteria
- #1 Any record type neither decoder recognises increments unhandled_record_types labelled by tool and type
- #2 The type label is bounded and overflows to other rather than growing without limit
- #3 An unhandled record is never dropped silently and never crashes the pipeline
- #4 A test feeds an invented record type and asserts the counter moves
Definition of Done
- #1 just check passes: fmt-check, lint, build, test-short, probe-ci, dashboard-check and docs-links all clean
Implementation Plan
Wave 1 lane 7: implement unhandled-record accounting, signature induction and probe/profile commands within assigned files; validate empty-corpus exit and content-free signatures; root integrates and runs the final gate.
Final Summary
Both decoders count bounded unknown record types without crashing or silently dropping them; invented-record tests passed.