r-zakarya
0bcf9b95a2
The plan said to create a personal token "limited to this repo". Gitea has no such thing - checked against 1.26.1: its scopes are per category and account-wide, so read:repository grants read on every repo the account can read. That is not GitHub's fine-grained model, and the difference changes what you actually do. So the section now says what is available instead, cheapest first: read:repository alone while the phone only reads, a separate token on the PC when publishing lands, and a dedicated Gitea account as collaborator if real isolation is ever needed. Also recorded: the contents endpoint answers 404 unauthenticated on a private repo, which is the same snapshot-absent-or-no-access ambiguity the PHP endpoint has, and the client already treats it as "nothing to download". Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
