hdrprobe v0.4.0

New

• Per-video-track reports. Files with more than one independent video track now get one report section per track: a multi-track MKV or MP4 reports each video track, and a multi-program TS capture reports one track per service with its program number. A Dolby Vision base layer + enhancement layer pair still reads as one logical track, classified by each stream's own DV signaling rather than by track count, so a P7 dual-track remux keeps its single Dual track, dual layer report. In the text report each track's sections are grouped under a full-width track rule with the body indented beneath it, so which sections belong to which track reads at a glance, and -q prints one line per track tagged [k/N]. Single-track files render byte-identical to before.
• Metadata cadence verdict. Dolby Vision reports gain a Metadata cadence line stating whether the title's dynamic metadata was authored shot-by-shot or frame-by-frame, decided by comparing consecutive frames' creative DM payloads. The verdict appears only when the evidence is complete: a --full video scan, a raw RPU sidecar, or a DV XML's own declared shot structure. The default sampled scan never guesses.
• Schema 2.0 migration guide. A step-by-step consumer migration guide for the new JSON shape ships as docs/MIGRATION-2.0.md and is included in the release archives.

Schema

• 1.2 to 2.0 (breaking). The JSON report is restructured for multi-video-track reporting: per-track fields moved from the old general, hdr, dolby_vision, and hdr10plus locations into the always-present video_tracks array (one entry per video track, including for sidecars, so consumers always iterate the array), each entry gaining track_number, program, and default. general.container, general.format_version, and general.duration_secs moved to the top level and general itself is gone. No field changed type, unit, or meaning. Also adds video_tracks[].dolby_vision.metadata_cadence. Documented in docs/SCHEMA.md, with the upgrade path in docs/MIGRATION-2.0.md.