Commerce Blocks

0.44.x

0.43.x

0.38.xMinor

• Catalog blocks now show live prices, images and stock, and add a shared product tile, a numbered contents list, an annotated product spotlight and a product gallery.

  • New block `product-gallery`. A product's frames at one steady ratio (4:5 by default), a thumbnail row with a cross-fade, and a swipe with dots on phones; the first frame loads first. Frames are authored, or come from the product's catalog media (the primary first, then by sort order) when you look it up by sku or slug. Hooks: data-gallery, data-gallery-frames, data-gallery-frame, data-gallery-thumbs, data-gallery-thumb (aria-current), data-gallery-dots.
  • New variant `category-strip` `contents`. Numbered rows ruled like a printed contents page: the number, the title, one line and a live piece count sit on one shared baseline, on the page grid's lanes from 1024px, under the shared opener. New fields kicker, moreLink, showCount, countLabel {one, other} and categories[].line. The order number and count are live when a commerce layer has registered a listing source, and absent otherwise. Hooks: data-contents-row, -no, -name, -line, -count.
  • New variant `featured-product` `annotated`. The shared opener, an in-use plate, the product's line and margin notes. New fields media (the in-use frame, 3:2), mediaAlt, notes[] {label, text} and moreLink; the plate falls back to the live second image, then to the image. The notes stand in the left margin beside the plate and become a two-column list on phones. Hooks: data-annotated-media, data-margin-notes, data-margin-note, data-note-label, data-note-text.
  • Shared product tile and shared opener. ProductTile (from ./render) is a plate (image, flags, add) over an info block, carrying data-product-tile, data-tile-plate, data-tile-image, data-tile-flags, data-edition-tag, data-tile-badge, data-tile-eyebrow, data-tile-name, data-tile-desc, data-price, data-price-now, data-price-was, data-tile-soon and data-availability. The add goes through blocks-core's resolveAddToBag, so it is a plain link to the product until a commerce layer registers the real control. Opener emits the data-opener-* masthead hooks. The ProductTileData contract and pickTileBadge() are exported.
  • Live commerce data through registered sources. registerCatalogListingSource() and registerCatalogAvailabilitySource() (from ./server) let a commerce layer supply prices, images, stock and category counts without this pack importing it. With a listing source, product-card and featured-product overlay the lowest active price ("from" when variant prices differ), a real compare-at price as the struck previous price, the product image and a stock line; the price pair is overlaid as a unit, so a stale authored strike never sits beside a live price. With an availability source, inventory-badge follows the SKU's real availability (resolveInventoryBadgeData()), and a stale authored count is cleared. listingQueryFromSearchParams() and listingQueryToSearchParams() give the server render and the filter island one URL state. createHydratedRenderers() now also returns inventory-badge and product-gallery.
  • `product-card` and `featured-product` gain an `image` field (and imageAlt). A bare upload id draws nothing, so a document that only carries a stale image key renders as before.
  • Part hooks on the existing cards. product-card emits data-tile-name, data-tile-desc, data-price, data-price-now and data-price-was, and featured-product emits data-price, data-price-now and data-price-was, so a theme can style them; the rest of every existing variant's markup is byte-identical (the snapshot tests hold a baseline and an explicit allowance list).

  With no source registered, every block renders its authored data exactly as before.

  • Theme hooks, additive. ProductTile's info block carries data-tile-info; the product-grid shelf inner wrapper carries data-shelf-inner; featured-product annotated carries data-annotated-body (the body), data-annotated-desc (the description) and data-annotated-action (the action link); and each product-gallery frame carries data-frame-role="primary" (the first frame, which is the product's primary image when the frames come from the catalog) or "detail", so a theme can treat a close-up differently from the packshot. Stored renders differ only by these attributes.
  • Empty filter options meet AA. An option with no results was faded with opacity: 0.45, which fails contrast. It now takes the muted-ink token at full opacity; data-facet-empty (and the disabled checkbox) still mark it, and no opacity is applied.
  • Checkpoint B fixes, all opt-in or additive. The shelf grid now passes restock to every tile, so a sold-out tile (or a priced tile that cannot be bought) renders the restock control instead of nothing. The add and the restock control sit in a data-tile-add wrapper that the pack places bottom right of the plate, so the control's own styling can no longer move it over the edition tag. The sale badge reads "Save $22.00" (compareAtCents - priceCents, formatted on the server); the new product-grid field saveLabel (and the tile's saveLabel prop) sets the wording with {amount}, and a tile with no real saving gets no badge. The "New" badge now needs edition.isNew === true from the listing source: isCurrent alone only says the piece is in the current batch, so by default no tile is marked New (new optional isNew on the tile's edition). Each facet option carries data-facet-box, a drawn checkbox that follows the input's checked, disabled and focus states; the baseline hides it, a theme that hides the native input turns it on. The sort control's featured option is labeled "Featured" instead of "Shelf order"; it orders by the catalog's manual product order (see the storefront and catalog changesets), and "Newest" stays its own sort.
  • `category-strip` `contents` counts. A row shows its own count whenever it has one. The opener total (showCount) uses the listing source's own total when it gives one, else the sum of the rows only if every row has a count. The live counts and total no longer depend on a catalog-categories name match: the resolver used to return early when none matched, which dropped every count.

  Checkpoint B round 2:

  • Shop at 1024px and up. The filter bar's main column (toolbar, results, more link) carries data-filter-main, so a theme can place it as one grid area. The Shelf theme's rule expected the three as direct children of the rail layout and never matched.
  • Sold-out tiles on the occasion row. A tile that shows its second image (imageRole: 'second'), or is given compactRestock, asks for the restock in size: 'compact': one line, "Email me when it's back", instead of the form over the plate. The shop's primary-image tile keeps the small form. compactRestock is a new optional ProductTile prop.
  • A count-only opener is a caption. An opener with only a count (no label, title or link) carries data-opener-bare, so a theme can drop its rule and gap; the count still rides in the label when there is one.

  Polish:

  • One restock rule for grid tiles. ProductTile now asks for the compact restock chip ("Email me when it's back", size: 'compact') on every grid tile, so the shop's sold-out tile matches the occasion row; the full form lives on the product page. It used to use the compact chip only on a tile showing its second image. compactRestock: false opts a tile back into the small form ("Tell me when it is back"). Stored sold-out shop tiles change from the small form to the chip, which is the one intended markup change; the occasion row is unchanged.

  Parity pass (2026-10-19):

  • Occasion tabs hold one height. The tab panels now share one grid cell (data-grid-panels), so the row takes the tallest panel's height and swapping tabs never moves the page below it. An inactive panel is visibility: hidden, aria-hidden and inert (out of the tab order and the accessibility tree) instead of the hidden attribute, and each panel carries data-active. Untabbed grids render as before.
  • Guide tile kicker and links. The product-grid shelf guideTile gains optional kicker and links[] (up to four {label, href}); both render only when set. The tile's box carries data-guide-plate, with data-guide-kicker, data-guide-title, data-guide-links and data-guide-link, so a theme can stand it on the shelf line at plate height. A guide tile with only title, line and href renders as before apart from the new hook attributes.
• product-grid goes live, gains the shelf variant and a real filter bar.

  (Bullets for the grid half of storefront S5; the tile, category-strip, featured-product, product-gallery and inventory-badge bullets are in the sibling changeset.)

  • `dataSource: 'live'`. A server renderer reads the listing source the host registered (CatalogListingSource) for the block's query: category, tag, edition, explicit ids ("goes with", which ignores every other filter), sort and limit. The default variants take the live tiles as their list, in the same markup. With no source registered, a static data source or any error, the authored products list renders exactly as before; the existing variants are byte-identical, held by a baseline test captured from the pre-change source.
  • New variant `shelf`. An opener (kicker, heading, moreLink, showCount; hooks data-opener-*), a four-across row (two on phones) of the shared product tile on a shelf line (data-shelf-row, data-shelf-line), a dashed nextSlot (data-next-slot), a guideTile placed after N pieces (data-guide-tile), imageRole: 'second' for the occasion row, and tabs[] {label, tag} that swap the row between tag queries (data-grid-tabs, data-grid-tab with aria-pressed). Every tab's row is rendered on the server and a tab is offered only when its query fills the row, so the swap is a client toggle with no fetch and the row never changes height. An empty state (data-grid-empty) offers clear filters and a link to the latest edition.
  • `showFilters` is real on `shelf`. Left rail or bar (filterLayout): numbered shelves with counts, checkbox facets with counts (empty options dimmed and not pickable), removable chips, clear all, sort, a live result count in an aria-live="polite" region, and paging by pageSize ("Show the next 6", a real link). The page URL holds the state: ?category=&attr.<axis>=a,b&price=&availability=in-stock&sort=&page=, where page is cumulative. The host passes the URL in through the render context ({ searchParams, pathname }). Below 48rem the rail becomes sideways shelf tabs and a Filter button that opens a bottom sheet: focus moves in, Tab is trapped, Escape closes it and focus returns to the button. Every control has a label and a 44px target.
  • Two client islands (ProductGridFilters, ProductGridTabs); ProductGridShelf and the tiles stay server-safe. The rsc-boundaries manifest count for this pack goes from 1 to 3. Filter changes navigate through the link adapter, so a Next site gets soft navigation and a plain site a normal one, with no router dependency.
  • Hook names follow shelf/HOOK-CONTRACT for the grid, filter bar and sheet.

0.37.x

0.36.x

0.28.x

0.27.x

0.25.xMinor

• Breaking: block stylesheets are now per-block (`.tome-css`). Each block's CSS ships only on pages that render it, instead of in every page's CSS bundle.

  The 6 stylesheets moved from X.module.css to X.tome-css, and each renderer renders <BlockStyles sheet={styles} /> from @wabbit/tome-blocks-core/block-styles.

  Required in the consuming site: wrap next.config with withTomeBlockStyles (@wabbit/tome-blocks-core/next, blocks-core 0.22.0 or later); without it the .tome-css imports fail to build. See the blocks-core README, "Per-block stylesheets".

  • The @wabbit/tome-blocks-core peer range is now >=0.22.0 <1.0.0.
  • ProductGrid (a client component) renders its stylesheet itself; <BlockStyles> works in client components since blocks-core 0.22.0. Exported names and props are unchanged.
  • Block CSS now loads after all bundled CSS. A site-level rule that overrode one of this pack's classes at equal specificity, and won only by loading later, no longer wins.

0.20.x

0.18.x

0.17.xMinor

• Tome block packs now install into an existing Payload project the way the README says: one npm install, one CSS import, no undocumented steps.

  Proven by the new fresh-install smoke test (scripts/blocks-fresh-install-smoke.mjs) against a brand-new create-payload-app website-template site.

  Consumers: list `@wabbit/tome-blocks-core` and `@wabbit/tome-ui` in your own `package.json` if you import from them (npm 7+ and pnpm install required peers automatically, so a fresh npm install of a pack already brings them in).

  • One shared `blocks-core` per site. Every pack, blocks-house and blocks-extras now declare @wabbit/tome-blocks-core (and, where used, -house / -extras) as a required peer with an explicit range instead of a regular dependency, so a site gets exactly one hoisted copy and one adapter registry.
  • No more ERESOLVE in plain Payload sites. blocks-core no longer declares @wabbit/tome-core or @wabbit/tome-catalog (their optional peer graph pulled better-auth → @sveltejs/kit → vite@8 against a site's vite@7). The block-bundle product type still auto-registers when both are installed; new structural types BlockBundleProductTypeDeps, BlockBundleProductTypeRegistryLike, RegisterProductTypeHooksLike.
  • Tokens in one line: @import '@wabbit/tome-blocks-core/styles.css'; (new export; imports @wabbit/tome-ui/tokens). @wabbit/tome-ui is now a required peer of blocks-core.
  • Rich text and images render with no adapter setup. Built-in defaults render Lexical through @payloadcms/richtext-lexical/react and resolve populated Payload uploads; an unpopulated upload id warns once in every environment (previously content vanished silently in production). Registered adapters still win.
  • Payload's spread-props convention: new adaptRenderersForPayload(renderers) / adaptRendererForPayload(Component) wrap any pack's renderers map for a site that renders <Block {...block} />.
  • Slug collisions with Payload's templates (cta, banner, archive, content, code): new applyBlockSlugOverrides(blocks, overrides) and remapRendererSlugs(renderers, overrides) (@wabbit/tome-blocks-core/slugOverrides). Defaults are unchanged; no stored data migrates.
  • `blocks-house` owns gsap and hls.js as dependencies (previously optional peers that still broke the build when missing), and registers GSAP's ScrollTrigger itself before first use.
  • Full-bleed bands actually span the grid. Eight pinnedBand blocks (cinema-pack AmbientBand, MediaPanel, PullInterlude, SceneCaption, ScenePlate, ScrubStory, StatementBand; blocks-house FullBleedInterstitial) now declare grid-column: 1 / -1 at their root as the contract requires. Visible change: inside a tome-ui .grid, these render edge to edge where they were previously squeezed to content width.
  • `@wabbit/tome-ui`: .grid declares reading-start / reading-end below 768px (aliased to the content column), so blocks placed on the reading column no longer collapse to a sliver on phones.
  • Every pack README gains an "Install into an existing Payload project" section and a peer table that matches package.json; blocks-core's README carries the full walkthrough.

0.16.xMinor

• Raise the react / react-dom peer floor to >=19.0.0 across the linked blocks family.

  Every pack advertised react: >=18.0.0 while @wabbit/tome-core, chrome, forms, dispatch, longform and readout all require >=19 — so the React 18 support the packs claimed was unreachable in any real Tome stack: no consumer could satisfy both halves of the graph. The advertised range was not a supported configuration, it was a range nobody could install into.

  Ruled 2026-09-01: the floor becomes the truth.

  Their devDependencies said the same thing from the other direction: react and @types/react pinned to ^18.0.0 while the root pnpm.overrides has pinned @types/react to 19.2.14 for months, so every pack has in fact been developed and tested against React 19 types the whole time. Those pins move to ^19.0.0 — a manifest correction, not a version change; the resolved tree is byte-identical.

  One coordinated bump for the family (these eleven are linked in .changeset/config.json, so they version together by design).

  Consumer impact: a consumer genuinely on React 18 can no longer install these packs. That consumer could not have had a working Tome install anyway — the kernel would have refused the same graph.

  Anyone on React 19 sees no change.

• dist now raw-Node loadable: relative specifiers get explicit extensions post-build.

  build gains && node ../../scripts/fix-dist-extensions.mjs --strict as its last step, joining the 13 packages that already ran it. tsup builds bundle: false and emits relative specifiers exactly as the TypeScript source wrote them — extensionless — which bundlers resolve and raw Node does not (ESM ERR_MODULE_NOT_FOUND; CJS worse, require('./x') finds the ESM .js twin and Node 22+ require(esm) then dies on that file's own extensionless import). Every consumer outside a bundler hit this: the payload CLI under plain node, generate:types, generate:importmap, ops scripts, codegen tools.

  No source changes, no API changes, and bundler consumers are unaffected — extensioned relative specifiers are universally resolvable.

  Two supporting changes made the wiring possible, both in repo scripts rather than package source. fix-dist-extensions.mjs now skips bundler-asset specifiers (.css, .module.css, .scss, fonts, images, shaders) by explicit extension allowlist instead of reporting them as unresolvable — that single gap is why the 13 prior adopters were exactly the 13 packages that ship no CSS, since --strict exited 1 on any package with a relative stylesheet import.

  Dotted MODULE names (./config.meta, ./x.variants, ./y.demo) are deliberately NOT treated as assets and still get .js/.cjs appended. assert-node-loadable.mjs gained the matching carve-outs so the new repo-wide CI gate reports real defects only: a resolution failure whose path lands under node_modules is a peer SKIP (next@15 has no exports map, so next/image fails as an absolute path), and a bundler-asset load failure is an environmental SKIP (CJS surfaces it as SyntaxError: Unexpected token '.' raised from inside the stylesheet).

  Verified before/after on four packages built one at a time: print 8 FAIL → 0, readout 22 FAIL → 0, ai 3 FAIL → 0, gamification 2 FAIL → 0 (its failure was the other signature — a directory import missing /index). cop was already clean on a fresh build, so the audit's "27 of 46 fail" figure includes at least one package whose local dist was merely stale.

• Manifest metadata: homepage, bugs, engines.

  All 46 publishable manifests were missing the three fields a consumer sees before any code (2026-09-01 sale-readiness audit §6). Metadata only — no source, no build, no runtime change.

  • homepage deep-links to that package README on GitHub (.../tree/main/packages/<dir>#readme). Without it a registry page links to the monorepo root and the reader has to guess which of 46 folders they want.
  • bugs.url points at the repo issue tracker, so a paying customer has a place to report a defect that is not email.
  • engines.node is >=22, matching the root engines and .nvmrc set the same day. This is a real floor, not decoration: CI on Node 20 could not expand the glob the block packs use for node --test, and a package installed on Node 20 fails at a runtime the installer cannot connect back to the version.

  The forcing function ships with the change: scripts/assert-manifest-metadata.mjs (root pnpm assert:manifest-metadata, wired into platform-discipline.yml beside assert:license-metadata) fails when any publishable manifest lacks description, repository.directory matching its own folder, homepage, bugs, engines.node equal to the repo floor, license, files or sideEffects. It reported 138 violations before this change and 0 after.

• README peer tables, and the gate that now requires them.

  Sixteen packages declared peerDependencies and documented them nowhere a reader could scan — in prose inside an install paragraph, in a transposed "compatibility matrix" with the peers as columns, or not at all. Docs only; no source, no manifest, no runtime change (the one manifest change in this PR, admin's sonner peer, has its own changeset).

  Each of the sixteen gains a ## Peer dependencies section generated from its own package.json — | Peer | Range | Required |, one row per peer, the range verbatim, no (optional) read from peerDependenciesMeta, plus one sentence on what is a real dependency rather than a peer and why the optional ones are optional. The worst omissions this surfaced: @wabbit/tome-core documented 2 of its 13 peers and left out both next and @payloadcms/richtext-lexical, which are required; @wabbit/tome-admin listed 5 of 20; @wabbit/tome-readout and @wabbit/tome-sc listed none.

  Eight block packs carried a hand-typed compatibility table that had drifted a full React major — still >=18 after the peer floor moved to >=19.0.0 — and none of the eight listed react-dom at all. Those tables are retired in favor of the generated one, with a line saying what they used to claim so the next reader does not reinstate them.

  The forcing function ships with the fix: scripts/assert-readme-contract.mjs now FAILS a package that declares peers without a peer table (a markdown table whose header row names a Peer and a Range column — the existing Optional? and Notes third columns still pass, so the thirty already-conforming READMEs were not touched). It is deliberately shape-only, not row-level: asserting that each row agrees with the manifest is the Tier 2 generation work.

  Verified non-vacuous by breaking one table's header and watching the gate fail, then restoring it. CONTRIBUTING.md's assert-script list — which said "five" while sixteen existed — and the three guides that describe this gate were corrected in the same pass.

• Updated dependencies [57875ba]

• Updated dependencies [b01ca1f]

• Updated dependencies [0836ef5]

• Updated dependencies [73081e6]

• Updated dependencies [090e984]

• Updated dependencies [73081e6]

  • @wabbit/tome-blocks-core@0.16.0

0.15.xMinor

• Route pack block links through the LinkAdapter instead of raw <a href>.

  LinkAdapter (0.14.0) shipped the seam; this connects it. 67 anchors across 55 renderer files in 10 packs now render through <TomeLink>, so a consuming site that registers a link adapter gets its route transition on pack blocks — previously impossible by construction, since a pack cannot import the consumer's transition component and the consumer cannot reach into a pack's render tree.

  New in `@wabbit/tome-blocks-core`: `<TomeLink>`, a component form of resolveLink(). resolveRichText() / resolveMedia() are functions because they turn a data value into content; a link _wraps children_, and the function form forces multi-line JSX through a children: prop.

  <TomeLink href={…}>…</TomeLink> is a drop-in for the <a> it replaces. It delegates to resolveLink(), so there is exactly one resolution path, and it stays directive-free so RSC pack renderers can use it without becoming client components.

  `LinkProps.href` is now `string | null | undefined`. Block data routinely carries an optional URL, and the raw <a href={undefined}> these calls replaced was legal markup. Narrowing it to string would have forced ~10 non-null assertions across the packs and changed behavior at each.

  NOOP_LINK_ADAPTER normalizes null to undefined so React omits the attribute — the unregistered path stays byte-identical to the pre-adapter markup.

  Behavior is unchanged for every consumer that has not registered a link adapter, which is currently all of them: resolveLink falls back to a plain <a>.

  Deliberately left as raw <a>:

  • EditorialFootnotes — its #fnref-* anchors are in-page backlinks. Client-routing them would play a page transition for a jump within the same document.
  • PricingPlans / PricingPlanCard — these already accept an injectable anchor component, a more expressive consumer mechanism that predates the adapter.
  • LogoSlider — a self-closing, childless target="_blank" overlay anchor. Always external, so the adapter would hand it straight back to the browser.
  • @wabbit/tome-longform — it has zero runtime dependencies and does not peer on blocks-core. Adding that edge to the layer graph is its own decision, not a sweep side effect.
• Updated dependencies [510036f]

  • @wabbit/tome-blocks-core@0.15.0

0.14.x

0.13.x

0.12.xMinor

• Neutralize pack-block base styling to the --tome-\* token system (extract-don't-delete; the brand treatment moved to @wabbit/tome-blocks-industrial-theme).

  • lms-pack: CourseCard.module.css rewritten tokens-only — the legacy safety-yellow CTA/featured strip, charcoal italic type, and hard-coded gray palette are gone from the base; the card now inherits the consuming site's theme.
  • catalog-pack: ProductGrid.module.css and CategoryStrip.module.css rewritten tokens-only (same extraction).
  • catalog-pack: FeaturedProduct, ProductCard, PriceTable, and InventoryBadge previously shipped NO styles and rendered as bare text stacks; each now has a neutral token-driven CSS module baseline (org-pack pattern), so they render designed-neutral on any consumer out of the box.

  Visual-breaking for consumers that relied on the baked-in industrial look: opt back in with @wabbit/tome-blocks-industrial-theme (one stylesheet import + data-tome-theme="industrial").

0.11.xMinor

• v1 hydration contract: new @wabbit/tome-blocks-catalog-pack/server subpath (import 'server-only').

  createHydratedRenderers({ getPayload }) returns server-component wrappers for product-card, featured-product, and category-strip — spread over the pack's static components map to overlay verified live @wabbit/tome-catalog fields on top of authored props, with zero client fetching and zero loading state. Per-block resolvers (resolveProductCardData, resolveFeaturedProductData, resolveCategoryStripData) are exported individually for use outside the block pipeline.

  The v1 matrix (verified against the real @wabbit/tome-catalog schema, not the original design guess): product-card/featured-product overlay title and description (from Product.excerpt) keyed by sku — price/comparePrice/image/CTA stay authored, since @wabbit/tome-catalog carries no pricing or stock field at all and neither block has an image render prop. category-strip overlays each item's label (from Category.name) keyed by slug, in one batched query — url stays authored and there is no live count (no render slot for one).

  inventory-badge is deliberately NOT hydrated in v1: @wabbit/tome-catalog models no stock/inventory field anywhere. price-table stays fully static by design (unchanged).

  product-grid is out of scope for this wave (its own 'use client' boundary).

  Access boundary: every hydration query runs overrideAccess: false with no user — anonymous-visible data only (publicReadActiveOnly restricts Products to status: active; Categories are always public). Layer absent, entity missing, or a thrown query all fall back to the untouched authored props — never a crash, never an empty hole.

  Static usage is completely untouched: every block still renders exactly the authored props by default, with zero peer dependency and zero behavior change, whether or not a consumer ever imports /server.

• sc-pack: dead CSS-copy tsup hook deleted (the pack ships zero CSS); its deliberately-lightweight profile (no meta.ts, rides tome-sc's token theme) is now documented in the source header with the convergence trigger (gallery browse surface needs meta).

  ./demo subpath rule: all 10 renderer packs now expose it — added to org/lms/catalog/sc packs plus agency-essentials (found missing in the consistency sweep); verified the demo import graph never reaches registering code.

• Documentation truth pass: all "hydrates from @wabbit/tome-X when present" claims across READMEs, block meta, bundle descriptions, render headers, and admin field descriptions are rewritten to the honest contract — these blocks are fully static today; the layer-presence flags are the seam for a future hydration wave (trigger documented in place). content-writer's RelatedPosts (auto mode) and Archive (collection mode) no longer render fake placeholder UI — the unimplemented modes render nothing and say so in the admin field description.

• Peer/dependency contracts now tell the truth. blocks-core: importing the root barrel no longer hard-crashes when the optional peers (@wabbit/tome-core, @wabbit/tome-catalog) are absent — productHooks registration is lazily guarded; NEW explicit registerBlockBundleProductType() export (root barrel + ./registry/productHooks subpath) for deterministic, format-safe registration from payload.config.ts (the import-time auto path no-ops under native ESM, which affects generate:types-visible product-type options — call the explicit API when composing catalog). chrome: next is now a required peer (>=14) — it was declared optional while next/navigation/next/link were hard-imported. readout: declares its real next peer; createReadoutBlocks({ accentPalette }) is now implemented (field-tree narrowing, dispatch's mechanism) instead of a documented no-op. blocks-lms-pack / blocks-catalog-pack: @wabbit/tome-core moves from hard dependencies to optionalDependencies, matching org-pack and the packs' own documented degrade-gracefully design.

• Every package now declares an explicit sideEffects field (38 added; motion/engine/forms already correct).

  Registration-bearing modules (render files' registerRenderer, blocks/*/index.ts defineBlock self-registration, widget register.ts files, productHooks, permission self-registrations, print templates, chrome built-in variants) are listed so bundlers can tree-shake everything else WITHOUT dropping import-time registrations — previously the field was unset, which blocked cross-module tree-shaking through the barrels entirely. Never blanket false on a package with registration or CSS.

• The clientization migration: 127 render components across seven packs dropped 'use client' — every file individually re-verified hook/handler/context-free before stripping; adapter-consuming static blocks converted to resolveRichText/resolveMedia.

  Exactly 20 of 155 renderers remain client, each for a verified reason (state/effects/motion, or a documented client-shell composition contract), enforced by the new assert:rsc-boundaries CI script (per-pack manifest; fails loudly if a directive creeps back or a count drifts). Every renderer-bearing pack now exports ./render/register (renderers map + explicit registerRenderers()), aggregated by @wabbit/tome-blocks's new registerAllRenderers() — the format-safe registration path for server component graphs, where the legacy import-time barrel registration never executes (that legacy path is unchanged and remains supported until the spec's deprecation trigger).

  RenderBlock is rewritten server-safe: directive-free, optional components prop (RenderBlocks parity) → registry fallback, dev warn-once naming both fixes on a miss; its docs state the explicit-registration prerequisite. Rendered output is byte-identical everywhere; behavior change only for consumers rendering migrated blocks in RSC WITHOUT a provider or registration — they get the documented warn + graceful degradation instead of silent client bundling.

• Updated dependencies [26dfa07]

• Updated dependencies [36e537a]

• Updated dependencies [36e537a]

• Updated dependencies [36e537a]

• Updated dependencies [a93f478]

• Updated dependencies [5f78397]

• Updated dependencies [5f78397]

• Updated dependencies [aef2725]

  • @wabbit/tome-blocks-core@0.11.0

0.10.x

0.9.x

0.8.xMinor

• Batch 6 (domain packs) + Batch 7 (primitives + usage manifest) of the 2026-06-27 inserter/variant architecture — audit + usage/intent authoring (Decision 4).

  The domain packs pull from distinct collections (courses / products / members / fleet), so per the spec they stay schema-distinct — this is metadata, not consolidation.

  • Authored usage/intent metadata on all 25 domain blocks: LMS (course-card, lesson-list, progress-bar, quiz-summary, instructor-card, enrollment-cta), Catalog (product-card, product-grid, category-strip, price-table, inventory-badge, featured-product), Org (division-card, member-card, member-grid, event-calendar, event-list-item, org-chart, document-link, campaign-banner), SC (fleet-summary, signal-hero-sc, task-force-roster, op-briefing-panel, rsi-handle-card). Also authored usage on the 9 free extras-primitives (section, spacer, grid, stacking-wrapper, content, text-block, code, section-header, content-two-column — in @wabbit/tome-blocks-extras, already bumping).
  • Audit (clean): no dual-mechanism drift, no slug-splits, and the card-vs-grid / item-vs-calendar pairs are genuine single-object-vs-array shape differences (NOT layout variants) — correctly kept as separate blocks. The relationship is encoded in each block's usage.pairsWith/avoidWhen so an assembling agent picks the right one.
  • `buildUsageManifest` verified end-to-end (@wabbit/tome-blocks-core, Batch 0): builds a sane manifest from the now-authored descriptors — byRegister (application / editorial / marketing-landing / structural / dossier), byPageType, variant flow-through, and unauthored tracking. The consumer-side manifest generation + exposure to assembling agents is a live-run wiring step.

  Note: the domain packs use the inline-meta pattern (BlockMeta passed to defineBlock in each block's index.ts), so usage was added there. Ships in the linked family's 0.8.0 minor.

• Updated dependencies [249b670]

  • @wabbit/tome-blocks-core@0.8.0

0.7.x

0.6.x

0.5.xMinor

• Linked cohort version alignment (no functional change in this package).

0.4.x

0.3.xMinor

• Sprint 3 blocks split — v0.2.0

  Extracted the Tome blocks monolith (@wabbit/tome-blocks) into independently publishable bundle packages. Each bundle is independently installable, tree-shakeable, and testable in isolation.

  New packages (all v0.2.0):

  • @wabbit/tome-blocks-core — registries, defineBlock/defineBundle, variants, thumbnails, admin components (BlockPicker, VariantPicker)
  • @wabbit/tome-blocks-marketing-starter (free) — 8 marketing blocks: Hero, FeatureHero, CTA, LogoSlider, Pricing, Testimonial, FAQ, Banner
  • @wabbit/tome-blocks-content-writer (free) — 10 editorial blocks: Blog, Archive, PostHero, RelatedPosts, EditorialOpener, EditorialBridge, EditorialSidenote, EditorialFigure, EditorialColophon, EditorialFootnotes
  • @wabbit/tome-blocks-agency-essentials (starter) — 10 agency blocks: About, Contact/Form, Gallery, Media, SplitView, Stat, StatBar, TeamRoster, Timeline
  • @wabbit/tome-blocks-editorial-pack (pro) — 8 editorial blocks: DataHero, Feature, InfoPanel, MessagePanel, MetricStrip, SplitPanel, StatusBoard, TextReveal
  • @wabbit/tome-blocks-signal-theme (pro) — 33 Signal narrative blocks
  • @wabbit/tome-blocks-lms-pack (pro) — scaffold for LMS blocks (Wave 3)
  • @wabbit/tome-blocks-catalog-pack (pro) — scaffold for catalog/ecommerce blocks (Wave 3)
  • @wabbit/tome-blocks-sc-pack (niche) — scaffold for Star Citizen blocks (Wave 3)
  • @wabbit/tome-blocks-extras (pro) — 47 residual blocks (heroes, layout, content, marketing)

  @wabbit/tome-blocks is now a meta-package that re-exports all bundle packages and provides registerAll(blockRegistry, bundleRegistry) as a convenience function.

  Render colocation: All 113 render .tsx components migrated from the monolith into their owning bundle packages (./render subpath on each bundle).

  Breaking changes (internal):

  • @wabbit/tome-blocks/blocks and @wabbit/tome-blocks/bundles subpaths removed (were Sprint 2 shims)
  • packages/blocks/src/render/ category index files removed (replaced by per-bundle ./render subpaths)

  Migration:

  // Before (monolith singleton, all blocks loaded)
  import "@wabbit/tome-blocks";
  
  // After (explicit registration, tree-shakeable)
  import {
    blockRegistry,
    bundleRegistry,
  } from "@wabbit/tome-blocks-core/registry";
  import { register } from "@wabbit/tome-blocks-marketing-starter";
  register(blockRegistry, bundleRegistry);
  
  // Or use the meta-package convenience function
  import {
    blockRegistry,
    bundleRegistry,
    registerAll,
  } from "@wabbit/tome-blocks";
  registerAll(blockRegistry, bundleRegistry);

• Updated dependencies [f2202cd]

  • @wabbit/tome-blocks-core@0.3.0