Blocks Agency Essentials

0.47.xMinor

• contact can print a short caption under its link-out button.

  The estimate variant gains an optional primaryAction.caption ("Opens our scheduler in a new tab"), rendered as data-contact-action-caption in the actions row, and only when the button itself renders.

  Unset or blank, the markup is identical to before; the existing contact golden and a new blank-equals-unset test hold that. Schema: one new optional localized text column on the block (primaryAction.caption), so SQL sites need a migration; Mongo sites need none.

0.46.xMinor

• The gallery block gains an offset layout: one large lead image beside smaller ones.

  gallery gains an opt-in offset variant: one large lead image beside small ones with bold-lead captions (hooks data-gallery-offset, data-gallery-lead, data-gallery-small, data-gallery-caption). The layout-only admin fields hide for it.

  Every other variant renders exactly as before.

• Fixes the gallery image height default, which was not one of its own options.

  Fix: the gallery element's imageHeight select defaulted to 21rem, which was not one of its options (12rem to 32rem in 2rem steps), so any gallery element saved without an explicit height failed Payload validation ("21rem is not a valid enum value for path imageHeight"). Present since the pack's extraction.

  21rem is now an option between 20rem and 22rem; the default stays 21rem, which is also the renderer's own fallback height (--_item-height: 21rem), so stored blocks and new ones render exactly as before. A new schema test checks that every select and radio default in the pack is one of its options.

  Consumers: regenerate Payload types (the imageHeight union gains '21rem'); with a SQL adapter the enum gains one value.

0.43.xMinor

• stat and stat-bar can now cite the record behind each figure, and stat gains a sourced ledger variant.

  Each stat row takes an optional source group (statSourceGroup(): serial, label, href). A stat with a source prints p[data-stat-source] with span[data-stat-source-serial] ("No. 2026-02"), a middle dot and the label as a link: under the description on stat, under the row on stat-bar.

  Two block-level fields on both blocks: requireSource (off by default) drops any stat with no source label or link and hides the block when none is left, so a figure never shows without the record it cites; sourcePrefix (default "No.") is the word before each number. A stat without a source renders as before.

  The new sourced variant of stat is a ruled strip for such figures: a label cell (data-stat-label-cell) holding the headline and, on a demo, sampleLabel as span[data-stat-sample][data-compliance-label], then data-stat-cells of data-stat-cell, each led by its source line, then p[data-stat-value] and p[data-stat-caption]. It prints a stat's suffix only when set; the field still defaults to "%", so clear it.

  sampleLabel shows in the admin for sourced only.

  Additive change to existing markup: every stat root now carries data-block-variant beside data-variant (the public variant hook), in all variants. The block's stored-render goldens were cut from the pre-change renderer and differ only by that attribute.

  stat-bar has no change to its markup. The block catalog lists the new variant.

0.42.x

0.41.xMinor

• team-roster people can put a button after the statement tile with the new statement.link.

  statement.link (label, href) shows only with both halves and is off by default, so stored documents without it render byte-identical. The button carries data-person-statement-link.

  contact estimate gains signOff.order: 'name-first' (default line-first): the name, then the line, with data-contact-signoff-order="name-first" on the sign-off. Unset or line-first renders byte-identical.

0.39.xMinor

• Two opt-in additions for a business that shows its coaches and answers by the hour.

  team-roster people gains people[].tag (a short tag beside the name, data-person-tag), people[].credentialTags[] (chips in a row under the fact, data-person-credentials and data-person-credential-tag) and a block-level credentialNote (set after each person's chips, data-person-credential-note). All three are optional, default-free and shown only for the people variant; empty values render nothing.

  contact estimate gains promiseOpen and promiseClosed, each a { text } group. With either set, the promise sentence renders as three copies marked data-when-neutral (from promise.text), data-when-open and data-when-closed, and the block's stylesheet chooses by <html data-tome-open="true|false">, the attribute chrome writes from the site's hours.

  With the attribute absent the neutral copy shows, so a site without hours never reads "closed". A side left empty falls back to the neutral text.

  Stored documents that set none of the new fields render byte-identical markup (pinned by golden tests).

  Purely additive: no peer is added or tightened, no field has a default, and nothing changes for a site that sets none of them.

0.38.xMinor

• The form block gains a signup-band variant, and split-view gains part hooks.

  signup-band is a dark closing band: eyebrow, heading (an h2), body, the form slot, a promise line and a secondaryLink (label and link). The new fields show only for this variant, carry no default, and every part renders only when set.

  The root carries data-block-variant="signup-band" and data-band-tone="solid-dark"; the parts carry data-band-meta, data-band-title, data-band-body, data-band-form (on the form slot, which keeps data-form-slot and data-form-id), data-band-promise and data-band-link. A form with one field lays its field and button on one row.

  Existing variants render exactly as before.

  split-view marks a text column's content [data-sv-text] and a media column's figure [data-sv-media], next to the existing [data-sv-ratio], so a theme can address the two parts of a pair.

  split-view gains structure hooks and a 7-5 ratio: [data-sv-inner] on the columns' grid, [data-sv-col="media|text"] on each media or text column, and [data-sv-media-side="start|end"] on the root when the block has a media column (start when the media column comes first). The asymmetryRatio select gains 7-5 and its mirror 5-7, with the matching 7fr 5fr / 5fr 7fr layout.

  The signup-band variant marks its inner wrapper [data-band-inner] and the column holding the form slot and the promise [data-band-action]. Stored renders are unchanged apart from the new attributes.

0.37.xMinor

• The contact estimate variant can close a page beside a face: a portrait, a motif, a link-out button and a sign-off.

  Four optional fields, shown only for estimate and without defaults, so existing documents render the same markup as before:

  • media (image, alt, label): a portrait beside the note. Alt text is required once an image is set; the label renders only with the image.
  • motif (image, alt): a small decorative image, alt required with the image.
  • primaryAction (label, href, newTab): a link-out button rendered through TomeLink, so a new-tab link gets data-new-tab and the hidden "(opens in a new tab)" hint. It is separate from the tel-only callAction.
  • signOff (line, name): a closing line and a name at the end of the note, above the form.

  The images relate to a new mediaCollection option (default 'media'). New theme hooks: data-contact-action, data-contact-media with data-compliance-label for its label, data-contact-motif, data-contact-signoff, data-contact-signoff-line, data-contact-signoff-name.

  The form area is unchanged: it takes a form you host through formSlot or the form builder's cardForm.

0.36.xMinor

• enhanceReserveBands now accepts an opening-hours option, so a reservation band's sample time chips and time select respect the venue's hours.

  Call enhanceReserveBands(document, { hours, listWindows, schedule?, lastSeatingMinutes?, lastPickupMinutes?, maxSlots?, notes? }) with a @wabbit/tome-local OpenStateSource and its listWindows (passed in, so this package takes no new dependency). Chips and select options outside the chosen date's hours, or already past today, hide; a note says when the date is closed or no sample time is left; a date still on today with no time left moves to the next open date.

  The existing enhanceReserveBands(root, now) call is unchanged. The contact reserve group gains two optional localized fields, closedNote and noTimesNote, for the notes' wording; unset, a neutral default shows.

• Phone links in the contact, high-impact-hero and local-logistics code now use the shared core tel: helper, so a site can qualify national numbers to E.164.

  The exported toTelHref helpers (and resolveContactValueLink, resolveInlineCall) accept an optional { defaultCallingCode }. The high-impact-hero reads defaultCallingCode from the render context passed to RenderBlocks({ context }); without it, hrefs stay digits-only as before.

  Requires @wabbit/tome-core 1.22.0 or later as a peer.

• The contact renderer reads defaultCallingCode from the host's render context (RenderBlocks({ context })) for its contact rows, the estimate and reserve call buttons, and reserve call actions, so tel: links are E.164 when the site sets a default.

  Unset, links are unchanged.

0.35.x

0.34.xMinor

• contact estimate: the form slot is marked whatever fills it, and the band's padding no longer doubles.

  • The slot now always carries data-contact-form-slot. Its data-form-id came from cardForm only, so a form passed as formSlot (a tome-forms form, for instance) left it unmarked and theme rules keyed on [data-form-id] never reached it. New optional prop formSlotId: the hosted form's id, written to data-form-id (it wins over cardForm when a formSlot is passed). A site that wrapped its hosted form in its own data-form-id element can drop the wrapper.
  • The block padding (--tome-section-py) moves from .estInner to the section, the element that is the band. On the inner element it stacked with any padding a theme gave the band, so the Counsel intake ran double space above and below. Without a theme band rule the spacing is unchanged.
• team-roster people sits on the page grid, and its columns are a token.

  • The section kept its children on 1 / -1, so the header and the portrait grid ran edge to edge with no page gutter. The section still paints full-bleed, but it now subgrids the page grid and places the header and grid on the content lane (content-start / content-end), like the pack's other blocks.
  • New token --tome-roster-people-cols: the grid's column count. Defaults are 2 on phones, 3 from 640px and 4 from 1024px (it was 3). The statement tile and the empty-cell rules are unchanged: across the row on phones, across two cells from 640px, one cell from 1024px, where the empty cells appear. The demo's emptyCells [5, 8] now open the start and end of row two.
  • The header group carries hooks: data-block-header on the group, data-block-eyebrow (section label), data-block-heading (h2) and data-block-subtext.

  The member variants are unchanged.

• Narrow-screen rules that never fired now fire.

  These blocks wrote their phone layout as an unnamed @container query, but nothing around them declares a size container (not tome-ui, the blocks core or the starter), so the rules never matched: the high-impact-hero split and default layouts never stacked on phones. Declaring the container on the block root would not work either, because size containment turns a subgrid root into a plain grid and drops the page-grid lines its children sit on.

  The rules are viewport queries now, at the same breakpoints; the blocks are full-bleed, so the viewport is their width.

  • @wabbit/tome-blocks-marketing-starter: high-impact-hero (two columns stack to one, large headline sizes step down, at 768px and below).
  • @wabbit/tome-blocks-extras: BlogHero, ChapterHero, CustomHero, ImageHero, LowImpactHero, MediumImpactHero, PageHero, StudyHero, TypographyHero (768px) and SectionHeader (640px).
  • @wabbit/tome-blocks-content-writer: PostHero (768px).
  • @wabbit/tome-blocks-agency-essentials: SplitView stacks at 768px.

  Above those widths nothing changes.

0.33.xMinor

• New venue variant for high-impact-hero and new reserve variant for contact, for places people visit.

  • `high-impact-hero` `venue`: the venue name set very large, with a meta line, one line and one action. The background photo sits either behind the copy, over a theme-set scrim (--tome-hero-scrim), or full width above it. It is chosen by the new optional venue.mediaPlacement field (behind, the default when empty, or above). Hooks: data-hero-media-placement, data-hero-scrim, data-hero-meta, data-hero-name and data-hero-line, plus the existing data-hero-media and data-hero-actions.
  • `contact` `reserve`: a dark booking band that links out to the venue's booking provider. It has a GET form for party, date and time (labels partyLabel, dateLabel and timeLabel, default "Party", "Date" and "Time"), built from an editor-written reserve.urlTemplate with {party}, {date} and {time} tokens, and works without JavaScript when each token is a whole query value. Under the form come labeled sample-time chips (sampleSlots[] and sampleSlotsLabel, never live availability), then an "Or:" row (lead-in altLabel, default "Or:") with a tel: call action and altActions[] (link, call, or order, which opens the ordering drawer). Every label is optional and localized; empty, it renders the English default. With no provider set, the form hides and the band leads with its actions; contact rows render as a facts row. eyebrow and callAction are now also shown for reserve.
  • New subpath `@wabbit/tome-blocks-agency-essentials/reserve`: the band's pure URL helpers, plus enhanceReserveBands(), an optional, framework-free client enhancement. It fills today's date, keeps the chips in step with the form, and fills templates the GET form cannot carry whole. The renderer stays a server component.

  All new fields are optional, variant-gated and have no default value, so existing content renders byte-identical.

0.32.xMinor

• Counsel v1 agency pieces: a people variant for team-roster and an aside for the contact estimate variant.

  `team-roster` `people`: a statement tile, then tall portrait cards. The variant has its own optional fields, shown only when it is picked: people[] (name required, role, credential, fact, photo, photoLabel), statement (text, label) and emptyCells (1-based positions of deliberate empty cells, counted across every cell including the statement).

  Each card shows the name, role, a credential line and one personal fact in italic. photoLabel renders on the portrait as data-compliance-label, only when there is a photo.

  Empty cells are aria-hidden and appear from 1024px, where the grid has three columns. Hooks: data-block-variant="people", data-roster-statement, data-roster-person, data-person-name, data-person-role, data-person-credential, data-person-fact, data-roster-empty.

  members[] and epigraph are now hidden in the admin for people only. The other four variants render exactly as before.

  `contact` `estimate`: an optional aside group (label, plus a body of a few short paragraphs in limited rich text, bold and italic only), for a note such as a confidentiality notice. It renders last in the intro column as <aside data-contact-aside>, named by its label.

  With no label and no body text, the output is unchanged.

0.31.xMinor

• Groundwork v1.1 block fields for the quick-ask hero and the estimate contact band.

  `high-impact-hero` `quick-ask`: proofLine gains an optional proofLead text field, rendered as a <strong data-hero-proof-lead> before the proof text (for example "Next opening:"). Fixed: at phone widths the status dot could wrap onto its own line away from its text.

  The proof line is now inline flow, and the dot shares a no-wrap run (data-hero-proof-start) with its first phrase: the lead, or the first word of the text. The rest of the line wraps normally.

  With no lead and no dot, the markup is unchanged.

  `contact` `estimate`: two optional text fields. eyebrow is a small meta-voice kicker above the heading (data-contact-eyebrow).

  formNote is a short meta line beside the form card heading (data-contact-form-note). When it is set, the heading and note share a wrapping head row (data-contact-card-head).

  When both fields are empty, the output is unchanged.

0.30.xMinor

• The contact block's estimate variant takes an optional cardHeading, rendered at the top of the form card with a [data-contact-card-heading] hook.

  The field is shown only for estimate and renders nothing when empty, so existing estimate blocks are unchanged.

0.29.xMinor

• Contact gains an estimate variant (a two-column request band with a form card), and phone and email values in every variant now render as tel: / mailto: links.

  Additive: the new fields are optional, carry no defaults and appear in the admin only when estimate is selected. Adding them to a Payload config adds their columns, so run your usual migration.

  • Links. A contactBlocks[].value that is exactly one email address renders as a mailto: link, and one that is exactly a phone number (7 to 15 digits, phone punctuation only) as a tel: link. Every other value, including addresses, year ranges and dates, renders as text, as before.
  • `estimate` variant. Left: the richText heading and intro, a promise (value shown as a big numeral, unit, text), a callAction (prompt, label, phone), hours[] (days, time, tabular figures) under an optional hoursLabel, and areas[] (name, rendered as chips) under an optional areasLabel. Right: a form card around the same data-form-id slot the form block renders, and an optional responseLine. Phones stack heading, form, then call, hours and areas.
  • Form picker is opt-in. By default the block still relates to no collection. Register it with contactBlock.block({ formsCollection: 'forms' }) to add a cardForm relationship; the ContactBlockConfig type is exported.
  • Filling the slot. Pass your site's form to the renderer as formSlot (ContactProps is exported from ./render); without it the slot stays empty, like the form block's.
  • Theme hooks: data-block-variant="estimate", data-contact-intro, data-contact-promise, data-contact-promise-numeral, data-contact-form-card, data-form-id, data-contact-response-line, data-contact-side, data-contact-call, data-contact-hours, data-contact-areas, data-contact-chip, and data-contact-link="phone|email" on detected values. Every contact variant root now also carries data-block-variant.

0.28.x

0.27.x

0.24.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 10 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.
  • No client renderers. 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.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.

• Fix a hydration mismatch in Testimonial and adopt the shared UTC-pinned date formatter across five renderers.

  @wabbit/tome-blocks-marketing-starter's Testimonial is a 'use client' component and rendered its publication date with a bare new Date(iso).toLocaleDateString(). That resolves against the RUNTIME locale and the RUNTIME time zone, so the server produced one string and the browser produced another and React reported a hydration mismatch on the block.

  The 2026-07-11 audit flagged it; it was still there on 2026-09-01.

  The same bare call sat in four server renderers — blocks-editorial-pack's MetricStrip and StatusBoard, blocks-agency-essentials' TeamRoster (twice) and Timeline. No hydration mismatch there, but the rendered output changed with the deploy host's locale and offset, which is its own kind of wrong.

  All six call sites now use formatDisplayDate from @wabbit/tome-blocks-core/utilities/formatDisplayDate with an explicit locale: 'en-US', a numeric M/D/YYYY dateStyle and timeZone: 'UTC'. The numeric shape is deliberate: it is byte-identical to what a US-locale runtime already produced, so this fixes the determinism without silently restyling anyone's dates.

  Every pack already declared @wabbit/tome-blocks-core, so no dependency changes.

  Shipped with its forcing function: a no-restricted-syntax rule in eslint.config.mjs warns on bare toLocaleDateString/toLocaleString/toLocaleTimeString in every packages/*/src/**/*.tsx and every block pack's render/ directory, and points at formatDisplayDate and at blocks-gallery's ADDED_AT_FORMATTER as the two accepted shapes.

• 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
  • @wabbit/tome-blocks-extras@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
  • @wabbit/tome-blocks-extras@0.15.0

0.14.x

0.13.x

0.11.x

0.10.x

0.9.xMinor

• layoutGrid nesting capability audit + render hardening (Wave 2).

  Tags the nestable capability flag (and a minColSpan floor for internally-wide blocks) across the offered blocks in the core packs (extras, marketing, content, agency, editorial, signal), so the layoutGrid container's derived child allowlist — blockRegistry.getNestableBlocks() — is populated rather than empty. Excluded by design (left non-nestable): containers (editorialSpread, editorialSection, split-view, stacking-wrapper, grid, layoutGrid) to enforce the one-level depth cap; full-bleed heroes/banners (band-owners); and inline Lexical blocks (not block-level grid children).

  minColSpan: 2 is set on the internally multi-column blocks (card-grid, bento-section, content-two-column, signal-stats, signal-image-grid, signal-data-table) so they cannot be crammed into a single-column cell.

  Also hardens LayoutGrid's child↔span pairing: children are now flattened with null slots preserved (instead of React.Children.toArray, which drops nulls), so an unrenderable child can no longer shift every later child's span metadata onto the wrong block. Adds a dev-mode warning when the consumer's child count doesn't match the item count.

  @wabbit/tome-blocks-core is bumped to release the layoutGrid platform primitives merged earlier but never published (the registry's 0.8.0 predates that merge): BlockMeta.nestable/minColSpan, withChildPlacement, the reserved _colSpan/_rowSpan/_order field constants, and blockRegistry.getNestableBlocks(). Without this, a consumer wiring the layoutGrid allowlist would call a getNestableBlocks that its installed blocks-core@0.8.0 does not have.

  Domain packs (lms, catalog, sc, org) are intentionally deferred — they compose into their own domain layouts and can opt in when a consumer needs them.

• Updated dependencies [c7d0afc]

  • @wabbit/tome-blocks-core@0.9.0
  • @wabbit/tome-blocks-extras@0.9.0

0.8.x

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