Luxar Viewer API Documentation - v2026.9.22
    Preparing search index...
    LadderRollbackPlan:
        | { action: "none"; dropped: 0 }
        | { action: "retry-folded-pass"; dropped: 0 }
        | { action: "unwind-restored-full"; dropped: number }
        | {
            action: "truncate";
            keep: number;
            dropped: number;
            invalidateConcatCache: boolean;
        }

    What a loader should do to undo a failed pass.

    Type Declaration

    • { action: "none"; dropped: 0 }
    • { action: "retry-folded-pass"; dropped: 0 }
    • { action: "unwind-restored-full"; dropped: number }
    • {
          action: "truncate";
          keep: number;
          dropped: number;
          invalidateConcatCache: boolean;
      }
      • action: "truncate"
      • keep: number
      • dropped: number
      • invalidateConcatCache: boolean

        Whether the memoized concat must be discarded. True exactly when the memo covers MORE logical levels than survive, in which case it describes a prefix the loader no longer holds. A memo at or below keep is still a faithful concatenation of retained levels, so it is deliberately kept — the commit layer's append fast path gates on pure IDENTITY between the memo and committedData, and dropping a valid memo would downgrade the next commit to a full rewrite.