fix(onboarding): run the connect ladder after the bootstrap publish step

Commit

peyton-alt2mo ago

On a bootstrapped enable (non-git dir), the connect ladder ran before the deferred publish phase — but that phase is what creates the origin remote and GitHub repo, so the mirror rung could only report 'couldn't check' and the mirror offer could never fire on the very first enable. The ladder now runs as its own 'Connecting to entire.io' step after 'Publishing to GitHub', and enable prints the closing 'Done.' after it.

Mirroring itself is untouched: same createAndAwaitMirror path, same 'entire repo mirror' commands — only when enable invokes the offer moves.

Also: a repo with no origin remote at all (local-only bootstrap) now reads 'no origin remote' (not applicable) instead of 'couldn't check' with a retry hint that could never resolve — gitremote gains an ErrRemoteNotFound sentinel (git remote get-url exit status 2) to make that state detectable.

Co-Authored-By: Claude Fable 5 noreply@anthropic.com Entire-Checkpoint: 01KXNKX51KJ4C56AEYZV93VBQ0

Checkpoints

Fix Onboarding History and Scan Cache Issues

Claude CodeFable 5
View session
Checkpoint 1