astroidjs 0.12.1 → 0.13.0

package/dist/workflow/config.js

@@ -1,11 +1,11 @@
 // Copyright (c) 2026 BowenLabs. Astroid is MIT licensed.
 //
-// `defineWorkflow` — staged, audited pipelines.
+// `defineWorkflow`—staged, audited pipelines.
 //
 // The shape this generalizes is ghostfire.coffee's production floor, and the
 // framing correction in #256 is the important part: despite the name "order
 // tracker", it is NOT queue- or Durable-Object-driven. It is a synchronous SSR
-// + D1 state machine — an integer `stage` column advanced by sign-off rows,
+// + D1 state machine—an integer `stage` column advanced by sign-off rows,
 // where "liveness" is an email plus a page reload. That maps to a workflow
 // module, distinct from the queues module and from #71's realtime DO. If live
 // push is wanted later it layers on top; it is not required for the pattern.
@@ -15,7 +15,7 @@
 // the same four things:
 //
 //   1. an ordered list of stages, and one integer saying which is in progress;
-//   2. exactly one audit row per completed stage — who, when, and what they
+//   2. exactly one audit row per completed stage—who, when, and what they
 //      recorded;
 //   3. an advance that is safe when two operators press the button at once;
 //   4. a per-stage side-effect hook (issue the invoice on packaging).
@@ -58,7 +58,7 @@ export function defineWorkflow(config) {
             throw new AstroidConfigError(`Workflow stage keys must be lowercase identifiers; got ${JSON.stringify(stage.key)}`);
         }
         // Duplicates would make `stationFields` ambiguous and an audit row's stage
-        // key non-unique — both silent, both awful to debug later.
+        // key non-unique—both silent, both awful to debug later.
         if (seen.has(stage.key)) {
             throw new AstroidConfigError(`Workflow ${JSON.stringify(config.key)} has a duplicate stage ${JSON.stringify(stage.key)}`);
         }

package/dist/workflow/generate.d.ts

@@ -3,7 +3,7 @@ import { type WorkflowConfig } from "./config.js";
  * The Drizzle table sources a workflow adds: the audit table, and the override
  * log when enabled.
  *
- * The `stage` column itself is NOT emitted here — it belongs to the project's
+ * The `stage` column itself is NOT emitted here—it belongs to the project's
  * own entity table (orders, applications, tickets), which Astroid doesn't own.
  * The returned `stageColumn` is the line to paste into it, which keeps the
  * ownership boundary honest rather than generating a table the project already has.
@@ -13,7 +13,7 @@ export declare function generateWorkflowSchema(config: WorkflowConfig): {
     stageColumn: string;
 };
 /**
- * `src/pages/api/<key>/advance.ts` — the guarded advance route.
+ * `src/pages/api/<key>/advance.ts`—the guarded advance route.
  *
  * Thin by design: `advanceWorkflowStage` owns the concurrency guard and the
  * status contract, so what's left here is authentication and the per-stage side

package/dist/workflow/generate.js

@@ -3,15 +3,15 @@
 // Workflow → Drizzle schema + the advance route.
 //
 // The schema half is a pure function of the config (regenerate freely); the
-// route is SCAFFOLD-ONCE, because per-stage side effects — issue the invoice
-// when packaging is signed, email the customer on every move — are the whole
+// route is SCAFFOLD-ONCE, because per-stage side effects—issue the invoice
+// when packaging is signed, email the customer on every move—are the whole
 // reason a project reaches for this module, and regenerating would erase them.
 import { workflowAuditTable, workflowOverrideTable, workflowStages, } from "./config.js";
 /**
  * The Drizzle table sources a workflow adds: the audit table, and the override
  * log when enabled.
  *
- * The `stage` column itself is NOT emitted here — it belongs to the project's
+ * The `stage` column itself is NOT emitted here—it belongs to the project's
  * own entity table (orders, applications, tickets), which Astroid doesn't own.
  * The returned `stageColumn` is the line to paste into it, which keeps the
  * ownership boundary honest rather than generating a table the project already has.
@@ -68,7 +68,7 @@ export function generateWorkflowSchema(config) {
     return { source: lines.join("\n"), stageColumn: 'stage: integer("stage").notNull().default(0),' };
 }
 /**
- * `src/pages/api/<key>/advance.ts` — the guarded advance route.
+ * `src/pages/api/<key>/advance.ts`—the guarded advance route.
  *
  * Thin by design: `advanceWorkflowStage` owns the concurrency guard and the
  * status contract, so what's left here is authentication and the per-stage side

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "astroidjs",
-  "version": "0.12.1",
+  "version": "0.13.0",
   "description": "Astroid — an opinionated meta-framework over Louise Toolkit and Astro for building editable, multi-editor sites on Cloudflare Workers.",
   "keywords": [
     "astro",
@@ -59,20 +59,19 @@
   "publishConfig": {
     "access": "public"
   },
-  "dependencies": {
-    "louise-toolkit": "^0.31.0"
-  },
   "devDependencies": {
     "@types/node": "^24.13.3",
     "@typescript/native-preview": "7.0.0-dev.20260707.2",
     "@vitest/coverage-v8": "4.1.11",
     "astro": "^7.2.9",
+    "louise-toolkit": "^0.31.0",
     "solid-js": "^1.9.15",
     "typescript": "^5.9.3",
     "vitest": "^4.1.11"
   },
   "peerDependencies": {
     "astro": "^7.0.9",
+    "louise-toolkit": "^0.31.0",
     "solid-js": "^1.9.0"
   },
   "peerDependenciesMeta": {

package/src/components/Collection.tsx

@@ -1,6 +1,6 @@
 // Copyright (c) 2026 BowenLabs. Astroid is MIT licensed.
 //
-// `<Collection>` — the typed list primitive (ADR 0003, item 3). It renders a list
+// `<Collection>`—the typed list primitive (ADR 0003, item 3). It renders a list
 // and hands each item to a render function that is FULLY TYPED, with no
 // hand-written interface: the item type is inferred from `items`, so `item` in the
 // slot carries whatever shape you passed.
@@ -10,7 +10,7 @@
 //   </Collection>
 //
 // Why a Solid render-prop and not an `.astro` component: Astro slots can't type a
-// per-item `{item}`, but a Solid children-as-function can — this is the only shape
+// per-item `{item}`, but a Solid children-as-function can—this is the only shape
 // that delivers the ADR's "`{item}` in its slot is fully typed". Server-render it
 // by using it inside a Solid island without a `client:*` directive: it emits
 // static HTML and ships no JS. Add `client:load`/`client:visible` only if the list
@@ -19,8 +19,8 @@
 // On the item type + ADR 0003 §6 ("infers from the collection's Zod schema"):
 // Louise's `CollectionConfig` is type-erased (`fields: Record<string,
 // FieldConfig>`), so the item shape can't be recovered from the collection VALUE.
-// Instead you type `items` from your data — per ADR 0001, a Zod-inferred query
-// result — and it flows through to the slot. Same guarantee (a typed `item`),
+// Instead you type `items` from your data—per ADR 0001, a Zod-inferred query
+// result—and it flows through to the slot. Same guarantee (a typed `item`),
 // sourced from the data rather than the erased config.
 
 import { For, type JSX } from "solid-js";
@@ -28,7 +28,7 @@ import { For, type JSX } from "solid-js";
 export interface CollectionProps<T> {
   /** The items to render, in order. The item type `T` is inferred from here. */
   items: readonly T[];
-  /** Render one item — receives the fully-typed `item` and a reactive `index`. */
+  /** Render one item—receives the fully-typed `item` and a reactive `index`. */
   children: (item: T, index: () => number) => JSX.Element;
   /** Rendered when `items` is empty. */
   fallback?: JSX.Element;

package/src/components/Editable.astro

@@ -1,5 +1,5 @@
 ---
-// `<Editable>` — the Astroid inline-edit primitive (ADR 0003, checklist item 1).
+// `<Editable>`—the Astroid inline-edit primitive (ADR 0003, checklist item 1).
 //
 // It owns the `data-louise-*` marker contract so sites stop stamping it by hand:
 // in edit mode it renders your element with the markers the Louise client
@@ -8,25 +8,25 @@
 // the public HTML.
 //
 // Two flavors, per which surface the field lives on:
-//   • PAGE field  — pass `collection` + `key` + `field`; emits
+//   • PAGE field: pass `collection` + `key` + `field`; emits
 //                   `data-louise-field="<collection>:<key>:<field>"` (saved as a
 //                   versioned draft when the page is mounted with `versionedPageId`).
-//   • SECTION field — pass `base` (this item's path, e.g. `"2"` or `"2.blocks.0"`)
+//   • SECTION field: pass `base` (this item's path, for example, `"2"` or `"2.blocks.0"`)
 //                   plus `field`; emits `data-louise-node="<base>.<field>"` for
 //                   the on-canvas section editor. `sfield` stays as the escape
-//                   hatch for a path you build yourself — an array entry:
+//                   hatch for a path you build yourself—an array entry:
 //                   sfield={`${base}.items.${i}.title`}.
 //
 //                   Since ADR 0010 A2 this is the SAME attribute the section
 //                   boundary carries, one path deeper. The catalog says whether a
 //                   field is edited in place and with which editor, so `type` and
-//                   `multiline` no longer affect a section field's markup — they
+//                   `multiline` no longer affect a section field's markup—they
 //                   are accepted for compatibility and ignored.
 //
 // The `base` form is what ADR 0005 §2 asks for: "a site author writes `<Editable
 // field="heading">` and never hand-stamps the deeper path". `<Section>` supplies
 // `base`, so the SAME component renders correctly whether it sits at the top level
-// (`"2.heading"`) or inside a block (`"2.blocks.0.heading"`) — the depth never
+// (`"2.heading"`) or inside a block (`"2.blocks.0.heading"`)—the depth never
 // appears in the component's source, which is what makes a section component
 // reusable as a block component.
 //
@@ -38,11 +38,11 @@ import type { HTMLAttributes, HTMLTag } from "astro/types";
 interface Props extends HTMLAttributes<"div"> {
   /** The element to render. Default `"div"`. */
   as?: HTMLTag;
-  /** PAGE-field mode: the Louise collection slug (e.g. `"pages"`). */
+  /** PAGE-field mode: the Louise collection slug (for example, `"pages"`). */
   collection?: string;
   /** PAGE-field mode: the row key/id the field is on. */
   key?: string | number;
-  /** PAGE-field mode: the field name (e.g. `"title"`, `"body"`). Also the field
+  /** PAGE-field mode: the field name (for example, `"title"`, `"body"`). Also the field
    *  name in SECTION mode, where it's joined onto `base`. */
   field?: string;
   /** SECTION-field mode: this item's path prefix (`"2"`, `"2.blocks.0"`),
@@ -87,7 +87,7 @@ let markers: Record<string, string> = {};
 if (editing) {
   if (sectionPath) {
     // ONE marker (ADR 0010 A2). This used to emit `data-louise-sfield` plus
-    // `data-louise-type="richtext"` plus `data-louise-multiline` — three
+    // `data-louise-type="richtext"` plus `data-louise-multiline`—three
     // attributes describing a field the catalog already fully describes. The
     // editor now reads the field's type to know whether it's rich text and
     // whether it holds more than one line, so `type` and `multiline` are inert

package/src/components/JustifiedGallery.astro

@@ -1,18 +1,18 @@
 ---
-// `<JustifiedGallery>` — Flickr-style row-balanced photo grid (#257).
+// `<JustifiedGallery>`—Flickr-style row-balanced photo grid (#257).
 //
 // Images keep their aspect ratios, rows fill the container exactly, and row
 // heights land near a target. CSS alone can't do it: `grid` wants uniform
 // tracks, and `columns` gives a masonry *column* flow where reading order runs
-// down the page instead of across it — wrong for a portfolio, and wrong for
+// down the page instead of across it—wrong for a portfolio, and wrong for
 // keyboard/screen-reader order.
 //
 // Two layers, so it never depends on JavaScript to be usable:
 //
 //   1. SSR emits a flex-wrap floor. Each tile carries its declared aspect ratio
 //      (from the media library's recorded dimensions) as `flex-grow`/`flex-basis`,
-//      which already produces a justified, gap-correct grid with no layout shift
-//      — that's what someone with JS blocked, or on the first paint before the
+//      which already produces a justified, gap-correct grid with no layout shift—that's
+//      what someone with JS blocked, or on the first paint before the
 //      bundle lands, sees.
 //   2. On the client, once the images decode and their TRUE dimensions are known,
 //      `justifyRows` recomputes exact rows and pins each tile's box. This is the
@@ -23,7 +23,7 @@
 // right, so the correction isn't visible as a jump on a well-populated library.
 //
 // CSP: the layout script is a normal (bundled) `<script>`, so Astro hashes it
-// into `script-src` — no `is:inline`, no `unsafe-inline`. Per-tile sizing is
+// into `script-src`—no `is:inline`, no `unsafe-inline`. Per-tile sizing is
 // written as inline `style`, which is what the `style-src` rewrite in #253
 // exists for.
 import { DEFAULT_ASPECT, type GalleryItem } from "./justify.js";
@@ -129,7 +129,7 @@ const aspectOf = (item: GalleryItem) =>
   }
 
   /* Reveal-on-scroll. The visible state is the DEFAULT so that a browser with
-     no IntersectionObserver — or no JS at all — shows every tile; the script
+     no IntersectionObserver—or no JS at all—shows every tile; the script
      opts tiles into the hidden state only once it can guarantee it will undo it. */
   .astroid-gallery--reveal .astroid-gallery__tile[data-reveal="pending"] {
     opacity: 0;
@@ -164,7 +164,7 @@ const aspectOf = (item: GalleryItem) =>
 
     const targetHeight = Number(root.dataset.targetHeight) || 260;
     const gap = Number(root.dataset.gap) || 8;
-    // clientWidth excludes the scrollbar, which offsetWidth does not — using the
+    // clientWidth excludes the scrollbar, which offsetWidth does not—using the
     // wrong one overflows the row by the scrollbar width on Windows.
     const containerWidth = root.clientWidth;
 
@@ -242,7 +242,7 @@ const aspectOf = (item: GalleryItem) =>
 
     if (typeof ResizeObserver !== "undefined") {
       let frame = 0;
-      // Coalesce to one layout per animation frame — a drag-resize fires this
+      // Coalesce to one layout per animation frame—a drag-resize fires this
       // continuously, and each run touches every tile's style.
       const observer = new ResizeObserver(() => {
         cancelAnimationFrame(frame);

package/src/components/MediaSlot.astro

@@ -1,5 +1,5 @@
 ---
-// `<MediaSlot>` — the responsive-image primitive (#257).
+// `<MediaSlot>`—the responsive-image primitive (#257).
 //
 // One place that knows how to put a media-library image on a page correctly:
 // a width-descriptor `srcset` over Cloudflare Image Resizing, a `sizes` hint so
@@ -7,7 +7,7 @@
 // box so the image can't shift the page as it loads, and lazy/async decoding by
 // default.
 //
-// The math is not new — `louise-toolkit/media` already ships `cfImageSrcset`
+// The math is not new—`louise-toolkit/media` already ships `cfImageSrcset`
 // (width descriptors, ratio-derived heights, cover-crop gravity, `format=auto`)
 // and `circleImage`. What every consuming site rebuilt by hand was the *component*
 // around it: the ratio box, the `sizes` string, the focal-point crop, and
@@ -15,13 +15,13 @@
 // Contentful Paint regression. That's what this owns.
 //
 // CSP: the focal/zoom knobs emit a data-driven inline `style` attribute. That is
-// exactly the case astroid's middleware rewrites `style-src` for (#253) — scripts
+// exactly the case astroid's middleware rewrites `style-src` for (#253)—scripts
 // stay hash-pinned with no `unsafe-inline`.
 import { cfImageSrcset, circleImage } from "louise-toolkit/media";
 import type { HTMLAttributes } from "astro/types";
 
 interface Props extends Omit<HTMLAttributes<"img">, "src" | "srcset" | "sizes" | "width" | "height"> {
-  /** Image URL — a media-library asset, or any URL on a resizing-enabled zone. */
+  /** Image URL—a media-library asset, or any URL on a resizing-enabled zone. */
   src: string;
   /**
    * Alternative text. REQUIRED, and `""` is a legitimate value: an image that
@@ -33,18 +33,18 @@ interface Props extends Omit<HTMLAttributes<"img">, "src" | "srcset" | "sizes" |
   alt: string;
   /**
    * The largest width, in CSS px, this image is displayed at on a 1× screen.
-   * Drives the srcset ladder — not a hard render width.
+   * Drives the srcset ladder—not a hard render width.
    */
   width?: number;
   /**
-   * The `sizes` attribute: how wide the image renders at each breakpoint, e.g.
+   * The `sizes` attribute: how wide the image renders at each breakpoint, for example,
    * `"(max-width: 640px) 100vw, 33vw"`. Without it the browser assumes `100vw`
    * and over-fetches on every multi-column layout, which is the single most
    * common way a "responsive" image ends up slower than a fixed one.
    */
   sizes?: string;
-  /** Aspect ratio as `"w/h"` (e.g. `"16/9"`). Reserves the box and derives each
-   *  derivative's height so the crop matches what's shown — no wasted pixels. */
+  /** Aspect ratio as `"w/h"` (for example, `"16/9"`). Reserves the box and derives each
+   *  derivative's height so the crop matches what's shown—no wasted pixels. */
   ratio?: string;
   /** `rect` (default) or `circle`. A circle uses a square focal crop + 2× retina. */
   shape?: "rect" | "circle";
@@ -57,7 +57,7 @@ interface Props extends Omit<HTMLAttributes<"img">, "src" | "srcset" | "sizes" |
   /** Encode quality, 1–100. Default 82. */
   quality?: number;
   /**
-   * Focal point as percentages, for when `gravity: auto` picks wrong — a portrait
+   * Focal point as percentages, for when `gravity: auto` picks wrong—a portrait
    * where the subject sits high, say. Applied as `object-position`, so it's a
    * render-time framing choice and the same derivative is reused.
    */
@@ -65,7 +65,7 @@ interface Props extends Omit<HTMLAttributes<"img">, "src" | "srcset" | "sizes" |
   /** Scale factor inside the box, for a punch-in crop. Default 1. */
   zoom?: number;
   /**
-   * `lazy` (default) or `eager`. Set `eager` — and `priority` — for anything
+   * `lazy` (default) or `eager`. Set `eager`—and `priority`—for anything
    * above the fold: lazy-loading the LCP image delays it by a full network
    * round-trip after layout.
    */
@@ -111,7 +111,7 @@ const sizesAttr = sizes ?? (circle ? `${size}px` : `${width}px`);
 
 // Framing lives on the <img>: `object-position` moves the visible window of a
 // cover-crop, `scale` punches in. Both are per-placement, so they must NOT go
-// through the CDN — that would mint a second derivative of the same source.
+// through the CDN—that would mint a second derivative of the same source.
 const frame = [
   focal ? `object-position:${focal.x}% ${focal.y}%` : "",
   zoom !== 1 ? `transform:scale(${zoom})` : "",
@@ -132,7 +132,7 @@ const img = {
   src: derived.src,
   srcset: derived.srcset,
   // A circle's srcset uses DPR descriptors (`1x`/`2x`), which `sizes` does not
-  // apply to — supplying it there would be ignored at best and confusing at worst.
+  // apply to—supplying it there would be ignored at best and confusing at worst.
   ...(circle ? {} : { sizes: sizesAttr }),
   alt,
   loading,

package/src/components/PortalShell.astro

@@ -1,5 +1,5 @@
 ---
-// `<PortalShell>` — the account-area chrome: a sidebar of nav items and a main
+// `<PortalShell>`—the account-area chrome: a sidebar of nav items and a main
 // column, collapsing to a burger on small screens.
 //
 // Theme-tokened, never brand-styled. Every colour here is a daisyUI token
@@ -14,11 +14,11 @@ import type { PortalNav } from "astroidjs";
 
 interface Props {
   nav: PortalNav;
-  /** The signed-in user's role — decides which nav items are visible. */
+  /** The signed-in user's role—decides which nav items are visible. */
   role?: string | null;
   /** Current path, for the active highlight. Defaults to the rendered URL. */
   path?: string;
-  /** Heading above the nav, e.g. the account holder's name. */
+  /** Heading above the nav, for example, the account holder's name. */
   title?: string;
 }
 
@@ -26,7 +26,7 @@ const { nav, role, path, title } = Astro.props;
 const current = path ?? Astro.url.pathname;
 
 // Filtered by role BEFORE render: an item the viewer can't reach is never
-// drawn, rather than drawn and then 403'd — which reads as a broken link.
+// drawn, rather than drawn and then 403'd—which reads as a broken link.
 const items = nav.forRole(role);
 const active = nav.activeFor(current);
 ---

package/src/components/RegisterSW.astro

@@ -1,10 +1,10 @@
 ---
-// `<RegisterSW>` — registers the PWA service worker.
+// `<RegisterSW>`—registers the PWA service worker.
 //
 // A bundled `<script>`, never an inline one: Astro hashes it into `script-src`,
 // so this works under the strict CSP without `unsafe-inline`. That's also why
 // the scope rides on a `data-` attribute rather than being interpolated into
-// the script — `define:vars` forces `is:inline`, whose content varies per
+// the script—`define:vars` forces `is:inline`, whose content varies per
 // render and therefore can't be hashed.
 //
 // Registration is best-effort by design. A service worker is an enhancement:
@@ -36,7 +36,7 @@ const { scope = "/", src = "/sw.js" } = Astro.props;
     navigator.serviceWorker
       .register(el.dataset.src ?? "/sw.js", { scope: el.dataset.scope ?? "/" })
       .catch((error) => {
-        // Not fatal — the app works without it. Logged rather than swallowed so
+        // Not fatal—the app works without it. Logged rather than swallowed so
         // a scope/MIME misconfiguration is findable instead of just "the PWA
         // doesn't install and nobody knows why".
         console.warn("[astroid] service worker registration failed", error);

package/src/components/Section.astro

@@ -1,10 +1,10 @@
 ---
-// `<Section>` — the section-library dispatcher (ADR 0003 item 2, on the ADR 0005
+// `<Section>`—the section-library dispatcher (ADR 0003 item 2, on the ADR 0005
 // model).
 //
 // It renders ONE stored `SectionItem`: dispatch on `_type`, hand the component
 // its `base` path, and let the component own every pixel. What changed from the
-// old `kind`-prop version is where the truth lives — the item is data loaded from
+// old `kind`-prop version is where the truth lives—the item is data loaded from
 // the page's `sections` column, not props a template hand-wrote, so what renders
 // is exactly what the on-canvas editor edits in place.
 //
@@ -14,7 +14,7 @@
 //   • the FIELDS are stamped by `<Editable base={base} field="…">` inside each
 //     component, because only the component knows which of its text nodes are
 //     editable. Since A2 those carry the SAME `data-louise-node` attribute, one
-//     path deeper — the catalog says whether a field is edited in place, so the
+//     path deeper—the catalog says whether a field is edited in place, so the
 //     marker no longer has to.
 //
 // Blocks recurse through this same component with a deeper `base`. That's the
@@ -51,8 +51,8 @@ interface Props {
 /**
  * `_type` → render component. A map rather than a chain of `{type === "x" && …}`
  * for one reason that matters: it can be checked. A catalog entry whose type is
- * missing here renders NOTHING — a silent hole in the page rather than an error
- * — so the test suite asserts these keys and the catalog's are the same set.
+ * missing here renders NOTHING—a silent hole in the page rather than an error—so
+ * the test suite asserts these keys and the catalog's are the same set.
  */
 const COMPONENTS: Record<string, ((props: SectionRenderProps) => unknown) | undefined> = {
   hero: Hero,
@@ -82,12 +82,12 @@ const type = String(item._type);
 const blocks = Array.isArray(item.blocks) ? item.blocks : [];
 
 // The boundary marker the on-canvas chrome draws its ring on. It is the item's
-// path, verbatim — pre-0010 this line string-sniffed `base` for ".blocks." to pick
+// path, verbatim—pre-0010 this line string-sniffed `base` for ".blocks." to pick
 // between two attribute names, which was the three-attribute editing model leaking
 // into an otherwise uniform recursive render (ADR 0010, Context). The editor
 // resolves what a path CAN do from the catalog; the render just says where it is.
 //
-// `class="contents"` keeps this wrapper out of layout entirely — the ring is drawn
+// `class="contents"` keeps this wrapper out of layout entirely—the ring is drawn
 // as a box-shadow on the element itself, so an extra block box here would offset
 // every section's spacing for the sake of an attribute.
 const boundary = editing ? { "data-louise-node": base } : {};
@@ -95,7 +95,7 @@ const boundary = editing ? { "data-louise-node": base } : {};
 const shared = { item, base, edit: editing, mediaMeta };
 
 // Resolved in the frontmatter so the template is one dynamic tag rather than a
-// ladder of comparisons. The map itself is the dispatch check — an unknown
+// ladder of comparisons. The map itself is the dispatch check—an unknown
 // `_type` (legitimate mid-migration, and already rejected on write) simply
 // finds nothing and renders nothing, which is why the lookup is typed as
 // possibly-undefined rather than asserted.

package/src/components/Sections.astro

@@ -1,10 +1,10 @@
 ---
-// `<Sections>` — render a page's whole `sections` array.
+// `<Sections>`—render a page's whole `sections` array.
 //
 // This exists for one reason `<Section>` can't serve: the media lookup has to
 // span the page. A section stores an image as a URL, but the `alt`/`caption` an
 // editor typed live on the media ASSET, so rendering images correctly means
-// joining back to the registry — and doing that per image is thirty D1
+// joining back to the registry—and doing that per image is thirty D1
 // round-trips for one gallery. Here it's ONE bounded `IN (...)` per page,
 // threaded down as `mediaMeta`.
 //
@@ -16,7 +16,7 @@ import { astroidSectionCatalog } from "./sections.js";
 import Section from "./Section.astro";
 
 interface Props {
-  /** The page's stored `sections` array. Untrusted JSON — a non-array, or an
+  /** The page's stored `sections` array. Untrusted JSON—a non-array, or an
    *  item with an unknown `_type`, renders nothing rather than throwing. */
   items: unknown;
   /** D1, for the media alt/caption lookup. Omit to skip it entirely. */
@@ -24,7 +24,7 @@ interface Props {
   /** Public media base, for turning a stored URL back into a registry key.
    *  Matches the site's `MEDIA_URL`. */
   mediaBase?: string;
-  /** Override the catalog — a site that extends Astroid's set passes its own. */
+  /** Override the catalog—a site that extends Astroid's set passes its own. */
   catalog?: SectionCatalog;
   /** Force edit markers on/off. Defaults to `Astro.locals.editMode`. */
   edit?: boolean;
@@ -42,7 +42,7 @@ const {
 } = Astro.props;
 
 // A page with no sections column yet, or a malformed one, is a normal state
-// (nothing seeded) — not an error worth failing the render over.
+// (nothing seeded)—not an error worth failing the render over.
 const list: SectionItem[] = Array.isArray(items) ? (items as SectionItem[]) : [];
 
 // One lookup for the page. Skipped when the caller already did it (a layout that
@@ -54,7 +54,7 @@ const mediaMeta =
 {/*
   The host element. `mountSections(el, opts)` takes the element to scan for
   `[data-louise-node]` markers and to hang on-canvas chrome off, so rendering
-  it here — rather than asking every page to remember a wrapper — is what makes
+  it here—rather than asking every page to remember a wrapper—is what makes
   `<Sections>` self-sufficient: drop it on a page and the editor can find it.
   A plain block wrapper, not `display: contents`, because the chrome positions
   toolbars against a real box.

package/src/components/Seo.astro

@@ -1,11 +1,11 @@
 ---
-// `<Seo>` — the settings-driven `<head>` block: title (templated), description,
+// `<Seo>`—the settings-driven `<head>` block: title (templated), description,
 // canonical, robots, Open Graph, and the Twitter/X card.
 //
 // Tags are emitted directly rather than through a wrapper library. There are
 // about fifteen of them, the shapes are frozen by the OG and Twitter specs, and
 // owning them means the resolution rules (see `resolvePageSeo`) are the ONLY
-// place a value can come from — which is what makes the layer predictable.
+// place a value can come from—which is what makes the layer predictable.
 //
 // JSON-LD is not here: it's a separate concern with different escaping rules and
 // its own component (`<StructuredData>`).
@@ -40,7 +40,7 @@ const seo = resolvePageSeo(settings, page, {
 {seo.noindex && <meta name="robots" content="noindex, nofollow" />}
 
 <meta property="og:type" content={seo.ogType} />
-{/* The bare title, not the templated one — og:site_name already carries the brand. */}
+{/* The bare title, not the templated one—og:site_name already carries the brand. */}
 <meta property="og:title" content={seo.bareTitle} />
 <meta property="og:url" content={seo.canonical} />
 {seo.description && <meta property="og:description" content={seo.description} />}

package/src/components/StageBar.astro

@@ -1,5 +1,5 @@
 ---
-// `<StageBar>` — a pipeline's progress as a segmented bar.
+// `<StageBar>`—a pipeline's progress as a segmented bar.
 //
 // Generalized from ghostfire's six-stage floor tracker, which hard-coded the
 // segment count, the corner radii, the brand hex codes, and a mascot image.
@@ -17,7 +17,7 @@ interface Props {
   stage: number;
   /**
    * An optional marker (an emoji, a mascot glyph) that rides above the active
-   * segment. Off by default — the reference's bobbing ghost is brand, not
+   * segment. Off by default—the reference's bobbing ghost is brand, not
    * mechanism.
    */
   marker?: string;
@@ -81,7 +81,7 @@ const markerLeft = complete ? null : `${(((current + 0.5) / stages.length) * 100
     transition: background-color 300ms ease;
   }
   /* Round only the outer ends, so the bar reads as one track rather than a row
-     of separate pills — at any segment count. */
+     of separate pills—at any segment count. */
   .astroid-stagebar__step:first-child .astroid-stagebar__seg {
     border-start-start-radius: 999px;
     border-end-start-radius: 999px;

package/src/components/StructuredData.astro

@@ -1,5 +1,5 @@
 ---
-// `<StructuredData>` — the schema.org JSON-LD `@graph` for rich results and AI
+// `<StructuredData>`—the schema.org JSON-LD `@graph` for rich results and AI
 // answer surfaces: the business (its `@type` from the archetype), the WebSite,
 // and optionally the entity this page is about.
 //
@@ -16,7 +16,7 @@ interface Props {
   /** Absolute origin serving this page. Defaults to the current origin, which
    *  keeps a preview deploy describing itself rather than the live domain. */
   siteUrl?: string;
-  /** The thing this page is about — a Product, VisualArtwork, Article. */
+  /** The thing this page is about—a Product, VisualArtwork, Article. */
   entity?: JsonLdNode;
 }