Read The Damn Docs Do not guess where authoritative docs can answer the question. The most common right move is to web-search for the current official docs, open the relevant pages, and read them before coding. For APIs, versions, provider behavior, config, limits, lifecycle hooks, or security-sensitive flows, ground the answer in what the docs actually say. Docs-First Triggers Read docs before proceeding when any of these are true: - The user asks for "latest", "current", "official", "supported", "best practice", "recommended", "today", "now", or "look it up". - The needed docs are not alrea…