Repository navigation

store/s3: sparse-aware, chunked, content-addressed checkpoint transfer - #364

Merged

CMGS merged 21 commits into

mainfrom

feat/362-s3-chunks

Oct 18, 2026

Merged

store/s3: sparse-aware, chunked, content-addressed checkpoint transfer#364
CMGS merged 21 commits into
mainfrom
feat/362-s3-chunks

Commits on Oct 17, 2026
- store/s3: store exports as sparse-aware chunk manifests
  CMGS
  committed
  1ae04b3
- store/s3: dedup chunks per lineage and sweep generations
  CMGS
  committed
  7dbca62
- store/peer: ship sparse files as size plus non-zero chunks
  CMGS
  committed
  2ce93ee
- docs: describe the s3 chunk layout, retention and the upgrade step
  CMGS
  committed
  219d68e
- store: tighten sparse, sweep and peer tests
  CMGS
  committed
  f25b355
- store/s3: reuse only chunks a committed manifest references
  CMGS
  committed
  a0af18e
- store/s3: Delete keeps manifests and the sweep reclaims them
  CMGS
  committed
  658fdc4
- store/s3: judge the meta age from the GET, not the listing
  CMGS
  committed
  9b93848
- store/s3: index a lineage by markers so a publish reads only its records
  CMGS
  committed
  5427197
- pool: sweep a shared store prefix once per tick
  CMGS
  committed
  e23a62f
- docs: drop the lifecycle-rule hint and say every file ships as chunks
  CMGS
  committed
  cab35bc
- review: plain lineage parameter, s3.go layout, sparse cleanups
  CMGS
  committed
  e42a3bd
- store/s3: keep a vanished record's listed references live for the sweep
  CMGS
  committed
  a1362be
- docs: describe the real order of the lineage marker write
  CMGS
  committed
  e878c66
- docs: limit the chunked peer transfer to export files
  CMGS
  committed
  b5b4dd6
Commits on Oct 18, 2026