add_repo/GitHub API access to public repos now requires push permission, breaking read-only issue checks

Previously, this Claude Code cloud environment could read public GitHub data (e.g. GET /repos/{owner}/{repo}/issues/{n}) for repos the connected account has no write access to — this worked reliably across multiple scheduled sessions over several days.

As of today, every path to api.github.com/github.com from the session (curl, WebFetch, and the add_repo MCP tool) returns a block:

• curl/WebFetch → 403, body: "GitHub access to this repository is not enabled for this session. Use add_repo to request access."
• add_repo with access:"push" → "you need push access to anthropics/claude-code for Claude to make changes there"

This reproduces for arbitrary public repos (tested anthropics/claude-code and torvalds/linux), not just one repo, and persists after fully reconnecting GitHub via claude.ai. It appears add_repo's API-access tier now requires push/write permission on the target repo even for a pure read (e.g. fetching one public issue), with no read-only API tier available. That's a hard blocker for any automated task that only needs to read public GitHub data on a repo the user doesn't own