Fix card list to be cross-board by default

[waynemsmith]

Summary

• card list called defaultBoard(), injecting the configured default board into every query and silently scoping results to a single board
• This made --tag and --assignee filters appear broken when matching cards lived on other boards — the same bug fixed for search in Fix search to be cross-board by default #114, but in the sibling card list command
• Fix: only add board_ids[] when --board is explicitly passed, so card list is cross-board by default (matching search and the API)

Bare fizzy card list now spans all boards instead of the configured default board, consistent with the cross-board API default.

Follow-up to #113 / #114.

Test plan

• go test ./internal/commands/ -run TestCardList — all pass (updated the default-board test to assert no injection; added cross-board --tag and --assignee tests)
• Manual: fizzy card list --tag TAG_ID --all returns cards across all boards
• Manual: fizzy card list --board BOARD_ID --tag TAG_ID still scopes when --board is explicit

🤖 Generated with Claude Code

---

Summary by cubic

Make fizzy card list cross-board by default so --tag and --assignee return results across all boards. Only add board_ids[] when --board is passed, matching search and the API default.

• Bug Fixes

  • Removed implicit default board injection; now only scopes when --board is set.
  • --tag and --assignee filters work across boards.
  • Updated tests for cross-board default and explicit board scoping.

• Migration

  • Behavior change: bare fizzy card list now spans all boards. Use --board BOARD_ID to limit results.

^{Written for commit 3991e2d. Summary will update on new commits.}

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[cubic-dev-ai]

No issues found across 2 files

_{Re-trigger cubic}

[robzolkos]

Thanks for digging into this. Before we remove the default-board scoping, I want to lay out how the current behavior actually works, because I don't think it's broken in the way the description suggests.

card list calls defaultBoard(cardListBoard), which returns the configured board (cfg.Board / FIZZY_BOARD / profile) only when it's set, and an empty string otherwise. So:

• No default board configured → no board_ids[] is added → card list (and --tag / --assignee) already span all boards today.
• Default board configured → everything scopes to that board.

So the scoping only affects people who have deliberately set a default board, and for them I'd argue this is the expected behavior: my default board is my workspace, so a bare fizzy card list - and filters on top of it - should stay within it. That's the convenience of configuring a default in the first place.

I'd rather keep that behavior and add an explicit opt-out for when you want to go wide, rather than make the default board silently stop affecting card list:

• fizzy card list → default board if configured, else all boards (unchanged)
• fizzy card list --all-boards --tag X → search across every board

Note --all is already taken here (fetch all pages), so the override needs its own name - I'm leaning --all-boards.

The one real tradeoff: under this approach card list --tag X with a default board set still scopes to that board, which is the opposite of what this PR (and #113) assumed. I think that's the more predictable model, but happy to talk it through.