Blocks Signal Theme

A demo link is now the caller's placeholderHref or #, so rendered demos stop emitting real <a href>s to pages that exist on no site. README: subpath and file mentions are written package-qualified (for example @wabbit/tome-x/render) or as code text, so crawlers no longer resolve them as site URLs.

• @wabbit/tome-ui@0.22.1
• @wabbit/tome-blocks-console@0.1.2

• @wabbit/tome-ui@0.22.0

• @wabbit/tome-ui@0.21.0
• @wabbit/tome-blocks-console@0.1.2

53 block and variant descriptions carried package names, "Fully static — no peer required", data-variant, slots and hydration details. These are what a visitor reads in a block catalog, so each now says in plain words what the block shows and when to use it.

The developer facts aren't lost: each one moves into the block's usage.howToUse (or, where a block has none, a code comment above its description), and the 20 that howToUse already covered are simply dropped from the description. CTA's with-form variant no longer claims to render lead-capture fields: it says it leaves room for a form the site supplies, which is what it does.

• @wabbit/tome-ui@0.20.0
• @wabbit/tome-blocks-console@0.1.2

These blocks placed their content at 1 / -1, which only matched the content column when the host wrapped blocks at 2 / -2. On a host that leaves defaultColumnSpan unset, the text sat at the window edge.

Full-bleed bands stay full-bleed, and their content now sits on content-start / content-end. Affected: editorial-pack's feature walk-strip, message-panel, split-panel (its band now wraps an inner .splitInner) and status-board; extras' bento-section, card-grid, content-pro bento, skill-showcase and section-header statement-hero and ruled-split; marketing-starter's banner with no grid placement, cta door-strip, exhibit gallery-wall, and the Full Width layout of feature-hero and cta.

In signal-theme, signal-note's aside-left, aside-right and author-overlay sit on the marginalia tracks at 80rem and wider on the page grid; aside-left used to be pulled past the left window edge.

• @wabbit/tome-ui@0.19.0
• @wabbit/tome-blocks-console@0.1.2

./demo (dispatch, longform, readout): the root barrel's demo props (getDemoProps, the per-block getters, DemoContext) on their own subpath, with no Payload import, so a client bundle such as a block gallery can use them without pulling in the block configs. Additive; the root barrel still exports them.

These packages ship raw Payload Block configs rather than defineBlock descriptors, so they have no ./meta entry.

./meta (extras, signal-theme): new extrasDeprecatedBlockMeta and signalThemeDeprecatedBlockMeta lists describe the 16 deprecated blocks each pack still registers for stored content but no longer offers. extrasBlockMeta and signalThemeBlockMeta are unchanged: they still list only the offered blocks.

The deprecated signal-theme blocks' metadata moved from inline defineBlock arguments into payload-free <block>.meta.ts files; the registered descriptors are unchanged.

./meta (extras, marketing-starter): six motion blocks (image-marquee, marquee, showcase, logo-slider, pricing-plans, testimonial) now declare requiredCapabilities: ['motion'] in their metadata. defineBlock already added it at registration, so the registered descriptors are unchanged, but the ./meta entries lacked it and a gallery reading them could not tell these blocks need a motion provider.

• @wabbit/tome-ui@0.18.0
• @wabbit/tome-blocks-console@0.1.2

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.

• @wabbit/tome-blocks-console@0.1.2
• @wabbit/tome-ui@0.17.1

signal-classification-banner and signal-system-alert are registered by SignalBanner; signal-comm-intercept and signal-comms-transcript by SignalComms; signal-phase-marker, signal-chapter-divider and signal-anchor-section by SignalDivider; signal-cross-link and signal-series-nav by SignalNav; signal-aside, signal-author-aside and signal-epigraph by SignalNote; signal-key-facts, signal-metric-grid and signal-stat-strip by SignalStats. Each is an alias that renders the parent's lane for that slug with the stored block as is, so a document set to a designVersion renders exactly as the parent set to the matching _variant, and an unset value renders as before.

The renderers map from ./render/register keys these slugs to the aliases. Every slug stays a registered block with its own field schema, demo props and catalog entry, and every renderer component is still exported from ./render with the same props.

signal-callout keeps its own renderer: it writes its own _variant as data-variant, which differs from what signal-note's callout variants write. No consumer action is needed.

The renderers are signal-accordion, signal-anchor-section, signal-aside, signal-author-aside, signal-callout, signal-chapter-divider, signal-cross-link, signal-data-table, signal-epigraph, signal-footnotes, signal-image-grid, signal-key-facts, signal-series-nav, signal-spoiler and signal-tabbed-content, and the parents that dispatch to them. signal-drop-cap keeps its own renderer.

Each keeps its stylesheet, passed to the core as the skin. What changes is for assistive technology and the keyboard:

• Tabs: only the selected tab is in the tab order; the arrow keys, Home and End move between tabs; each panel is named by its tab.
• Spoiler: the reveal button's spoken name now contains its visible words ("Click to reveal spoiler content", "[REDACTED]: reveal spoiler content").
• Chapter divider NUMBERED: the title is a level-2 heading, styled exactly as the text it replaces, and the divider is no longer a separator (a separator's contents are not read). ORNAMENTAL and SYMBOL stay separators.
• Data table: header cells are column headers, and the caption names the table.
• Key facts: a fact with a status carries the status word (its option label), visually hidden.
• Footnotes: each note carries id="fn-<number>" so text can link to it.
• Accordion SINGLE: only a click on a row's heading opens or closes it, so a click or a link inside an open panel no longer closes the row.

No consumer action is needed.

Their markup, stylesheets, stored fields and look are unchanged, and so is the signal-stats and signal-divider parents' output where they dispatch to them. No consumer action is needed.

Eight renderers (comm intercept, comms transcript, classification banner, log header, redacted, system alert, ambient audio, threat panel) now render through the shared cores in @wabbit/tome-blocks-console, a new regular dependency. Their markup, stylesheets and stored fields are otherwise unchanged.

Three behaviors for assistive technology change with the cores: the classification banner is a note (role="note") rather than a page banner landmark; only HULL_BREACH system alerts are announced (role="alert"), the other variants are notes; and the ambient audio label is readable, with only the waveform hidden. The active status word, visible only where a site shows status words, is red to match the dot.

No consumer action is needed.

• @wabbit/tome-blocks-console@0.1.1

One default changes on purpose: those two callsign colors are lighter, because the old ones failed as text on the dark panel (details at the end).

Every read is now var(--signal-<name>, var(--tome-console-<role>, <today's value>)). Nothing declares the roles by default, so every block computes the color it did before, and a --signal-* value set by a site or by @wabbit/tome-cop still wins.

Composition roles let the light set match the approved board: a single 2px hue rule on the threat, sensor, objective and comms panels (today's 1px neutral top edge when unset), hairlines round metric cards and callouts, a neutral threat outline, no washes behind the threat badge, system alert, DECLASSIFIED band and personnel badges, outlined badges, an unfilled RESTRICTED band framed by rules (SECRET stays filled), and no dimming on redacted or degraded lines. Each is zero-width, today's percentage or today's opacity when unset.

The mapping is in the README.

Threat indicators and the sensor readout's SYSTEM cards now carry a status word (the field's option label), and objective items carry theirs for screen readers. The word is always in the markup and visually hidden by default (the clip pattern, so the layout does not change); threat and sensor words show when --tome-console-status-word-display is set.

Deliberate default change: the comms transcript's red and blue callsign colors were hsl(0 72% 50%) (3.71:1 on the dark panel) and hsl(215 65% 45%) (3.23:1). They now use the pack's on-panel values, hsl(0 80% 68%) (6.07:1) and hsl(215 75% 65%) (6.36:1).

Transcripts using gold, cyan, amber, green or ghost callsigns render as before.

• @wabbit/tome-ui@0.17.0

Every color keeps today's value as the var() fallback, and no variable is declared at :root. The seven accent hues are applied through one shared helper instead of a pasted .accent-<hue> rule in each of 27 stylesheets; each hue's three roles resolve to the same values as before.

The new variable names are listed in the README token tables.

The region is labeled with the block title (or Sensor contacts). The grid layout's card minimum also caps at the container width.

Each renderer's .tome-css stylesheet is compiled when the pack is built, into a JS module next to it (<Name>.tome-css.js / .cjs), and the renderers import that. A site no longer has to wrap next.config with withTomeBlockStyles to use the pack, and ./render and ./render/register now load under plain Node, so seed scripts, tests and the Payload CLI can import them.

Each block's CSS is still inlined only on pages that render the block. A site that already uses withTomeBlockStyles needs no change.

Scoped class names change once, because they are now keyed on the package rather than on where it is installed. The raw .tome-css files stay in the package as readable source.

• @wabbit/tome-ui@0.16.0

• @wabbit/tome-ui@0.15.0

They read the undeclared --tome-space-xxxl and now read --tome-space-3xl. The ambient-audio and progress-bar --tome-motion-normal timings now resolve because @wabbit/tome-ui declares that token.

• @wabbit/tome-ui@0.14.0

Before, both variants only set data-variant; the look still came from the in-block designVersion select, so picking a variant changed nothing visible. The renderers now map _variant onto designVersion the way signal-note does: single → SINGLE, lore → LORE.

The default variant (now labeled "Default") still follows designVersion, so documents on the default variant render as before. A saved document on single or lore whose designVersion disagreed now renders the variant it names.

The designVersion select is hidden in the admin while a forcing variant is picked. data-variant is still emitted.

signal-accordion's variants moved to a payload-free signal-accordion.variants.ts so signalThemeBlockMeta can list them. The package description and bundle description now give the real count: 39 registered, 23 offered.

Behavior and signature are unchanged. The @wabbit/tome-blocks-core peer floor goes up to >=0.18.0 because that is the first version exporting the helper.

• @wabbit/tome-ui@0.13.0

The 0.15.11 line shipped defaultBreakout in its version notes but not in its tarballs: source on main carried all 151 descriptors, the published dist/ carried zero. pnpm publish does not build — it packs whatever is already in dist/ — so a release ships whatever a previous, possibly unrelated, build left behind.

Here the dist had been built from a branch that predated the metadata, and nothing in the pipeline compares artifact to source.

Caught by grepping the _installed_ package in a consumer rather than trusting the version number.

Systemic fix: prepublishOnly: pnpm run build added to all 41 publishable packages that lacked it (only blocks-org-pack had one — which is why it was the single package whose build ran during the previous publish). Every publish now rebuilds from source first, so a stale-dist release becomes impossible rather than merely unlikely.

Same family as the two publish hazards already documented in this repo (workspace:* literals reaching the registry, and exact-pin dependencies forcing nested duplicate copies): the publish path had no guard that what ships matches what is committed.

• @wabbit/tome-blocks-extras@0.15.12

The 2026-06-28 layout-grid + nesting contract (Decision 3 / Amendment A1) defined defaultBreakout as the per-block breakout POLICY co-located with the block, replacing a central hand-maintained table. No pack had ever filled it in, so every consumer fell through to 'article' (the reading column) and a full-bleed hero previewed at prose width.

Values are drawn from the canonical @wabbit/tome-ui BreakoutWidthValue vocabulary and assigned from each block's render CSS, not its name:

• Root at a named grid line (content-start / content-end, full-start / full-end, marginalia-right-*, …) — defaultBreakout mirrors that exact line.
• Root 1 / -1 + subgrid with an inner wrapper at content-start / content-end — a self-banding block: 'full-bleed'.
• Root and inner both 1 / -1 (width-agnostic) — assigned editorially: bands/heroes 'full-bleed', page sections 'content', cards and single-column components 'breakout-md', prose/inline components 'article'.
• Where a block already ships its own breakoutWidthField({ defaultValue }), defaultBreakout matches that value exactly rather than contradicting it.

Distribution: content 52, full-bleed 41, article 33, breakout-md 23, breakout-lg 1, marginalia-right 1.

Also declares pinnedBand: true on the three blocks that are unambiguously full-bleed bands whose own breakoutWidth field drives INNER content (compareColumns, editorialSection, editorialSpread), and nestable: false on 22 full-bleed heroes / band primitives / containers that carried no nestable declaration.

Purely additive optional metadata: no descriptor field, block structure, or CSS changed, and no existing nestable: true was flipped, so the derived layoutGrid child allowlist is byte-identical (98 nestable blocks before and after).

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

• @wabbit/tome-blocks-extras@0.15.11
• @wabbit/tome-ui@0.11.2

• 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.

• @wabbit/tome-blocks-extras@0.15.9
• @wabbit/tome-blocks-core@0.15.9
• @wabbit/tome-ui@0.11.1

• @wabbit/tome-ui@0.11.0

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

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

• @wabbit/tome-ui@0.10.0

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

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.

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.

• @wabbit/tome-blocks-core@0.11.0
• @wabbit/tome-blocks-extras@0.11.0
• @wabbit/tome-ui@0.9.9

signal-theme — reclassified SC-tier under the @wabbit/tome-sc umbrella. tier stays 'addon' (no new tier enum value — already the correct value per the blocks family's 0.7.0 tier-formalization release); ownership is expressed via an 'sc' bundle tag (added alongside the existing 'star-citizen' tag) and an updated bundle description/README section.

This package remains independently installable on any editorial site — its non-SC usability is a bonus, not a design constraint. Also fixes a stale test assertion (test/smoke.test.ts) still expecting the pre-0.7.0 tier: 'pro' value.

sc-pack — README no longer says "scaffold-only" (stale since the 5 blocks were fully authored in Wave 3): documents the real block inventory (fleet-summary, signal-hero-sc, task-force-roster, op-briefing-panel, rsi-handle-card), corrects the wrong slug list the old README carried, and notes each block is _variant-native with self-contained data (no dependency on @wabbit/tome-sc's collection layer). Fixes two stale test assertions (test/smoke.test.ts, test/v2-coverage.test.ts) still expecting the pre-0.7.0 tier: 'pro' value instead of the shipped 'addon'.

• @wabbit/tome-ui@0.9.8

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

• @wabbit/tome-blocks-extras@0.9.5

@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.

• @wabbit/tome-blocks-core@0.9.4
• @wabbit/tome-blocks-extras@0.9.4
• @wabbit/tome-ui@0.9.7

• @wabbit/tome-ui@0.9.6

• @wabbit/tome-blocks-core@0.9.2
• @wabbit/tome-ui@0.9.5
• @wabbit/tome-blocks-extras@0.9.2

• @wabbit/tome-blocks-extras@0.9.1

• blocks-core: add 'addon' to the BundleMeta.tier union (additive; existing 'pro' values stay valid).
• blocks-extras: register TWO bundles from one package (Option B) — a free extras-primitives sub-bundle (9 structural primitives) + the paid extras remainder (39 blocks, was 48). Mechanically additive: no import-path changes, all blocks still exported + registered, existing content keeps rendering, existing extras entitlements keep working (the primitives are now free to everyone). The tier-scope change is the only semantic shift.
• signal-theme + sc-pack: tier 'pro' → 'addon' (sold independently of the tiered subscription track).
• blocks-gallery: widen the @wabbit/tome-blocks-core peer to ^0.5.9 || ^0.6.0 || ^0.7.0 so the 0.7.0 bump doesn't force a spurious major (it's a types-only peer). Patch.

Release note: the blocks family is linked, so this aligns the whole family to 0.7.0. Minor (not major) is deliberate — 0.7.0 still gates explicit consumer adoption (^0.6 does not auto-resolve 0.7.0), without declaring a symbolic 1.0.0 before the marketplace launch.

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

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

Each pack now ships a demo.ts barrel with a getDemoProps(blockSlug, variant, ctx?) dispatcher and per-block demo functions. The auto-gallery route in tome-starter can replace the noopDemoProps stub for all three bundles, eliminating the warning cards that appeared for every block × variant.

• agency-essentials: 10 blocks × 4 variants each (about, contact, team-roster, gallery, timeline, stat, stat-bar, split-view, media, form)
• marketing-starter: 8 blocks × 4-5 variants each (high-impact-hero, feature-hero, cta, logo-slider, pricing, testimonial, faq, banner)
• signal-theme: 33 blocks (all signal-\* slugs); blocks with multi-variant configs covered (accordion: stacked/single, callout: tactical/lore)
• DemoContext interface, individual block-level functions, and getDemoProps all re-exported from each pack barrel
• richText fields intentionally omitted — GalleryRichTextProvider supplies the Lexical state at gallery render time
• Relationship fields (pricing, testimonial) emit sentinel strings; gallery degrades gracefully

Fixes risk R1 from the gallery gap audit.

• @wabbit/tome-blocks-core@0.5.9

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

• @wabbit/tome-blocks-extras@0.4.1
• @wabbit/tome-blocks-core@0.4.0

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