framework-drift-guardlisted

# The problem A fast-moving framework's current API can differ from what an agent learned in training — route conventions, config file shape, even which primitives still exist. An agent that doesn't know this writes confident, fluent, wrong code: it compiles in the agent's head and fails against the actual `node_modules` on disk. The fix is not "know more" — it's forcing a read of the installed docs before the first line of code, every session, for exactly the dependencies where drift is likely. ## The canonical banner This is the literal text to emit, unedited except where noted below. Keep the HTML comment markers — they let a later pass find and update the block without touching anything else in `AGENTS.md`. ```markdown <!-- BEGIN:nextjs-agent-rules --> # This is NOT the Next.js you know This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in `node_modules/next/dist/docs/` before writing any code. Heed deprecation notices. <!-- END:nextjs-agent-rules --> ``` ## The evidence Kintwadi (Best Design) and Sonar (First Place, Million-scale Global) — two unrelated winning projects, different teams, different hackathons — ship this banner byte-identical. Sonar's entire `AGENTS.md` is these five lines and nothing else. That is not a coincidence of two people copying each other; it is evidence that this exact wording is a settled form for the problem, not something to workshop. See `../securi