@tikoci/centrs
    Preparing search index...

    Interface ExplainCommandReading

    A resolved command: a path AND the verb that was decided on it.

    interface ExplainCommandReading {
        arguments?: ExplainArguments;
        command: { args?: Record<string, string>; path: string; verb: string };
        kind: "command";
        resolution: "resolved";
        transport?: ExplainTransport;
        unresolved?: undefined;
    }
    Index

    Properties

    arguments?: ExplainArguments

    ABSENT rather than refused where no attempt was made — the same convention transport follows. Statements always carry it; a […] subcommand does not, because its inner text has its own coordinate space that phase 1 does not rebase (see ExplainSubcommand).

    command: { args?: Record<string, string>; path: string; verb: string }

    args is present exactly when arguments read: it is that reading's object view (last occurrence wins), in the ratified sketch's place (commands/explain/README.mdResult shape). Absent is not {} — a command with no arguments reads as {}.

    kind: "command"
    resolution: "resolved"
    transport?: ExplainTransport

    Present on document statements after the #202c-2 transport pass. Absent on subcommands, whose inner argument coordinates phase 1 does not rebase.

    unresolved?: undefined