fix(task): resolve close/reopen statuses from the list instead of hardcoding

[timimsms]

Summary

Fixes #32. task close sent the literal status "complete" and task reopen sent "open". Those names only exist on lists using ClickUp's default status set — against any custom set the API rejects the update:

$ cu task close 86e2y09rd
Failed to close task: PUT https://api.clickup.com/api/v2/task/86e2y09rd: 400 Status does not exist ITEM_114

That list's statuses are backlog → scoping → in design → in development → in review → testing → ready for development → shipped → cancelled. Nothing is called "complete", so close was simply unusable there.

Both commands now resolve the status from the task's own list by status type rather than name — done (falling back to closed) for close, and the first open status in board order for reopen:

$ cu task close 86e2y09rd
✓ Closed task 86e2y09rd: …
$ cu task view 86e2y09rd | grep Status
Status: shipped
$ cu task reopen 86e2y09rd
  New status: backlog

--status overrides on both, for lists with more than one done status.

Bulk close resolves per task rather than once, since a bulk close can span lists with different status sets, and caches per list so one list still costs one lookup. A task whose list has no done status fails that task and continues, rather than aborting the batch.

Adds Client.GetList, which the SDK supported but the client did not expose.

Tests

TestClosedStatus / TestOpenStatus cover a real custom set (done wins over closed), the default set, tie-breaking by orderindex among several done statuses, and the error path naming the available statuses. Verified live against a list with a custom status set — the failing command above is from main, the passing ones from this branch.

Checklist

• ./scripts/ci.sh passes locally — except errcheck, which reports the same 27 pre-existing findings on main, none in files this PR touches
• Commit messages use conventional prefixes
• CLI docs regenerated (cu docs markdown --dir docs/site/commands) — new --status flags on close/bulk close
• Docs updated if user-facing behavior changed

[timimsms]

Review — no blockers, ship it

Cleanest of the three. Resolving by status type rather than name is the correct read of the ClickUp model, the done-over-closed preference is the right default, and --status gives an escape hatch for lists with several terminal statuses. Building the test fixtures via json.Unmarshal because the SDK models Statuses as an anonymous struct slice is the right workaround, and the TestClosedStatus cases cover the actual failure that motivated this — a status set where nothing is named complete.

Nice detail: bulk close resolving per task rather than once, since a bulk close can legitimately span lists with different status sets.

Non-blocking

1. bulk close now costs one extra GetTask per task on the default path. listForTask fetches the task before consulting the list cache — it has to, that's how it learns the list id — so the cache saves the GetList but not the GetTask. A 200-task bulk close is 200 extra rate-limited calls it didn't make before. Passing -s skips resolution entirely, so the escape hatch is already there; worth a line in the command's Long help pointing at -s for large closes across a known-uniform list.

2. Regenerated doc timestamps read 22-Aug-2026 against a PR opened the 25th. Cosmetic, only mentioning it because all three doc files carry it.