Document agent upgrades across Next.js (#99293)
### Why? Document the supported `next upgrade --agent` workflow without presenting the unfinished `experimental-future` policy as the recommended path in feature guides. ### How? - Add a human-facing Agent Upgrade guide and an `experimental.agentUpgrade` API reference. - Link the workflow from the App and Pages upgrade docs, CLI reference, and AI agent guide. - Document the `security`, `latest`, and `experimental-future` policies in the upgrade guide, CLI reference, and config reference. - Keep the dedicated Skills as the recommended path for Cache Components, Partial Prefetching, and the combined Instant Navigation migration. - Explain that version upgrades provide the applicable migration guides and Skills to the coding agent. - Show the interactive agent, model, reasoning, Auto-permission, and worktree prompts. - Document the non-blocking `next dev` and `next build` reminders, the DevTools Vulnerability Insight, and the default `security` policy from #99311. ### Verification - Prettier passes on all changed documentation files. - Targeted ESLint passes with no errors. - Alex reports no new warnings in the changed content. - Feature guides recommend the dedicated Skills instead of `experimental-future`. <!-- NEXT_JS_LLM --> Closes NAR-944 --------- Co-authored-by:Aurora Scharff <aurora.sofie@gmail.com> Co-authored-by:
Claude Opus 5.5 <noreply@anthropic.com>
Showing
Please
register
or
sign in
to comment