fix(cli): Ctrl-C escapes shell loops and aborts cleanly

[toothbrush]

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

while true; do entire mirror create …; done couldn't be stopped with Ctrl-C, and interrupts spewed raw transport/keyring errors.

Cause: entire trapped SIGINT and exited normally. A shell only breaks a loop when the child is killed by SIGINT, so each Ctrl-C just ended one iteration and the loop respawned entire instantly.

Fixes:

• On abort, re-raise SIGINT to self → the process dies by the signal → enclosing loops break on a single Ctrl-C.
• Second Ctrl-C force-quits (escape hatch for a stuck shutdown).
• context.Canceled exits silently (130) instead of printing do request: Post ".../mirrors": … context canceled.
• Keyring reads now abort on Ctrl-C instead of waiting out the 5s timeout (or hanging on a daemon-less box).

Try it: while true; do entire repo mirror create …; done, then Ctrl-C once — the loop now exits.

Verified with a PTY harness driving interactive zsh: one Ctrl-C breaks the loop (0 further iterations) vs. the old behavior (loop kept running). mise run test:ci green.

🤖 Generated with Claude Code

---

Note

Medium Risk
Changes global signal handling and exit semantics for all CLI invocations; incorrect behavior could affect shutdown, loop scripts, or interrupt during credential access.

Overview
Fixes Ctrl-C so it reliably stops the CLI and breaks enclosing shell loops (e.g. while true; do entire …; done), instead of respawning each iteration or printing noisy cancellation/keyring errors.

Process shutdown (main): The first SIGINT cancels the root context and prints a short “Interrupting…” hint; a second Ctrl-C force-quits. User aborts that surface as context.Canceled no longer print as failures—they go through dieFromInterrupt, which resets SIGINT and re-raises it to the process so the shell sees a signal-killed child (not a plain exit 130), which is what breaks while loops.

Keyring reads: Wrapped OS keyring calls now also listen for SIGINT for the duration of the call, returning immediately with an error wrapping context.Canceled (same silent abort path) instead of waiting for the full timeout when the backend is stuck.

Adds a unit test for the injectable interrupt path on keyring calls.

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

[Copilot]

Pull request overview

This PR improves interrupt (Ctrl-C) behavior across the Entire CLI so cancellations abort cleanly, break enclosing shell loops, and avoid noisy “context canceled” / keyring transport errors.

Changes:

• Updates process-level signal handling so a canceled root context exits via a SIGINT-style termination (vs. a normal exit) to escape shell loops.
• Makes OS keyring operations abort promptly on Ctrl-C (instead of waiting for the keyring timeout), surfacing as context.Canceled.
• Adds a unit test to exercise the keyring interrupt path via an injected interrupt channel.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
cmd/entire/main.go	Adjusts global signal handling and cancellation exit semantics to better match Ctrl-C expectations in shells.
internal/entireclient/tokenstore/keyring_timeout.go	Adds SIGINT listening to keyring calls so Ctrl-C unblocks stuck keyring reads before the timeout.
internal/entireclient/tokenstore/keyring_timeout_test.go	Adds a unit test validating the interrupt branch returns promptly and wraps context.Canceled.