command.md: say where each refuse_and_stop refusal is held (improvise-rtud)
#213 merged before this correction was pushed; the push re-created a branch main never saw. This lands the final wording on gh/main. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VdfEGXA7aJ6ftMsCc9PJze
This commit is contained in:
+12
-6
@@ -634,12 +634,18 @@ Consequences:
|
||||
path and the `:` line, which is what the headless exit code reads. The wire
|
||||
table cannot see the refusal half of a `refuse_and_stop` site, because
|
||||
`Host::mutating_frame` rejects on `refused || aborted`, and the abort alone
|
||||
suffices. So each `refuse_and_stop` site needs a case in both tables:
|
||||
the key-path table for its refusal, and
|
||||
`a_failed_load_or_import_does_not_run_the_quit_after_it` for its abort
|
||||
(improvise-514o). Each key-path case has a succeeding twin, so a site
|
||||
that refused unconditionally would fail too. That matters because
|
||||
these are exactly the lines a merge conflict could silently drop.
|
||||
suffices. So each `refuse_and_stop` site needs a key-path assertion for its
|
||||
refusal as well as one for its abort. The abort is
|
||||
`a_failed_load_or_import_does_not_run_the_quit_after_it` (improvise-514o).
|
||||
Three sites are not in the key-path table (improvise-rtud). The quit test's
|
||||
"setup:" assertion holds the refusal of `load` and `import-json absent.json`.
|
||||
`a_formula_that_does_not_parse_keeps_the_user_in_the_editor_with_their_text`
|
||||
holds `AddFormula`'s parse arm, which has no case in the quit test. The other
|
||||
five import arms are in
|
||||
`every_refusal_site_refuses_its_failure_and_only_its_failure`.
|
||||
Each case in that table has a succeeding twin, so a site that refused
|
||||
unconditionally would fail too. That matters because these are exactly the
|
||||
lines a merge conflict could silently drop.
|
||||
- **Not covered:** a no-op *inside* a view that does resolve. Examples are
|
||||
`SetAxis` on a category the view does not have, `HideItem` of an absent
|
||||
item, and `RemoveItem`/`RemoveCategory`/`RemoveFormula` of something already
|
||||
|
||||
Reference in New Issue
Block a user