AniLink - v3.0.0
    Preparing search index...

    Interface TransportStateSnapshot

    The read-only transport-state snapshot for one state owner, as returned by snapshotTransportState and exposed per provider by AniLink#getTransportState. Every nested object and array is deep-frozen: mutating a snapshot throws (in strict mode) instead of silently succeeding, and the snapshot never aliases the live mutable state, so a consumer cannot perturb transport behavior through it.

    The snapshot is a point-in-time copy, not a live view: fields reflect the values observed when the snapshot was taken, and capturedAt stamps that moment so a polling consumer can judge staleness without recording receipt time itself.

    interface TransportStateSnapshot {
        capturedAt: number;
        circuit: readonly CircuitStateSnapshot[];
        paceDeadlines: readonly PaceDeadlineSnapshot[];
        responseCache?: ResponseCacheStats;
        retryBudget?: RetryBudgetSnapshot;
    }
    Index
    capturedAt: number

    Epoch milliseconds at which the snapshot was built, set once at build time.

    circuit: readonly CircuitStateSnapshot[]

    Frozen per-host circuit-breaker records, one per host the client has sent breaker-tracked traffic to.

    paceDeadlines: readonly PaceDeadlineSnapshot[]

    Frozen per-host rate-limit pacing deadlines, one per host with a recorded (not yet elapsed-and-cleared) deadline.

    responseCache?: ResponseCacheStats

    Frozen response-cache counters, present only when the client's transport options enable a ResponseCache: the live entry count and the lifetime hit/miss/expiration/eviction counters, so cache tuning (ttlMs/maxEntries) is data-driven through the same facade surface as the breaker/budget/pacing state, without holding the ResponseCache instance (which a consumer wiring the cache through a provider credentials slot never held).

    retryBudget?: RetryBudgetSnapshot

    Frozen retry-budget record, present only when the client has a recorded budget window.