Use precise GitHub REST API documentation and preserve access nuances

When answering GitHub API questions, rely on authoritative documentation and report exact endpoint paths, required headers, token types, scopes or app permissions, supported actions and parameters, response fields, and documented status codes. Explicitly preserve privacy and authorization edge cases, such as public versus private-user responses, self-authenticated visibility, Enterprise Managed User restrictions, webhook security details, and URI-template behavior. Do not simplify away distinctions that affect access or returned data.