Resize, stale pack state and history trails
Follow one order: loading/versions → routes/active closure → resources/bindings → static interface → matching runtime report → appearance/lifecycle. Change one factor at a time.
Locate the failing layer
Record generation, actual window/render extent, resource extents and selection before/after changes. Viewport-sized resources follow lifecycle rebuilds; absolute-size probes are not fullscreen targets. Identical screenshots do not prove a resize occurred. Reproduce first with a history-free feature, then add history incrementally.
Inspect and repair
History needs a real writer, valid current/previous views, fallback and at most one historyCommit after every writer. A persistent resource cannot be committed; this release includes that real negative example. Skipped producers must not advance history. Reload, world/device/owner/camera/extent changes and camera cuts follow invalidation rules. GPU-history validity and view_history_valid are distinct conditions.
Recheck and recover
Old reports against a new generation can trigger DLREPORT1001–1010; use DLAST/DLDATA for temporal input/AST errors. Static success does not establish device-loss recovery, multiple views, other drivers or TAA quality. See advanced boundaries.