Marmot-TS
    Preparing search index...

    A resulting state already known for one of our own applied commits, together with the confirmation tag of the exact parent it was applied to (CONV-04).

    The parent tag is load-bearing, not bookkeeping: candidatesAt admits any pooled message whose framed epoch matches the DFS node's epoch and never checks parentage, so without it the short-circuit would fire while exploring a COMPETING fork node at the same epoch and splice our canonical chain onto that branch — inflating its depth (the primary key selectCanonicalBranch scores on) and, if it then won, corrupting RetainedHistoryStore with a parent→child edge that never happened.

    interface KnownNextState {
        parentTag: string;
        priority?: CommitOrderingPriority;
        state: ClientState;
    }
    Index
    parentTag: string

    The commit's ordering class recorded when it was authored, used only when its proposals cannot be rebuilt from the parent snapshot.