create-zudo-doc 0.2.7 → 0.2.8

package/dist/scaffold.js

@@ -304,7 +304,7 @@ function generatePackageJson(choices) {
         // .github/workflows/publish-zudo-doc.yml. The pin here is bumped in
         // lockstep by scripts/release-create-zudo-doc.sh whenever zudo-doc's
         // version moves, so a fresh scaffold pulls the version we just published.
-        "@takazudo/zudo-doc": "^0.2.7",
+        "@takazudo/zudo-doc": "^0.2.8",
         // zod — used by the generated zfb.config.ts. zfb-config-gen emits
         // `import { z } from "zod"` for the content-collection schema +
         // `z.toJSONSchema(...)` conversion. Without this dep, the consumer
@@ -359,7 +359,7 @@ function generatePackageJson(choices) {
         // @takazudo/zudo-doc/integrations/doc-history which in turn imports
         // @takazudo/zudo-doc-history-server/git-history. Without this dep the
         // plugin host fails at init with ERR_MODULE_NOT_FOUND — W8A (#1739).
-        deps["@takazudo/zudo-doc-history-server"] = "^0.2.7";
+        deps["@takazudo/zudo-doc-history-server"] = "^0.2.8";
         // W7A (#1736): doc-history-plugin.mjs spawns `tsx -e <inline-script>` to
         // run the v2 runtime in a TS-aware Node subprocess; without tsx the
         // plugin's preBuild step exits with ENOENT before zfb finishes config
@@ -375,7 +375,7 @@ function generatePackageJson(choices) {
     if (choices.features.includes("designTokenPanel")) {
         // @takazudo/zdtp requires preact >= 10.29.1 — see the preact floor comment
         // above (~line 382) for why the floor is set there and the coupling this creates.
-        deps["@takazudo/zdtp"] = "0.2.0-next.2";
+        deps["@takazudo/zdtp"] = "0.2.3";
     }
     if (choices.features.includes("tagGovernance")) {
         // gray-matter is already in `deps` unconditionally (base template uses it),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-zudo-doc",
-  "version": "0.2.7",
+  "version": "0.2.8",
   "description": "Create a new zudo-doc documentation site",
   "license": "MIT",
   "author": "Takeshi Takatsudo",

package/templates/base/src/config/color-schemes.ts

@@ -11,9 +11,11 @@ export interface ColorScheme {
     string, string, string, string, string, string, string, string,
     string, string, string, string, string, string, string, string,
   ];
-  /** Optional Shiki theme for the zdtp panel's client-side code-block preview.
-   *  Falls back to the panel config's DEFAULT_SHIKI_THEME when omitted.
-   *  Static highlighting (syntect via zfb's Rust pipeline) is unaffected. */
+  /** Optional, vestigial. Carried only in the zdtp panel's color-scheme
+   *  config envelope (falls back to DEFAULT_SHIKI_THEME when omitted), but has
+   *  no visible effect: zdtp's Shiki integration is a no-op stub, and page code
+   *  highlighting is done by syntect (dual-theme, configured via `codeHighlight`
+   *  in zfb.config.ts), not Shiki. */
   shikiTheme?: string;
   /** Optional semantic overrides — when omitted, defaults are used:
    *  surface=p0, muted=p8, accent=p5, accentHover=p14

package/templates/base/zfb-shim.d.ts

@@ -109,12 +109,23 @@ declare module "zfb/config" {
     base?: string;
     /**
      * Configures the syntect-based syntax highlighter shipped with zfb.
-     * Mirrors `code_highlight` in crates/zfb/src/config.rs (Takazudo/zudo-front-builder#188 / sub #194; landed in commit 339e30f).
+     * Mirrors `CodeHighlightConfig` / `code_highlight` in crates/zfb/src/config.rs
+     * (single-theme: Takazudo/zudo-front-builder#188 / sub #194, commit 339e30f;
+     * dual-theme themeLight/themeDark added in the follow-up shipped in
+     * zfb 0.1.0-next.45+).
      * When omitted, the engine falls back to the hardcoded default theme `base16-ocean.dark`.
+     *
+     * Single-theme mode: set `theme` — tokens get inline `style="color:#hex"`.
+     * Dual-theme mode: set BOTH `themeLight` and `themeDark` (mutually exclusive
+     * with `theme`) — tokens get `--shiki-light`/`--shiki-dark` CSS custom
+     * properties and the `<pre>` gains `class="syntect-dual"` + `--shiki-*-bg`.
+     * All names are SYNTECT theme names, not Shiki names.
      */
     codeHighlight?: {
       theme?: string;
       themesDir?: string;
+      themeLight?: string;
+      themeDark?: string;
     };
     /**
      * Markdown link resolver (port of `remarkResolveMarkdownLinks`).