camox 0.71.0 → 0.72.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "camox",
-  "version": "0.71.0",
+  "version": "0.72.0",
   "license": "MIT",
   "bin": {
     "camox": "./bin/camox.mjs"
@@ -148,9 +148,9 @@
     "unhead": "^3.4.3",
     "yaml": "^2.9.0",
     "zod": "^4.6.7",
-    "@camox/api-contract": "0.71.0",
-    "@camox/cli": "0.71.0",
-    "@camox/ui": "0.71.0"
+    "@camox/ui": "0.72.0",
+    "@camox/api-contract": "0.72.0",
+    "@camox/cli": "0.72.0"
   },
   "devDependencies": {
     "@earendil-works/pi-ai": "1.3.0",

package/skills/camox/SKILL.md

@@ -45,6 +45,6 @@ Use the platform. Build tabs, dialogs, carousels, menus and disclosures from nat
 
 ## Content
 
-Code definitions do not place blocks on existing Pages or assign their layouts; `blocks.initial` only seeds the initial homepage. When the request includes placement or assignment on existing Pages, make it as a content change once Camox has discovered the new definition. Singleton pages and derived routes are declared in code, never created as Pages.
+Code definitions do not place blocks on Pages, assign layouts, or write content. When the request includes placement, assignment, or content, make it as a content change once Camox has discovered the new definition. Singleton pages and derived routes are declared in code, never created as Pages.
 
 A request can cross boundaries. Load an additional reference only once that need is established.

package/skills/camox/references/artifacts.md

@@ -12,23 +12,23 @@ A definition that would fit one place on one site, or settings bolted on only to
 
 ```tsx
 content: (field) => ({
-  heading: field.string({ default: "How it works" }),
+  heading: field.string({ title: "Heading" }),
   visual: field.artifact({ size: "fill", title: "Diagram" }),
 }),
 ```
 
 - `size` (required): `"fill"` fills a container whose size the block controls, for example with an aspect ratio; `"content"` is for frames whose height follows their page, such as calculators. See [Size to the content](#size-to-the-content).
 - `data` (optional): sibling content fields and settings shared with the artifact as **Artifact Data**, so editors can change what it shows without touching its source. Inside a repeater item, the siblings are the item's own fields and settings. The names are type-checked; artifacts, repeaters and references can't be listed. See [`camox.data`](#camoxdata).
-- `default` (optional): a starting source. Leave it out; agents write sources as content. An empty artifact renders nothing on the website and a placeholder in the studio preview.
+- Agents write sources as content, never in the definition. An empty artifact renders nothing on the website and a placeholder in the studio preview.
 - Artifacts work in block content and repeater items, so also in layout and synced blocks. Collection records can't hold them.
 
 ```tsx
 content: (field) => ({
-  label: field.string({ default: "Uptime" }),
+  label: field.string({ title: "Label" }),
   gauge: field.artifact({ size: "fill", data: ["label", "tone"] }),
 }),
 settings: (setting) => ({
-  tone: setting.enum({ default: "calm", options: { calm: "Calm", bold: "Bold" } }),
+  tone: setting.enum({ options: { calm: "Calm", bold: "Bold" } }),
 }),
 ```
 

package/skills/camox/references/block-definitions.md

@@ -16,7 +16,7 @@ const myBlock = createBlock({
   title: "My Block",
   description: "A page introduction with an editable heading.",
   content: (field) => ({
-    title: field.string({ default: "Welcome" }),
+    title: field.string({ title: "Title" }),
   }),
   toReact: MyBlockComponent,
   toTitle: ({ content }) => content.title,
@@ -45,7 +45,7 @@ For DOM listeners, scrolling, scripts, widgets, or JavaScript-driven animation,
 | `description`      | yes      | Agent guidance on placement, expected content, and tone.                                       |
 | `content`          | yes      | `(field) => ({ ... })`: field names mapped to `field.*` builders for editable content.         |
 | `settings`         | no       | `(setting) => ({ ... })`: settings-panel options; only `setting.enum` and `setting.boolean`.   |
-| `layoutOnly`       | no       | If true, restricts placement to layouts and hides the type from the add-block picker.          |
+| `layoutOnly`       | no       | If true, restricts placement to layouts.                                                       |
 | `synced`           | no       | Defaults to false. Shares content/settings across placements; see below.                       |
 | `toReact`          | yes      | Named React function component. Receives `{ content, settings }` as props.                     |
 | `toTitle`          | yes      | `({ content, settings }) => ...` one-line title; see below.                                    |
@@ -58,7 +58,7 @@ For DOM listeners, scrolling, scripts, widgets, or JavaScript-driven animation,
 
 For shared navbar/footer data across layouts, use `layoutOnly: true, synced: true`. These flags are independent: synced blocks can also be ordinary page-content blocks.
 
-- Editing any placement updates the shared content everywhere. New placements reuse existing data rather than resetting to defaults.
+- Editing any placement updates the shared content everywhere. New placements reuse the shared content.
 - Position, layout slot, and deletion remain per placement; deleting one placement leaves the others.
 - Enabling syncing on an existing type applies the oldest placement's data to all placements. Disabling it leaves independently editable copies.
 
@@ -119,7 +119,9 @@ Only Boolean/Enum settings support these conditionals. A repeater's `settings` r
 
 ## Content Field Types
 
-`content` and a repeater's `content` receive a `field` builder; `settings` receive a `setting` builder. Each builder only offers what its context accepts: `field` has no `enum` or `boolean`, and `setting` has nothing else. Supply defaults for scalar fields; images/files get automatic placeholders (empty images paint with the stylesheet's `--camox-placeholder` and `--camox-placeholder-ink`), lists use `defaultItems`, and repeaters use their item schemas and bounds.
+`content` and a repeater's `content` receive a `field` builder; `settings` receive a `setting` builder. Each builder only offers what its context accepts: `field` has no `enum` or `boolean`, and `setting` has nothing else.
+
+A definition declares a block's shape, never its content: the agent writes every field's content when it places the block. A field nobody has written reads as the empty value of its kind: `""` for strings, embeds, icons and artifacts, an empty link, `null` for an image, file or reference, no items for lists and repeaters, `false` for a boolean setting, and an enum setting's first option. So render well with any content, including empty optional fields: a short or long title, a missing subtitle, one repeatable item or many. An empty image paints Camox's placeholder with the stylesheet's `--camox-placeholder` and `--camox-placeholder-ink`; an empty file, image list or file list renders nothing.
 
 ### field.string
 
@@ -127,7 +129,6 @@ Inline-editable text supporting formatting and links while remaining a string. S
 
 ```tsx
 field.string({
-  default: "Hello world",
   title: "Heading", // Optional label
   maxLength: 280, // Optional
   minLength: 1, // Optional
@@ -143,34 +144,33 @@ Choose one Iconify collection in Vite config:
 camox({ projectId: "01a15fff-627b-7fa1-938b-93ab659c1acc", icons: "lucide" });
 ```
 
-Declare a non-nullable icon with a required, prefixed default, then render inline SVG:
+Declare an icon field, then render inline SVG:
 
 ```tsx
 // In content:
-icon: field.icon({ default: "lucide:zap", title: "Icon" })
+icon: field.icon({ title: "Icon" })
 
 // In the component (also supported as <item.Icon> inside repeaters):
 <block.Icon name="icon" className="size-6 text-brand" />
 <block.Icon name="icon" aria-label="Fast" />
 ```
 
-Icons are decorative unless given `aria-label` or `aria-labelledby`. Clicking an icon in preview opens the searchable collection picker. Values remain namespaced strings; editors cannot select another collection or an empty value.
+Icons are decorative unless given `aria-label` or `aria-labelledby`. Clicking an icon in preview opens the searchable collection picker. Values are namespaced strings such as `"lucide:zap"`; editors cannot select another collection or clear the icon.
 
 Run `pnpm exec camox typegen` **before TypeScript checking in CI**, for example `camox typegen && tsc --noEmit`. This resolves Vite config without starting a server. It generates `src/camox/icons.gen.d.ts`; ensure your tsconfig includes it. Dev and build regenerate it automatically. Generation requires network access to the pinned Iconify snapshot.
 
-Camox resolves selected SVGs from that same versioned snapshot and serves them through its API. Server rendering preloads selected/default SVGs into hydration data; no visitor requests to Iconify and no rebuild is needed when content changes. Only the editor fetches collection metadata and picker previews, not a whole SVG catalog.
+Camox resolves selected SVGs from that same versioned snapshot and serves them through its API. Server rendering preloads selected SVGs into hydration data; no visitor requests to Iconify and no rebuild is needed when content changes. Only the editor fetches collection metadata and picker previews, not a whole SVG catalog.
 
 Collection licenses still apply. SVG responses retain author/license attribution. Include any copyright notices, license text, or attribution required by your chosen collection in your site's distributed notices; Iconify does not relicense the icons. Changing collections or migrating existing icon values is not supported in v1.
 
 ### setting.boolean and setting.enum
 
-Settings only: configuration choices are never block or repeater content. Enum defaults must match an option key.
+Settings only: configuration choices are never block or repeater content. An unset enum reads as its first option, so list the most common or neutral one first. An unset boolean reads as `false`, so name it for what turning it on does (`showBackground`, not `hideBackground`).
 
 ```tsx
 settings: (setting) => ({
-  showBackground: setting.boolean({ default: false, title: "Show background" }),
+  showBackground: setting.boolean({ title: "Show background" }),
   alignment: setting.enum({
-  default: "left",
     options: { left: "Left", center: "Center", right: "Right" },
     title: "Alignment",
   }),
@@ -182,10 +182,7 @@ settings: (setting) => ({
 Text, destination, and new-tab toggle. Curated page links store page IDs; singleton links store fixed URLs using the existing `type: "external"` representation, which also supports site-relative URLs: `{ type: "external", href: "/pokedex", text: "Pokédex", newTab: false }`. Both page kinds appear in Studio's destination picker. Inline `[Pokédex](/pokedex)` links stay in the current tab.
 
 ```tsx
-field.link({
-  default: { text: "Learn more", href: "/", newTab: false },
-  title: "CTA",
-});
+field.link({ title: "CTA" });
 ```
 
 ### Images and files
@@ -194,19 +191,18 @@ Files support MIME filtering. Render each type with its matching helper; asset l
 
 ```tsx
 field.image({ title: "Cover photo" });
-field.imageList({ defaultItems: 6, title: "Gallery images" });
+field.imageList({ title: "Gallery images" });
 field.file({ accept: ["application/pdf"], title: "PDF Document" });
-field.fileList({ accept: ["application/pdf"], defaultItems: 0, title: "Documents" });
+field.fileList({ accept: ["application/pdf"], title: "Documents" });
 ```
 
 ### field.embed
 
-A URL validated against a regex. A nonmatching default throws at definition time.
+A URL validated against a regex. Content that doesn't match is rejected.
 
 ```tsx
 field.embed({
   pattern: "https:\\/\\/(www\\.)?(youtube\\.com|youtu\\.be)\\/.+",
-  default: "https://www.youtube.com/watch?v=dQw4w9WgXcQ",
   title: "YouTube URL",
 });
 ```
@@ -222,16 +218,16 @@ field.artifact({ size: "fill", data: ["headline", "variant"] }); // shares sibli
 
 ### field.repeater
 
-Structured items with their own content, optional settings, and required `toTitle` and `toMarkdown`. `minItems` must be at least 1; repeaters cannot be empty. Nest repeaters in an item's `content` when needed.
+Structured items with their own content, optional settings, and required `toTitle` and `toMarkdown`. `minItems` must be at least 1: editors can't remove the last item. A block whose repeater was never written has no items, so render well with none. Nest repeaters in an item's `content` when needed.
 
 ```tsx
 field.repeater({
   content: (field) => ({
-    name: field.string({ default: "Feature" }),
-    description: field.string({ default: "Description" }),
+    name: field.string({ title: "Name" }),
+    description: field.string({ title: "Description" }),
   }),
   settings: (setting) => ({
-    highlighted: setting.boolean({ default: false, title: "Highlighted" }),
+    highlighted: setting.boolean({ title: "Highlighted" }),
   }),
   minItems: 1,
   maxItems: 10,
@@ -279,7 +275,7 @@ Place a repeater's token where its items' nodes go, such as an FAQ's questions:
 
 ```tsx
 items: field.repeater({
-  content: (field) => ({ question: field.string({ default: "Why?" }), answer: field.string({ default: "Because" }) }),
+  content: (field) => ({ question: field.string({ title: "Question" }), answer: field.string({ title: "Answer" }) }),
   minItems: 1,
   maxItems: 20,
   toTitle: ({ content }) => content.question,

package/skills/camox/references/dom-integrations.md

@@ -2,7 +2,7 @@
 
 Use this reference for block DOM listeners, scrolling, browser scripts, and third-party widgets. It can be read independently of [Block Definitions](block-definitions.md); read that reference only if also changing the block schema or field rendering API.
 
-**Do not use component-global `window` or `document` to target a block's DOM.** Camox preview (including block thumbnails) renders blocks into an iframe through a React portal, but component code executes in the editor's JavaScript realm. Global scroll listeners observe the editor; scripts appended to the global document load there instead of beside your block.
+**Do not use component-global `window` or `document` to target a block's DOM.** Camox preview renders blocks into an iframe through a React portal, but component code executes in the editor's JavaScript realm. Global scroll listeners observe the editor; scripts appended to the global document load there instead of beside your block.
 
 Use `getElementContext` from `camox/dom` inside an effect or event handler, passing a rendered element. It returns `{ window, document }` from the element's `ownerDocument` and `defaultView`, or `null` for a missing element or a document without a window. It never falls back to globals, requires no provider, and works in regular rendering too. Don't access DOM APIs during SSR.
 

package/skills/camox/references/layout-definitions.md

@@ -23,7 +23,6 @@ const myLayout = createLayout({
   blocks: {
     before: [navbarBlock],
     after: [footerBlock],
-    initial: [() => import("../blocks/hero")],
   },
   toReact: MyLayoutComponent,
   toTitle: ({ page, project }) => `${page.title} | ${project.name}`,
@@ -50,7 +49,7 @@ export { myLayout as layout };
 | `id`               | yes      | Unique kebab-case identifier matching the filename without extension.                                  |
 | `title`            | yes      | CMS display name.                                                                                      |
 | `description`      | yes      | Guidance for users and agents on which pages suit this layout.                                         |
-| `blocks`           | yes      | `before`, `after`, and optional `initial` arrays; see layout slot rules below.                         |
+| `blocks`           | yes      | `before` and `after` arrays; see layout slot rules below.                                              |
 | `toReact`          | yes      | Named function component receiving the context and `{ children }` as props.                            |
 | `toTitle`          | yes      | `(context) => string`: the head title, `og:title`, and the Markdown front matter's `title`.            |
 | `toDescription`    | yes      | `(context) => string \| undefined`: the head description and `og:description`. May return `undefined`. |
@@ -68,20 +67,12 @@ Every `to*` option receives the same context object, and none receives another o
 
 Singleton and derived layouts also receive `data` and `params`, and record pages `content`; see [Routed layouts](routed-layouts.md#metadata-and-markdown).
 
-## Layout Slots — `before`, `after`, and `initial`
+## Layout Slots — `before` and `after`
 
 - `before` and `after` require blocks with `layoutOnly: true`. Either array may be empty.
 - Render groups with `<myLayout.BeforeBlocks />` and `<myLayout.AfterBlocks />`, not individual blocks. Array order controls rendering order; edit the config to add or reorder blocks.
 - For identical navbar/footer content across layouts, also set `synced: true`. `layoutOnly` restricts a block to layout slots; it does not enable syncing. See [Synced blocks](block-definitions.md#synced-blocks-synced-optional) for sharing and existing-placement behavior.
-
-## Initial Blocks — `blocks.initial` (optional)
-
-`initial` seeds the homepage at project creation, using block defaults in array order. It does not populate existing Pages.
-
-- List each block as an import of its module, `() => import("../blocks/hero")`, never a statically imported block. Layouts load on every page, so a static import would ship the block to every visitor.
-- Accepts only blocks with `layoutOnly` omitted or `false`.
-- At most one layout per app may define `initial`; multiple definitions cause a startup error.
-- Without `initial`, Camox seeds an empty homepage using the first curated layout. Apps with only singleton/derived layouts do not seed a curated homepage.
+- A slot's new blocks start with no content when the layout syncs. Fill them as a [content change](../SKILL.md#content) once Camox has discovered the layout.
 
 ## OG Image — `toImage` (optional)
 

package/skills/camox/references/routed-layouts.md

@@ -53,7 +53,7 @@ function PokedexPage() {
 - `loader` is optional. Return `{ kind: "data", data }`, synchronously or asynchronously. `layout.useData()` infers and returns the unwrapped `data`, not the envelope. It runs server-side for document requests and client navigation; the entire envelope travels through JSON to hydration. Keep data JSON-serializable (no functions, symbols, BigInt, or cyclic objects). Without a loader, `useData()` returns `undefined`. The loader also receives `locale`, the page's locale tag; Camox renders its data untranslated (see [Localization](localization.md#loaders)).
 - Before/after blocks must be `layoutOnly: true`. Put editable headings, introductions, and other bespoke content in these blocks; keep structural application UI in the component. See [Block Definitions](block-definitions.md).
 - For a navbar or footer whose content must stay identical across different layouts, also set `synced: true` in its `createBlock` options. `layoutOnly: true` alone only restricts placement. See [Synced blocks](block-definitions.md#synced-blocks-synced-optional) for sharing behavior.
-- No `children` slot or `blocks.initial`: editors do not compose or create these pages.
+- No `children` slot: editors do not compose or create these pages.
 - No curated page record is created. Never create, duplicate, move, or assign a singleton as a Page.
 - Studio lists singletons as directly navigable pages with block editing, without deletion or URL/layout controls. They also appear in link destination pickers (including inline text links), “Go to page” actions, and the runtime sitemap. Derived pages appear in the sitemap only when their layout declares `routes` (see [Route discovery](#route-discovery)).
 - Singleton links are saved as fixed internal URLs, not synthetic database page IDs: link fields use `{ type: "external", href: "/pokedex", text: "Pokédex", newTab: false }` (the existing URL representation), while inline text uses `[Pokédex](/pokedex)`. Renaming a code-owned URL requires updating links or adding a redirect. Curated-page links retain their page-ID references.
@@ -65,7 +65,7 @@ function PokedexPage() {
 
 ## Derived routes
 
-Use the same file-based form with `kind: "derived"`, for example `createLayout("pokemon.$name")`. Its required `loader: ({ params }) => ...` receives typed `params.name` and returns `{ kind: "data", data }`. Read its unwrapped data through `layout.useData()`. Use `throw notFound()` (imported from `camox/createLayout`) for a missing record; other loader errors remain server errors. Like singletons, derived routes have before/after blocks but no page-owned `children` or `blocks.initial`. Unlike singletons, curated URLs retain precedence over derived routes.
+Use the same file-based form with `kind: "derived"`, for example `createLayout("pokemon.$name")`. Its required `loader: ({ params }) => ...` receives typed `params.name` and returns `{ kind: "data", data }`. Read its unwrapped data through `layout.useData()`. Use `throw notFound()` (imported from `camox/createLayout`) for a missing record; other loader errors remain server errors. Like singletons, derived routes have before/after blocks but no page-owned `children`. Unlike singletons, curated URLs retain precedence over derived routes.
 
 ### Route discovery
 

package/skills/camox-expand/SKILL.md

@@ -51,11 +51,11 @@ Stop suggesting when the next idea would be filler; there is no target count. Th
 
 Make only these kinds of change:
 
-- **New Block Definitions**, following [Block Definitions](../camox/references/block-definitions.md), [Localized code](../camox/SKILL.md#localized-code) (every visible text in fields, internal links through `useLocalizedHref` without a locale prefix), and Camoxify's rules on [styling](../camoxify/SKILL.md#use-the-existing-styling-stack), [genericity and default content](../camoxify/SKILL.md#keep-definitions-generic), [repeaters](../camoxify/SKILL.md#model-repetition-not-a-fixed-screenshot), [Settings](../camoxify/SKILL.md#use-settings-for-constrained-choices), and [formatted text](../camoxify/SKILL.md#keep-formatted-text-in-one-field).
-- **New Settings on existing Block Definitions**, with defaults that leave current rendering unchanged. Existing content schemas stay exactly as they are. Before editing the block, capture it at desktop and mobile on a Page that places it, on the running dev server; step 6 compares against this capture.
+- **New Block Definitions**, following [Block Definitions](../camox/references/block-definitions.md), [Localized code](../camox/SKILL.md#localized-code) (every visible text in fields, internal links through `useLocalizedHref` without a locale prefix), and Camoxify's rules on [styling](../camoxify/SKILL.md#use-the-existing-styling-stack), [genericity](../camoxify/SKILL.md#keep-definitions-generic), [repeaters](../camoxify/SKILL.md#model-repetition-not-a-fixed-screenshot), [Settings](../camoxify/SKILL.md#use-settings-for-constrained-choices), and [formatted text](../camoxify/SKILL.md#keep-formatted-text-in-one-field).
+- **New Settings on existing Block Definitions** whose unset value (`false`, or an enum's first option) leaves current rendering unchanged, since existing blocks read it. Existing content schemas stay exactly as they are. Before editing the block, capture it at desktop and mobile on a Page that places it, on the running dev server; step 6 compares against this capture.
 - **Description edits.** A new block's `description` says when to choose it over its siblings. Edit the siblings' descriptions so each one names what sets it apart, and the Agent can choose between them.
 
-New blocks live only in code, plus one review Page in the development draft: create it with the CLI (see [Managing Pages and Blocks](../camox-cli/references/cli-content.md)) and place each new block on it with its default content. Leave every other Page, layouts, and publishing alone. This rules out new Layout-only Blocks: a Page can't hold them, and they only sync once a layout uses them. An existing Layout-only Block that gains a Setting is captured and checked on a Page whose layout uses it.
+New blocks live only in code, plus one review Page in the development draft: create it with the CLI (see [Managing Pages and Blocks](../camox-cli/references/cli-content.md)) and place each new block on it with representative content. Leave every other Page, layouts, and publishing alone. This rules out new Layout-only Blocks: a Page can't hold them, and they only sync once a layout uses them. An existing Layout-only Block that gains a Setting is captured and checked on a Page whose layout uses it.
 
 ## 6. Verify
 
@@ -66,5 +66,5 @@ The run is complete when:
 - every approved item is built, and every rejected one is deleted,
 - the review Page is deleted once the operator has reviewed it,
 - the project's `check` script passes, and so does `vp lint --type-aware --type-check`, since `vp check` skips type errors unless the project's Vite config sets `lint.options.typeCheck`,
-- every new block renders correctly with its default content at desktop and mobile on the review Page,
-- every existing block that gained a Setting renders the same as its capture with default Settings.
+- every new block renders correctly with its review content, and with its optional fields empty, at desktop and mobile on the review Page,
+- every existing block that gained a Setting renders the same as its capture with the new Setting unset.

package/skills/camoxify/SKILL.md

@@ -47,9 +47,9 @@ Express layout, spacing, typography, colors, responsive behavior, and interactiv
 
 ## Keep definitions generic
 
-Block names, schemas, rendering, and **default content** must work on other pages. Use `feature-grid`, not `acme-homepage-features`. Defaults are neutral examples, not the reference's copy, links, assets, or item data.
+Block names, schemas, and rendering must work on other pages. Use `feature-grid`, not `acme-homepage-features`.
 
-Apply reference-specific content **only to instances through the CLI**, never by changing definition defaults or hardcoding it in JSX.
+Apply reference-specific content **only to instances through the CLI**, never in the definition or hardcoded in JSX.
 
 Keep the result translatable, following [Localized code](../camox/SKILL.md#localized-code): every visible text in the shell, navigation and footer included, lives in blocks, and internal links go through `useLocalizedHref`, written without a locale prefix.
 
@@ -63,7 +63,7 @@ Choose bounds from real constraints, not the number of items visible in the refe
 
 Before adding a `content` field, ask whether the editor is writing free-form content or choosing from known options. For configuration choices such as alignment, theme, size, or variant, use `settings` with `setting.enum`. For on/off choices such as showing a background or enabling autoplay, use `settings` with `setting.boolean`.
 
-Do not model these choices as `content` fields using `field.string`, even if rendering code could interpret strings such as `"left"`, `"dark"`, or `"true"`. Editors should choose a valid option or toggle a setting, not type a magic string. Reserve `content`'s `field.string` for genuinely free-form text, such as headings and descriptions. Enum defaults must match an option key.
+Do not model these choices as `content` fields using `field.string`, even if rendering code could interpret strings such as `"left"`, `"dark"`, or `"true"`. Editors should choose a valid option or toggle a setting, not type a magic string. Reserve `content`'s `field.string` for genuinely free-form text, such as headings and descriptions.
 
 ## Keep formatted text in one field
 
@@ -81,7 +81,7 @@ Use inline formatting and `textStyle`, including highlights, instead of fields s
 
 Follow the [Camox CLI workflow](../camox-cli/SKILL.md) to assign layouts, place blocks, and populate content, including shared navigation/footer content. Don't publish unless asked.
 
-Compare the rendered site with the reference at desktop and mobile sizes. Verify that fields remain editable and that longer text and different repeater counts still work. Fix the reusable implementation, not just the one captured arrangement.
+Compare the rendered site with the reference at desktop and mobile sizes. Verify that fields remain editable and that longer text, empty optional fields, and different repeater counts still work. Fix the reusable implementation, not just the one captured arrangement.
 
 In multi-page runs, give this full check to every page that introduced or changed a definition, and to each page family's representative page. Compare the remaining pages with their source at desktop size. The run is complete when every page in `camoxify-progress.md` is verified.
 

package/dist/features/canvas/canvasInsertionSeams.js

@@ -1,44 +0,0 @@
-//#region src/features/canvas/canvasInsertionSeams.ts
-/** Main block wrappers publish insertion permissions, including layout boundaries.
-* Detached block targets and fields deliberately do not publish this metadata. */
-function readBlockInsertion(element) {
-	const value = element.getAttribute("data-camox-block-insertion");
-	if (!value) return;
-	try {
-		const insertion = JSON.parse(value);
-		if (!insertion || typeof insertion.position !== "string" || typeof insertion.before !== "boolean" || typeof insertion.after !== "boolean" || insertion.afterPosition !== void 0 && insertion.afterPosition !== null && typeof insertion.afterPosition !== "string") return;
-		return insertion;
-	} catch {
-		return;
-	}
-}
-/** Walk boundaries, not blocks: the bottom of one block and the top of its
-* successor describe ONE insertion seam, even when both permit insertion. */
-function canvasInsertionSeams(targets) {
-	const blocks = targets.filter((target) => target.insertion && target.bounds.width > 0 && target.bounds.height > 0);
-	const seams = [];
-	for (let index = 0; index <= blocks.length; index++) {
-		const previous = blocks[index - 1];
-		const next = blocks[index];
-		const anchor = previous?.insertion?.after ? previous : next?.insertion?.before ? next : null;
-		if (!anchor?.insertion) continue;
-		const insertPosition = anchor === previous ? "after" : "before";
-		const { position, afterPosition } = anchor.insertion;
-		const y = previous && next ? (previous.bounds.y + previous.bounds.height + next.bounds.y) / 2 : anchor.bounds.y + (insertPosition === "after" ? anchor.bounds.height : 0);
-		seams.push({
-			key: `${previous?.element.getAttribute("data-camox-block-id") ?? "start"}:${next?.element.getAttribute("data-camox-block-id") ?? "end"}`,
-			x: anchor.bounds.x + anchor.bounds.width / 2,
-			y,
-			request: {
-				type: "CAMOX_ADD_BLOCK_REQUEST",
-				blockPosition: position,
-				insertPosition,
-				...afterPosition !== void 0 ? { afterPosition } : {}
-			}
-		});
-	}
-	return seams;
-}
-
-//#endregion
-export { canvasInsertionSeams, readBlockInsertion };