@soloworks/smking-next 0.10.0 → 0.12.1

package/CHANGELOG.md

@@ -1,5 +1,82 @@
 # @soloworks/smking-next
 
+## 0.12.1 — 2026-05-21
+
+**Fix: `npx @soloworks/smking-next doctor` failed for all customers.**
+
+### Fixed
+
+- `bin/install.ts` shipped as raw TypeScript on the assumption that Node 22+'s `--experimental-strip-types` would handle it. It doesn't — by design, Node excludes files under `node_modules/` from type-stripping (packages should ship compiled JS). Every `npx @soloworks/smking-next install|doctor` invocation failed with "Type-Stripping is not supported for files under node_modules" the moment a customer's install reached the doctor check. smking-wizard reproduced the bug 3× and filed ticket `dr_e0b7d8e924cd`.
+- Renamed to `bin/install.mjs` with TypeScript syntax stripped (JSDoc type hints retained for editor / dev ergonomics). Pure ESM, no build step, no runtime type stripping needed.
+- Source modules (`src/*.ts`) unchanged — Next.js's bundler handles them at customer build time. Only the standalone-executable bin script needed JS form.
+
+## 0.12.0 — 2026-05-15
+
+**AI crawler + AI referral telemetry — `smkingProxy` Next.js middleware.**
+
+### Added
+
+- **`@soloworks/smking-next/proxy` subpath export.** New `smkingProxy({ apiKey, baseUrl? })` middleware factory + `composeProxy([...handlers])` helper. Detects AI bot UAs (17 patterns covering GPTBot / ClaudeBot / PerplexityBot / Google-Extended / Applebot / CCBot / Bytespider / meta-externalagent / Amazonbot / Cohere / Diffbot) and AI-referrer hostnames (chatgpt.com / perplexity.ai / claude.ai / gemini.google.com / copilot.microsoft.com / bing.com), then fire-and-forgets a `POST /api/v1/crawler-hit` ingest via Vercel `after()` so the customer's response is never delayed.
+
+  Install:
+
+  ```ts
+  // proxy.ts
+  import { smkingProxy } from "@soloworks/smking-next/proxy";
+
+  export const proxy = smkingProxy({ apiKey: process.env.SMKING_API_KEY! });
+
+  export const config = {
+    matcher: ["/((?!_next/static|_next/image|favicon.ico).*)"],
+  };
+  ```
+
+  Composing with an existing proxy:
+
+  ```ts
+  import { composeProxy, smkingProxy } from "@soloworks/smking-next/proxy";
+  import { customerProxy } from "./their-proxy";
+
+  export const proxy = composeProxy([
+    smkingProxy({ apiKey: process.env.SMKING_API_KEY! }),
+    customerProxy,
+  ]);
+  ```
+
+  Fail-open: missing `SMKING_API_KEY` / `SMKING_BASE_URL` → no-op (matches `getAeoContent` convention). Ingestion endpoint down / 4xx / 5xx → silent skip. Customer site never breaks because of telemetry.
+
+### Why
+
+Crawler telemetry feeds the new 4-pillar AEO Scorecard (visibility / bot engagement / content readiness / traffic impact). Without per-customer-site detection, the scorecard's Bot Engagement and Traffic Impact pillars stay at zero forever. SDK ships the detection so customers don't need to roll their own — `pnpm update @soloworks/smking-next` + add 5-line `proxy.ts` = done.
+
+### Customer migration
+
+- **Caret rule reminder**: `^0.11` resolves to `>=0.11.0 <0.12.0`, so `pnpm update` will NOT pull 0.12 automatically. Bump constraint to `^0.12` in `package.json` to receive this release.
+- No other breaking changes vs 0.11. AEO / CMS / webhook surfaces unchanged.
+
+## 0.11.0 — 2026-05-15
+
+**Substrate pivot: unified webhook channel.**
+
+### BREAKING
+
+- **Unified webhook endpoint.** `@soloworks/smking-next/webhook` replaces the previous split: `/route` (AEO Bearer-authed) AND `/cms-webhook` (CMS HMAC). Single HMAC-signed endpoint, payload `.kind` (`"aeo" | "cms_page" | ...`) dispatches which revalidate tag namespace to use.
+
+  Customer migration:
+  1. **Env**: `SMKING_WEBHOOK_TOKEN` → `SMKING_WEBHOOK_SECRET` (HMAC key — same secret you got from the install prompt for CMS, now used for everything).
+  2. **Route shim**: replace both `app/api/smking-revalidate/route.ts` (AEO) AND `app/api/smking/webhook/route.ts` (CMS) with a single `app/api/smking/webhook/route.ts` exporting `POST` from `@soloworks/smking-next/webhook`.
+  3. **Dashboard webhook URL** field should point at the single `/api/smking/webhook` path.
+
+- **Revalidate tag namespaces changed.** Customer code calling `revalidateTag` directly (rare — most customers use `<SmkingAEO />` / `<SmkingCms />` which handle this internally) must update:
+  - `smking:path:*` → `smking:aeo:*`
+  - `smking:cms:*` → `smking:cms_page:*`
+
+- **`/route` and `/cms-webhook` exports removed.** Importing either at v0.11 fails with a "Module not found" error pointing customers at the migration. Old source files deleted from the package (git history preserves them).
+
+### Why
+
+PostHog architectural pattern study (`docs/cms-tech-suggestions-posthog.md`) flagged the split webhook as substrate-discipline violation. One channel for the substrate; payload `kind` distinguishes projection. Future product surfaces (widget config, crawler analytics, Shopify connector) extend the discriminator without growing the SDK.
+
 ## 0.10.0 — 2026-05-14
 
 **`SmkingCms` typing fix + CMS revalidate default aligned to 5 min.**

package/README.md

@@ -84,6 +84,71 @@ Content-Type: application/json
 
 Response: `{ revalidated: number, errors: number }`. `errors > 0` means some tags couldn't be revalidated (others still succeeded — partial-success delivery).
 
+## CMS rendering (optional, v0.11.0+)
+
+The base install only wires AEO. If you author content in the smking dashboard's CMS and want to render it on your Next.js site, use the `<SmkingCms slug="…" />` Server Component.
+
+The SDK **does not have a "CMS root" config** — you choose any URL prefix (`/blog`, `/knowledge`, `/shop/articles`) and wire your own route. The component takes a `slug` prop, fetches the published page from `${SMKING_BASE_URL}/api/v1/public/page?slug=…`, and renders the Tiptap ProseMirror JSON as `<article class="smk-cms">…</article>` via `@tiptap/static-renderer/pm/react`. SEO `<title>` / `<meta>` / `og:*` / canonical hoist into `<head>` automatically via React 19.
+
+### Catch-all route (handles flat + nested slugs)
+
+smking CMS slugs can be nested — e.g. `blog/123`, `blog/seo/intro`. Use Next.js catch-all `[...slug]` (three dots, not single `[slug]`) so one route handles every depth:
+
+```tsx
+// app/blog/[...slug]/page.tsx
+import { SmkingCms } from "@soloworks/smking-next/cms";
+
+export default async function Page({
+  params,
+}: {
+  params: Promise<{ slug: string[] }>;
+}) {
+  const { slug } = await params;
+  return (
+    <SmkingCms
+      apiKey={process.env.SMKING_API_KEY!}
+      slug={slug.join("/")}  // ← array → "blog/seo/intro" matches dashboard slug format
+    />
+  );
+}
+```
+
+`[...slug]` accepts both flat (`/blog/hello` → `["hello"]`) and nested (`/blog/seo/intro` → `["seo", "intro"]`). The `.join("/")` reconstructs the dashboard slug string.
+
+Single-bracket `[slug]` (without the three dots) **only matches one segment** — pick this if you know your slugs are always flat.
+
+### Markup contract for CSS
+
+```html
+<article class="smk-cms" data-smking="cms">
+  <h1 class="smk-cms__title">…</h1>
+  <p>standard prose</p>
+  <h2>headings</h2>
+  <ul><li>lists</li></ul>
+  <blockquote>…</blockquote>
+  <pre><code>code blocks</code></pre>
+  <a href="…">links</a>
+  <img src="…" alt="…">
+  <div data-type="gallery"
+       data-layout="grid"
+       data-columns="3"
+       class="smk-gallery smk-gallery--grid">
+    <figure class="smk-gallery__item">
+      <img src="…" alt="…" loading="lazy">
+      <figcaption>optional</figcaption>
+    </figure>
+  </div>
+</article>
+```
+
+Standard nodes inherit your site's prose styling. Gallery is the only opinionated structure — provide CSS for `.smk-gallery` (typically a grid with `grid-template-columns: repeat(var(--smk-gallery-cols, 3), 1fr)` since the SDK injects `--smk-gallery-cols` inline).
+
+### Cache invalidation
+
+CMS responses cache for 5 minutes by default via Next.js data cache (`tags: ["smking:cms_page:<slug>"]`). When you publish, rename, or archive a page in the dashboard, smking SaaS POSTs a signed webhook to `https://<your-site>/api/smking/webhook` (mount with one-line re-export — see Install). The handler verifies HMAC against `SMKING_WEBHOOK_SECRET` and calls `revalidateTag` so the next visitor reads fresh content.
+
+If `SMKING_WEBHOOK_SECRET` is unset, the webhook route returns 503 and cache invalidation falls back to TTL-based expiry.
+
 ## Versions
 
 See [CHANGELOG.md](./CHANGELOG.md). Aligned with `smking/laravel` for SaaS-side parity.

package/bin/{install.ts → install.mjs}

@@ -2,8 +2,14 @@
 /**
  * `npx @soloworks/smking-next [install|doctor] [--json]`
  *
- * Two subcommands share this entry point (Node 22+ strips TS at runtime, so
- * the package ships .ts source directly — no build step):
+ * Two subcommands share this entry point. The file ships as plain ESM
+ * (`.mjs`) since Node's `--experimental-strip-types` is excluded from
+ * files under `node_modules` by design — so `bin/install.ts` (the
+ * previous v0.12.0 layout) fails with "Type-Stripping is not supported
+ * for files under node_modules" the moment a customer runs `npx
+ * @soloworks/smking-next`. Source modules (`src/*.ts`) are still TS —
+ * Next.js's bundler handles them at customer build time. Only this
+ * standalone-executable bin script needed to drop TS.
  *
  * - **install** (default) — One-shot scaffold for the three takeover
  *   drop-in files (sitemap.ts / robots.ts / llms.txt route). Idempotent:
@@ -19,36 +25,32 @@
 import { existsSync, mkdirSync, readFileSync, writeFileSync } from "node:fs";
 import { join } from "node:path";
 
-// ── install (既有功能) ──────────────────────────────────────────
+// ── install (file scaffold) ─────────────────────────────────────
 
-interface FileSpec {
-  path: string; // relative to detected app root
-  content: string;
-  label: string;
-}
+/**
+ * @typedef {{ path: string, content: string, label: string }} FileSpec
+ */
 
-const FILES: FileSpec[] = [
+/** @type {FileSpec[]} */
+const FILES = [
   {
     path: "sitemap.ts",
     label: "sitemap.ts → /sitemap.xml",
-    content:
-      'export { default } from "@soloworks/smking-next/sitemap";\n',
+    content: 'export { default } from "@soloworks/smking-next/sitemap";\n',
   },
   {
     path: "robots.ts",
     label: "robots.ts → /robots.txt",
-    content:
-      'export { default } from "@soloworks/smking-next/robots";\n',
+    content: 'export { default } from "@soloworks/smking-next/robots";\n',
   },
   {
     path: "llms.txt/route.ts",
     label: "llms.txt/route.ts → /llms.txt",
-    content:
-      'export { GET } from "@soloworks/smking-next/llms-txt";\n',
+    content: 'export { GET } from "@soloworks/smking-next/llms-txt";\n',
   },
 ];
 
-function detectAppDir(): string | null {
+function detectAppDir() {
   const candidates = ["app", "src/app"];
   for (const c of candidates) {
     if (existsSync(c)) return c;
@@ -56,7 +58,7 @@ function detectAppDir(): string | null {
   return null;
 }
 
-function runInstall(): number {
+function runInstall() {
   const appDir = detectAppDir();
   if (!appDir) {
     console.error(
@@ -90,15 +92,18 @@ function runInstall(): number {
   return 0;
 }
 
-// ── doctor (新增) ──────────────────────────────────────────────
+// ── doctor (self-check) ─────────────────────────────────────────
 
-interface DoctorCheck {
-  name: string;
-  status: "pass" | "fail" | "info";
-  detail: string;
-}
+/**
+ * @typedef {{ name: string, status: "pass" | "fail" | "info", detail: string }} DoctorCheck
+ */
 
-function checkEnv(name: string, prefix?: string): DoctorCheck {
+/**
+ * @param {string} name
+ * @param {string} [prefix]
+ * @returns {DoctorCheck}
+ */
+function checkEnv(name, prefix) {
   const value = process.env[name];
   if (!value) {
     return {
@@ -121,7 +126,11 @@ function checkEnv(name: string, prefix?: string): DoctorCheck {
   };
 }
 
-function checkLayoutUsage(appDir: string): DoctorCheck {
+/**
+ * @param {string} appDir
+ * @returns {DoctorCheck}
+ */
+function checkLayoutUsage(appDir) {
   // Mirror Next.js's layout file resolution. Order matters — TS > JS to
   // match what Next.js itself would pick.
   const candidates = [
@@ -140,9 +149,6 @@ function checkLayoutUsage(appDir: string): DoctorCheck {
   }
 
   const content = readFileSync(layoutPath, "utf-8");
-  // Substring check is intentional rather than AST parsing. A customer
-  // commenting it out or aliasing the import shows up as fail/info either
-  // way, and AST adds a TypeScript parser dependency for trivial value.
   if (!content.includes("SmkingAEO")) {
     return {
       name: "<SmkingAEO /> in root layout",
@@ -157,7 +163,10 @@ function checkLayoutUsage(appDir: string): DoctorCheck {
   };
 }
 
-async function checkApiReachable(): Promise<DoctorCheck> {
+/**
+ * @returns {Promise<DoctorCheck>}
+ */
+async function checkApiReachable() {
   const apiKey = process.env.SMKING_API_KEY;
   const baseUrl = process.env.SMKING_BASE_URL;
   if (!apiKey || !baseUrl) {
@@ -222,16 +231,21 @@ async function checkApiReachable(): Promise<DoctorCheck> {
   }
 }
 
-async function runDoctor(jsonOutput: boolean): Promise<number> {
+/**
+ * @param {boolean} jsonOutput
+ * @returns {Promise<number>}
+ */
+async function runDoctor(jsonOutput) {
   const appDir = detectAppDir();
-  const checks: DoctorCheck[] = [
+  /** @type {DoctorCheck[]} */
+  const checks = [
     checkEnv("SMKING_API_KEY", "pk_"),
     checkEnv("SMKING_BASE_URL", "http"),
     appDir
       ? checkLayoutUsage(appDir)
       : {
           name: "<SmkingAEO /> in root layout",
-          status: "info" as const,
+          status: "info",
           detail: "no app/ or src/app/ directory found — skipped",
         },
     await checkApiReachable(),
@@ -272,7 +286,7 @@ async function runDoctor(jsonOutput: boolean): Promise<number> {
 
 // ── Entry dispatcher ────────────────────────────────────────────
 
-async function main(): Promise<number> {
+async function main() {
   const subcommand = process.argv[2];
   const jsonOutput = process.argv.includes("--json");
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@soloworks/smking-next",
-  "version": "0.10.0",
+  "version": "0.12.1",
   "description": "AI-native SEO (AEO) for Next.js — auto-inject JSON-LD, FAQ, AI summary, and SEO metadata so AI crawlers (ChatGPT, Perplexity, Google AI) can cite your pages.",
   "license": "MIT",
   "homepage": "https://github.com/sillyleo/smking/tree/main/packages/smking-next",
@@ -19,13 +19,9 @@
       "types": "./src/components/smking-cms.tsx",
       "default": "./src/components/smking-cms.tsx"
     },
-    "./cms-webhook": {
-      "types": "./src/lib/cms-webhook-route.ts",
-      "default": "./src/lib/cms-webhook-route.ts"
-    },
-    "./route": {
-      "types": "./src/route.ts",
-      "default": "./src/route.ts"
+    "./webhook": {
+      "types": "./src/lib/webhook-route.ts",
+      "default": "./src/lib/webhook-route.ts"
     },
     "./robots": {
       "types": "./src/lib/robots.ts",
@@ -38,10 +34,14 @@
     "./llms-txt": {
       "types": "./src/lib/llms-txt-route.ts",
       "default": "./src/lib/llms-txt-route.ts"
+    },
+    "./proxy": {
+      "types": "./src/lib/proxy.ts",
+      "default": "./src/lib/proxy.ts"
     }
   },
   "bin": {
-    "smking-next": "./bin/install.ts"
+    "smking-next": "./bin/install.mjs"
   },
   "files": [
     "src",
@@ -63,29 +63,7 @@
   ],
   "peerDependencies": {
     "next": "^15.0.0 || ^16.0.0",
-    "react": "^18.0.0 || ^19.0.0",
-    "@tiptap/static-renderer": "^3.0.0",
-    "@tiptap/core": "^3.0.0",
-    "@tiptap/starter-kit": "^3.0.0",
-    "@tiptap/extension-image": "^3.0.0",
-    "@tiptap/extension-link": "^3.0.0"
-  },
-  "peerDependenciesMeta": {
-    "@tiptap/static-renderer": {
-      "optional": true
-    },
-    "@tiptap/core": {
-      "optional": true
-    },
-    "@tiptap/starter-kit": {
-      "optional": true
-    },
-    "@tiptap/extension-image": {
-      "optional": true
-    },
-    "@tiptap/extension-link": {
-      "optional": true
-    }
+    "react": "^18.0.0 || ^19.0.0"
   },
   "devDependencies": {
     "@testing-library/jest-dom": "^6.9.1",

package/src/components/smking-cms.tsx

@@ -1,11 +1,5 @@
-import { renderToReactElement } from "@tiptap/static-renderer/pm/react";
-import StarterKit from "@tiptap/starter-kit";
-import Image from "@tiptap/extension-image";
-import Link from "@tiptap/extension-link";
-import { Gallery } from "./cms-nodes/gallery-extension";
-import { GalleryNodeView } from "./cms-nodes/gallery-node";
 import { getCmsPage } from "../lib/cms-client";
-import type { CmsParams } from "../types";
+import type { Block, CmsParams } from "../types";
 
 /**
  * Server Component that renders a published smking CMS page.
@@ -24,19 +18,19 @@ import type { CmsParams } from "../types";
  * }
  * ```
  *
- * Fetches the page server-side, walks the Tiptap ProseMirror JSON via
- * `@tiptap/static-renderer/pm/react`, and renders it as a React tree.
- * Standard nodes (paragraph / heading / image / list / link / blockquote
- * / code-block) come from StarterKit. The custom Gallery node is
- * mapped to GalleryNodeView whose markup is byte-equal to the SaaS
- * preview side and the Laravel SDK PHP renderer.
+ * v0.11+ substrate pivot: fetches a Block[] array and dispatches each
+ * block by `component`. Article block carries pre-rendered HTML
+ * (server-rendered at write time via tiptap-html, so the customer SDK
+ * needs zero Tiptap dependencies). Hero / nav-* blocks render inline;
+ * full server-side data fetch for nav-recent-posts / nav-taxonomy-list
+ * / nav-search arrives in M2+ — they emit pending markers for now so
+ * customer pages don't 500 if the page contains them.
  *
  * Returns null when the response isn't ready (pending / not_found /
  * unreachable / mis-configured) — fail-open by design.
  *
- * Customer install requires four Tiptap peer deps:
- *   pnpm add @tiptap/static-renderer @tiptap/starter-kit \\
- *     @tiptap/extension-image @tiptap/extension-link
+ * Emits `<title>` / `<meta>` / `og:*` / canonical inline; React 19
+ * hoists them into `<head>` automatically.
  */
 export async function SmkingCms(props: CmsParams) {
   const data = await getCmsPage(props);
@@ -47,6 +41,7 @@ export async function SmkingCms(props: CmsParams) {
   // (last write wins on duplicate tags), so a deeper layout / page that
   // also sets these still overrides ours where present.
   const seo = data.seo;
+  const blocks = data.page.blocks ?? [];
   return (
     <>
       {seo?.title && <title data-smking="cms">{seo.title}</title>}
@@ -74,23 +69,95 @@ export async function SmkingCms(props: CmsParams) {
         <link rel="canonical" href={seo.canonicalUrl} data-smking="cms" />
       )}
 
-      <article className="smk-cms" data-smking="cms">
+      <article
+        className="smk-cms"
+        data-smking="cms"
+        data-content-type={data.page.contentType}
+      >
         {data.page.title && (
           <h1 className="smk-cms__title">{data.page.title}</h1>
         )}
-        {renderToReactElement({
-          extensions: [StarterKit, Image, Link, Gallery],
-          content: data.page.body,
-          options: {
-            nodeMapping: {
-              // Custom node renderer for our gallery; standard nodes
-              // (paragraph, heading, list, etc.) auto-render from
-              // StarterKit's schema.
-              gallery: GalleryNodeView,
-            },
-          },
-        })}
+        {blocks.map((block) => renderBlock(block))}
       </article>
     </>
   );
 }
+
+/**
+ * Dispatch a single block to its rendered React element.
+ *
+ * Trust boundary for `article` blocks: HTML is rendered server-side at
+ * write time by `@tiptap/html/server` inside the SaaS (Tiptap's renderer
+ * only emits HTML for known nodes per the configured schema, so author
+ * input can't smuggle arbitrary tags through). Customer site renders
+ * that HTML as-is via React's raw-HTML escape hatch. If customer wants
+ * defence-in-depth beyond the SaaS sanitisation tier, layer CSP on
+ * their host page (smking SDK does not ship a customer-side sanitiser
+ * to keep zero-dep customer install).
+ */
+function renderBlock(block: Block) {
+  switch (block.component) {
+    case "article": {
+      const articleHtml: { __html: string } = { __html: block.props.html };
+      return (
+        <div
+          key={block.id}
+          className="smk-block smk-block--article"
+          data-block-id={block.id}
+          // eslint-disable-next-line react/no-danger -- HTML pre-rendered server-side via @tiptap/html/server; trust boundary = SaaS schema. See function-level doc-comment above.
+          dangerouslySetInnerHTML={articleHtml}
+        />
+      );
+    }
+    case "hero":
+      return (
+        <section
+          key={block.id}
+          className="smk-block smk-block--hero smk-hero"
+          data-block-id={block.id}
+        >
+          {block.props.image && (
+            <img
+              src={block.props.image.url}
+              alt={block.props.image.alt}
+              className="smk-hero__image"
+            />
+          )}
+          <h2 className="smk-hero__title">{block.props.title}</h2>
+          {block.props.subtitle && (
+            <p className="smk-hero__subtitle">{block.props.subtitle}</p>
+          )}
+          {block.props.cta && (
+            <a className="smk-hero__cta" href={block.props.cta.href}>
+              {block.props.cta.label}
+            </a>
+          )}
+        </section>
+      );
+    case "nav-recent-posts":
+    case "nav-taxonomy-list":
+    case "nav-search":
+      // Server-side data fetch + render lands in M2+ alongside the
+      // public posts / taxonomy / search endpoints. Emit a marker so
+      // customer pages don't 500 if an editor publishes a page with
+      // one of these blocks before M2 ships.
+      return (
+        <section
+          key={block.id}
+          className={`smk-block smk-block--${block.component} smk-nav-pending`}
+          data-block-id={block.id}
+          data-block-component={block.component}
+        />
+      );
+    default:
+      // Forward-compat: unknown block component — emit empty marker
+      // so the page renders. Better than throwing.
+      return (
+        <section
+          key={(block as { id: string }).id}
+          className="smk-block smk-block--unknown"
+          data-block-component={(block as { component: string }).component}
+        />
+      );
+  }
+}

package/src/lib/client.ts

@@ -26,8 +26,11 @@ function warnOnce(key: string, message: string): void {
  *   - JSON parse failure
  *
  * On success, cached by Next.js data cache for 1h (ISR backstop). Tagged
- * with `smking:path:<path>` so the webhook handler at `@soloworks/smking-next/route`
- * can `revalidateTag` to invalidate instantly when SaaS pushes an update.
+ * with `smking:aeo:<path>` so the unified webhook handler at
+ * `@soloworks/smking-next/webhook` can `revalidateTag` to invalidate
+ * instantly when SaaS pushes an update. Namespace changed from
+ * `smking:path:*` in v0.11 — unified channel uses payload.kind to
+ * scope tag prefix.
  *
  * Sends `{ key, path, url }` — `url` is required for first-sight
  * registration: when the SaaS hasn't seen this path before it queues a
@@ -82,7 +85,7 @@ export async function getAeoContent(
       signal: AbortSignal.timeout(FETCH_TIMEOUT_MS),
       next: {
         revalidate: params.revalidate ?? DEFAULT_REVALIDATE_SECONDS,
-        tags: [`smking:path:${path}`],
+        tags: [`smking:aeo:${path}`],
       },
     });
     if (!res.ok) return null;

package/src/lib/cms-client.ts

@@ -33,9 +33,10 @@ function warnOnce(key: string, message: string): void {
  *
  * On success, cached by Next.js data cache for 5min by default
  * (ISR backstop — see DEFAULT_REVALIDATE_SECONDS rationale).
- * Tagged with `smking:cms:<slug>` so the `cms-webhook` handler can
- * `revalidateTag` to invalidate instantly when SaaS publishes an
- * update.
+ * Tagged with `smking:cms_page:<slug>` so the unified `/webhook` handler
+ * can `revalidateTag` to invalidate instantly when SaaS publishes an
+ * update. Namespace changed from `smking:cms:*` in v0.11 — unified
+ * channel uses payload.kind to scope tag prefix.
  */
 export async function getCmsPage(
   params: CmsParams,
@@ -76,7 +77,7 @@ export async function getCmsPage(
       signal: AbortSignal.timeout(FETCH_TIMEOUT_MS),
       next: {
         revalidate: params.revalidate ?? DEFAULT_REVALIDATE_SECONDS,
-        tags: [`smking:cms:${params.slug}`],
+        tags: [`smking:cms_page:${params.slug}`],
       },
     });
     if (!res.ok) return null;