Org Blocks

0.10.xMinor

• A save now moves renamed keys to their American names and empties the old ones.

  This is the second of three steps toward American spelling in stored values.

  On the class schedule block and collection, enrolLabel, enrolHref, enrol and labels.enrol move to enrollLabel, enrollHref, enroll and labels.enroll. On the event list board, labels.cancelled moves to labels.canceled.

  Anything that still writes an old key lands in the new one.

  This fixes clearing a field: a value sent for the new key, even a blank one, wins and the old value is emptied, so it no longer comes back on the next read or shows on the public page.

  The old group and label no longer have default values, so a new block stores nothing under them. Renderers still read the old keys, so a block that hasn't been saved or backfilled looks the same.

  The class schedule and event calendar demos use the new names.

  BREAKING: @wabbit/tome-blocks-local-pack now needs @wabbit/tome-local 0.6.0 or later, which exports these save hooks from @wabbit/tome-local/classes.

0.9.xMinor

• The event list gains a live same-day board variant, facility links and a lead event; the division card can link its facility.

  Everything is opt-in: a block you already have renders exactly as before.

  • `board` variant. A new event-list variant (after default and filed) for a same-day board. Each row carries a state chip computed from its start and end in the block's time zone: "Live now", "Starts 6:30 PM" or "Finished", plus "Canceled". The clock decides, never the status text, and a row without a usable end gets no chip rather than a guess. In Today mode the board keeps today's finished events (new showFinished, on by default for the board) and lists them last, after closures and the events still to come, so the item cap drops finished rows first. Closure rows read "Until 3:30 PM". All the words are in a new labels group, including {clock} for a time without AM or PM.
  • The board stays true on a cached page. The board ships this pack's first client file, EventBoardEnhance.client.tsx, mounted only on board. It works on the rendered markup: at load it corrects any state that changed since the page was rendered, without announcing it; after that it sets one timer for the next start or end, re-checks when the tab comes back, and announces a real change once through a polite live region ("Under-12 final is now live"). At the end of the zone's day it hides the board rather than show yesterday. It never adds, removes or re-sorts rows. Without JavaScript the board shows the states true when it was rendered. Hooks: root data-block-variant="board", data-event-timezone, data-event-day-end; rows data-event-state, data-event-start, data-event-end, data-event-facility; span[data-event-state-chip] in [data-event-aside]; div[data-event-board-live].
  • The chip state is a public function. eventChipState(entry, now), exported from the package root, is pure and isomorphic; the renderer and the island both call it, so they agree for any instant.
  • Selection keeps finished events on request. selectEvents takes includeFinished (Today mode only, default off). With it unset the function behaves exactly as before.
  • Facility links. Set facilityHrefTemplate (for example #plan-{key}) and give events a facility key, and each row's place becomes one link holding the facility's plate and name, a[data-event-facility-link] > span[data-event-facility-plate]. Plates come from the block's new facilityPlates list, else the event's own facilityPlate. Keys are lowercase letters, numbers and hyphens, up to 24 characters. A row without a key, or a blank template, links nothing.
  • Reading the facility key and three more fields from your events. ResolveEventListOptions.fieldNames gains facilityKey, summary, registrationUrl and leadImage. Each is read only when you name it, so the default query selects exactly what it did before. Invalid keys, summaries over 140 characters and unsafe links are dropped. The lead photo is read with one extra query, for the lead event only. The /server entry now exports eventFacilityKeyField(), a ready-made indexed text field with the key's validation, for your Event collection's extraFields, and buildEventSelect.
  • Filed list: summaries, type tags and a lead event. showSummary prints each event's one-line summary under its title (any variant). On filed, showEventType prints the event type as a tag (eventTypeLabels sets the words), and leadLayout: 'first' shows the first event as a lead with its photo and credit, a meta line ("Saturday and Sunday · Tournament", set by leadMetaTemplate), its summary and place, and "Event details" and "Register" links (leadActions). New hooks: p[data-event-summary], span[data-event-type], article[data-event-lead] with figure[data-event-lead-media], figcaption[data-event-lead-credit], p[data-event-lead-meta] and a[data-event-lead-action="details|register"].
  • Authored rows. The block's own events rows gain optional facilityKey, facilityPlate and summary.
  • Division card facility plate. The entry variant gains optional facilityKey, facilityPlate, facilityName and facilityHrefTemplate. With a key and a template it prints a plate link just before the name, a[data-division-facility-link] > span[data-division-facility-plate], named "Show Field 4 on the plan". Without them the card is unchanged.
  • Choose the lead. On filed with leadLayout: 'first', leadEvent (an event id or slug) picks which event leads instead of the earliest, so one block can show a lead that is not first in date order. excludeLeadFromRows (default on once leadEvent is set) leaves the lead out of the rows; off lists it in both. The cap cannot drop the chosen lead, its photo is read for it, and a leadEvent the list does not select falls back to the first. selectEvents takes a matching keep option. With neither field set nothing changes.

  New fields are nullable columns: on a SQL database, regenerate your migration.

  Checkpoint A: row times. The time range on a row (every variant) now uses an en dash, "12:30 PM – 2:00 PM", where it printed a spaced hyphen, "12:30 PM - 2:00 PM". This is a deliberate fix to the default output, and the golden fixtures are updated for it; nothing else about the default changes.

  New opt-in timeDisplay (range, the default, or start): with start, a row prints the start time only. Board closure rows keep "Until 3:30 PM".

  The new field is a nullable column: on a SQL database, regenerate your migration.

• Internal Tome dependencies are published as compatible ranges, not exact versions, so installs share one copy of tome-core.

  Before, these packs pinned the exact tome-core version that was current when they shipped, so an install could end up with two copies of tome-core and split its shared registries. They now declare a compatible ^ range that npm can resolve to a single copy.

0.8.xMinor

• division-card gains an entry variant: a program or team entry with a captioned photo, a lead line, the name, the purpose, an authored next date and a link.

  The text comes first in the DOM (data-division-text, with data-division-lead, -name, -body, -next and -link), then the photo as figure[data-division-media] with its label and credit in a figcaption after the image, never on it. mediaSide places the photo on the start or end from 48rem without reordering the DOM; headingLevel sets the name as an h3 (default) or h2; *run* in the lead line sets a weight-only emphasis.

  With no photo the text spans. The photo upload relates to media by default and to divisionCardBlock.block({ mediaCollection }) when given.

  memberCount, logoUrl and leaderName are hidden for entry and ignored.

  The default variant is unchanged: its markup is held byte for byte by a golden cut from the pre-change renderer, and it gains no attribute.

0.7.xMinor

• Adds the event-list block: a live list of org events with an optional "N spots left" chip, a "today" mode that renders nothing on quiet days, and an optional .ics link per event.

  It reads upcoming, same-day or date-range events through the new ./server entry (createHydratedRenderers), as an anonymous visitor and public events only, and falls back to its authored events when no wrapper is wired or a read fails. The chip shows "N spots left", "Full" or "Waitlist open" and is hidden when capacity data is missing.

  Rows carry data-event-* theme hooks and ship a default and a filed (dated rows) variant. capacityChip, buildEventIcs, eventIcsDataUri and selectEvents are exported from the root.

  event-calendar and event-list-item are unchanged.

0.6.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 8 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.5.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.4.xMinor

• Raise the react / react-dom peer floor to >=19.0.0 (ruled 2026-09-01).

  The platform declared React peers in five different shapes — >=18.0.0, >=18, ^18 || ^19, ^18.3.0 || ^19.0.0, ^19.0.0 — while its kernel (@wabbit/tome-core) and five app-layer packages already required >=19. Any package advertising React 18 was advertising a configuration that could not be installed alongside the kernel, so the split was never a supported matrix; it was drift.

  One shape now, and it is the honest one.

  These nine version independently of the linked blocks family (which gets its own coordinated bump), so they are listed here:

  • @wabbit/tome-admin, @wabbit/tome-admin-pro — from ^18.3.0 || ^19.0.0
  • @wabbit/tome-blocks-gallery — from ^18 || ^19; devDeps react/@types/react ^18.0.0 → ^19.0.0
  • @wabbit/tome-blocks-org-pack — from >=18.0.0; same devDep correction
  • @wabbit/tome-engine, @wabbit/tome-motion, @wabbit/tome-rpg, @wabbit/tome-webgl — from >=18
  • @wabbit/tome-ui — from >=18.0.0

  The ^18 devDependency pins on the two block-shaped packages were already fiction: the root pnpm.overrides pins @types/react to 19.2.14, so both have been building against React 19 types regardless. Correcting them changes the manifest, not the resolved tree.

  Consumer impact: a React 18 consumer can no longer install these. That install was already impossible with the kernel in the graph.

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

• 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.3.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.2.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.1.x