AutoBE
    Preparing search index...

    Compile outcome captured from a phase history when the agent finished but its output did not compile (or the compiler itself threw). Mirrors the three-way IAutoBeTypeScriptCompileResult discriminator without pulling the full diagnostic payload onto the summary — readers who need the details still load the underlying history.

    Day-0 ledger goal: an external reader of summary.json.gz can tell "compile failed with N diagnostics" apart from "compiler threw" apart from "agent stopped before compiling" (which surfaces via reason) without re-parsing histories.

    interface IPhaseCompileFailure {
        blocker?: IPhaseCompileBlocker;
        diagnosticsCount?: number;
        kind: "failure" | "exception";
        rootCategory?:
            | "sdk_accessor_mismatch"
            | "invalid_authorize_helper_shape"
            | "invalid_literal_union"
            | "unobservable_side_effect"
            | "unsafe_sdk_module_cast";
    }
    Index

    Properties

    First diagnostic selected as the user-facing compile blocker.

    diagnosticsCount?: number

    Number of diagnostics in the failure payload. Populated only when kind === "failure"; an exception carries an error value rather than a structured diagnostic list and has diagnosticsCount absent.

    kind: "failure" | "exception"

    "failure" when the compiler ran and produced diagnostics. "exception" when the compiler itself threw (typically a bug in the generated source or the compile pipeline).

    rootCategory?:
        | "sdk_accessor_mismatch"
        | "invalid_authorize_helper_shape"
        | "invalid_literal_union"
        | "unobservable_side_effect"
        | "unsafe_sdk_module_cast"

    Root category propagated from the final compile blocker, when known.