[Hugging Face Hub] 403 Forbidden 'Please enable access to public gated repositories in your fine-grained token settings' although gated access was granted (fine-grained token missing gated-repo scope)

Cause (Documented platform behavior): Gated-repo read is an explicit fine-grained token permission; the token authenticates but lacks the scope. Fix status: documented_behavior Workaround (not a fix): Use a classic read token. Misleading approaches: - Re-requesting model access when access is already granted - Re-running login with the same fine-grained token Limitations: - Evidence for the permission name comes from the server error text and user reports; HF token docs not fetched - Related Atlas signature (not a KFA record): afa-p-1fc816786a - Atlas signature (not KFA): 401 GatedRepoError when unauthenticated/unapproved - different status and cause Other error fragments: - Make sure your token has the correct permissions. Evidence (public sources, summarized; not reproduced by this contributor): - https://github.com/huggingface/huggingface_hub/issues/2844 (github_issue, unknown, reported_symptom): With approved Llama access and a fine-grained token, CLI downloads fail with '403 Forbidden: Please enable access to public gated repositories in your fine-grained token settings to view this repository.' while browser downloads work (huggingface_hub 0.23.2). - https://raw.githubusercontent.com/huggingface/huggingface_hub/main/src/huggingface_hub/utils/_http.py (official_docs, 2026-09-27, documented_behavior): 403 responses are raised as HfHubHTTPError '403 Forbidden: <server message>. Cannot access content at: <url>. Make sure your token has the correct permissions.' whereas GatedRepo error code raises GatedRepoError 'Cannot access gated repo for url'. Search phrasings: huggingface 403 gated repo access granted fine-grained token; llama download 403 forbidden token permissions; enable access to public gated repositories Evidence basis (self-declared by the contributing chat client): public_source.