create-zudo-doc 3.2.0 → 4.0.0

package/dist/features/dynamic-page-transition.js

@@ -1,216 +1,28 @@
 /**
  * Dynamic page transition feature.
  *
- * When enabled:
- * - Sets `enableClientRouter={settings.dynamicPageTransition}` on every
- *   `<DocLayoutWithDefaults>` render site — the SSR `<ClientRouter />` render
- *   self-activates the SPA router on the client as a top-level module side
- *   effect (primary activation path).
- * - Wires the ClientRouterBootstrap island and the PageLoadingOverlay (pure
- *   SSR) into body-end-islands — the island is now a redundant fallback;
- *   PageLoadingOverlay provides the loading spinner UI.
- * - Injects `@import "@takazudo/zudo-doc/page-loading.css"` at the
- *   `@slot:global-css:imports` anchor (top of global.css, before rule blocks).
- * - Injects the `--color-page-loading-overlay` token into `@theme` at the
- *   `@slot:global-css:theme-tokens` anchor.
- * - Injects the View-Transitions CSS into global.css at
- *   `@slot:global-css:feature-styles`.
- *
- * Bug fix (#2265): the page-loading overlay CSS (.page-loading-overlay /
- * .page-loading-spinner / @keyframes page-loading-spin / [data-zd-nav-pending])
- * was never reaching scaffolded projects because it lived unconditionally in
- * the host global.css but had no corresponding injection for the template.
- * Gating this feature makes both the JS island and the CSS land together.
- *
- * The page-loading CSS now ships as a package artifact
- * `@takazudo/zudo-doc/page-loading.css` (Topic A, #2283) — the generator
- * injects a gated `@import` instead of inline rule bodies. The
- * `--color-page-loading-overlay` token is defined inline (inside `@theme`) so
- * it lives alongside the other project tokens and can be overridden per-project.
- *
- * The ClientRouterBootstrap component lives in
- * templates/features/dynamicPageTransition/files/src/components/ and is
- * byte-identical to the host src/components/client-router-bootstrap.tsx.
- * The feature-template drift checker enforces this parity automatically.
+ * Minimal-scaffold cutover (epic zudolab/zudo-doc#2651, Wave 6 #2660):
+ * purely a `zudoDoc({ dynamicPageTransition: true })` field now (see
+ * `zfb-config-gen.ts`). The primary activation path —
+ * `<ClientRouter enableClientRouter={settings.dynamicPageTransition} />`
+ * rendered by the package's own `doc-page-shell`/`doclayout` — and the
+ * pure-SSR `<PageLoadingOverlay/>` mount are BOTH already handled inside
+ * `doc-body-end-islands/index.tsx`, gated on the same flag; the View-
+ * Transitions CSS ships unconditionally from `@takazudo/zudo-doc/features.css`.
+ *
+ * DROPPED: the host `ClientRouterBootstrap` island
+ * (`templates/features/dynamicPageTransition/files/src/components/`) —
+ * its old host-owned mount point (`pages/lib/_body-end-islands.tsx`) no
+ * longer exists, and the package's own doc-body-end-islands header comment
+ * already calls it "a redundant fallback" once PageLoadingOverlay covers the
+ * loading UI. Known gap (documented, out of this generator's scope): the
+ * package's SSR-only `<ClientRouter/>` import may still need a "use client"
+ * bootstrap to guarantee the click-intercept ships to the browser bundle —
+ * same class of issue as tauri's find-in-page island (see tauri.ts). If a
+ * project needs it restored, wire a custom island through
+ * `settings.chromeBindingsModule`'s `BodyEndIslands` slot.
  */
 export const dynamicPageTransitionFeature = () => ({
     name: "dynamicPageTransition",
-    injections: [
-        // 1. Import ClientRouterBootstrap and PageLoadingOverlay.
-        //    Inserted AFTER the `// @slot:body-end-islands:imports` anchor.
-        {
-            file: "pages/lib/_body-end-islands.tsx",
-            anchor: "// @slot:body-end-islands:imports",
-            position: "after",
-            content: `import ClientRouterBootstrap from "@/components/client-router-bootstrap";
-import { PageLoadingOverlay } from "@takazudo/zudo-doc/page-loading";`,
-        },
-        // 2. Stable island marker name for ClientRouterBootstrap.
-        //    Inserted AFTER the `// @slot:body-end-islands:display-names` anchor.
-        {
-            file: "pages/lib/_body-end-islands.tsx",
-            anchor: "// @slot:body-end-islands:display-names",
-            position: "after",
-            content: `(ClientRouterBootstrap as { displayName?: string }).displayName =
-  "ClientRouterBootstrap";`,
-        },
-        // 3. Gated island mount + PageLoadingOverlay.
-        //    Inserted AFTER the `{/* @slot:body-end-islands:extra-islands */}` anchor.
-        //    Gated on `settings.dynamicPageTransition` — mirrors the designTokenPanel
-        //    and aiAssistant gating patterns in the same file.
-        //    ClientRouterBootstrap: hydrates on "load" so the SPA-router click
-        //    intercept is registered as soon as the islands runtime mounts the marker
-        //    (zudolab/zudo-doc#1524 W7A fix). PageLoadingOverlay: pure SSR — the
-        //    component emits its overlay div and the inline script that wires
-        //    zfb:before-preparation / zfb:after-swap listeners at runtime.
-        {
-            file: "pages/lib/_body-end-islands.tsx",
-            anchor: "{/* @slot:body-end-islands:extra-islands */}",
-            position: "after",
-            content: `      {settings.dynamicPageTransition ? (
-        <>
-          {/* Pure SSR — no Island wrap. The component emits its overlay div,
-              inline styles, and a small inline script that self-wires
-              zfb:before-preparation / zfb:after-swap listeners at runtime. */}
-          <PageLoadingOverlay />
-          {Island({
-            when: "load",
-            children: <ClientRouterBootstrap />,
-          }) as unknown as VNode}
-        </>
-      ) : null}`,
-        },
-        // 4. Page-loading CSS import — gated at the top-of-file imports anchor.
-        //    `@import` must precede rule blocks in CSS; the `@slot:global-css:imports`
-        //    anchor sits immediately after the content.css import line so this lands
-        //    in a legal position. The CSS itself (overlay, spinner, keyframes) now
-        //    ships as a package artifact `@takazudo/zudo-doc/page-loading.css`
-        //    (see #2283 — Topic A) instead of being duplicated inline here.
-        {
-            file: "src/styles/global.css",
-            anchor: "/* @slot:global-css:imports */",
-            position: "after",
-            content: `@import "@takazudo/zudo-doc/page-loading.css";`,
-        },
-        // 5. `--color-page-loading-overlay` token — injected inside `@theme`.
-        //    Defined here so each scaffolded project can override it per-project.
-        //    Uses the same `--color-overlay` base token as the dialog backdrops.
-        {
-            file: "src/styles/global.css",
-            anchor: "/* @slot:global-css:theme-tokens */",
-            position: "after",
-            content: `--color-page-loading-overlay: color-mix(in oklch, var(--color-overlay) 60%, transparent);`,
-        },
-        // 6. View-Transitions CSS (chrome extraction + cross-fade + reduced motion).
-        //    Injected AFTER `/* @slot:global-css:feature-styles */` in global.css.
-        //    These rules are required for SPA page transitions via ClientRouter.
-        {
-            file: "src/styles/global.css",
-            anchor: "/* @slot:global-css:feature-styles */",
-            position: "after",
-            content: `/* Root cross-fade for same-document View Transitions (Strategy B).
- *
- * @view-transition { navigation: auto; } (Strategy A, cross-document) is
- * deleted — Strategy B uses <ClientRouter /> which drives same-document
- * transitions via document.startViewTransition on each navigation.
- *
- * Chrome extraction via view-transition-name (Strategy B+, zudolab/zudo-doc#1558):
- * <header>, <aside id="desktop-sidebar">, <footer>, and the desktop-sidebar-toggle
- * button each carry a data-zfb-transition-persist attribute whose value is keyed
- * by locale and nav-section. The four attribute selectors below assign a stable
- * view-transition-name based on the attribute value prefix, extracting those
- * elements from the root snapshot into their own named layers:
- *   - header-{lang}          → zfb-header
- *   - sidebar-{locale}-…     → zfb-sidebar
- *   - footer-{lang}          → zfb-footer
- *   - desktop-sidebar-toggle → zfb-sidebar-toggle
- *
- * Once extracted, the root cross-fade animates only non-chrome content (main,
- * article, TOC, etc.). The twelve ::view-transition-{old,new,group}(<name>)
- * rules disable animation for all four chrome layers. The group pseudo must be
- * neutralised too — even when old/new are static the group container can still
- * produce a geometry-morph animation when snapshot size/position differs.
- *
- * Entry/exit cross-fade (zudolab/zudo-doc#2072): animation: none is only
- * correct when the chrome element exists on BOTH pages of a navigation.
- * When it exists on one side only (docs page with sidebar → top page
- * without), the named group holds a single snapshot — frozen at full
- * opacity for the whole transition, then dropped abruptly at finish. The
- * :only-child rules below detect that one-sided case and cross-fade the
- * lone snapshot in sync with the root content fade (spec-standard
- * entry/exit pattern; :only-child outranks the animation: none rules via
- * the extra pseudo-class specificity). */
-
-/* Chrome extraction — assign view-transition-name from data-zfb-transition-persist */
-[data-zfb-transition-persist^="header-"]               { view-transition-name: zfb-header; }
-[data-zfb-transition-persist^="sidebar-"]              { view-transition-name: zfb-sidebar; }
-[data-zfb-transition-persist^="footer-"]               { view-transition-name: zfb-footer; }
-[data-zfb-transition-persist="desktop-sidebar-toggle"] { view-transition-name: zfb-sidebar-toggle; }
-
-/* Disable animation for all four chrome layers (old, new, and group) */
-::view-transition-old(zfb-header),
-::view-transition-new(zfb-header),
-::view-transition-group(zfb-header),
-::view-transition-old(zfb-sidebar),
-::view-transition-new(zfb-sidebar),
-::view-transition-group(zfb-sidebar),
-::view-transition-old(zfb-footer),
-::view-transition-new(zfb-footer),
-::view-transition-group(zfb-footer),
-::view-transition-old(zfb-sidebar-toggle),
-::view-transition-new(zfb-sidebar-toggle),
-::view-transition-group(zfb-sidebar-toggle) { animation: none; }
-
-/* Entry/exit: chrome element present on one side only (#2072).
- * Exit — lone old snapshot fades out with the content cross-fade. */
-::view-transition-old(zfb-header):only-child,
-::view-transition-old(zfb-sidebar):only-child,
-::view-transition-old(zfb-footer):only-child,
-::view-transition-old(zfb-sidebar-toggle):only-child {
-  animation: 150ms ease-in both contentFadeOut;
-}
-/* Entry — lone new snapshot fades in with the content cross-fade. */
-::view-transition-new(zfb-header):only-child,
-::view-transition-new(zfb-sidebar):only-child,
-::view-transition-new(zfb-footer):only-child,
-::view-transition-new(zfb-sidebar-toggle):only-child {
-  animation: 300ms ease-out both contentFadeIn;
-}
-
-/* Root cross-fade rules — animate only the non-chrome snapshot */
-::view-transition-old(root) {
-  animation: 150ms ease-in both contentFadeOut;
-}
-::view-transition-new(root) {
-  animation: 300ms ease-out both contentFadeIn;
-}
-
-/* Reduced motion: collapse all view-transition animation to an instant
- * swap (zudolab/zudo-doc#2086). With every snapshot animation at none the
- * transition settles immediately — no cross-fade, no translateY slide.
- * Covers the root cross-fade and the #2072 :only-child entry/exit rules;
- * the both-sides chrome layers are already animation: none above. Equal
- * specificity per selector, but later in source order, so these win.
- * ::view-transition-group(root) must be neutralized too (zudolab/zzmod#845):
- * the UA animates the root group for its full duration even when the old/new
- * root snapshots are at animation: none, leaving a brief frozen,
- * non-interactive frame. The chrome groups are already animation: none in the
- * unconditional chrome block above, so only the root group is added here. */
-@media (prefers-reduced-motion: reduce) {
-  ::view-transition-old(root),
-  ::view-transition-new(root),
-  ::view-transition-group(root),
-  ::view-transition-old(zfb-header):only-child,
-  ::view-transition-old(zfb-sidebar):only-child,
-  ::view-transition-old(zfb-footer):only-child,
-  ::view-transition-old(zfb-sidebar-toggle):only-child,
-  ::view-transition-new(zfb-header):only-child,
-  ::view-transition-new(zfb-sidebar):only-child,
-  ::view-transition-new(zfb-footer):only-child,
-  ::view-transition-new(zfb-sidebar-toggle):only-child {
-    animation: none;
-  }
-}`,
-        },
-    ],
+    injections: [],
 });

package/dist/features/footer-taglist.d.ts

@@ -2,7 +2,7 @@ import type { FeatureModule } from "../compose.js";
 /**
  * Footer taglist feature.
  *
- * Purely a settings toggle: `settings-gen.ts` emits
+ * Purely a settings toggle: `zfb-config-gen.ts` emits
  * `footer.taglist = { enabled: true, groupBy: "group" }` when selected,
  * and the footer component (part of the footer pseudo-feature) reads
  * `settings.footer.taglist` to decide whether to render the column(s).

package/dist/features/footer-taglist.js

@@ -1,7 +1,7 @@
 /**
  * Footer taglist feature.
  *
- * Purely a settings toggle: `settings-gen.ts` emits
+ * Purely a settings toggle: `zfb-config-gen.ts` emits
  * `footer.taglist = { enabled: true, groupBy: "group" }` when selected,
  * and the footer component (part of the footer pseudo-feature) reads
  * `settings.footer.taglist` to decide whether to render the column(s).

package/dist/features/footer.d.ts

@@ -2,7 +2,8 @@ import type { FeatureModule } from "../compose.js";
 /**
  * Footer pseudo-feature.
  *
- * W7A (#1736): post-cutover, `pages/lib/_footer-with-defaults.tsx` mounts
- * the footer unconditionally — no doc-layout injection is required.
+ * Purely a `zudoDoc({ footer: {...} })` field (see `zfb-config-gen.ts`,
+ * triggered by footerNavGroup / footerCopyright / footerTaglist) — the
+ * footer chrome is fully package-owned. No injection required.
  */
 export declare const footerFeature: FeatureModule;

package/dist/features/footer.js

@@ -1,8 +1,9 @@
 /**
  * Footer pseudo-feature.
  *
- * W7A (#1736): post-cutover, `pages/lib/_footer-with-defaults.tsx` mounts
- * the footer unconditionally — no doc-layout injection is required.
+ * Purely a `zudoDoc({ footer: {...} })` field (see `zfb-config-gen.ts`,
+ * triggered by footerNavGroup / footerCopyright / footerTaglist) — the
+ * footer chrome is fully package-owned. No injection required.
  */
 export const footerFeature = () => ({
     name: "footer",

package/dist/features/i18n.d.ts

@@ -2,16 +2,21 @@ import type { FeatureModule } from "../compose.js";
 /**
  * i18n feature — gates the locale-prefixed page set.
  *
- * Page templates are shipped under `templates/features/i18n/files/pages/`
- * and copied by `composeFeatures → copyFeatureFiles` whenever `i18n` is in
- * the selected feature set.
+ * Locked manifest (#2653 Decision 4, i18n addendum): "i18n ON adds
+ * `pages/[locale]/docs/[[...slug]].tsx` (a second doc stub, locale variant)
+ * … No other pages." That ONE self-contained stub — required for the same
+ * injected-DYNAMIC-route dev-mode 404 gap the default-locale stub fixes —
+ * is shipped under `templates/features/i18n/files/pages/[locale]/docs/`
+ * and copied by `composeFeatures → copyFeatureFiles` whenever `i18n` is
+ * selected. The old `pages/[locale]/index.tsx` home-route template is GONE
+ * (the locked manifest doesn't want it — the package-owned `/` route
+ * already handles every locale via `[[locale]]`-style resolution inside
+ * `routes/index.tsx`'s own logic).
  *
- * No injections: header / language-switcher wiring was retired with the
- * Astro cutover (#1736 / W7A) — `pages/lib/_header-with-defaults.tsx` now
- * gates `LanguageSwitcher` on `Object.keys(settings.locales).length > 0`.
- * The pages are locale-agnostic — they iterate `settings.locales` at build
+ * No injections: the stub iterates `settings.locales` at build/request
  * time, so no postProcess regex patching is required for non-default
- * languages.
+ * languages. Secondary-language content mirrors under
+ * `src/content/docs-<lang>/` are seeded by `scaffold.ts`.
  *
  * Loud-failure check: per spec-lock Decision 8 (#1737), abort scaffolding
  * if the feature template dir is missing or empty. Without this guard,

package/dist/features/i18n.js

@@ -4,16 +4,21 @@ import { fileURLToPath } from "url";
 /**
  * i18n feature — gates the locale-prefixed page set.
  *
- * Page templates are shipped under `templates/features/i18n/files/pages/`
- * and copied by `composeFeatures → copyFeatureFiles` whenever `i18n` is in
- * the selected feature set.
+ * Locked manifest (#2653 Decision 4, i18n addendum): "i18n ON adds
+ * `pages/[locale]/docs/[[...slug]].tsx` (a second doc stub, locale variant)
+ * … No other pages." That ONE self-contained stub — required for the same
+ * injected-DYNAMIC-route dev-mode 404 gap the default-locale stub fixes —
+ * is shipped under `templates/features/i18n/files/pages/[locale]/docs/`
+ * and copied by `composeFeatures → copyFeatureFiles` whenever `i18n` is
+ * selected. The old `pages/[locale]/index.tsx` home-route template is GONE
+ * (the locked manifest doesn't want it — the package-owned `/` route
+ * already handles every locale via `[[locale]]`-style resolution inside
+ * `routes/index.tsx`'s own logic).
  *
- * No injections: header / language-switcher wiring was retired with the
- * Astro cutover (#1736 / W7A) — `pages/lib/_header-with-defaults.tsx` now
- * gates `LanguageSwitcher` on `Object.keys(settings.locales).length > 0`.
- * The pages are locale-agnostic — they iterate `settings.locales` at build
+ * No injections: the stub iterates `settings.locales` at build/request
  * time, so no postProcess regex patching is required for non-default
- * languages.
+ * languages. Secondary-language content mirrors under
+ * `src/content/docs-<lang>/` are seeded by `scaffold.ts`.
  *
  * Loud-failure check: per spec-lock Decision 8 (#1737), abort scaffolding
  * if the feature template dir is missing or empty. Without this guard,
@@ -31,7 +36,7 @@ export const i18nFeature = (_choices) => {
     const stat = fs.existsSync(pagesDir) ? fs.statSync(pagesDir) : null;
     if (!stat || !stat.isDirectory() || fs.readdirSync(pagesDir).length === 0) {
         throw new Error(`i18n feature template dir is missing or empty: ${pagesDir}\n` +
-            `Expected to find [locale]/index.tsx.\n` +
+            `Expected to find [locale]/docs/[[...slug]].tsx.\n` +
             `This is a generator bug — please file an issue.`);
     }
     return {

package/dist/features/image-enlarge.d.ts

@@ -2,31 +2,12 @@ import type { FeatureModule } from "../compose.js";
 /**
  * Image-enlarge feature.
  *
- * W7A (#1736): post-cutover, the image-enlarge island is mounted by the
- * pages/lib body-end wrapper (always present; runtime-gated via the
- * always-loaded stub-or-real ImageEnlarge component). Image-enlarge CSS
- * lives unconditionally in `@takazudo/zudo-doc/features.css` (moved from
- * `global.css` in S3 #2348) — the selectors only activate when the runtime
- * mounts the .zd-enlarge-btn.
- *
- * S2 (#1825): the server-side figure/button emission was re-implemented via an
- * MDX paragraph (p) component override in pages/_mdx-components.ts. Three
- * injections installed the ENLARGE_SVG + EnlargeableParagraph code when
- * imageEnlarge was enabled.
- *
- * S8 / #2360 (E2): the full MDX component assembly moved into the
- * @takazudo/zudo-doc/mdx-components factory (createMdxComponentsBase). The
- * factory reads settings.imageEnlarge at render time and conditionally wraps
- * block-level images in <figure class="zd-enlargeable"> — the same logic the
- * old injections installed, now handled once inside the package. The three
- * _mdx-components.ts injections (enlarge-imports, enlarge-defs,
- * enlarge-p-entry) are therefore removed; the feature is a no-op from the
- * compose engine's perspective (the runtime gate in the factory is always
- * present in the scaffolded template).
- *
- * S3 (#2348): the ImageEnlarge island and its SSR fallback moved from
- * src/components/image-enlarge.tsx into @takazudo/zudo-doc/image-enlarge.
- * The pages/lib/_body-end-islands.tsx template now imports them from the
- * package, so no file-copy injections exist in this feature module either.
+ * Purely a `zudoDoc({ imageEnlarge: true })` field (see `zfb-config-gen.ts`).
+ * The island, its SSR fallback, and its CSS are all package-owned
+ * (`@takazudo/zudo-doc/image-enlarge`, mounted by
+ * `doc-body-end-islands/index.tsx`; CSS from `features.css`) and the MDX
+ * `<figure class="zd-enlargeable">` wrapping is handled inside
+ * `@takazudo/zudo-doc/mdx-components` at render time, reading
+ * `settings.imageEnlarge`. Nothing to inject or copy.
  */
 export declare const imageEnlargeFeature: FeatureModule;

package/dist/features/image-enlarge.js

@@ -1,32 +1,13 @@
 /**
  * Image-enlarge feature.
  *
- * W7A (#1736): post-cutover, the image-enlarge island is mounted by the
- * pages/lib body-end wrapper (always present; runtime-gated via the
- * always-loaded stub-or-real ImageEnlarge component). Image-enlarge CSS
- * lives unconditionally in `@takazudo/zudo-doc/features.css` (moved from
- * `global.css` in S3 #2348) — the selectors only activate when the runtime
- * mounts the .zd-enlarge-btn.
- *
- * S2 (#1825): the server-side figure/button emission was re-implemented via an
- * MDX paragraph (p) component override in pages/_mdx-components.ts. Three
- * injections installed the ENLARGE_SVG + EnlargeableParagraph code when
- * imageEnlarge was enabled.
- *
- * S8 / #2360 (E2): the full MDX component assembly moved into the
- * @takazudo/zudo-doc/mdx-components factory (createMdxComponentsBase). The
- * factory reads settings.imageEnlarge at render time and conditionally wraps
- * block-level images in <figure class="zd-enlargeable"> — the same logic the
- * old injections installed, now handled once inside the package. The three
- * _mdx-components.ts injections (enlarge-imports, enlarge-defs,
- * enlarge-p-entry) are therefore removed; the feature is a no-op from the
- * compose engine's perspective (the runtime gate in the factory is always
- * present in the scaffolded template).
- *
- * S3 (#2348): the ImageEnlarge island and its SSR fallback moved from
- * src/components/image-enlarge.tsx into @takazudo/zudo-doc/image-enlarge.
- * The pages/lib/_body-end-islands.tsx template now imports them from the
- * package, so no file-copy injections exist in this feature module either.
+ * Purely a `zudoDoc({ imageEnlarge: true })` field (see `zfb-config-gen.ts`).
+ * The island, its SSR fallback, and its CSS are all package-owned
+ * (`@takazudo/zudo-doc/image-enlarge`, mounted by
+ * `doc-body-end-islands/index.tsx`; CSS from `features.css`) and the MDX
+ * `<figure class="zd-enlargeable">` wrapping is handled inside
+ * `@takazudo/zudo-doc/mdx-components` at render time, reading
+ * `settings.imageEnlarge`. Nothing to inject or copy.
  */
 export const imageEnlargeFeature = () => ({
     name: "imageEnlarge",

package/dist/features/index.js

@@ -14,6 +14,7 @@ import { docHistoryFeature } from "./doc-history.js";
 import { llmsTxtFeature } from "./llms-txt.js";
 import { claudeResourcesFeature } from "./claude-resources.js";
 import { designTokenPanelFeature } from "./design-token-panel.js";
+import { themePackSwitcherFeature } from "./theme-pack-switcher.js";
 import { i18nFeature } from "./i18n.js";
 import { versioningFeature } from "./versioning.js";
 import { tauriFeature } from "./tauri.js";
@@ -35,6 +36,7 @@ export const featureModules = {
     // sidebarFilter — built into sidebar-tree.tsx, stays in base
     claudeResources: claudeResourcesFeature,
     designTokenPanel: designTokenPanelFeature,
+    themePackSwitcher: themePackSwitcherFeature,
     sidebarResizer: sidebarResizerFeature,
     sidebarToggle: sidebarToggleFeature,
     versioning: versioningFeature,

package/dist/features/llms-txt.d.ts

@@ -2,10 +2,8 @@ import type { FeatureModule } from "../compose.js";
 /**
  * llms-txt feature.
  *
- * W7A (#1736): the inject() that previously added `<link rel="alternate">`
- * tags to `<head>` is dropped per locked spec §6.3 — `_head-with-defaults.tsx`
- * does not emit those tags today (neither does host). If a follow-up decides
- * to emit them, add the gated `<link>` rendering inside `_head-with-defaults.tsx`
- * — not in a feature inject. The plugin itself is wired by `zfb-config-gen.ts`.
+ * Purely a `zudoDoc({ llmsTxt: true })` field (see `zfb-config-gen.ts`) —
+ * `zudoDocPreset()` wires `@takazudo/zudo-doc/plugins/llms-txt` whenever the
+ * flag is on. Nothing to inject.
  */
 export declare const llmsTxtFeature: FeatureModule;

package/dist/features/llms-txt.js

@@ -1,11 +1,9 @@
 /**
  * llms-txt feature.
  *
- * W7A (#1736): the inject() that previously added `<link rel="alternate">`
- * tags to `<head>` is dropped per locked spec §6.3 — `_head-with-defaults.tsx`
- * does not emit those tags today (neither does host). If a follow-up decides
- * to emit them, add the gated `<link>` rendering inside `_head-with-defaults.tsx`
- * — not in a feature inject. The plugin itself is wired by `zfb-config-gen.ts`.
+ * Purely a `zudoDoc({ llmsTxt: true })` field (see `zfb-config-gen.ts`) —
+ * `zudoDocPreset()` wires `@takazudo/zudo-doc/plugins/llms-txt` whenever the
+ * flag is on. Nothing to inject.
  */
 export const llmsTxtFeature = () => ({
     name: "llmsTxt",

package/dist/features/search.d.ts

@@ -2,8 +2,12 @@ import type { FeatureModule } from "../compose.js";
 /**
  * Search feature.
  *
- * W7A (#1736): post-cutover, `pages/lib/_header-with-defaults.tsx` includes
- * the search widget unconditionally — no header injection is required.
- * The search-index plugin is still wired by `zfb-config-gen.ts`.
+ * The `@takazudo/zudo-doc/plugins/search-index` plugin runs unconditionally
+ * (every project gets a `search-index.json`) — `zudoDocPreset()` always
+ * wires it. This feature only controls whether the header shows the search
+ * trigger (`{ type: "component", component: "search" }` in
+ * `headerRightItems`, see `zfb-config-gen.ts`) — the widget itself is
+ * package-owned (`chrome/derive.tsx`'s `SearchWidget`), so there is nothing
+ * left to inject.
  */
 export declare const searchFeature: FeatureModule;

package/dist/features/search.js

@@ -1,9 +1,13 @@
 /**
  * Search feature.
  *
- * W7A (#1736): post-cutover, `pages/lib/_header-with-defaults.tsx` includes
- * the search widget unconditionally — no header injection is required.
- * The search-index plugin is still wired by `zfb-config-gen.ts`.
+ * The `@takazudo/zudo-doc/plugins/search-index` plugin runs unconditionally
+ * (every project gets a `search-index.json`) — `zudoDocPreset()` always
+ * wires it. This feature only controls whether the header shows the search
+ * trigger (`{ type: "component", component: "search" }` in
+ * `headerRightItems`, see `zfb-config-gen.ts`) — the widget itself is
+ * package-owned (`chrome/derive.tsx`'s `SearchWidget`), so there is nothing
+ * left to inject.
  */
 export const searchFeature = () => ({
     name: "search",

package/dist/features/sidebar-resizer.d.ts

@@ -2,13 +2,9 @@ import type { FeatureModule } from "../compose.js";
 /**
  * Sidebar-resizer feature.
  *
- * W7A (#1736): post-cutover, sidebar resizer pre-paint scripts and runtime
- * initialization are runtime-gated on `settings.sidebarResizer` inside the
- * pages/lib wrappers — no doc-layout injection is required.
- *
- * NOTE: spec-lock §6.5 flagged a pre-paint FOUC question for the
- * `applySidebarWidth` IIFE that previously ran inline in the layout `<head>`.
- * The post-cutover model relies on the pages/lib head wrapper emitting the
- * inline script (when present); this feature module no longer injects it.
+ * Purely a `zudoDoc({ sidebarResizer: true })` field (see `zfb-config-gen.ts`)
+ * — the pre-paint script and runtime init are package-owned
+ * (`sidebar-resizer/sidebar-resizer-init.tsx`), gated on `settings.sidebarResizer`
+ * inside the package's own chrome. Nothing to inject.
  */
 export declare const sidebarResizerFeature: FeatureModule;

package/dist/features/sidebar-resizer.js

@@ -1,14 +1,10 @@
 /**
  * Sidebar-resizer feature.
  *
- * W7A (#1736): post-cutover, sidebar resizer pre-paint scripts and runtime
- * initialization are runtime-gated on `settings.sidebarResizer` inside the
- * pages/lib wrappers — no doc-layout injection is required.
- *
- * NOTE: spec-lock §6.5 flagged a pre-paint FOUC question for the
- * `applySidebarWidth` IIFE that previously ran inline in the layout `<head>`.
- * The post-cutover model relies on the pages/lib head wrapper emitting the
- * inline script (when present); this feature module no longer injects it.
+ * Purely a `zudoDoc({ sidebarResizer: true })` field (see `zfb-config-gen.ts`)
+ * — the pre-paint script and runtime init are package-owned
+ * (`sidebar-resizer/sidebar-resizer-init.tsx`), gated on `settings.sidebarResizer`
+ * inside the package's own chrome. Nothing to inject.
  */
 export const sidebarResizerFeature = () => ({
     name: "sidebarResizer",

package/dist/features/sidebar-toggle.d.ts

@@ -2,12 +2,12 @@ import type { FeatureModule } from "../compose.js";
 /**
  * Sidebar-toggle feature.
  *
- * W7A (#1736): post-cutover, the sidebar-toggle is hosted by the pages/lib
- * wrappers which runtime-gate on `settings.sidebarToggle`. The supporting
- * CSS (toggle button positioning, sidebar transitions, `[data-sidebar-hidden]`
- * styles) lives unconditionally in `templates/base/src/styles/global.css`
- * — the selectors only match when the runtime attaches the
- * `data-sidebar-hidden` attribute or mounts the toggle button, so the cost
- * to scaffolds without the feature is one inert rule block.
+ * Purely a `zudoDoc({ sidebarToggle: true })` field (see `zfb-config-gen.ts`).
+ * `DesktopSidebarToggle` is fully package-owned
+ * (`@takazudo/zudo-doc/desktop-sidebar-toggle-island`, wired into
+ * Header/Sidebar directly) and its CSS ships unconditionally from
+ * `@takazudo/zudo-doc/features.css` — the old host re-export shim
+ * (`src/components/desktop-sidebar-toggle.tsx`) is gone; nothing to inject
+ * or copy.
  */
 export declare const sidebarToggleFeature: FeatureModule;

package/dist/features/sidebar-toggle.js

@@ -1,13 +1,13 @@
 /**
  * Sidebar-toggle feature.
  *
- * W7A (#1736): post-cutover, the sidebar-toggle is hosted by the pages/lib
- * wrappers which runtime-gate on `settings.sidebarToggle`. The supporting
- * CSS (toggle button positioning, sidebar transitions, `[data-sidebar-hidden]`
- * styles) lives unconditionally in `templates/base/src/styles/global.css`
- * — the selectors only match when the runtime attaches the
- * `data-sidebar-hidden` attribute or mounts the toggle button, so the cost
- * to scaffolds without the feature is one inert rule block.
+ * Purely a `zudoDoc({ sidebarToggle: true })` field (see `zfb-config-gen.ts`).
+ * `DesktopSidebarToggle` is fully package-owned
+ * (`@takazudo/zudo-doc/desktop-sidebar-toggle-island`, wired into
+ * Header/Sidebar directly) and its CSS ships unconditionally from
+ * `@takazudo/zudo-doc/features.css` — the old host re-export shim
+ * (`src/components/desktop-sidebar-toggle.tsx`) is gone; nothing to inject
+ * or copy.
  */
 export const sidebarToggleFeature = () => ({
     name: "sidebarToggle",

package/dist/features/tag-governance.d.ts

@@ -2,13 +2,8 @@ import type { FeatureModule } from "../compose.js";
 /**
  * Tag governance feature.
  *
- * Ships the tag audit and suggest scripts. Settings (`tagVocabulary`,
- * `tagGovernance`) are emitted by `settings-gen.ts`; devDeps and
- * `tags:audit` / `tags:suggest` package scripts are added in
- * `scaffold.ts#generatePackageJson`.
- *
- * `src/config/tag-vocabulary.ts` and `tag-vocabulary-types.ts` stay in the
- * base template because `src/utils/tags.ts` and `settings-types.ts` import
- * from them regardless of whether governance is on.
+ * Writes one project-owned tag vocabulary module. Its named vocabulary export
+ * feeds zfb while its default TagCliConfig export feeds both package-owned
+ * bins through an explicit `--config` package-script argument.
  */
 export declare const tagGovernanceFeature: FeatureModule;