Summary

When PARSEC_GITHUB_TOKEN is unset, PR creation fails with 401. However, a valid token may be available via gh auth token.

Proposed Solution

Token resolution priority:

1. PARSEC_GITHUB_TOKEN
2. GITHUB_TOKEN
3. GH_TOKEN
4. gh auth token command output (fallback, only when gh CLI is installed)

Context

Token existed in ~/.claude/.atlassian-env but wasn't loaded in the session → parsec 401 → gh CLI worked fine via its own auth