@homepages/template-kit 0.9.0-dev-20260719224319 → 0.9.0

package/CHANGELOG.md

@@ -1,6 +1,6 @@
 # @homepages/template-kit
 
-## 0.9.0-dev-20260719224319
+## 0.9.0
 
 ### Minor Changes
 
@@ -24,6 +24,34 @@
   `resolveImportedFile`, `resetClientFileCache`) that the plugin's rules consume
   over the peer edge.
 
+- f868a43: **Breaking:** the CLI has moved to its own package, `@homepages/template-cli`.
+  Installing the kit no longer installs the `template-kit` command, and the
+  `./canvas-core` subpath is gone.
+
+  The command itself is unchanged — it is still `template-kit dev`, `template-kit
+check`, and so on. Add the new package as a devDependency alongside your existing
+  kit dependency:
+
+  ```
+  npm i -D @homepages/template-cli
+  ```
+
+  The kit stays the package your templates import, under the same name and with the
+  same authoring API, so no `import` in a workspace changes. The CLI declares the kit
+  as a `peerDependency`, which is what guarantees a workspace resolves exactly one
+  copy of it.
+
+  Why: the CLI and its dev playground were 53% of the kit's published bytes while the
+  code that reaches a visitor's browser was under 1%, and they change on playground
+  cadence rather than contract cadence. Sharing one version number meant a
+  playground fix and an authoring-contract change were indistinguishable in the
+  number a template author reads.
+
+  `./ssr` additionally now exports `wrapClientModuleMagic`, `flattenLayout`,
+  `isShortSlot`, `resolveSectionRef`, `resolveAnchorMap` and `parseTreatment` — the
+  node-side schema and island helpers the CLI reaches across the peer edge. They are
+  deliberately absent from the authoring barrel: a renderer never imports `./ssr`.
+
 - b7bfc96: Fixtures state media asset ids instead of URLs, and the kit resolves them.
 
   A fixture now states what a saved page actually holds — `{ photo_id, alt }` — and
@@ -57,69 +85,11 @@
 
 ### Patch Changes
 
-- 10f53a7: `template-kit dev`'s canvas hover/select ring no longer overflows the page's
-  x-axis when hovering a full-bleed section (e.g. a hero or header flush with
-  both page edges). The ring's geometry inflated the target's bounding rect by
-  a fixed offset on every side with no bound, so a rect already touching the
-  document edge pushed the ring 2px past it, growing the iframe's horizontal
-  scroll extent. The ring box is now clamped to `[0, containerWidth]`.
-- f3f6d70: `template-kit check` no longer fails on a tsconfig `paths` alias (e.g.
-  `"@/platform/*": ["../platform/*"]`) or on a section whose contract files
-  share a module large enough for esbuild to code-split. Previously the
-  loader's css-stub plugin decided "external vs. bundle" from the specifier's
-  own text, so a `paths`-resolved alias got re-emitted as a literal bare
-  import Node couldn't resolve; separately, the loader's build applied
-  `publicPath` to code-split `chunk-*.js` cross-imports the same way it does
-  to real asset files, producing an import path Node couldn't resolve either.
-  Both are now decided from the actual resolved file, and `publicPath` is no
-  longer set on the loader's build.
-- 1c2c2db: `template-kit dev`'s preview server no longer 500s on `/runtime/base.css`.
-  The route resolved the file at a path the build never emits to
-  (`dist/css/base.css`; the build copies it flat to `dist/base.css`), so every
-  section rendered unstyled — Tailwind-derived colors and layout were silently
-  missing everywhere, only arbitrary-value element geometry survived. The
-  route now checks the built (flat) path first and falls back to the source
-  (`src/css/`) layout, so it resolves correctly both from an installed kit and
-  when running the CLI unbuilt via `tsx` during kit development.
-- 989d23e: `template-kit dev` gains an optional `--diagnostics-cmd` flag: point it at any
-  command that prints `{"violations": [...]}` JSON for a `--template`/`--section`
-  pair, and the standalone section preview
-  (`/sections/<template>/<section>/<fixture>`) shows a dismissible banner when it
-  reports violations. Unset by default — no behavior change for a workspace that
-  doesn't configure it.
-- e1d5792: `template-kit dev`'s preview server now compiles a template's theme-color
-  Tailwind utilities (`bg-primary`, `text-ink`, `bg-background`, etc.) instead
-  of silently dropping them. `assembleTemplateCss` used to concatenate the
-  compiled theme (`compileThemeToCss`, the `@theme inline` alias layer plus
-  its `:root` custom props) onto Tailwind's CLI output _after_ the CLI had
-  already run, so the theme's color tokens were never part of the build graph
-  Tailwind scanned — `@theme` outside that graph is inert, and silently so, so
-  any utility built on a template color never got generated. No error, no
-  warning: every section rendered with correct layout but default
-  black-on-white text and backgrounds. The theme partial is now written to the
-  dev cache and `@import`ed into the Tailwind entry ahead of the section
-  `@source` scans, mirroring how the registry's own publish pipeline
-  (`ci/build-css.ts`) has always assembled it. `fontFaces` is still prepended
-  to the final bundle separately, since a nested `@import url(...)` doesn't
-  hoist out of an imported partial.
-- 2e36277: Escape `>` and `&` as well as `<` in the dev server's island map, matching the escaping used by published pages.
 - 1c4c7dd: Island hydration is now nesting-safe: `hydrateIslands` skips any island marker
   nested inside another marker, so an island can render another island without the
   child being hydrated twice (once by its parent root, once independently). Enables
   interactive islands (accordion, card-slider, carousel) to wrap existing leaf
   islands (expandable-text) on published pages.
-- ff1d6de: `template-kit dev`'s canvas mirror now shows the Islands inspector panel for a
-  section-level selection, not just a slot selection. A `fill-parent`/`fill-self`
-  island with no owning slot of its own only ever gets its shield dropped by a
-  section-level click, so the panel previously could show it as `shielded` but
-  never `interactive`. Existing slot-selection behavior (edit panel + Islands
-  list) is unchanged.
-- 41d0e88: `template-kit dev` now honors a workspace's tsconfig `paths` when resolving
-  imports, the same way `check` already does via esbuild's native tsconfig
-  lookup. Previously the dev server's Vite instance had no `paths` awareness at
-  all, so a workspace mapping (e.g. `"@/lib/*": ["../lib/*"]`) that made `check`
-  pass left `dev` 500ing with `Cannot find module`. A workspace with no `paths`
-  mapping is unaffected.
 
 ## 0.8.0
 

package/README.md

@@ -1,7 +1,9 @@
 # @homepages/template-kit
 
 The authoring surface for HomePages marketing-section templates: schema system,
-contract primitives, the theme system, and the `template-kit` CLI.
+contract primitives, and the theme system. The `template-kit` command lives in its
+own package, [`@homepages/template-cli`](#install) — the kit is what your templates
+`import`.
 
 **Status: 0.0.x.** The **schema system** (the section authoring contract and the closed
 vocabulary it validates against), the **contract primitives**, and the **theme system**
@@ -31,9 +33,16 @@ Prefer to wire a workspace by hand? See **Install** below.
 
 ```bash
 npm install @homepages/template-kit react react-dom
+npm install -D @homepages/template-cli                               # the `template-kit` command
 npm install -D typescript eslint @typescript-eslint/parser esbuild   # the authoring toolchain
 ```
 
+The **command is `template-kit`; the package that provides it is
+`@homepages/template-cli`** — a package/bin mismatch in the same spirit as
+`typescript`/`tsc`. Everything you write is imported from `@homepages/template-kit`;
+the CLI declares the kit as a peer dependency, so a workspace resolves exactly one
+copy of it.
+
 React 19 is a **peer dependency** — the kit never bundles its own copy.
 
 The kit has exactly **one runtime dependency** (`zod`). The authoring toolchain the
@@ -97,6 +106,7 @@ Full contract: **[guide/primitives.md](guide/primitives.md)**.
 | `@homepages/template-kit/browser` | Browser helpers for published pages (site config, signed ingest) |
 | `@homepages/template-kit/styles.css` | The global Tailwind preamble: the breakpoint ladder, the spacing base unit, the motion defaults, kit source registration |
 | `@homepages/template-kit/base.css` | Cascade-layer order, the three reset gaps Tailwind's preflight leaves, `.tr-section`, and the motion tokens |
+| `@homepages/template-cli` | The `template-kit` command (its own package) |
 | `@homepages/eslint-plugin-template` | ESLint flat-config preset (its own package) |
 | `@homepages/template-kit/tsconfig` | tsconfig preset (`"extends"`) |
 
@@ -158,7 +168,7 @@ section also has a standalone page, and so does the whole template at
 payload), and `/api/screenshot` (a full-page PNG, section or whole template). Like
 `check`, it runs **your** toolchain — Vite and Tailwind resolved from your workspace,
 installed with `npm i -D vite @vitejs/plugin-react tailwindcss @tailwindcss/cli` — not
-shipped by the kit. Full contract: **[guide/dev.md](guide/dev.md)**.
+shipped by either package. Full contract: **[guide/dev.md](guide/dev.md)**.
 
 ## Checking a workspace
 
@@ -229,5 +239,5 @@ that vocabulary — your template names its own.
 
 Don't — changesets owns `package.json`'s version. There is nothing else to keep
 in step with it: `KIT_VERSION` is read from `package.json` and inlined at build
-time, and the test suite asserts `template-kit --version` against `package.json`
-to prove the inlining happened.
+time, and the test suite asserts it against `package.json` to prove the inlining
+happened.

package/dist/contracts/fill-treatments.d.ts

@@ -0,0 +1,23 @@
+//#region src/contracts/fill-treatments.d.ts
+declare const GENERATED_KINDS: readonly ["text", "list<text>"];
+type GeneratedKind = (typeof GENERATED_KINDS)[number];
+declare const COMPUTED_FNS: readonly ["haversine_miles", "mint_id"];
+type ComputedFn = (typeof COMPUTED_FNS)[number];
+declare const CATALOG_FIELDS: readonly ["key", "label", "icon", "slot"];
+type CatalogField = (typeof CATALOG_FIELDS)[number];
+type Treatment = {
+  kind: "source";
+  path: string | null;
+} | {
+  kind: "computed";
+  fn: ComputedFn;
+} | {
+  kind: "catalog";
+  field: CatalogField;
+} | {
+  kind: "generated";
+  outKind: GeneratedKind;
+};
+declare function parseTreatment(raw: string): Treatment | null;
+//#endregion
+export { CATALOG_FIELDS, COMPUTED_FNS, CatalogField, ComputedFn, GENERATED_KINDS, GeneratedKind, Treatment, parseTreatment };

package/dist/index.d.ts

@@ -34,8 +34,8 @@ import { TokenNameSchema, TokenTheme, TokenThemeSchema, compileThemeToCss } from
  * Read from package.json and inlined at build time, so it cannot drift: changesets
  * owns package.json's version, and a hardcoded constant here would have to be
  * hand-edited on every release — on a branch changesets force-pushes, which would
- * silently discard the edit. `dist/cli.js --version` is asserted against
- * package.json to prove the inlining actually happened.
+ * silently discard the edit. src/index.test.ts asserts it against package.json to
+ * prove the inlining actually happened.
  */
 declare const KIT_VERSION: string;
 //#endregion

package/dist/index.js

@@ -27,8 +27,8 @@ import { TokenNameSchema, TokenThemeSchema, compileThemeToCss } from "./design-s
 * Read from package.json and inlined at build time, so it cannot drift: changesets
 * owns package.json's version, and a hardcoded constant here would have to be
 * hand-edited on every release — on a branch changesets force-pushes, which would
-* silently discard the edit. `dist/cli.js --version` is asserted against
-* package.json to prove the inlining actually happened.
+* silently discard the edit. src/index.test.ts asserts it against package.json to
+* prove the inlining actually happened.
 */
 const KIT_VERSION = version;
 

package/dist/islands/discover.js

@@ -1,6 +1,6 @@
 import { isClientComponentFile } from "./detect.js";
-import { readdir } from "node:fs/promises";
 import { extname, join } from "node:path";
+import { readdir } from "node:fs/promises";
 
 //#region src/islands/discover.ts
 const COMPONENT_EXTS = /* @__PURE__ */ new Set([".tsx", ".jsx"]);

package/dist/islands/esbuild-plugin.js

@@ -1,7 +1,7 @@
 import { islandKey } from "./detect.js";
 import { wrapClientModuleSource } from "./wrap.js";
-import { readFile } from "node:fs/promises";
 import { basename, extname } from "node:path";
+import { readFile } from "node:fs/promises";
 
 //#region src/islands/esbuild-plugin.ts
 const LOADER = {

package/dist/islands/wrap.d.ts

@@ -1,5 +1,13 @@
 import MagicString from "magic-string";
 //#region src/islands/wrap.d.ts
+/**
+ * The codemod as a `MagicString`, so a caller (the Vite plugin) can emit a
+ * hi-res sourcemap alongside the rewritten code. Returns null on the same terms
+ * as `wrapClientModuleSource` — a non-client module or one with no default
+ * export. The rebound original is `__trIslandReal`; it still flows through the
+ * consumer's JSX/TS transform unchanged.
+ */
+declare function wrapClientModuleMagic(code: string, islandKey: string): MagicString | null;
 /**
  * Rewrite a client module's source so its default export renders through
  * `IslandMarker` with `islandKey`. Returns null when `code` is not a client
@@ -9,4 +17,4 @@ import MagicString from "magic-string";
  */
 declare function wrapClientModuleSource(code: string, islandKey: string): string | null;
 //#endregion
-export { wrapClientModuleSource };
+export { wrapClientModuleMagic, wrapClientModuleSource };

package/dist/media/resolve-fixture-media.d.ts

@@ -0,0 +1,22 @@
+//#region src/media/resolve-fixture-media.d.ts
+/**
+ * `resolveFixtureMedia` over a built fixture set — the form every node-only caller
+ * (the SSR loader, `template-kit check`) actually needs.
+ */
+declare function resolveFixtureSetMedia<T extends {
+  props: unknown;
+}>(fixtures: T[]): T[];
+/** A fixture stating a media asset id the pack does not carry. */
+type UnresolvedMedia = {
+  /** Where the id sits — `photo_id`, `video_id`, `floor_plans[].id`. */
+  field: string;
+  id: string;
+};
+/**
+ * Every media asset id a fixture states that the pack does not carry. Run over
+ * PRE-resolution props — after resolution the id is gone, replaced by the empty
+ * default.
+ */
+declare function findUnresolvedMedia(props: unknown): UnresolvedMedia[];
+//#endregion
+export { UnresolvedMedia, findUnresolvedMedia, resolveFixtureSetMedia };

package/dist/package.js

@@ -1,5 +1,5 @@
 //#region package.json
-var version = "0.9.0-dev-20260719224319";
+var version = "0.9.0";
 
 //#endregion
 export { version };

package/dist/schema/resolve-section-ref.d.ts

@@ -0,0 +1,4 @@
+//#region src/schema/resolve-section-ref.d.ts
+declare function resolveSectionRef(templateKey: string, ref: string): string;
+//#endregion
+export { resolveSectionRef };

package/dist/schema/rows.d.ts

@@ -0,0 +1,9 @@
+//#region src/schema/rows.d.ts
+type LayoutEntry = string | readonly [string, string];
+declare function flattenLayout(layout: readonly LayoutEntry[]): string[];
+declare function isShortSlot(slot: {
+  type: string;
+  size?: string;
+}): boolean;
+//#endregion
+export { LayoutEntry, flattenLayout, isShortSlot };

package/dist/schema/section-nav.d.ts

@@ -3,5 +3,9 @@ type SectionNav = {
   selfAnchor: string;
   anchors: Record<string, string>;
 };
+declare function resolveAnchorMap(sections: ReadonlyArray<{
+  key: string;
+  anchor: string;
+}>): Record<string, string>;
 //#endregion
-export { SectionNav };
+export { SectionNav, resolveAnchorMap };

package/dist/schema/slot-types.d.ts

@@ -11,8 +11,8 @@ declare function slotDefTypes(): SlotType[];
 declare const ContentSlot: z.ZodObject<{
   type: z.ZodEnum<{
     number: "number";
-    select: "select";
     text: "text";
+    select: "select";
     image: "image";
     image_collection: "image_collection";
     list: "list";

package/dist/ssr.d.ts

@@ -1,11 +1,16 @@
+import { resolveAnchorMap } from "./schema/section-nav.js";
 import { ResolvedFixture } from "./schema/fixture-schema.js";
 import "./schema/index.js";
 import { hasClientDirective, isClientFile, resetClientFileCache, resolveImportedFile } from "./islands/client-directive.js";
 import { isClientComponentFile, islandKey } from "./islands/detect.js";
-import { wrapClientModuleSource } from "./islands/wrap.js";
+import { wrapClientModuleMagic, wrapClientModuleSource } from "./islands/wrap.js";
 import { findSectionIslands } from "./islands/discover.js";
 import { islandTransformEsbuildPlugin } from "./islands/esbuild-plugin.js";
 import { DEV_MEDIA_URL_PREFIX, MediaAsset, MediaKind, getMediaAsset, listMediaAssets, mediaPackHasFile, packRelativeFromUrl } from "./media/pack.js";
+import { UnresolvedMedia, findUnresolvedMedia, resolveFixtureSetMedia } from "./media/resolve-fixture-media.js";
+import { Treatment, parseTreatment } from "./contracts/fill-treatments.js";
+import { LayoutEntry, flattenLayout, isShortSlot } from "./schema/rows.js";
+import { resolveSectionRef } from "./schema/resolve-section-ref.js";
 import { ComponentType } from "react";
 //#region src/ssr/index.d.ts
 type LoadedSection = {
@@ -43,4 +48,4 @@ declare function loadSectionBundle(dir: string, load?: SectionModuleLoader): Pro
  */
 declare function renderSectionHtml(renderer: ComponentType<Record<string, unknown>>, props: Record<string, unknown>): string;
 //#endregion
-export { DEV_MEDIA_URL_PREFIX, LoadedSection, type MediaAsset, type MediaKind, SectionModuleLoader, findSectionIslands, getMediaAsset, hasClientDirective, isClientComponentFile, isClientFile, islandKey, islandTransformEsbuildPlugin, listMediaAssets, loadSectionBundle, mediaPackHasFile, nativeSectionLoader, packRelativeFromUrl, renderSectionHtml, resetClientFileCache, resolveImportedFile, wrapClientModuleSource };
+export { DEV_MEDIA_URL_PREFIX, type LayoutEntry, LoadedSection, type MediaAsset, type MediaKind, SectionModuleLoader, type Treatment, type UnresolvedMedia, findSectionIslands, findUnresolvedMedia, flattenLayout, getMediaAsset, hasClientDirective, isClientComponentFile, isClientFile, isShortSlot, islandKey, islandTransformEsbuildPlugin, listMediaAssets, loadSectionBundle, mediaPackHasFile, nativeSectionLoader, packRelativeFromUrl, parseTreatment, renderSectionHtml, resetClientFileCache, resolveAnchorMap, resolveFixtureSetMedia, resolveImportedFile, resolveSectionRef, wrapClientModuleMagic, wrapClientModuleSource };

package/dist/ssr.js

@@ -3,9 +3,13 @@ import { DEV_MEDIA_URL_PREFIX, getMediaAsset, listMediaAssets, mediaPackHasFile,
 import { findUnresolvedMedia, resolveFixtureSetMedia } from "./media/resolve-fixture-media.js";
 import { hasClientDirective, isClientFile, resetClientFileCache, resolveImportedFile } from "./islands/client-directive.js";
 import { isClientComponentFile, islandKey } from "./islands/detect.js";
-import { wrapClientModuleSource } from "./islands/wrap.js";
+import { wrapClientModuleMagic, wrapClientModuleSource } from "./islands/wrap.js";
 import { findSectionIslands } from "./islands/discover.js";
 import { islandTransformEsbuildPlugin } from "./islands/esbuild-plugin.js";
+import { parseTreatment } from "./contracts/fill-treatments.js";
+import { flattenLayout, isShortSlot } from "./schema/rows.js";
+import { resolveSectionRef } from "./schema/resolve-section-ref.js";
+import { resolveAnchorMap } from "./schema/section-nav.js";
 import { createElement } from "react";
 import { basename, join } from "node:path";
 import { pathToFileURL } from "node:url";
@@ -61,4 +65,4 @@ function renderSectionHtml(renderer, props) {
 }
 
 //#endregion
-export { DEV_MEDIA_URL_PREFIX, findSectionIslands, getMediaAsset, hasClientDirective, isClientComponentFile, isClientFile, islandKey, islandTransformEsbuildPlugin, listMediaAssets, loadSectionBundle, mediaPackHasFile, nativeSectionLoader, packRelativeFromUrl, renderSectionHtml, resetClientFileCache, resolveImportedFile, wrapClientModuleSource };
+export { DEV_MEDIA_URL_PREFIX, findSectionIslands, findUnresolvedMedia, flattenLayout, getMediaAsset, hasClientDirective, isClientComponentFile, isClientFile, isShortSlot, islandKey, islandTransformEsbuildPlugin, listMediaAssets, loadSectionBundle, mediaPackHasFile, nativeSectionLoader, packRelativeFromUrl, parseTreatment, renderSectionHtml, resetClientFileCache, resolveAnchorMap, resolveFixtureSetMedia, resolveImportedFile, resolveSectionRef, wrapClientModuleMagic, wrapClientModuleSource };

package/guide/INDEX.md

@@ -11,6 +11,11 @@ This tree **ships in the npm tarball** (`guide/` is listed in `package.json`'s
 LLM agents, reading it from inside `node_modules`. Keep it free of internal-only
 detail.
 
+Every `template-kit <command>` on these pages is spelled exactly as you type it.
+The package that provides that command is `@homepages/template-cli`, a
+devDependency alongside the kit — see [Upgrading](upgrading.md) for its separate
+version line.
+
 | Doc | What it covers | Read when you're touching... |
 |---|---|---|
 | `quickstart.md` | The cold-start tutorial: create a workspace, preview the starter's `hero` section, read its four files, make one edit, and check it — owns the author-loop anchor every recipe links to | your first section, end to end |

package/guide/check.md

@@ -28,6 +28,7 @@ one or pass `--all`.
 ### What it needs installed
 
 ```bash
+npm i -D @homepages/template-cli   # provides the `template-kit` command
 npm i -D typescript eslint @typescript-eslint/parser esbuild @homepages/eslint-plugin-template
 ```
 

package/guide/dev.md

@@ -28,6 +28,7 @@ command runs until you interrupt it (Ctrl-C).
 ### What it needs installed
 
 ```bash
+npm i -D @homepages/template-cli   # provides the `template-kit` command
 npm i -D vite @vitejs/plugin-react tailwindcss @tailwindcss/cli
 ```
 

package/guide/llms.txt

@@ -1,8 +1,8 @@
 # @homepages/template-kit
 
 > The authoring kit for HomePages marketing-section templates. This corpus ships
-> inside the npm package so an agent can read it locally, versioned in lockstep
-> with the code it describes.
+> inside the npm package so an agent can read it locally, versioned with the
+> authoring contract it describes.
 
 Status: 0.x — pre-1.0, so a minor is the breaking axis and a patch carries features
 as well as fixes; see [Upgrading](upgrading.md). The schema system, the contract
@@ -13,6 +13,12 @@ implemented — see [Check](check.md), [Theme and CSS](theme-and-css.md#generati
 [Dev](dev.md), [Pack](pack.md), and [Adding templates](new.md); its remaining
 commands arrive with the surfaces they drive.
 
+The **command is `template-kit`; the package that provides it is
+`@homepages/template-cli`**, a devDependency alongside the kit. It versions on its
+own line and declares the kit as a peer dependency, so a workspace resolves exactly
+one kit. Every command written in this corpus is spelled the same either way — only
+the install line names the CLI package.
+
 Everything an author writes a section against is imported from the package root —
 `@homepages/template-kit`. The exceptions are deliberate: the two CSS entries
 (`./styles.css`, `./base.css`), and `./fixtures` — the golden scenarios, which only
@@ -102,7 +108,9 @@ and [Pick a scenario](recipes/pick-a-scenario.md).
   patch (0.4.0 → 0.4.1) carries features AND fixes and `npm update` takes it, while
   a minor (0.4.x → 0.5.0) is breaking and needs an explicit
   `npm install @homepages/template-kit@^0.5.0` — a 0.x caret never crosses a minor.
-  Submissions are accepted against the current kit line and the one before it.
+  `@homepages/template-cli` and `@homepages/eslint-plugin-template` each version on
+  their own line and update separately. Submissions are accepted against the current
+  kit line and the one before it.
 - [Adding templates](new.md): the `template-kit new <template>` and
   `template-kit new-section <template>/<section>` CLI commands — scaffolding a new
   template with a working starter section, or adding a bare section (the four

package/guide/upgrading.md

@@ -43,19 +43,21 @@ npm run check
 CHANGELOG in the package (`node_modules/@homepages/template-kit/CHANGELOG.md`) for
 what changed and why.
 
-## The lint preset upgrades separately
+## The CLI and the lint preset upgrade separately
 
-`@homepages/eslint-plugin-template` is its own package with its own version line,
-so the kit's number tells you nothing about it and `npm update
-@homepages/template-kit` never moves it. Update it the same way, on its own:
+`@homepages/template-cli` (which provides the `template-kit` command) and
+`@homepages/eslint-plugin-template` (the lint preset) are each their own package on
+their own version line, so the kit's number tells you nothing about them and `npm
+update @homepages/template-kit` never moves them. Update each on its own:
 
 ```bash
+npm update @homepages/template-cli
 npm update @homepages/eslint-plugin-template
 ```
 
-It declares the kit as a **peer dependency**, so its range says which kit line it
-supports. If `npm install` reports a peer conflict after a kit minor, the preset is
-the package to bump — not the kit to hold back.
+Both declare the kit as a **peer dependency**, so each one's range says which kit
+line it supports. If `npm install` reports a peer conflict after a kit minor, the
+package to bump is the one reporting it — not the kit to hold back.
 
 ## How long you have
 
@@ -74,4 +76,6 @@ npm ls @homepages/template-kit    # what you have installed
 npm view @homepages/template-kit version   # the current release
 ```
 
-The same two commands work for `@homepages/eslint-plugin-template`.
+The same two commands work for `@homepages/template-cli` and
+`@homepages/eslint-plugin-template`. `template-kit --version` prints the pair the
+command is actually running as `<cli> (kit <kit>)`.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@homepages/template-kit",
-  "version": "0.9.0-dev-20260719224319",
-  "description": "Authoring kit for HomePages marketing-section templates: schema system, contract primitives, theme tokens, and the template-kit CLI.",
+  "version": "0.9.0",
+  "description": "Authoring kit for HomePages marketing-section templates: schema system, contract primitives, theme tokens, and the design-system CSS layer.",
   "license": "UNLICENSED",
   "type": "module",
   "engines": {
@@ -22,9 +22,6 @@
     "tsconfig.base.json",
     "CHANGELOG.md"
   ],
-  "bin": {
-    "template-kit": "dist/cli.js"
-  },
   "exports": {
     ".": {
       "types": "./dist/index.d.ts",
@@ -50,10 +47,6 @@
       "types": "./dist/rules.d.ts",
       "default": "./dist/rules.js"
     },
-    "./canvas-core": {
-      "types": "./dist/canvas-core.d.ts",
-      "default": "./dist/canvas-core.js"
-    },
     "./styles.css": "./dist/styles.css",
     "./base.css": "./dist/base.css",
     "./tsconfig": "./tsconfig.base.json",
@@ -64,10 +57,9 @@
   ],
   "scripts": {
     "prepack": "npm run build",
-    "build": "tsdown && node scripts/build-dev-client.mjs && node scripts/build-cli-assets.mjs",
+    "build": "tsdown",
     "typecheck": "tsc --noEmit",
     "lint": "eslint .",
-    "pretest": "node test/link-fixture-workspace.mjs",
     "test": "node --import tsx --test 'src/**/*.test.ts' 'src/**/*.test.tsx'",
     "lint:pkg": "publint --strict && attw --pack . --profile esm-only --exclude-entrypoints styles.css base.css",
     "verify:consumer": "node scripts/verify-consumer.mjs",
@@ -81,15 +73,12 @@
   "devDependencies": {
     "@arethetypeswrong/cli": "^0.18.5",
     "@eslint/js": "^9.39.4",
-    "@playwright/test": "^1.60.0",
     "@tailwindcss/cli": "^4.3.0",
     "@types/jsdom": "^21.1.7",
     "@types/node": "^20.17.10",
     "@types/react": "^19.0.0",
     "@types/react-dom": "^19.0.0",
     "@typescript-eslint/parser": "^8.60.1",
-    "@vitejs/plugin-react": "^4.3.4",
-    "chokidar": "^4.0.1",
     "esbuild": "^0.28.1",
     "eslint": "^9.39.4",
     "jsdom": "^26.1.0",
@@ -100,8 +89,7 @@
     "tsdown": "0.22.7",
     "tsx": "^4.19.2",
     "typescript": "^5.7.2",
-    "typescript-eslint": "^8.60.1",
-    "vite": "^6.0.5"
+    "typescript-eslint": "^8.60.1"
   },
   "dependencies": {
     "magic-string": "^0.30.21",

package/dist/canvas-core/chrome-css.d.ts

@@ -1,24 +0,0 @@
-import { MarkerAttrs } from "./types.js";
-//#region src/canvas-core/chrome-css.d.ts
-/**
- * Custom properties the chrome CSS reads but deliberately does not declare —
- * the host must set them on the iframe document's root element. This is the
- * host's obligation, not a suggestion: an adapter that skips one leaves the
- * declared inline fallback in force, which renders plausibly and silently
- * wrong rather than failing.
- *
- * - `--we-panel-w`: the floating panel's measured width, mirrored onto the
- *   iframe root so the page card's right padding clears it. Unset, the card
- *   lays out against the 436px base-width fallback and drifts out of alignment
- *   whenever the real panel is any other width.
- * - `--we-content`: the host's interior scaling unit, mirrored in so hidden-tab
- *   chrome scales with the rest of the UI. Unset, it pins to the 1px fallback
- *   and the tabs stay laptop-sized while every surrounding surface scales.
- *
- * Anything added here must actually be read by the kernel; the token test
- * fails on a stale entry.
- */
-declare const HOST_INJECTED_PROPERTIES: readonly ["--we-panel-w", "--we-content"];
-declare function buildChromeCss(markers: MarkerAttrs): string;
-//#endregion
-export { HOST_INJECTED_PROPERTIES, buildChromeCss };