The README's output blocks predate rule IDs, so they showed neither the
CCxxx identifiers nor the Docs links that every failure now prints. Same
staleness #530 fixed in the demo GIF; the docs site is already current,
only the README had been left behind.

Measured by running each documented command against this checkout rather
than reading the code:

  Type message check failed ==> ...   ->  CC001 message check failed ==> ...
  Type branch check failed  ==> ...   ->  CC201 branch check failed  ==> ...

plus a trailing `Docs: https://commit-check.com/rules/#ccNNN` line on both,
and two commit types the list had never picked up (perf, build).

Four more blocks were stale in the same way, so they are refreshed too:

- --no-banner carried a line that no longer exists anywhere in the source:
  "It doesn't match regex: ^(build|chore|ci|...)". grep over *.py finds it
  only in a test comment.
- --compact prints the rule id: [FAIL] CC001 message: ...
- Both --format json examples were missing the rule_id and docs_url fields,
  showed value as "" where it is now populated on pass, and named a
  subject_imperative check that the default run does not emit — it reports
  subject_max_length (CC004) and subject_min_length (CC005), and lists
  passing checks alongside the failing one.
- The Python API return-value schema was missing rule_id and docs_url. The
  API code examples themselves were correct; each was re-run to confirm.

Every block was then re-captured and compared byte for byte against the
committed text (JSON via json.loads, text with ANSI colours and trailing
padding normalised), so these are transcripts, not transcriptions.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01U9zFxq8V4qxG4aMzJhGBFn