Official CodexBar 0.64.0 adds Helmcode, v0, and TypeSafe; 0.64.1 retires
Crof after the service shut down, leaving 77 registry records. The
installed 0.64.1 CLI reported all three additions while `make check`
failed locally on the missing icons, so the widget degraded them to the
unknown-provider fallback.

Bundle the name, an original non-vendor icon glyph, the upstream docs
link, and the dashboard entry point for each addition. Brand colors and
status links stay absent because upstream declares none; inventing them
would be worse than the theme highlight the widget already falls back to.

Scoped probes against the installed 0.64.1, run under `env -i` with an
empty temporary HOME and no credential environment, establish what Linux
can actually reach:

- `config set-api-key --provider v0` succeeds, and `usage --provider v0`
  classifies a synthetic key as a provider error, so v0 joins the
  widget's supported API-key setup allowlist.
- The same call is refused for Helmcode and TypeSafe. Both are
  cookie-only, both reject `--source api`, and their documented
  `cookieSource`/`cookieHeader` path has no CLI writer, so they stay
  metadata-only until the generic settings contract lands.
- `config enable --provider crof` now fails outright. The Crof metadata
  stays anyway: an installed 0.63.0 still emits the provider, and
  dropping it would downgrade a named provider to the unknown fallback
  for anyone who has not upgraded.

Both carried-forward blockers were rechecked and are unchanged at 0.64.1:
`config providers --descriptors` is still rejected, and `set-api-key` is
still the only supported writer.

Documentation impact: adds the dated 0.64.1 parity review and indexes it,
moves the TODO review baseline to 0.64.1 with two new verification
entries for the unmeasured Linux quota-window changes, and updates the
registry count and version in README and the usage guide.

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>