@homepages/template-kit 0.4.0 → 0.5.0

package/CHANGELOG.md

@@ -1,5 +1,101 @@
 # @homepages/template-kit
 
+## 0.5.0
+
+### Minor Changes
+
+- ac0d622: Fixtures: replace the single `sampleProperty` dataset with three named scenarios
+  (`scenarios.luxuryMultiUnit` / `sparseSingleFamily` / `forRentCondo`) plus fact-level
+  helpers (`primaryContact`, `contactCards`, `poisByCategory`, `propertyMetrics`). The raw
+  single-property exports (`sampleProperty`, `allPhotos`, `samplePois`, `sampleContacts`,
+  `sampleAmenities`, `sampleHeroSlots`) are removed — build fixtures from a scenario.
+  `mkResponsive` and the data types are unchanged.
+
+  A scenario's org name and logos live on `ContactFixture["fields"]`
+  (`org_name`/`logo_light`/`logo_dark`), matching where the real facts schema and
+  `SOURCE_FIELDS` (`logo_dark`/`logo_light`, `container: "contact"`) put them — there is
+  no separate `brand` field or `BrandFixture` type. `propertyMetrics`'s cross-unit
+  aggregates (`bedsMin`/`bedsMax`/`bathsMin`/`bathsMax`/`sqftMax`) are `string | null`,
+  matching the canonical `units.bedsMin`/etc. transforms' formatted output (e.g. `"3,800"`,
+  not `3800`); `beds`/`baths`/`sqft`/`price` (the lowest-position unit's raw figures) are
+  unchanged.
+
+- 0907653: The shipped authoring corpus moved from `docs/` to `guide/` inside the published
+  package (e.g. `node_modules/@homepages/template-kit/guide/quickstart.md`). Every
+  rule-id doc path (`docsPathForRule`, printed in `check`/lint failures) and the
+  `link`/`unlink`/`status` overlay now resolve against `guide/` as well. Update any
+  tooling or bookmarks that hardcoded the old `docs/` path.
+- a0712da: Add the `video` and `video_collection` slot types and the `<Video>` primitive — hosted
+  video a section declares like an image, not a link to a third-party player.
+
+  A `video` slot's value is `{ video_id, url, poster, alt, width?, height? }`; a
+  `video_collection` is an array of those. `url` always points at a single transcoded
+  progressive MP4 rendition, so — unlike `ImageValue` — there is no `responsive` ladder and
+  no `mobile` variant. Video slots have **no cropping or editing of any kind**: a video is
+  selected, never edited, so none of `ImageValue`'s `rect`/`ar`/`crop_key` re-edit state
+  exists, and authoring `crop` on a video slot is rejected. Defaults are non-null
+  (`{ url: "", poster: "", alt: "" }` and `[]`) so a renderer with a non-nullable slot
+  cannot crash on `slots.x.url`.
+
+  Playback is **author-declared per slot** via a `playback` config alongside `frame` —
+  a silent hero loop and a narrated tour need opposite behavior and the platform cannot
+  infer which from the asset:
+
+  ```ts
+  hero_loop: {
+    type: "video",
+    frame: { breakpoint: 768, desktop: { aspect: 16 / 9 } },
+    playback: { autoplay: true, muted: true, loop: true, controls: false, preload: "auto" },
+  }
+  ```
+
+  **`autoplay` requires `muted`** — every browser blocks unmuted autoplay, so declaring one
+  without the other fails `check` rather than shipping a video that silently never plays.
+  `preload: "none"` is the bandwidth lever for a below-fold video most visitors never reach.
+
+  **Upgrading: raw `<video>` is now banned.** `<Video>` is the sole lint-legal emitter of
+  the tag — `no-raw-element` bans it exactly as it does `<img>`, with no island exemption.
+  If a section of yours writes a raw `<video>`, `check` will fail until it moves to
+  `<Video>`; that is the one backward-incompatible part of this release.
+
+  `<Video>` renders the poster, passes playback through verbatim,
+  and — like `<Image>` — keeps its aspect-ratio box and fallback rect when `url` is empty,
+  which is what both an unfilled slot and a still-transcoding video look like. With no
+  `playback` declared it falls back to a plain controls player.
+
+### Patch Changes
+
+- aaa2e2f: Islands: `hydrateIslands({ applyEditorProps: true })` now hydrates an island's
+  server-rendered HTML instead of discarding it. Applying `editor.props` previously issued a
+  root-level re-render before hydration had flushed, which made React drop the SSR tree,
+  client-render the island from scratch, and log `This root received an early update, before
+anything was able hydrate` straight to the console — where the loader's `onError` could not
+  intercept it. The props are now merged in a layout effect after the hydration commit, so
+  the SSR tree survives and the console stays clean.
+
+  Because the island is now hydrated rather than replaced, `editor.props` arrive as an update
+  after mount rather than as part of the initial mount. A prop read only at mount time — a
+  `useState` initializer, an `<input defaultValue>` — must be read during render instead, or
+  the editor-only value will not apply.
+
+- c79d75a: Adds a guide page on upgrading: what a patch vs a minor release means while the kit
+  is pre-1.0, why a 0.x caret cannot cross a minor on its own, and how long submissions
+  built on the previous kit line keep being accepted. `npm create homepages-workspace` is
+  now published, and always carries the same version as the kit it scaffolds against.
+
+## 0.4.1
+
+### Patch Changes
+
+- 1e35f40: Fixes `wrapClientModuleSource`/`islandTransformEsbuildPlugin` (the `./ssr` subpath's
+  island codemod) throwing `MagicString is not a constructor` under `tsx`. `magic-string`
+  was missing from `dependencies`, so tsdown vendored an unpackaged private copy into the
+  kit's own `dist/node_modules/` (no `package.json` alongside it) instead of externalizing
+  the bare import — that copy's module type depended on ancestor-directory inference, which
+  diverges between plain Node and tsx's resolver. `magic-string` is now a declared runtime
+  dependency, so the shipped code imports it as a normal bare specifier resolved from the
+  consumer's own `node_modules`.
+
 ## 0.4.0
 
 ### Minor Changes

package/README.md

@@ -9,7 +9,7 @@ are complete — a section is authorable end to end against the kit. The `templa
 CLI's `check`, `theme`, `dev`, and `pack` commands are implemented — see
 [Checking a workspace](#checking-a-workspace), [Generating a theme](#generating-a-theme),
 and [Previewing a workspace](#previewing-a-workspace) below — and `new` / `new-section`
-scaffold a template or a section into a workspace (see [docs/new.md](docs/new.md)).
+scaffold a template or a section into a workspace (see [guide/new.md](guide/new.md)).
 
 ## Quick start
 
@@ -24,7 +24,7 @@ npm run dev        # preview the starter; the island hydrates
 ```
 
 Add more templates with `npx template-kit new <template>` and sections with
-`npx template-kit new-section <template>/<section>` — see [docs/new.md](docs/new.md).
+`npx template-kit new-section <template>/<section>` — see [guide/new.md](guide/new.md).
 Prefer to wire a workspace by hand? See **Install** below.
 
 ## Install
@@ -37,7 +37,7 @@ npm install -D typescript eslint @typescript-eslint/parser esbuild   # the autho
 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
-[`check` command](docs/check.md) and the [ESLint preset](docs/eslint.md) run on is
+[`check` command](guide/check.md) and the [ESLint preset](guide/eslint.md) run on is
 yours: both resolve TypeScript, ESLint, the parser and esbuild from your workspace, so
 your pinned versions are the ones that judge your code. The kit does not depend on them
 at all — which is why a linter never lands in the production install of an app that
@@ -65,30 +65,34 @@ export type Props = SectionProps<typeof schema>; // slots.headline is `string`
 
 Property facts come from a closed vocabulary, so `direct("listing_intentt")` is a
 compile error, not a runtime surprise. Full contract:
-**[docs/schema-system.md](docs/schema-system.md)**.
+**[guide/schema-system.md](guide/schema-system.md)**.
 
-Your fixtures build on the kit's golden property dataset (`sampleProperty`, `allPhotos`,
-`samplePois`, …) — a realistic 12-unit building, long labels and missing values included.
+Your fixtures build on the kit's golden scenarios (`scenarios.luxuryMultiUnit`,
+`sparseSingleFamily`, `forRentCondo`, plus helpers like `propertyMetrics()`) — real,
+self-consistent properties spanning multi/single unit and sale/rent, long labels and
+missing values included.
 
 ## The primitives
 
-The kit ships **five components and nothing else**: `Section` (the full-bleed section
-root), `Slot` and `SlotItem` and `SlotGroup` (the editor's marker attributes), and
-`Image` (responsive `<picture>` + a deterministic empty-state box). Each earns its place
+The kit ships **six components and nothing else**: `Section` (the full-bleed section
+root), `Slot` and `SlotItem` and `SlotGroup` (the editor's marker attributes),
+`Image` (responsive `<picture>` + a deterministic empty-state box), and `Video` (poster
+frame + author-declared playback + the same empty-state box). Each earns its place
 by emitting something the platform breaks without. Presentation — headings, links,
 layout, icons — is your template's own JSX.
 
 ```tsx
-import { Image, Section, Slot, SlotItem } from "@homepages/template-kit";
+import { Image, Section, Slot, SlotItem, Video } from "@homepages/template-kit";
 ```
 
-Full contract: **[docs/primitives.md](docs/primitives.md)**.
+Full contract: **[guide/primitives.md](guide/primitives.md)**.
 
 ## Exports
 
 | Entry | Use |
 |---|---|
-| `@homepages/template-kit` | Authoring API — schema system, primitives, marker contract, theme types, and the golden fixtures |
+| `@homepages/template-kit` | Authoring API — schema system, primitives, marker contract, theme types |
+| `@homepages/template-kit/fixtures` | The golden scenarios + helpers for `fixtures.ts` — a separate entry so dev-only sample data never reaches a published renderer bundle |
 | `@homepages/template-kit/island-runtime` | Browser loader that hydrates a page's islands |
 | `@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 |
@@ -96,8 +100,10 @@ Full contract: **[docs/primitives.md](docs/primitives.md)**.
 | `@homepages/template-kit/eslint` | ESLint flat-config preset |
 | `@homepages/template-kit/tsconfig` | tsconfig preset (`"extends"`) |
 
-The authoring API has **no subpath imports** — one specifier for everything you
-write a section against. The two CSS entries are the deliberate exception.
+One specifier for everything you write a section against. The exceptions are
+deliberate: the two CSS entries, and `/fixtures` — the golden scenarios, which only
+`fixtures.ts` imports, kept off the root barrel so dev-only sample data can never
+reach a published renderer's import graph.
 
 `styles.css` does **not** import Tailwind. Import it *after* Tailwind in your entry, then
 your generated theme after that:
@@ -113,15 +119,15 @@ belongs in this entry and nowhere else: it carries an `@theme` block, a Tailwind
 that is inert outside the build graph. `base.css` is not part of that entry — it loads as
 its own stylesheet on the page. `base.css` ships no reset of its own — it depends on the
 preflight your entry's `@import "tailwindcss"` brings. Both must be on the page. Full
-contract: **[docs/theme-and-css.md](docs/theme-and-css.md)**.
+contract: **[guide/theme-and-css.md](guide/theme-and-css.md)**.
 
 ## Rules
 
 The lint preset and the `template-kit check` CLI share one id namespace,
 `template-kit/<id>`. A rule-id printed by either resolves to a page —
-`docs/rules/<id>.md` — giving the rule, the reason it exists, and a before/after fix.
-Start at **[docs/rules/INDEX.md](docs/rules/INDEX.md)**; the full doc set is routed
-from **[docs/INDEX.md](docs/INDEX.md)**.
+`guide/rules/<id>.md` — giving the rule, the reason it exists, and a before/after fix.
+Start at **[guide/rules/INDEX.md](guide/rules/INDEX.md)**; the full doc set is routed
+from **[guide/INDEX.md](guide/INDEX.md)**.
 
 ## Generating a theme
 
@@ -133,7 +139,7 @@ template-kit theme --all    # generate every template's theme.css
 `theme` compiles a template's `theme.ts` into `templates/<key>/theme.css` — the file your
 Tailwind entry imports. The output is generated: don't hand-edit it, and re-run the
 command whenever `theme.ts` changes. Full contract:
-**[docs/theme-and-css.md](docs/theme-and-css.md#generating-themecss)**.
+**[guide/theme-and-css.md](guide/theme-and-css.md#generating-themecss)**.
 
 ## Previewing a workspace
 
@@ -152,7 +158,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: **[docs/dev.md](docs/dev.md)**.
+shipped by the kit. Full contract: **[guide/dev.md](guide/dev.md)**.
 
 ## Checking a workspace
 
@@ -167,7 +173,7 @@ contracts, runs a determinism render probe, and enforces per-section byte budget
 plus workspace-wide dependency gates (lockfile health, a single React, license and
 vulnerability checks) evaluated once per run. It exits non-zero on any failure and is
 the same gate the platform re-runs when you submit a template. Full contract:
-**[docs/check.md](docs/check.md)**.
+**[guide/check.md](guide/check.md)**.
 
 ## Development
 
@@ -199,9 +205,13 @@ token anywhere, and adding one would silently disable OIDC.
    ```bash
    npm run changeset
    ```
-   Pick the bump (patch / minor / major) and write a human-readable summary —
-   it becomes the changelog entry that template authors read. Commit the
-   generated file in `.changeset/`.
+   The kit is pre-1.0, so **minor is the breaking axis** — everything
+   non-breaking, features and fixes alike, is a **patch**. Never pick major
+   while 0.x: changesets offers it in its prompt, but taking it cuts 1.0.0, a
+   deliberate decision with its own issue, never a side effect of a
+   changeset. Write a human-readable summary — it becomes the changelog
+   entry that template authors read. Commit the generated file in
+   `.changeset/`.
 
 2. **Merge to `main`.** The release workflow opens (or updates) a
    **"Version Packages"** PR that consumes the changeset files, bumps
@@ -210,9 +220,10 @@ token anywhere, and adding one would silently disable OIDC.
 3. **Merge the Version Packages PR.** That merge publishes to npm.
 
 Semver contract: the platform vocabulary (slot types, sources, transforms) is
-closed and versioned. A breaking change to it is a **major**; a new optional
-capability is a **minor**. Design tokens are *not* part of that vocabulary —
-your template names its own.
+closed and versioned, and the kit is pre-1.0, so **minor is the breaking
+axis** — a breaking change to the vocabulary is a **minor**; a new optional
+capability, and any bug fix, is a **patch**. Design tokens are *not* part of
+that vocabulary — your template names its own.
 
 ### Bumping the version by hand
 

package/dist/base.css

@@ -9,7 +9,7 @@
  *   - The cascade-layer order declaration above — the one place it is stated
  *   - The three reset gaps Tailwind's preflight leaves (below)
  *   - The section box model (.tr-section, emitted by the <Section> primitive)
- *   - The <Image> frame's placeholder fill (.tr-image-frame)
+ *   - The <Image>/<Video> frame's placeholder fill (.tr-image-frame)
  *   - Universal tokens: motion
  *
  * REQUIRES A TAILWIND ENTRY ON THE PAGE. Your entry's `@import "tailwindcss"` brings
@@ -55,9 +55,11 @@
   margin: 0;
 }
 
-/* The <Image> frame's placeholder fill, showing while an image is absent or loading.
- * It is a plain class rather than a `bg-*` utility on the primitive because a template
- * names its own tokens — there is no colour token this primitive may assume exists.
+/* The <Image>/<Video> frame's placeholder fill, showing while an asset is absent or
+ * loading. It is a plain class rather than a `bg-*` utility on the primitive because a
+ * template names its own tokens — there is no colour token these primitives may assume
+ * exists. Both frames share this one class (and one token) deliberately: the fill is the
+ * same neutral rect, so a template retints it once.
  * Retint it by setting --tr-image-frame-bg in your theme's layout tokens. */
 .tr-image-frame {
   background-color: var(--tr-image-frame-bg, oklch(0.97 0 0));

package/dist/cli/dev/fill-state.js

@@ -3,13 +3,15 @@ const LIST_TYPES = /* @__PURE__ */ new Set([
 	"list",
 	"poi_list",
 	"image_collection",
+	"video_collection",
 	"object_list"
 ]);
+const ASSET_TYPES = /* @__PURE__ */ new Set(["image", "video"]);
 /** Whether a resolved slot value carries real content for its type. */
 function slotHasContent(value, type) {
 	if (value === null || value === void 0) return false;
 	if (LIST_TYPES.has(type)) return Array.isArray(value) && value.length > 0;
-	if (type === "image") return typeof value === "object" && Boolean(value.url);
+	if (ASSET_TYPES.has(type)) return typeof value === "object" && Boolean(value.url);
 	if (typeof value === "string") return value.trim().length > 0;
 	return true;
 }
@@ -44,9 +46,9 @@ function truncate(s, n = 80) {
 }
 function valuePreview(value, type) {
 	if (LIST_TYPES.has(type)) return Array.isArray(value) ? `[${value.length} items]` : void 0;
-	if (type === "image") {
+	if (ASSET_TYPES.has(type)) {
 		const url = value?.url;
-		return url ? `image:${truncate(url)}` : void 0;
+		return url ? `${type}:${truncate(url)}` : void 0;
 	}
 	if (typeof value === "string") return truncate(value);
 	if (typeof value === "number" || typeof value === "boolean") return String(value);

package/dist/cli/link/overlay.js

@@ -7,7 +7,7 @@ const KIT_PKG_SUBPATH = join("node_modules", "@homepages", "template-kit");
 const LINK_MARKER_NAME = ".template-kit-link.json";
 const PUBLISHABLE = [
 	"dist",
-	"docs",
+	"guide",
 	"package.json",
 	"tsconfig.json",
 	"tsconfig.base.json",

package/dist/cli/new/scaffold/template/sections/hero/fixtures.ts

@@ -1,17 +1,17 @@
 import type { FixtureModule } from "@homepages/template-kit";
-import { allPhotos, mkResponsive } from "@homepages/template-kit/fixtures";
+import { luxuryMultiUnit, mkResponsive } 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
 // needed for it. Add a `states` entry only for a designed scenario that
 // combines overrides at once (a content-length or option branch the section
 // renders differently).
-const heroImage = allPhotos[19]!; // exterior facade shot
+const heroImage = luxuryMultiUnit.photos[19]!; // exterior facade shot
 
 const fixtures: FixtureModule = {
   base: {
     slots: {
-      headline: "101 Queensway, Jamaica Plain, MA 02130",
+      headline: luxuryMultiUnit.facts.address,
       hero_image: {
         photo_id: heroImage.id,
         url: heroImage.url,
@@ -19,7 +19,7 @@ const fixtures: FixtureModule = {
         // Height set to a 16:9 ratio to match the slot's locked crop.
         responsive: mkResponsive(heroImage.url, 2048, 1152),
       },
-      blurb: "A bright corner home moments from the Emerald Necklace.",
+      blurb: "A 12-unit mansard Victorian in Jamaica Plain, moments from the Emerald Necklace.",
     },
     options: { align: "center" },
   },
@@ -30,9 +30,9 @@ const fixtures: FixtureModule = {
     "long-blurb": {
       slots: {
         blurb:
-          "A bright corner home moments from the Emerald Necklace, with a chef's " +
-          "kitchen, three sun-filled bedrooms, off-street parking, and a landscaped " +
-          "yard that backs onto a quiet dead-end street perfect for morning coffee.",
+          "A 12-unit mansard Victorian in Jamaica Plain, with a terrazzo lobby, an " +
+          "on-site gym, quartz kitchens throughout, and a top-floor penthouse with a " +
+          "private rooftop terrace and skyline views — all moments from the Emerald Necklace.",
       },
     },
   },

package/dist/contracts/slot-catalog.d.ts

@@ -1,7 +1,7 @@
 //#region src/contracts/slot-catalog.d.ts
-declare const CONTENT_SLOT_TYPES: readonly ["text", "number", "select", "image", "image_collection", "list", "object_list", "poi_list", "url"];
+declare const CONTENT_SLOT_TYPES: readonly ["text", "number", "select", "image", "image_collection", "list", "object_list", "poi_list", "url", "video", "video_collection"];
 declare const REF_SLOT_TYPES: readonly [];
-declare const SLOT_TYPES: readonly ["text", "number", "select", "image", "image_collection", "list", "object_list", "poi_list", "url"];
+declare const SLOT_TYPES: readonly ["text", "number", "select", "image", "image_collection", "list", "object_list", "poi_list", "url", "video", "video_collection"];
 type ContentSlotType = (typeof CONTENT_SLOT_TYPES)[number];
 type RefSlotType = (typeof REF_SLOT_TYPES)[number];
 type SlotType = (typeof SLOT_TYPES)[number];

package/dist/contracts/slot-catalog.js

@@ -8,7 +8,9 @@ const CONTENT_SLOT_TYPES = [
 	"list",
 	"object_list",
 	"poi_list",
-	"url"
+	"url",
+	"video",
+	"video_collection"
 ];
 const REF_SLOT_TYPES = [];
 const SLOT_TYPES = [...CONTENT_SLOT_TYPES, ...REF_SLOT_TYPES];

package/dist/eslint/rules/no-raw-element.js

@@ -3,13 +3,14 @@ import { docsPathForRule } from "../../rules/registry.js";
 //#region src/eslint/rules/no-raw-element.ts
 const FORBIDDEN = {
 	section: "<Section>",
-	img: "<Image>"
+	img: "<Image>",
+	video: "<Video>"
 };
 const noRawElement = {
 	meta: {
 		type: "problem",
 		docs: {
-			description: "Ban raw <section> and <img> in section JSX",
+			description: "Ban raw <section>, <img> and <video> in section JSX",
 			url: docsPathForRule("no-raw-element")
 		},
 		schema: [],

package/dist/fixtures/helpers.d.ts

@@ -0,0 +1,23 @@
+import { ContactFixture, PoiFixture } from "./sample-property.js";
+import { Scenario } from "./scenario.js";
+//#region src/fixtures/helpers.d.ts
+declare function primaryContact(s: Scenario): ContactFixture;
+declare function contactCards(s: Scenario): ContactFixture[];
+declare function poisByCategory(s: Scenario): Record<PoiFixture["category"], PoiFixture[]>;
+type PropertyMetrics = {
+  beds: number | null;
+  baths: number | null;
+  sqft: number | null;
+  price: string | null;
+  bedsMin: string | null;
+  bedsMax: string | null;
+  bathsMin: string | null;
+  bathsMax: string | null;
+  sqftMax: string | null;
+  priceStart: string | null;
+  addressLine1: string;
+  addressLine2: string;
+};
+declare function propertyMetrics(s: Scenario): PropertyMetrics;
+//#endregion
+export { PropertyMetrics, contactCards, poisByCategory, primaryContact, propertyMetrics };

package/dist/fixtures/helpers.js

@@ -0,0 +1,50 @@
+import { TRANSFORMS } from "../contracts/transforms.js";
+
+//#region src/fixtures/helpers.ts
+const POI_CATEGORIES = [
+	"restaurant",
+	"park",
+	"transit",
+	"shopping",
+	"coffee",
+	"fitness"
+];
+function primaryContact(s) {
+	const first = s.contacts[0];
+	if (!first) throw new Error(`scenario ${s.key} has no contacts`);
+	return first;
+}
+function contactCards(s) {
+	return s.contacts;
+}
+function poisByCategory(s) {
+	const out = Object.fromEntries(POI_CATEGORIES.map((c) => [c, []]));
+	for (const poi of s.pois) out[poi.category].push(poi);
+	return out;
+}
+function propertyMetrics(s) {
+	const units = s.facts.units;
+	const lines = s.facts.address_lines ?? [s.facts.address, ""];
+	const primary = [...units].sort((a, b) => a.position - b.position)[0] ?? null;
+	const fmt = (name) => {
+		const v = TRANSFORMS[name].impl({ units });
+		return v == null ? null : String(v);
+	};
+	return {
+		beds: primary?.beds ?? null,
+		baths: primary?.baths ?? null,
+		sqft: primary?.sqft ?? null,
+		price: primary?.price ?? null,
+		bedsMin: fmt("units.bedsMin"),
+		bedsMax: fmt("units.bedsMax"),
+		bathsMin: fmt("units.bathsMin"),
+		bathsMax: fmt("units.bathsMax"),
+		sqftMax: fmt("units.sqftMax"),
+		priceStart: fmt("units.priceStart"),
+		addressLine1: lines[0] ?? "",
+		addressLine2: lines[1] ?? ""
+	};
+}
+
+//#endregion
+export { contactCards, poisByCategory, primaryContact, propertyMetrics };

package/dist/fixtures/sample-property.d.ts

@@ -1,5 +1,4 @@
 import { ResponsiveImage } from "../contracts/image-descriptor.js";
-import { PropertyFacts } from "../schema/property-facts.js";
 //#region src/fixtures/sample-property.d.ts
 type PhotoFixture = {
   id: string;
@@ -10,18 +9,19 @@ type PhotoFixture = {
     category?: string;
   };
 };
-declare const allPhotos: PhotoFixture[];
 declare function mkResponsive(url: string, width: number, height: number): ResponsiveImage;
 type PoiFixture = {
   id: string;
   category: "restaurant" | "park" | "transit" | "shopping" | "coffee" | "fitness";
   name: string;
+  place_id: string;
+  address: string;
   distance: string;
+  distance_m: number;
   lat: number;
   lng: number;
   url: string;
 };
-declare const samplePois: PoiFixture[];
 type ContactFixture = {
   library_item_id: string;
   category: "contact";
@@ -36,13 +36,15 @@ type ContactFixture = {
     email: string;
     phone: string;
     address: string;
+    org_name: string;
+    logo_light: string | null;
+    logo_dark: string | null;
     socials: Array<{
       platform: "instagram" | "linkedin" | "x" | "facebook";
       url: string;
     }>;
   };
 };
-declare const sampleContacts: ContactFixture[];
 type AmenityItem = {
   id: string;
   label: string;
@@ -51,17 +53,5 @@ type AmenityItem = {
   description: string;
   items: string[];
 };
-declare const sampleAmenities: AmenityItem[];
-declare const sampleProperty: PropertyFacts;
-declare const sampleHeroSlots: {
-  readonly headline: "A mansard victorian single-family home in the heart of Jamaica Plain";
-  readonly hero_image: {
-    readonly photo_id: string;
-    readonly url: string;
-    readonly alt: string;
-  };
-  readonly brand_logo: null;
-  readonly listing_status: "for_sale";
-};
 //#endregion
-export { AmenityItem, ContactFixture, PhotoFixture, PoiFixture, allPhotos, mkResponsive, sampleAmenities, sampleContacts, sampleHeroSlots, samplePois, sampleProperty };
+export { AmenityItem, ContactFixture, PhotoFixture, PoiFixture, mkResponsive };