Repository navigation
History transfer: qualify incremental archives beyond bounded whole-project caps #67
Description
The new verified history transfer intentionally caps a whole-project snapshot (64 MiB by default, configurable to 512 MiB; 2,000 records per category). A long-lived or busy adopter will eventually exceed a bounded whole-store archive. Increasing the cap indefinitely would remove the memory/verification bound.
Follow-up acceptance: versioned incremental/sharded archive manifests with explicit complete ranges, retained cross-shard bundle/packet/invocation references and exact project/digest binding; bounded listing/verification; idempotent resume and recovery; newest canonical pointer preserved; no silent dropped generations, pruning or reinterpretation of existing archive/bundle versions.
Current 0.5.0 behavior is a clear cap error and no partial export. This is a scalability debt, not permission to omit older private history or call a partial backup complete.
Activity
abogun-product commentedon Oct 7, 2026
PR #69 implements bounded whole-project archive transfer and explicit combined-store/per-category admission caps. Offline synthetic restore and hostile archive/collision regressions pass.
Incremental or sharded transfer remains this issue's separate long-term scale work. The current implementation fails explicitly at the cap and does not silently prune or advertise a partial backup as complete.