Was the menu context in force BEFORE this statement known? (Q14 C3b, #192.)
false does NOT invalidate path: the resolver already degrades every
context-DEPENDENT statement to unresolved when context is lost, so a split
that still says resolved here resolved WITHOUT consuming the context — an
absolute path, a : directive, or a bare directive. What this carries is
the thing that was otherwise dropped on the floor: /ip) address followed
by /ip route print yields a perfectly correct resolved split whose
document had already lost its context, and a consumer ranking readings or
offering completions needs to know that.
This statement in DOCUMENT analyzed-byte space, straight from the resolver.
Carried because the walk FLATTENS: a block body's statements are appended
after their parent, so splits is longer than the top-level segmentation
and a caller pairing the two by index silently attaches the wrong span to every
statement after the first do={…}. With the span here there is nothing to
pair — the location travels with the reading.
The statement's own text, as the resolver segmented it (#202c).
Carried for the same reason DocumentVerbSplit.span is: the caller
that lexes ARGUMENTS from VerbSplitCommandReading.argsAt needs the
text those offsets index, and re-slicing the document by span to recover
it is exactly the step that silently succeeds when the span is a widened
FALLBACK (pathresolve.ts → Loc) rather than this statement's own bytes.
With both here the caller can CHECK that they agree instead of assuming it.
One statement's split, as seen by the DOCUMENT walker.
The two extra fields are the difference between the entry points, and both are required rather than optional on purpose.
resolveVerbis handed one statement and an explicit context, so it has nothing to say about where that statement sits or whether the context was knowable;resolveVerbswalks the document and always does. An optional flag would make "absent" mean both "single-statement call" and "certain", and the whole point of the field is that silence must not read as certainty.