docs: align the status note with the card's fallback counts

The note quoted a rounded zero for byte fallback and claimed the README
matched model_card.json field for field. The README now reports counts
where the card reports rates, so the note says that instead of asserting
an identity that no longer holds.

NEXT_STEPS.md

@@ -19,9 +19,10 @@ tokenizer.json (here)                          sha256 34d181532eee7e6754bf…
 mon_tokenizer/src/mon_tokenizer/data/…json     sha256 34d181532eee7e6754bf…
 ```
 
-**Byte-identical.** Every metric in `README.md` also matches `model_card.json`
-field for field — Mon at 4.686 chars/token over 29,600 lines, 100% round-trip,
-0.00% byte fallback.
+**Byte-identical.** Every metric in `README.md` also traces to `model_card.json`:
+Mon at 4.686 chars/token over 29,600 lines, 100% round-trip, 20 byte-fallback
+tokens in 486,631. The card records fallback as a rate and the README as a count,
+because Mon's rate rounds to a two-decimal zero and reads as *never*.
 
 That is the check that matters, because this repository has failed it before. The
 history records a release where `tokenizer.json` was silently the 4,000-piece