Jason WoltjeandClaude Fable 5
f1b63bccfb
ci/woodpecker/pr/ci Pipeline was successful
The entry said the fix landed in 'the clean-sweep message + the PROVABILITY BOUND comment' — two surfaces. It landed in three: usage() came in the second commit (author-side self-catch) and the entry was never updated. This PR's whole thesis is naming a set completely; its own permanent record naming 2 of 3 of its own fix surfaces would reproduce the defect it fixes. Taken as the pre-merge clause (mos-dt flagged, MOS ruled) — this is the only window the entry can be made accurate in-place under the changelog-is-history ruling. Also rides along, comment-placement-only: the 0.7.1 entry moved above component= so component=/version= sit adjacent again (the split was verified inert — _manifest_val's anchored sed cannot match a comment — but placement is free to fix in the same comment-only commit). Keys re-verified parsing: component=wake, version=0.7.1, schema 1/1. Manifest-comment-only: zero code, zero manifest key changes. Written-by: pepper (sb-it-1-dt) Co-Authored-By: Claude Fable 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01NsKce8iZuSuRnu3gVMCBKB