@tikoci/centrs
    Preparing search index...

    Interface Resolution

    A re-constituted […] command substitution (Q3).

    interface Resolution {
        candidates: string[];
        context: string;
        contextCertain: boolean;
        depth: number;
        inner: string;
        klass: string;
        path: string | null;
        span: Span;
        tokens: string[];
        unresolved?: string;
    }
    Index

    Properties

    candidates: string[]

    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: string

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

    contextCertain: boolean

    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.

    depth: number

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

    inner: string

    Raw text inside the brackets.

    klass: string

    Feature class, for per-class reporting.

    path: string | null

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

    span: Span

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

    tokens: string[]

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

    unresolved?: string