Ignores ancestors in snapshot

[brooksprumo]

Problem

Loading from a snapshot doesn't require reading the ancestors.

Summary of Changes

Ignore 'em.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.0%. Comparing base (f372294) to head (adcd705).
⚠️ Report is 4 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##           master   #10835     +/-   ##
=========================================
- Coverage    83.0%    83.0%   -0.1%     
=========================================
  Files         836      836             
  Lines      316307   316305      -2     
=========================================
- Hits       262640   262637      -3     
- Misses      53667    53668      +1     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[brooksprumo]

Digest changed because we renamed the field. No actual ABI change.

--- bank__serde_snapshot__tests__test_bank_serialize__BankAbiTestWrapper_frozen_abi__test_api_digest_FCDuswxZnGvvJURSkrQPshX45a25CR6UAmPgzGeUfMFv	2026-02-26 16:57:31
+++ bank__serde_snapshot__tests__test_bank_serialize__BankAbiTestWrapper_frozen_abi__test_api_digest_HKTVanoy2iLbtAVwrt2y8HxH8YaWsgw4LZC9B76X6EL4	2026-02-26 16:56:06
@@ -158,7 +158,7 @@
                                                 primitive u64
                             field max_age: usize
                                 primitive u64
-                    field ancestors: std::collections::hash::map::HashMap<u64, usize>
+                    field unused_ancestors: std::collections::hash::map::HashMap<u64, usize>
                         map (entries = 1)
                             key u64
                                 primitive u64

[brooksprumo]

Needed to rebase due to frozen abi digest after merging #10852.

[mergify]

Backports to the beta branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. Exceptions include CI/metrics changes, CLI improvements and documentation updates on a case by case basis.