Three operational lessons from the July squash windows, in generic terms:
- Git-backed remotes never shrink on force-push: the remote manifest keeps
every historical table file listed as current, so the store must be
replaced in place — delete refs/dolt/data and the __dolt_remote_info__
branch on the git remote, then force-push a fresh store (verified on two
production remotes: 587M->57.8M and 274M->2.6M reachable).
- Sync jobs and writers are separate switches: a peer's sync job stays off
until that machine has verifiably re-cloned; unfencing writers must not
implicitly re-arm peer sync (the re-pollution hole hit twice).
- First push from a re-cloned machine is far larger than a routine tick;
timeout-capped sync jobs orphan partial uploads — one manual uncapped
push before handing back to the schedule.
Gates: go test ./test/docsync PASS, check-doc-freshness.sh PASS.
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>