fix(doctor): report a fail-closed checkpoint sync election

[Soph]

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

Summary

When checkpoint_push_remote names a missing remote, checkpoint sync fails closed. entire doctor previously either claimed a remote was elected or, in single-remote repos, said nothing.

This change makes the shared doctor/enable note consult the actual election result and report Checkpoint sync: DISABLED with targeted guidance. A typed error distinguishes a missing configured remote from other settings failures, while dedicated checkpoint_remote destinations remain exempt because they bypass election.

Tests

• mise run check
• GOOS=windows go vet ./...

[Copilot]

🟡 Changes recommended

Three moderate findings remain around partial-sync reporting, probe-error classification, and dedicated-remote status consistency.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Updates checkpoint-sync diagnostics so doctor and enable report fail-closed elections instead of implying checkpoints are syncing.

Changes:

• Adds typed missing-remote election handling.
• Updates topology, doctor, and enable diagnostics.
• Adds unit/integration tests and documentation.

File summaries

File	Summary
cmd/entire/cli/strategy/checkpoint_sync_remote.go	Adds typed election errors. Moderate findings remain regarding probe-error classification and dedicated-remote status consistency.
cmd/entire/cli/setup.go	Updates enable-time diagnostic output.
cmd/entire/cli/remote_topology.go	Adds resolver-backed diagnostics. A moderate finding remains regarding overstatement for partially affected remotes.
cmd/entire/cli/remote_topology_test.go	Adds topology diagnostic and edge-case tests.
cmd/entire/cli/integration_test/checkpoint_sync_remote_test.go	Verifies doctor wiring for fail-closed elections.
cmd/entire/cli/doctor.go	Integrates checkpoint diagnostics.
CLAUDE.md	Documents the new fail-closed reporting behavior.

Review details

Suppressed comments (2)

cmd/entire/cli/strategy/checkpoint_sync_remote.go:107

• isConfiguredRemote currently turns every non-zero git remote get-url result into false, not just “remote is absent” (see strategy/manual_commit_push.go:373-380). Wrapping that result in CheckpointPushRemoteNotConfiguredError makes errors.As select the new “remove or rename the setting” remedy for config/readability failures too, so the diagnostic can misidentify why election failed. Preserve probe errors as an opaque cause and reserve this typed error for positive evidence that the named remote is missing.

	if name := s.GetCheckpointPushRemote(); name != "" {
		if !isConfiguredRemote(ctx, name) {
			return CheckpointSyncRemote{}, &CheckpointPushRemoteNotConfiguredError{Remote: name}

cmd/entire/cli/strategy/checkpoint_sync_remote.go:63

• Error() is still used verbatim by entire status, but this resolver can return it alongside a valid checkpoint_remote. In that mode the pre-push hook bypasses this election and sends checkpoints to the dedicated URL, while status prints ! Checkpoints NOT syncing; the new doctor path even treats all pinned remotes as healthy. Please make status account for the dedicated mode (or avoid presenting this as a global disabled result) so the commands do not contradict actual delivery.

		"checkpoint_push_remote %q is not a configured git remote; checkpoint sync disabled until fixed",
		e.Remote)

• Files reviewed: 7/7 changed files
• Comments generated: 1
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.