Ui

Before, the controller left the whole in-view block alone, so a tall block that starts above the fold (a menu page's cards) never animated its items. The block root and any item already on screen are still never hidden; the no-JS, reduced-motion, opt-out and self-animating (data-tome-motion="self") guarantees cover the per-item path too.

Touch browsers keep :hover on the last element tapped, so a tapped Button (a menu toggle, for example) stayed painted in its hover state until the user tapped elsewhere. The hover rules for every variant now sit inside @media (hover: hover), so they apply only where a real pointer can hover.

Mouse and trackpad behavior is unchanged.

What you install: one compiled .js (ESM) and .cjs (CommonJS) file per source module, its .d.ts / .d.cts declarations, and the stylesheets, fonts and other assets a package already shipped. Every JavaScript module opens with a comment naming the package and its license: /*! @wabbit/<package> — © Wabbit, LLC. Wabbit Tome Commercial License (see LICENSE.md). Not for redistribution. */.

The .map files and the sourceMappingURL comments that pointed at them are gone, which roughly halves the size of each tarball.

Debugging: the code is still unbundled and unminified, one readable file per module, so a stack trace points at real code with real names. Line numbers in a stack trace are one higher than before, because of the banner line.

A 'use client' directive stays the first statement of its module (the banner is a comment above it), so React Server Component boundaries are unchanged.

No API change, no runtime behavior change, and nothing to do on upgrade.

In @wabbit/tome-blocks-gallery, the source snapshots extractGallerySource writes from an installed pack leave out the license banner line, so a component or config snapshot starts at the code and a paid block's preview shows its first 15 lines of real code.

Under Industrial, the starter's Instrument Serif headings fell back to Instrument Sans. The four font families are now flagged { "reresolve": false } in tokens/layer2-aliases.json: still verified and aliased at :root, no longer re-declared in the block.

The 29 color and radius aliases are unchanged.

Rule for theme authors: a theme that changes fonts declares each --tome-type-* next to the matching --font-* on its own selector (for example --tome-type-display: var(--font-display);). assert-theme-conformance now fails a theme stylesheet that sets a --font-* slot without the matching --tome-type-* under the same selector.

--tome-color-surface-solid-dark now reads an optional ThemeConfig-owned --surface-solid-dark input (for example the site's ink); unset, it stays black. A new --tome-color-primary-on-solid-dark token is the brand accent for text on that surface.

It lifts primary's OKLCH lightness to a 0.66 floor with hue and chroma kept, which clears 5.5:1 on near-black across hues; an already-light primary passes through unchanged. A color-mix fallback covers engines without relative color syntax, and a site can pin an exact value with --primary-on-solid-dark.

The starter's oxide had measured 3.85:1 on black and 3.39:1 on its ink, against AA's 4.5:1. footer11's column labels use the new token, falling back to primary on a tome-ui without it.

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.

Measured live on starter.wabbit.com with a canvas-based contrast parser walking every rendered text node: the worst pairs sat at 1.00–1.03:1 — near-black text on a near-black surface, copy that renders but cannot be read. Nothing in CI could see it, because every unit test and every route smoke passes with perfectly invisible text.

This is the second time this bug family has shipped. The first sweep added --tome-color-on-solid-dark (blocks-lms-pack 0.12.1) and fixed chrome, lms-pack and catalog-pack; the themed packs were missed.

This closes the rest and adds the tokens whose absence is why the misuse kept spreading.

Three mechanisms, one root cause

1. Split pairs. Blocks paired --tome-color-card — not a house token at all; the house name is --tome-color-surface — carrying a DARK literal fallback, against --tome-color-foreground, which every themed consumer does define, carrying a LIGHT one.

A fallback pair is only safe when both sides fall back together. The same shape appeared as cross-family pairing (surface, the CARD family, paired with foreground, the PAGE family) and as clobbering: a band setting color: background on itself while its children hardcoded their own color: foreground, which wins. longform had a third variant — it read --tome-color-muted-foreground 32 times and --tome-color-muted 3 times, and neither has ever been a house token, so the entire muted tier silently fell through to currentColor and inherited whatever ink an ancestor happened to have.

2. Alpha-dimmed text. opacity: 0.4–0.9 on a label, and color-mix(<colour> 30–70%, transparent) as a color:, composite against whatever happens to be behind them, so the ratio is unknowable at author time.

Worst measured: 1.46:1. Several were an ancestor opacity aimed at a rule that dimmed the real text in the same container along with it.

3. Status and brand colors used as text. warning/success/error/ destructive are FILL colors, tuned to be painted as a badge with an ink on top.

Used as color: the default amber measures 2.13:1 and the green 2.82:1. Brand hues have the mirror problem: --tome-color-primary as text is fine on the page (near-black by default, 5.5:1 even under the starter's oxide theme) but becomes 2.22:1 inside a band whose fill the consumer chooses.

New in @wabbit/tome-ui

• `--tome-color-{success,warning,error,destructive,info}-text` — the missing text-weight companions. Literals with inverted [data-theme="dark"] values, each pinned to clear 4.5:1 against both --tome-color-background and --tome-color-surface. info never had a fill token either, which is why packs reached for primary. Rule of thumb: warning paints a box, warning-text writes a word.
• `--muted-foreground` retuned (hsl(215 16% 47%) → hsl(215 20% 38%) light, 65% → 72% dark). That token is --tome-color-on-surface-muted, the tier every pack uses for captions, labels, metadata and table headers, and at the old value it reached only 4.27:1 on --card. The entire secondary text tier platform-wide sat just under AA — which is also why packs kept reaching past it for something with more presence. Standalone default only.

Because these are literals rather than Layer 1 aliases, @wabbit/tome-cop restates them: a pack that is dark without being [data-theme="dark"] would otherwise inherit the light values.

Fix shape, per pack

dispatch, readout, blocks-signal-theme are permanently dark by product identity. Each owns a pack-scoped surface/ink SET (--dispatch-*, --readout-*, --signal-*) with internally consistent dark defaults compiled into every block module as inline fallbacks.

No rule in these packs reads a house surface or text token for a panel, so no consumer theming can split the pair. The house surface-solid-dark/on-solid-dark pair was rejected here for a stated reason: it is one flat pure-black surface with a single ink, and these packs need a layered palette. tome-cop drives all three sets so its theming still applies. signal-theme's accents split into three roles — identity fill, lightened on-panel text, and per-hue ink for accent fills — because one value cannot serve both a dark panel and a light article.

longform, content-writer, editorial-pack, marketing-starter, agency-essentials, extras follow the ambient theme and are fixed with the house vocabulary: correct pairs (surface/on-surface, background/ foreground, primary/on-primary), the new -text weights for status copy, and solid ink steps in place of alpha. Painted bands publish their own ink as a local --_on-band, and brand/status text reads `var(--_on-band, <its normal

• dispatch: demo content rewritten as an incident-war-room / ops-bridge scenario (SEV-1 bridge traffic, failover runbooks, recovered security-report transcript) plus neutral original fiction for inherently fictional variants (Relay Station Aurelia personal log, SV Aurelia ship log). Config field-description examples de-lored (old client- and universe-specific labels → neutral equivalents).
• readout: all 9 blocks' demo props rewritten as business-operations console data (deployment phases, sprint objectives, service status, perimeter traffic, on-call roster, infrastructure asset cards). Config examples de-lored.
• blocks-signal-theme: demo props for the 33-block pack rewritten as an original search-and-rescue expedition serial ("Operation Long Wake", SV Aurelia, Meridian Reach) with zero client or SC references; config examples de-lored. Pack positioning (SC-tier bundling per OQ-4) unchanged.
• blocks-extras / blocks-content-writer: Custom Hero and Post Hero meta descriptions stop name-dropping the client; "Callsign" field descriptions neutralized to "Author name or handle"; provenance comments neutralized.
• blocks-core: BLOCK_CATALOG mirror entries refreshed for custom-hero and post-hero only; registry comment neutralized.
• blocks-gallery: SourceBadge label for the vngd source value now renders "Legacy" (enum value unchanged).
• accounts / core / lms / ui / org / admin / motion / longform / cop / blocks: internal provenance comments, shipped CSS comments, and consumer-visible field descriptions that named a specific client replaced with neutral "upstream" phrasing; longform package description de-lored. Historical CHANGELOG entries left untouched.

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.

longform: VISIBLE CHANGE (hence minor) — its local ACCENT_MAP had drifted from the canonical palette its own header declared as the migration target; completing the migration shifts longform block accent hues slightly, makes borders match text, switches backgrounds from solid pale to translucent color-mix, and longform now honors --cop-accent-* theme overrides for the first time (parity with dispatch/readout). A visual pass on Callout/KeyFacts/DataTable-class blocks is recommended before adopting in a styled site.

Consumer pages no longer clientize the full navbar/footer variant set by importing the renderers. blocks-extras gains a ./render/shared subpath (hero background layer + link-list, hook-free so it serves RSC and client call sites) adopted by the four hero blocks that had verbatim copies.

@wabbit/tome-blocks-core now ships a standalone Node ESM CLI at scripts/emit-docs-manifests.mjs that emits per-package documentation manifests (index.json, packages/<slug>.json, changelog.json) by reading what packages already carry — READMEs, the payload-free <pkg>/meta block-usage barrels, package.json exports maps, and CHANGELOG.md. It is the docs-pipeline sibling of the gallery source extractor and is consumed by host sites at prebuild: node node_modules/@wabbit/tome-blocks-core/scripts/emit-docs-manifests.mjs --output-dir <dir> --scope <scope.json>.

To let the emitter import block metadata uniformly without dragging Payload config into a build script, the ./meta payload-free subpath (BlockMetaEntry[]) is extended to the remaining offered blocks packs — agency-essentials, catalog-pack, lms-pack, org-pack, and signal-theme — mirroring the existing editorial-pack / marketing-starter / content-writer / extras barrels. Each block's BlockMeta was relocated verbatim into a payload-free sibling meta module and re-imported by its block config; no meta values changed.

Every supported-core package additionally adds CHANGELOG.md to its published files array so the next publish cascade ships changelogs the emitter can read from installed tarballs at prebuild.

Existing consumers ride the byte-identical named-token facade unchanged.

resolveBreakoutWidth/breakoutWidthField preserved as a byte-identical facade (longform/editorial/readout unchanged).

The closed indicator ([data-state='hidden']) now has an explicit resting opacity: 0 + pointer-events: none, so it stays hidden once its exit animation (which has no forwards fill) completes instead of reverting to the base opacity: 1.

• @wabbit/tome-blocks-marketing-starter: add ./blocks/* subpath exports for the 8 block directories (banner, cta, faq, feature-hero, high-impact-hero, logo-slider, pricing, testimonial). Source already shipped these as directories with index.ts; the exports map only declared . and ./render, so any consumer of a specific block from the registry got a module-not-found error. Path-aliasing bypassed the exports map, hiding the gap.
• @wabbit/tome-core: add ./auth/collections/Roles (capital R) alongside the existing lowercase ./auth/collections/roles. Both resolve to the same file (./dist/auth/collections/Roles.{js,cjs,d.ts}). The source file is Roles.ts; the exports map declared only lowercase, so consumers using the file's actual case (which is what TS path-aliasing produced when reading the source directly) couldn't import via the package's public API.
• @wabbit/tome-ui: add ./tokens.css alongside the existing ./tokens (both point at ./dist/tokens.css). Lets consumers write import '@wabbit/tome-ui/tokens.css' to match the CSS-file naming convention as well as the existing import '@wabbit/tome-ui/tokens'.

All three additions are purely additive — no existing exports removed or changed, so existing consumers stay compatible.

NavigationMenu's .content and .viewport now read --tome-nav-surface-bg, --tome-nav-surface-border, and --tome-nav-surface-shadow, each falling back to the existing popover tokens (--tome-color-popover / --tome-color-border / --tome-shadow-md). Unset = byte-identical to before.

Lets a consumer (e.g. a navbar variant) recolor the dropdown/mega-menu panel — or drop its border — by setting those vars on any ancestor, without forking the primitive. Consumed by @wabbit/tome-chrome NavBar4's new mega-menu background-color field.

--tome-grid-marginalia-left-cols default goes from 2 to 3 at lg+ (lg/xl/2xl/3xl). --tome-grid-marginalia-right-cols default goes from 4 to 3 at 2xl/3xl (lg/xl was already 3).

Net effect: M_L=M_R=3 across all lg+ breakpoints, producing symmetric prose center (line 10 of the 18-track grid) by default. Retires the wider-right-margin editorial convention from the 2026-05-10 marginalia tracks spec — consumer pattern across Wabbit content routes showed every active route needed an override toward symmetry.

Non-breaking for any consumer that already overrides marginalia. Visible defaults change: prose narrows by 1 col at lg+ (7→6) and 2 cols at 2xl+ (8→6) for consumers without --tome-prose-max-width cap; right marginalia narrows by 1 col at 2xl+ (4→3).

See spec 2026-05-13-tome-ui-grid-symmetric-marginalia-defaults-design for the full design rationale, per-consumer audit, and migration path. Wabbit chapter route's existing --tome-grid-marginalia-left-cols: 3 override becomes redundant post-publish (optional cleanup); Wabbit Studies/Pages/Posts wider-reading override (M_L=M_R=2, P_pad=3) stays as-is.

Pure additive line-name remap — no track count change at any breakpoint, no integer column index shifts. Resolves the documented gap where both breakoutWidth='breakout-md' and 'breakout-lg' rendered identically to 'full-bleed' (both aliased to full-start/end previously).

Result: 4 distinct column-aligned widths from the 5 enum values exposed by @wabbit/tome-longform/utils/breakout's breakoutWidthField, with breakout-lg now a documented synonym for content. At base/sm where reading-start/end is not declared, both breakout-md-start/end and breakout-lg-start/end collapse to content-start/end (graceful mobile fallback, matching the prose-track pattern).

All marginalia and prose named lines unchanged. See spec 2026-05-12-tome-ui-grid-breakout-rings-design for the full design rationale, per-breakpoint diffs, and per-consumer audit.

[data-tome-block-wrapper] (RenderBlocks' full-width subgrid wrapper, grid-column: 1 / -1) now defaults to pointer-events: none inside .grid contexts; direct child gets pointer-events: auto restored. The wrapper's bounding box is the full content width regardless of which column the visible inner content occupies, so without this default the wrapper's invisible area intercepts clicks intended for underlying chrome — sidebars, chapter nav, marginalia panels rendered as siblings.

/* shipped in grid.module.css */
:where(.grid :global([data-tome-block-wrapper])) {
  pointer-events: none;
}
:where(.grid :global([data-tome-block-wrapper]) > *) {
  grid-column: 2 / -2; /* unchanged */
  pointer-events: auto; /* new */
}

The rule is :where()-wrapped (specificity 0) so consumers can still override when a wrapper genuinely needs to capture clicks. Retires the per-route [data-tome-block-wrapper] { pointer-events: none } band-aid pattern that an earlier wabbit-site-core fix introduced.

See prose-track spec amendment §12.7 (2026-05-11) for the symptom that surfaced this and §12.7 fix 1 for the deferred-then-built architectural decision.

breakout-lg aliases full (full viewport, padding-to-padding). breakout-md aliases margin-left-start / margin-right-end — wider than content, narrower than full.

Distinct from breakout-lg only by semantic intent at this grid resolution; no in-between track exists yet.

Adopted by @wabbit/tome-longform's DataTable + ImageGrid breakout-width variants (breakout-md, breakout-lg, full-bleed). Additive — no impact on existing consumers.

grid.module.css had a pure-global selector at the block-wrapper default rule (:global([data-tome-block-wrapper]) > :where(*)). Next's strict CSS-Module loader rejects pure-global selectors with "Selector ... is not pure (pure selectors must contain at least one local class or id)".

Anchoring on .grid makes the selector impure-but-deterministic; semantics are unchanged because the rule is only meaningful inside a .grid ancestor anyway.

Discovered during the Wabbit Phase A.3 grid-wrapper pilot (2026-04-28 audit) — without this fix, consumer sites couldn't import tomeGrid from '@wabbit/tome-ui/grid'.

Pack CSS Modules across blocks-extras, blocks-marketing-starter, blocks-content-writer, blocks-agency-essentials, blocks-editorial-pack reference 15 distinct --tome-type-size-* tokens (micro, xxs, xs, sm, base, md, lg, xl, 2xl, 3xl, 4xl, 5xl, xxl, xxxl, hero). The platform only ships --tome-text-* (h1–h6, lg, body, sm, xs).

Until now, font-size declarations in pack renderers fell through to the browser default (font-size: medium, ~16px) in any consumer that hadn't manually defined the family. Only Marquee and ImageMarquee carried inline fallbacks; ~140+ other references were bare var(--tome-type-size-*).

This adds the 15 aliases to tokens.css, mapping to the existing --tome-text-* clamp scale where the semantic intent matches. The 3 hero-marquee references with inline fallbacks are unaffected (their fallbacks remain authoritative for that oversized scale).

Discovered during the Wabbit ↔ tome-blocks alignment audit (2026-04-28). No pack-side changes; aliases activate the existing CSS as authored.