"Who changed the pricing page, why, and which release shipped it?" is usually answered by asking three people. The commit says what the bytes became, the ticket says what someone intended a fortnight earlier, and the release notes say neither.
This walkthrough uses the tool's public README and checked-in example files. Run the command from a repository checkout with Node.js 22+.
Run the checked-in example
node bin/content-change-ledger.mjs verify examples/ledger.jsonl --config examples/ledger-policy.jsonRead the result
--json writes the report to stdout, and only the report, so it can be piped straight into a parser. Diagnostics always go to stderr.
Scope
This is not tamper-proofing, and the README will not pretend otherwise.