@homepages/template-kit 0.6.0-dev-20260717012648 → 0.7.0-dev-20260717151640

package/CHANGELOG.md

@@ -1,6 +1,54 @@
 # @homepages/template-kit
 
-## 0.6.0-dev-20260717012648
+## 0.7.0-dev-20260717151640
+
+### Minor Changes
+
+- b55052d: The `luxuryMultiUnit` primary contact now carries a `facebook` social.
+
+  `"facebook"` was in the socials type union but on no fixture contact, so a slot resolving
+  `socials.find((s) => s.platform === "facebook")?.url ?? null` returned `null` in every
+  fixture of every scenario. Its populated branch rendered nowhere, and nullability
+  synthesis could not fill the gap from the other side — it nulls slots the base fixture
+  populates, never the reverse, and skips a slot already empty in base. A section could
+  break its Facebook link and every fixture would still look correct.
+
+  Okane Marketing's James Donovan (`luxuryMultiUnit`'s primary contact) now carries
+  `facebook` alongside `instagram`, `linkedin`, and `x`, so all four platforms behave
+  alike: populated in base, nulled by synthesis. Breadth belongs to the richest scenario's
+  primary contact by design — the other five contacts keep partial social sets, so sections
+  still render thin social rows.
+
+  Snapshots will show the diff wherever a fixture resolves a facebook slot off that contact
+  — it moves from `null` to `"https://facebook.com/okanemarketing/"`. Any assertion
+  expecting that slot to be null needs updating; a section that gates on the value now
+  renders its populated branch.
+
+### Patch Changes
+
+- e5b447f: Fill-specs can now declare `video-assign` and `video-collection` decisions.
+
+  The `video` and `video_collection` slot types have had nothing able to fill them: AI
+  fill could pool photos but not videos. These two decisions mirror `image-assign` and
+  `image-collection`, pooling from `property_facts.videos[]` instead of `photos[]` — a
+  video is picked by tags, caption, and duration, the same text-only contract as images
+  (no bytes ever reach the selection model).
+
+  ```ts
+  { id: "hero_video", type: "video-assign", tag_query: "exterior",
+    selection_prompt: "The most cinematic establishing shot.", produces: ["video"] }
+  ```
+
+  Both accept an optional `tag_query` (omit to pool across every video) and a
+  `selection_prompt`; `video-collection` adds `count: { min, max }` and produces one
+  ordered array slot. Two fields from the image side are deliberately absent:
+  `from_fact` (no fact names a video upload — videos only reach a slot by selection)
+  and `mode: "walkthrough"` (sequencing a room-by-room tour presumes a photo-sized
+  pool). Neither implements `source_filter`.
+
+  Additive: existing fill-specs are unaffected.
+
+## 0.6.0
 
 ### Minor Changes
 

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

@@ -229,7 +229,7 @@ declare function collectionForSlot(slot: {
 }): CollectionField | null;
 declare const DERIVED_INPUT_FIELDS: readonly ["units", "address_line_parts", "contact_address_parts", "coordinates", "clock"];
 type DerivedInputName = (typeof DERIVED_INPUT_FIELDS)[number];
-declare const DECISION_TYPES: readonly ["image-assign", "image-collection", "text-block", "text-seed", "list-extract", "structured-list"];
+declare const DECISION_TYPES: readonly ["image-assign", "image-collection", "video-assign", "video-collection", "text-block", "text-seed", "list-extract", "structured-list"];
 type DecisionType = (typeof DECISION_TYPES)[number];
 declare const FORMATTER_NAMES: readonly ["currency", "number"];
 type FormatterName = (typeof FORMATTER_NAMES)[number];

package/dist/contracts/slot-catalog.js

@@ -238,6 +238,8 @@ const DERIVED_INPUT_FIELDS = [
 const DECISION_TYPES = [
 	"image-assign",
 	"image-collection",
+	"video-assign",
+	"video-collection",
 	"text-block",
 	"text-seed",
 	"list-extract",

package/dist/fixtures/sample-property.js

@@ -665,6 +665,10 @@ const sampleContacts = [
 				{
 					platform: "x",
 					url: "https://x.com/okanemarketing"
+				},
+				{
+					platform: "facebook",
+					url: "https://facebook.com/okanemarketing/"
 				}
 			]
 		}

package/dist/package.js

@@ -1,5 +1,5 @@
 //#region package.json
-var version = "0.6.0-dev-20260717012648";
+var version = "0.7.0-dev-20260717151640";
 
 //#endregion
 export { version };

package/dist/schema/fill-spec.d.ts

@@ -21,6 +21,22 @@ declare const Decision: z.ZodDiscriminatedUnion<[z.ZodObject<{
   }, z.core.$strict>>;
   selection_prompt: z.ZodString;
   produces: z.ZodArray<z.ZodString>;
+}, z.core.$strict>, z.ZodObject<{
+  id: z.ZodString;
+  type: z.ZodLiteral<"video-assign">;
+  tag_query: z.ZodOptional<z.ZodString>;
+  selection_prompt: z.ZodOptional<z.ZodString>;
+  produces: z.ZodArray<z.ZodString>;
+}, z.core.$strict>, z.ZodObject<{
+  id: z.ZodString;
+  type: z.ZodLiteral<"video-collection">;
+  tag_query: z.ZodOptional<z.ZodString>;
+  count: z.ZodOptional<z.ZodObject<{
+    min: z.ZodNumber;
+    max: z.ZodNumber;
+  }, z.core.$strict>>;
+  selection_prompt: z.ZodString;
+  produces: z.ZodArray<z.ZodString>;
 }, z.core.$strict>, z.ZodObject<{
   id: z.ZodString;
   type: z.ZodLiteral<"text-block">;
@@ -110,6 +126,22 @@ declare const FillSpec: z.ZodObject<{
     }, z.core.$strict>>;
     selection_prompt: z.ZodString;
     produces: z.ZodArray<z.ZodString>;
+  }, z.core.$strict>, z.ZodObject<{
+    id: z.ZodString;
+    type: z.ZodLiteral<"video-assign">;
+    tag_query: z.ZodOptional<z.ZodString>;
+    selection_prompt: z.ZodOptional<z.ZodString>;
+    produces: z.ZodArray<z.ZodString>;
+  }, z.core.$strict>, z.ZodObject<{
+    id: z.ZodString;
+    type: z.ZodLiteral<"video-collection">;
+    tag_query: z.ZodOptional<z.ZodString>;
+    count: z.ZodOptional<z.ZodObject<{
+      min: z.ZodNumber;
+      max: z.ZodNumber;
+    }, z.core.$strict>>;
+    selection_prompt: z.ZodString;
+    produces: z.ZodArray<z.ZodString>;
   }, z.core.$strict>, z.ZodObject<{
     id: z.ZodString;
     type: z.ZodLiteral<"text-block">;

package/dist/schema/fill-spec.js

@@ -22,6 +22,24 @@ const ImageCollectionDecision = z.object({
 	selection_prompt: z.string(),
 	produces: z.array(z.string()).min(1)
 }).strict();
+const VideoAssignDecision = z.object({
+	id: z.string(),
+	type: z.literal("video-assign"),
+	tag_query: z.string().optional(),
+	selection_prompt: z.string().optional(),
+	produces: z.array(z.string()).min(1)
+}).strict();
+const VideoCollectionDecision = z.object({
+	id: z.string(),
+	type: z.literal("video-collection"),
+	tag_query: z.string().optional(),
+	count: z.object({
+		min: z.number().int().nonnegative(),
+		max: z.number().int().positive()
+	}).strict().optional(),
+	selection_prompt: z.string(),
+	produces: z.array(z.string()).min(1)
+}).strict();
 const TextBlockDecision = z.object({
 	id: z.string(),
 	type: z.literal("text-block"),
@@ -84,6 +102,8 @@ const StructuredListDecision = z.object({
 const Decision = z.discriminatedUnion("type", [
 	ImageAssignDecision,
 	ImageCollectionDecision,
+	VideoAssignDecision,
+	VideoCollectionDecision,
 	TextBlockDecision,
 	TextSeedDecision,
 	ListExtractDecision,

package/guide/recipes/collection-slot.md

@@ -2,7 +2,7 @@
 purpose: Add a repeating list whose items the editor selects and edits one at a time.
 status: living
 related: [../primitives.md, ../vocabulary.md, ../schema-system.md, bind-property-fact.md, pick-a-scenario.md]
-updated: 2026-07-16
+updated: 2026-07-17
 ---
 # A collection slot — a repeating, per-item list
 
@@ -96,7 +96,7 @@ Verify with [the author loop](../quickstart.md#the-author-loop).
   (`object_list` / `image_collection` / `video_collection` / `poi_list` / `list`) and the
   `direct()` List sources.
 - [The schema system](../schema-system.md#fill-spects--how-ai-fills-the-slots) — the
-  `produced_by` decision types (`structured-list`, `list-extract`, `image-collection`)
-  for a collection AI fills instead of binding to a fact.
+  `produced_by` decision types (`structured-list`, `list-extract`, `image-collection`,
+  `video-collection`) for a collection AI fills instead of binding to a fact.
 - [Bind a slot to a property fact](bind-property-fact.md) — the `direct()` pattern this
   extends from a scalar to a whole array.

package/guide/recipes/fill-spec-decision.md

@@ -2,7 +2,7 @@
 purpose: Have AI write a slot's content.
 status: living
 related: [../schema-system.md]
-updated: 2026-07-15
+updated: 2026-07-17
 ---
 # Have AI write a slot's content
 
@@ -44,12 +44,14 @@ summary: {
 },
 ```
 
-`text-block` is one of several decision types — the others include
-`image-assign`, `image-collection`, `text-seed`, `list-extract`, and
-`structured-list`, each producing a differently-shaped slot value. This
-recipe covers the common text case; see [the schema
+`text-block` is one of several decision types — the others are `image-assign`,
+`image-collection`, `video-assign`, `video-collection`, `text-seed`,
+`list-extract`, and `structured-list`, each producing a differently-shaped slot
+value. This recipe covers the common text case; see [the schema
 system](../schema-system.md#fill-spects--how-ai-fills-the-slots) for the
-full decision-type contract before reaching for one of the others.
+full decision-type contract before reaching for one of the others, and
+[Video slots](../schema-system.md#video-slots) for what the `video-*` pair
+deliberately does not take.
 
 ## Commands
 

package/guide/rules/determinism-drift.md

@@ -1,8 +1,8 @@
 ---
 purpose: The template-kit/determinism-drift authoring rule — what it enforces, why, and how to fix it.
 status: living
-related: [INDEX.md, server-vs-client.md]
-updated: 2026-07-14
+related: [INDEX.md, server-vs-client.md, ../schema-system.md]
+updated: 2026-07-17
 ---
 # template-kit/determinism-drift
 
@@ -18,12 +18,13 @@ The corpus is broader than the fixtures you wrote:
 
 - your **`base`** fixture;
 - each of your **`states`** fixtures;
-- one **synthesized** fixture per **optional** slot, with that slot set to its empty value
-  (`null` for a scalar or an image, `[]` for a list).
+- one **synthesized** fixture per **optional** slot your `base` populates, with that slot
+  set to its empty value (`null` for a scalar or an image, `[]` for a list).
 
 You do not declare that last set. Nullability coverage is derived from the schema — from
 `(type, required)` — so a nullable branch cannot be forgotten by forgetting to write a
-fixture for it.
+fixture for it. It only runs one way, though: a slot your `base` leaves empty is skipped,
+so [`base` should fill every slot it can](../schema-system.md#fixturests--content-for-local-preview).
 
 ## Reason
 

package/guide/rules/render-invariant.md

@@ -2,7 +2,7 @@
 purpose: The template-kit/render-invariant authoring rule — what it enforces, why, and how to fix it.
 status: living
 related: [INDEX.md, ../primitives.md, ../schema-system.md]
-updated: 2026-07-16
+updated: 2026-07-17
 ---
 # template-kit/render-invariant
 
@@ -21,8 +21,9 @@ output is checked for three defects:
 3. **An `<img>` whose `src` is absent, empty, `"undefined"`, or `"null"`.**
 
 The corpus is your `base` fixture, each of your `states` fixtures, and one **synthesized**
-fixture per optional slot with that slot set to its empty value (`null` for a scalar or an
-image, `[]` for a list) — derived from the schema, not declared by you.
+fixture per optional slot **your `base` populates**, with that slot set to its empty value
+(`null` for a scalar or an image, `[]` for a list) — derived from the schema, not declared
+by you. A slot already empty in `base` is skipped, having no filled branch to null.
 
 The check is deliberately biased toward **false negatives**: it would rather miss a bug than
 invent one. Everything it reports is a real defect, so there is nothing here to argue with

package/guide/schema-system.md

@@ -2,7 +2,7 @@
 purpose: The section authoring contract — schema.ts, fill-spec.ts, fixtures.ts, and the closed source/transform vocabulary.
 status: living
 related: [primitives.md, theme-and-css.md, vocabulary.md, recipes/pick-a-scenario.md]
-updated: 2026-07-16
+updated: 2026-07-17
 ---
 # The schema system
 
@@ -110,6 +110,21 @@ single progressive MP4 rendition — there is no `responsive` ladder and no `mob
 to pass along, unlike an image. Read `url`, `poster`, `alt`, and the intrinsic
 `width`/`height`, and hand them to `Video`.
 
+AI fills a `video` slot with a `video-assign` decision and a `video_collection` with
+`video-collection` — the video twins of `image-assign` / `image-collection`, pooling the
+property's videos rather than its photos. They are separate decision types rather than a
+filter on the image ones so a decision's candidate pool is legible from its `type` alone.
+Both take an optional `tag_query` (omit it to pool across every video) and a
+`selection_prompt`; selection reads only text — tags, caption, duration — never the video
+itself. Two fields the image side has are absent by design:
+
+- **No `from_fact`.** Nothing in the [closed vocabulary](vocabulary.md#direct-sources)
+  names a video upload the way `headshot` names an image one, so a video reaches a slot
+  only by selection.
+- **No `mode`.** The photo side's `walkthrough` sequences every photo into a room-by-room
+  tour, which presumes a pool large enough to order; a property carries a handful of
+  videos.
+
 ### Grouping slots into one editor card
 
 `meta.groups` collapses several slots into a single card in the editor sidebar. Each
@@ -201,8 +216,14 @@ export const fillSpec = {
 
 ## `fixtures.ts` — content for local preview
 
-`base` is one fully-specified baseline: every required slot, with a real value.
-`states` adds named states, each overriding part of it — use them for the
+`base` is one fully-specified baseline: every required slot with a real value —
+and every optional slot the scenario can plausibly fill, too. Coverage runs one
+way: the checks synthesize an empty fixture for each optional slot your `base`
+populates, but nothing populates a slot your `base` leaves empty. A slot empty
+in `base` has its filled branch rendered by no fixture at all, so a section can
+break that branch with every check green.
+
+`states` adds named states, each overriding part of `base` — use them for the
 structural cases your section is designed to handle (a missing logo, a long
 headline, an empty list).
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@homepages/template-kit",
-  "version": "0.6.0-dev-20260717012648",
+  "version": "0.7.0-dev-20260717151640",
   "description": "Authoring kit for HomePages marketing-section templates: schema system, contract primitives, theme tokens, and the template-kit CLI.",
   "license": "UNLICENSED",
   "type": "module",
@@ -74,6 +74,7 @@
     "check": "npm run typecheck && npm run lint && npm run build && npm run size:islands && npm run test && npm run lint:pkg && npm run verify:consumer && npm run check:scaffolder",
     "check:scaffolder": "npm run typecheck -w create-homepages-workspace && npm run build -w create-homepages-workspace && npm run test -w create-homepages-workspace",
     "changeset": "changeset",
+    "version": "changeset version && npm install --package-lock-only",
     "release": "changeset publish"
   },
   "peerDependencies": {