fix(ci): unset CLICOLOR_FORCE so NO_COLOR takes effect (#1325)

## Summary

- Unsets `CLICOLOR_FORCE` in `list-recent-runs.sh` before setting
`NO_COLOR=1`
- `CLICOLOR_FORCE=1` (set by the Claude Code environment) overrides
`NO_COLOR` per the [clicolors spec](https://bixense.com/clicolors/),
causing `gh` to emit ANSI codes in JSON output that break `jq` parsing

Fixes #1324

## Context

PR #1317 added `NO_COLOR=1` to fix ANSI codes in `gh` output, but the
Claude Code environment also sets `CLICOLOR_FORCE=1` which takes
precedence. Every hourly review run fails at startup because
`list-recent-runs.sh` can't parse the colorized JSON.

## Test plan

- [ ] Hourly review runs should no longer fail with `jq: parse error:
Invalid numeric literal`

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

Author: worktrunk-bot

.github/scripts/list-recent-runs.sh

@@ -12,6 +12,9 @@
 set -euo pipefail
 
 # Prevent gh from emitting ANSI color codes (even in non-TTY contexts).
+# CLICOLOR_FORCE overrides NO_COLOR per the clicolors spec, and Claude Code
+# sets CLICOLOR_FORCE=1 — so we must unset it for NO_COLOR to take effect.
+unset CLICOLOR_FORCE
 export NO_COLOR=1
 
 # Dynamically discover all claude-* workflows instead of maintaining a hardcoded list.