-
(bdddc09) Read only the underscore markers as unset, and bump to 0.18.1
released this
2026-08-22 22:52:39 +00:00 | 76 commits to master since this releaseis_unknown_valueaccepted-None-and-Not set-alongside the real
_None_and_Not set_. The ticket had them down as corrupted output handled
downstream instead of at the source, but the source never existed:git log -S
finds both spellings in exactly one commit,2a96abd, the one that added them to
the check. They were written by analogy with the**-Status**field name the mv
splicing bug really did produce, c230d2c, and they have been dead since the day
the function was written.So this is a deletion with nothing behind it. All five boards on this machine
hold no hyphenated marker in any metadata field, and the only files in this
repo that contain the spellings at all are the two tickets that describe the
bugs, in prose, whichparse_ticket_fielddoes not read.A field that somehow holds one now reads as the text it is rather than passing
for unset, which is the right way round for corruption nothing can produce.
a_hyphenated_marker_is_not_unsetpins that, because the risk here is not the
old code coming back but the analogy being drawn a second time. The
**-Status**repair inis_status_lineis the opposite case and stays: that
corruption was real, and AGENTS.md now says why the two are not alike.Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com
Downloads