Resolve nextra-migration merge conflicts and patch Next.js DoS vulnerability

[Copilot]

PR #496 (nextra-migration) had conflicts against main and introduced next@15.2.8, which is affected by an HTTP request deserialization DoS vulnerability in React Server Components.

Conflict resolutions

• next-env.d.ts — took updated TypeScript docs URL from nextra-migration
• pages/docs/_meta.json — deleted; superseded by _meta.ts from nextra-migration
• pages/docs/flows/_meta.ts — adopted TS export default format; preserved "Flow Editor" capitalisation from main
• pages/docs/interface/_meta.ts — adopted TS structured-object format from nextra-migration
• pages/docs/legal/_meta.ts — adopted TS format; retained all four entries (cookie-policy, data-deletion-policy) added in main after the branch diverged
• theme.config.tsx — took nextra-migration changes: removed FooterMenu/DocsFooter/FooterWrapper imports, removed lucide-react sidebar icons, dropped titleComponent (replaced by SidebarSwitcher), replaced footer.component with footer.content: null, removed useNextSeoProps

Security fix

Upgraded next from 15.2.8 → 15.2.9 (patched version for the >= 15.2.0-canary.0, < 15.2.9 affected range).

// package.json
- "next": "15.2.8"
+ "next": "15.2.9"

---

💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
site	Error		Mar 17, 2026 0:21am