Problem: It's unclear whether isq issue list requires the daemon to be running, or if it reads directly from SQLite cache. If daemon is required for reads, that's unnecessary coupling. If it's not required, that's not documented or guaranteed.
Goal: Ensure and document that read operations work independently of daemon state.
Success criteria:
isq issue list works when daemon is stopped (reads from last-synced cache)- Behavior documented: "reads work offline, writes require network"
- Clear error message if data is stale: "Last synced: 2 hours ago. Run isq sync to update."
- Test coverage for daemon-stopped read path
Context (Rich Hickey's Simple Made Easy): Simple = components work independently. Complecting read operations with daemon state adds hidden coupling. Each piece should function on its own.
Problem: It's unclear whether
isq issue listrequires the daemon to be running, or if it reads directly from SQLite cache. If daemon is required for reads, that's unnecessary coupling. If it's not required, that's not documented or guaranteed.Goal: Ensure and document that read operations work independently of daemon state.
Success criteria:
isq issue listworks when daemon is stopped (reads from last-synced cache)Context (Rich Hickey's Simple Made Easy): Simple = components work independently. Complecting read operations with daemon state adds hidden coupling. Each piece should function on its own.