You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 0a927b4
Browse filesBrowse the repository at this point in the historyBrowse files
🐛 Use the approved apostrophe, and refuse --save by name (#260)
The introduction claimed to be the approved wording and was one byte away from
it: `coding agent's plan` with an ASCII apostrophe where the contract has U+2019.
The regression that was supposed to catch that had copied the same byte, so it
pinned the file to itself rather than the file to the contract. Both now carry
E2 80 99, and the fixture's comment says why it is the byte and not the sentence
that is being held.
Two contract passages still described the earlier command. The ACP lifecycle
said the profile's scope closes before "the save and the execution"; it closes
before final admission and before whichever result was asked for. The command
spec said `xmd prompt` executes two root documents; it always executes the
command document and executes a second only under `--run`.
The terminology sweep reached the comments, messages and test names that the
earlier passes left behind: "the save" in the deadline and teardown comments, the
harness's `--save`, the profile's two directory failures now saying "nothing was
output or run", and the review-decision comments and test names that still called
stopping an abort. The unrelated abort in `runDocument` is left alone — it is
about a document's own failure, not this command's.
`--save` had no real proof it was gone. The case that passed it also passed two
mutually exclusive permission flags, so the earlier failure decided the outcome
and the assertion would have held whether or not the option still worked. That
case no longer carries it, and a focused one does — on a command line that is
otherwise entirely valid.
Making that case honest exposed something worth fixing. `--save out.md` was
refused, but as "unrecognized argument: out.md": the scanner passed the unknown
option to a parser that stops at the first option it does not define and drops
the rest, so what a caller heard about was the value rather than the flag. Fixed
preflight now refuses an option this command does not define, by name, and names
`--output` when the option was `--save`.
Claude-Session: https://claude.ai/code/session_015HcqB9kJM9KFnMNToAuZF6
0 commit comments