{"version":"2.1.280","anchor":"checkpoint-restore-records-now-track-a-generation-chain-wi","canonical_anchor":"checkpoint-restore-records-now-track-a-generation-chain-wi","heading":"Checkpoint restore records now track a generation 'chain' with hashes","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/checkpoint-restore-records-now-track-a-generation-chain-wi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Checkpoint restore records now track a generation 'chain' with hashes\n\nCheckpoint restore records can now track a generation chain of hashed entries\n\n**Unclear.** The finding does not say what readsResultEcho does or how the chain is used during an actual restore.\n\n**What**\n\nA new schema describes a checkpoint 'chain': an array of entries, each with a generation number, worktree commit, sha256 hash, size, and a `via` field, validated so generation numbers strictly increase. The restore-state schema now carries an optional `chain` field, a new `chained` boolean, and a new `readsResultEcho` flag, alongside the existing `attached` and `seedless` flags.\n\n**Why**\n\nThis lets Claude Code track and verify a sequence of checkpoint generations with hashes, giving restore operations a way to confirm the integrity and lineage of a chain of checkpoints.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}