Dual-write v2 checkpoints

[computermode]

https://entire.io/gh/entireio/cli/trails/290

➜  cli git:(dual-write-v2-checkpoints) ✗ entire migrate --checkpoints v2


Migration complete: 3191 migrated, 39 skipped, 0 failed

➜  cli git:(dual-write-v2-checkpoints) ✗ git push origin HEAD
[entire] Pushing entire/checkpoints/v1 to checkpoint remote...
[entire] Syncing entire/checkpoints/v1 with remote..... done
[entire] Pushing entire/checkpoints/v1 to checkpoint remote.... already up-to-date
[entire] Syncing and pushing v2 checkpoints...
[entire] Pushing v2/main, v2/full/current, v2/full/0000000000032...
[entire] All v2 checkpoints pushed

---

Note

Low Risk
Low risk config-only change, but it can change what refs/data the CLI pushes to the checkpoint remote if enabled in environments that consume this file.

Overview
Enables v2 checkpoint behavior via .entire/settings.json by adding checkpoints_v2 and push_v2_refs under strategy_options, allowing the CLI to migrate/sync and push v2 checkpoint refs in addition to existing behavior.

^{Reviewed by Cursor Bugbot for commit 5c68c57. Configure here.}

[Copilot]

Pull request overview

Enables this repository’s shared Entire project settings to start dual-writing and pushing checkpoint v2 refs alongside the existing v1 checkpoint branch, matching the migration/push workflow described in the PR.

Changes:

• Turn on strategy_options.checkpoints_v2 in the committed .entire/settings.json.
• Turn on strategy_options.push_v2_refs so pre-push sync also publishes v2 refs.
• Keep the existing dedicated checkpoint remote configuration in place for the new dual-write flow.