Add Avocado to your site

Wire Avocado Studio into this Next.js project (App Router, Next 15 or 16).
Reference: https://docs.avocadostudio.dev/quickstart

Do exactly this, then verify:

0. If this directory has no Next.js app in it yet, create one first:
   npx create-next-app@latest . --ts --app --tailwind --eslint --no-src-dir \
     --import-alias "@/*" --use-npm --yes
   If it already has one, change nothing about it and go to step 1.

1. npm install @avocadostudio-ai/site-sdk @avocadostudio-ai/orchestrator-core

2. next.config.ts — wrap the exported config in `withAvocado` from
   "@avocadostudio-ai/site-sdk/next-config". Do not hand-write
   serverExternalPackages or transpilePackages: withAvocado sets those and the
   server externals together, and setting one of the three alone silently fails
   on the native dependencies.

3. app/globals.css — add `@import "@avocadostudio-ai/blocks/styles.css";` as the
   first line. Without it the page renders correctly and renders unstyled.

4. content/pages.json — one page: { id, slug: "/", title, updatedAt, blocks: [] }
   with a "Hero" block (props: heading, subheading, ctaText, ctaHref) and a "CTA"
   block (props: title, description, ctaText, ctaHref). Both are built-in types.

5. lib/content.ts — getPage(slug), getSlugs(), getPages() reading that JSON,
   plus getSiteConfig() returning a literal like { name: "My Site" }: the file
   holds pages and has nowhere to put site config. Types PageDoc and SiteConfig
   come from "@avocadostudio-ai/shared".

6. app/api/editor/[...path]/route.ts — export { GET, POST, OPTIONS } from
   createEditorApiHandler({ getPages, onPublish, publishSecret }) where
   createEditorApiHandler is from "@avocadostudio-ai/site-sdk/routes",
   onPublish is
   createJsonFilePublishHandler(resolve(process.cwd(), "content/pages.json"))
   from "@avocadostudio-ai/site-sdk/publish-handlers/json-file", and
   publishSecret is process.env.PUBLISH_TOKEN?.trim() || undefined. That route
   overwrites the site's content, so it refuses every request under
   NODE_ENV=production while publishSecret is unset.

7. app/api/avocado/[[...path]]/route.ts — createOrchestrator from
   "@avocadostudio-ai/site-sdk/server" with jsonFileAdapter from
   "@avocadostudio-ai/orchestrator-core/cms" pointed at the same JSON file and
   passed writeOnPublish: true — it defaults to false, which leaves the adapter
   with no onPublish, and Publish then reports success and writes nothing. Plus
   `export const runtime = "nodejs"` and `export const dynamic = "force-dynamic"`.
   Export the handler as GET, POST and OPTIONS — createOrchestrator returns one
   callable, so assign it three times rather than destructuring it.
   Pass a siteId. It must be the same string as step 8's, or the page asks for a
   draft session the orchestrator never seeded.

8. app/[[...slug]]/page.tsx — createSitePage from
   "@avocadostudio-ai/site-sdk/page" with siteId, siteName, getPage, getSlugs,
   getSiteConfig, and siteUrl: process.env.NEXT_PUBLIC_SITE_URL.
   Export default Page AND export { generateStaticParams, generateMetadata } —
   without the second export every page inherits the root layout's title and
   ships no description. Without siteUrl the pages carry no canonical link, no
   og:url, and an og:image left as the relative path the content stores, which
   no social crawler resolves.

9. Delete or move every route that matches a slug now served by getPage,
   app/page.tsx included. A more specific route keeps winning, Next reports no
   conflict and logs nothing, so the site looks unchanged and the integration
   looks dead.

10. .env.local — ANTHROPIC_API_KEY (or OPENAI_API_KEY, or GOOGLE_GENAI_API_KEY),
    ORCHESTRATOR_URL=http://localhost:3000/api/avocado, DRAFT_MODE_SECRET set to
    any long random string, NEXT_PUBLIC_SITE_URL=http://localhost:3000, and
    PUBLISH_TOKEN set to a second long random string. Without DRAFT_MODE_SECRET
    the orchestrator boots and warns that draft mode will not work.

11. .gitignore — add a line for .data/. The orchestrator writes its SQLite state
    there, in the project root, on the first request; create-next-app's
    .gitignore does not cover it, so the first `git add .` after the first run
    commits a database.

Rules: use those import specifiers exactly, never a deep path into dist or src.
Add no middleware and no proxy — mode "auto" needs neither. If this project
already renders pages from a CMS, point getPage/getSlugs at that instead of the
JSON file and tell me you did.

Verify before reporting success. All four must pass:
- `npm run dev` starts with no error
- GET /api/avocado/health returns {"ok":true,"mode":"library"}
- GET /api/editor/pages returns the page from content/pages.json
- GET / returns HTML containing the hero heading and `class="hero"`

Do not verify with data-block-id. Those markers are editor-mode only, and in
development every request resolves an editor context, so asserting on them
proves "this is a dev server" rather than "the blocks rendered".

adapter: jsonFileAdapter({
  path: path.join(process.cwd(), "content", "pages.json"),
  writeOnPublish: true,
}),