Interface Resolution

Every path the inner command could resolve to: the context alone, then the context extended by each leading token in turn. Offline cannot pick one without knowing which token is the verb (Q6); path is the best guess.

Context in force at the bracket, / when at document root.

Was the menu context this bracket inherited (R3) known? False once an earlier unreadable statement destroyed it — a RELATIVE inner command is then unresolved rather than resolved against a stale value.

Nesting depth of this bracket (0 = directly in a statement).

Raw text inside the brackets.

Where inner itself sits, in the same document byte space.

Not derivable from span: the two bracket spellings do not agree on what span covers. collectBrackets spans […], so inner starts one byte in; scanInterpolations spans $[…] from the sigil (that $ is part of the substitution), so it starts two. inner is also trimmed, so any leading whitespace shifts it further right again. A consumer that guessed span.start + 1 therefore read one byte early on every interpolated substitution and, finding the text did not match, silently dropped the resolution — which is how a $[…] inside a string lost its path tokens to the string fill (#325). Widens with span when interior offsets cannot be mapped, so a consumer must still check the slice against inner.

Feature class, for per-class reporting.

Best single guess: the first bare token is the verb (Q1's rule).

The […] in DOCUMENT analyzed-byte space, closing bracket included. Widens to the enclosing statement where interior offsets cannot be mapped — see Loc.

Leading /-path token run of the inner command, context applied.