Missing context usage causes unresponsive CLI behavior #44
Description
The CLI does not propagate context.Context through its execution flow. Long-running or blocking operations (network calls, filesystem I/O, external commands) cannot be cancelled or timed out.
Impact
- Ctrl+C does not stop in-flight work.
- Hung network calls block the process indefinitely.
- External commands keep running after exit intent.
- Poor UX in CI and automation.