- parse_override_tokens distinguishes the grammar fault (no '=' / no
dotted path — prose unchanged) from a shape-valid token whose VALUE
fails the scalar-literal parse: the refusal now names the value and
the literal requirement (styled after the kind-mismatch sibling)
instead of falsely claiming a NODE.PARAM=VALUE violation. RED-first;
exit stays 2 on both branches.
- the authoring guide's multi-regime family ids corrected to the
executor's real shape (infix -r{k} after the window segment, -r0
explicit on the default regime), and §1's name-op paragraph no
longer claims naming dissolves same-name trace overwriting (that
trace-dir question is tracked on #311, not resolved here).
claude
024e8652c0