Summary

• align the interactive remove flow with switch so the no-query picker refreshes latest API usage before rendering account choices
• pass per-account usage overrides through the remove selectors so HTTP status and MissingAuth overlays render in both usage columns just like list and switch
• add q quit handling to the remove TUI, and update docs/tests to describe and cover the new behavior

Validation

• zig test src/main.zig -lc
• zig build run -- list
• zig test src/main.zig -lc --test-filter "Given remove query with one match when running remove then it deletes immediately and prints a summary"
• zig test src/main.zig -lc --test-filter "Given non-tty stdin when running interactive remove then it falls back to the numbered selector"

Risks

• the main behavior change is that remove without a query now does the same foreground Node/API preflight as the interactive switch picker when api.usage = true
• query-driven remove and remove --all intentionally stay local-only before deletion, so reviewers should verify that scope split matches expectations
• the remove picker now shares more of the switch-row rendering path, so extra attention on selector UI behavior and status overlays is useful

PR Loop Status

• latest push intent: send the remove/switch alignment changes for CI and review
• latest CI status: green across CI and preview-package checks
• review comments addressed in the latest push: none yet
• open comments intentionally left unresolved and why: none