docs(v0.5.0 E): claim accuracy — badges over drift-prone counts, RESULTS synth-0.49 provenance, D-split status

[avrabe]

What

v0.5.0 workstream E (docs accuracy + reader-friendliness). Closes the user's ask to stop hand-maintaining numbers ("do we really need the numbers or... via badges — or delete it") and to claim-verify stale docs without inflating capability.

Changes

• README: replaced drift-prone, self-contradicting hand-typed counts with the live badges / non-drifting language:
  • ~1015 runtime tests and a conflicting 995 tests → both removed; point at the Rust CI badge (cargo test --workspace).
  • 36 upstream test suites and a conflicting 20/20 → both removed; point at the Zephyr Tests badge.
  • Per-module property tables and the internally-consistent, already-footnoted Verus/Kani figures were left as-is (structural, not drift-prone).
  • grep -nE "1015|995|20/20" README.md → now empty (contradictions resolved).
• Driver RESULTS.md (×10): one honest provenance line each — current pins are synth 0.49.0 / loom 1.2.0 (wip(toolchain): adopt synth 0.49 + loom 1.2 (v0.5.0 workstream C) — thin-driver regen, pending gate verify #208), with the grounded old→new .text byte delta from the byte-check (incl. the honest gpio +9% outlier, filed as synth#846). Register effects unchanged, 0-SRAM preserved.
• Silicon RESULTS-*.md / esp32c3: note the current pins and that on-silicon gust_mix predates the 0.49 adoption (not re-measured — no invented numbers).
• Release plan: recorded the workstream-D split — D.1 target-model ADC done (feat(gust): ADC/Vrefint(ch17) in F100 target model + generator (v0.5.0 workstream D) #215); D.2 silicon Vrefint blocked on adc-thin: absolute CR2 writes block F1 internal channels (Vrefint/temp need TSVREFE) #216 (adc-thin absolute CR2 writes drop TSVREFE → can't drive F1 internal channels).

Honesty

No new hand-typed number introduced. A full cargo test --workspace was run to ground the claim (1953 passed) but deliberately not hardcoded — a badge avoids re-drifting next release. "Verified" wording checked: only Verus-proven modules / already-caveated claims use it.

🤖 Generated with Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!