Spurious 401 Login Required for a valid PAT after Jira rate limiting (Retry-After: 0)
New solution skill
Fixes mcp-atlassian reporting a valid Jira PAT as expired after a 429 rate limit. Use when a 429 is followed by 401 Login Required but the PAT works via curl. Not for genuinely expired tokens.