feat(issue): add --from/--to bulk project-to-project mode to lc issue move

[bougyman]

Summary

Extends the existing lc issue move command (which moves explicit issue IDs via --project) with a second bulk project-to-project mode: lc issue move --from SOURCE --to TARGET.

• Optimus spec updated with --from/--to/--all options alongside the existing --project/--team (single spec, two modes)
• issue_move/1 dispatches on presence of --from/--to vs issue IDs — all existing ID-based behavior is unchanged
• Bulk mode resolves both projects (UUID used directly; name searched within --team), guards against same-project moves, lists open issues from source (mine: false, all: flags.all), then fans out concurrent mutations (max 20, ordered, 30s timeout) following the issue_status/1 pattern
• Per-issue "moved to" lines + summary count on completion; --output json emits an array of updated issue maps; --dry-run lists without mutating

Test plan

• 7 new issue move --from/--to tests: happy path (3 mutations), --all (no date guards in filter), --dry-run (no mutations), error mid-batch (non-zero exit), --output json (decodable array of 3), UUID bypass (no $teamId query), same-ID guard (halts before list query)
• All 333 existing tests still pass (ID-based mode unchanged)
• mix ci passes (compile clean, credo no issues, usage_rules sync, 340/340 tests)

Closes EXT-10.

🤖 Generated with Claude Code

[Copilot]

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

[bougyman]

Rework summary (addressing code review feedback)

Three minor issues from the review have been addressed in commit a1a87e0:

1. Silent decline in bulk mode → fixed

When the user declines the --from/--to confirmation prompt, the code now prints "Move cancelled" (same as the ID-based mode). Previously it returned :ok silently.

File: app/lib/linear_cli/cli/commands.ex — move_issues_by_project/2 cond branch.

2. Partial --from/--to → clear error

Passing only one of --from or --to now returns {:error, {:smells_bad, "--from and --to must both be given for bulk project-to-project mode"}} immediately, exiting with code 22 and a readable message. Previously it fell through to ID mode, producing confusing downstream errors.

File: app/lib/linear_cli/cli/commands.ex — issue_move/1 dispatch, converted if to cond with a third branch.

3. UUID-as-name in output → short label

resolve_bulk_project/2 now creates the synthetic project struct with name: "00000000…" (first 8 hex chars + ellipsis) instead of the full UUID string. Summary lines now read "Moved 3 issue(s) from 00000000… to 00000000…" rather than full UUIDs.

File: app/lib/linear_cli/cli/commands.ex — resolve_bulk_project/2.

Tests added

Three new tests in issue_commands_test.exs:

• --from/--to user declines prints 'Move cancelled'
• --from without --to exits 22 with a clear error
• --to without --from exits 22 with a clear error

Quality suite: mix ci exits 0 — compile clean, format clean, credo clean, 343/343 tests (3 new).

Observations not acted on

• IssueHelpers.move_issue/2 is intentionally not used by the concurrent paths (correct — tasks should not print during streaming).
• Duplicate async_stream logic left as-is (small, not worth an abstraction at this scale).