|
Fix a self-inflicted DOCFIX counter inflation in the entry that restated the rule
The 2026-08-02 queued-findings entry wrote the next-free DOCFIX number in hyphenated identifier form. ledger-scan derives the high-water mark by matching that form anywhere in prose, so it read highest=208 / next-free=209 when only 207 was ever assigned -- the exact decoy-token defect the standing numbering rule (hardened in DOCFIX-174) exists to prevent, committed one paragraph after restating that rule. The first correction then reproduced the same token inside the sentence explaining the mistake, and ledger-scan stayed at 209. Both are recorded in the entry rather than quietly fixed: the rule is unenforceable by reading, because a decoy token looks exactly like correct bookkeeping. Only re-running the scan catches it. Verified: ledger-scan now reports DOCFIX highest=207 next-free=208, matching the single number this session assigned. D 141 / BUNDLEFIX 053 unchanged. repo-lint 0 fail. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HvCyrwvYTTcDYnRErfMsNf |
|---|
|
|
| docs/CURRENT-STATE.md |
|---|