Monitor Binary Version Baselines

Build and maintain comparable, version-keyed records of which feature-system markers appear in a CLI harness binary, so additions, removals, and dark-launched capabilities can be detected mechanically across releases.

When to Use

• Tracking a feature's lifecycle across multiple releases of a closed-source CLI harness
• Probing for dark-launched capabilities (shipped but gated off) or quietly-removed ones
• Verifying that a marker scanner still detects known-good markers on old binaries (regression-testing the scanner itself)
• Building the Phase 1 substrate that later phases (flag discovery, dark-launch detection, wire capture) consume
• Any context where ad-hoc grep answers "is X present today" but you actually need "how has the system composed of X, Y, Z moved across versions"

Inputs

• Required: One or more installed binary versions of the same CLI harness (or extracted bundles)
• Required: A working catalog file for the marker definitions (created on first run, extended across versions)
• Optional: A previously-recorded baseline file from prior runs (extended in place, never rewritten)
• Optional: A list of versions known to be never-published (skipped releases, withdrawn builds)
• Optional: A list of feature-systems already under tracking, to extend rather than re-discover