@homepages/create-workspace 0.9.0-dev-20260719205406 → 0.9.0

package/dist/index.js

@@ -18,12 +18,23 @@ const NAME_RE = /^[a-z][a-z0-9-]*$/;
  * on fails at `npm install`, not at lint time, so this is not optional.
  */
 const ESLINT_PLUGIN_VERSION = "0.1.0";
+/**
+ * The CLI's caret pin. Same reasoning as ESLINT_PLUGIN_VERSION: @homepages/template-cli
+ * versions independently of the kit, so it cannot be derived from this package's own
+ * version and is a committed constant, bumped when that package releases a new minor.
+ *
+ * It is what supplies the `template-kit` command the scaffolded scripts invoke — the
+ * kit no longer carries a bin — so a workspace missing it fails on `npm run dev` with
+ * "command not found", which reads as a broken scaffold rather than a missing pin.
+ */
+const TEMPLATE_CLI_VERSION = "0.1.0";
 export async function scaffoldWorkspace(name, targetDir, opts) {
     await mkdir(targetDir, { recursive: true });
     await stampTree(join(ASSETS, "workspace"), targetDir, {
         WORKSPACE_NAME: name,
         KIT_VERSION: opts.kitVersion,
         ESLINT_PLUGIN_VERSION: opts.eslintPluginVersion ?? ESLINT_PLUGIN_VERSION,
+        TEMPLATE_CLI_VERSION: opts.templateCliVersion ?? TEMPLATE_CLI_VERSION,
     });
     await stampTree(join(ASSETS, "template"), join(targetDir, "templates", "starter"), {
         TEMPLATE_KEY: "starter",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@homepages/create-workspace",
-  "version": "0.9.0-dev-20260719205406",
+  "version": "0.9.0",
   "description": "Scaffold a HomePages template workspace.",
   "license": "UNLICENSED",
   "type": "module",

package/scaffold/template/sections/hero/fixtures.ts

@@ -1,5 +1,5 @@
 import type { FixtureModule } from "@homepages/template-kit";
-import { luxuryMultiUnit, mkResponsive } from "@homepages/template-kit/fixtures";
+import { luxuryMultiUnit } from "@homepages/template-kit/fixtures";
 
 // Base content the section is designed for. Nullability coverage (each optional
 // slot rendered empty) is derived automatically from schema.ts — no fixture
@@ -12,12 +12,12 @@ const fixtures: FixtureModule = {
   base: {
     slots: {
       headline: luxuryMultiUnit.facts.address.display,
+      // State the asset id, exactly as a saved page does — the preview server
+      // resolves it to a URL and a responsive ladder, the same way the API does
+      // when the page is published. A fixture never states a URL.
       hero_image: {
         photo_id: heroImage.id,
-        url: heroImage.url,
         alt: heroImage.alt,
-        // Height set to a 16:9 ratio to match the slot's locked crop.
-        responsive: mkResponsive(heroImage.url, 2048, 1152),
       },
       blurb: "A 12-unit mansard Victorian in Jamaica Plain, moments from the Emerald Necklace.",
     },

package/scaffold/workspace/AGENTS.md

@@ -9,9 +9,12 @@ You are authoring HomePages marketing-section templates in this workspace.
 - **Templates live in `templates/`.** Each is a plain folder — not an npm package.
   Add one with `npx template-kit new <name>`; add a section with
   `npx template-kit new-section <name>`.
-- **One kit, one version.** `@homepages/template-kit` is the only toolchain
-  dependency; every template shares it. Do not add per-template `package.json`,
-  `tsconfig`, or `eslint` files — there is exactly one of each, at this root.
+- **One kit, one version.** `@homepages/template-kit` carries the authoring
+  contract every template imports; `@homepages/template-cli` provides the
+  `template-kit` command and `@homepages/eslint-plugin-template` the lint preset.
+  All three are declared once, at this root, and every template shares them. Do not
+  add per-template `package.json`, `tsconfig`, or `eslint` files — there is exactly
+  one of each, at this root.
 - **The docs corpus is your whole universe:** `node_modules/@homepages/template-kit/guide/`
   (`llms.txt` is the router). Read it before authoring; do not guess the contract.
 

package/scaffold/workspace/CLAUDE.md

@@ -7,9 +7,12 @@ You are authoring HomePages marketing-section templates in this workspace.
 - **Templates live in `templates/`.** Each is a plain folder — not an npm package.
   Add one with `npx template-kit new <name>`; add a section with
   `npx template-kit new-section <name>`.
-- **One kit, one version.** `@homepages/template-kit` is the only toolchain
-  dependency; every template shares it. Do not add per-template `package.json`,
-  `tsconfig`, or `eslint` files — there is exactly one of each, at this root.
+- **One kit, one version.** `@homepages/template-kit` carries the authoring
+  contract every template imports; `@homepages/template-cli` provides the
+  `template-kit` command and `@homepages/eslint-plugin-template` the lint preset.
+  All three are declared once, at this root, and every template shares them. Do not
+  add per-template `package.json`, `tsconfig`, or `eslint` files — there is exactly
+  one of each, at this root.
 - **The docs corpus is your whole universe:** `node_modules/@homepages/template-kit/guide/`
   (`llms.txt` is the router). Read it before authoring; do not guess the contract.
 

package/scaffold/workspace/README.md

@@ -1,7 +1,10 @@
 # {{WORKSPACE_NAME}}
 
-A HomePages template workspace. Templates live in `templates/`. The kit toolchain
-is one dependency (`@homepages/template-kit`) shared by every template here.
+A HomePages template workspace. Templates live in `templates/`. The toolchain is
+declared once at this root — `@homepages/template-kit` (the authoring contract),
+`@homepages/template-cli` (the `template-kit` command) and
+`@homepages/eslint-plugin-template` (the lint preset) — and shared by every
+template here.
 
 ## Commands
 

package/scaffold/workspace/_package.json

@@ -14,6 +14,7 @@
   },
   "devDependencies": {
     "@homepages/eslint-plugin-template": "^{{ESLINT_PLUGIN_VERSION}}",
+    "@homepages/template-cli": "^{{TEMPLATE_CLI_VERSION}}",
     "@tailwindcss/cli": "^4.3.0",
     "@types/react": "^19.0.0",
     "@types/react-dom": "^19.0.0",