Blocks Industrial Theme

775f90a: Published packages now contain compiled JavaScript and type declarations under a one-line licence banner, and no longer include source maps. 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 licence: `/*! @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 behaviour change, and nothing to do on upgrade. In `@wabbit/tome-blocks-gallery`, the source snapshots `extractGallerySource` writes from an installed pack leave out the licence 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.

• 775f90a: Published packages now contain compiled JavaScript and type declarations under a one-line licence banner, and no longer include source maps. 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 licence: `/*! @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 behaviour change, and nothing to do on upgrade. In `@wabbit/tome-blocks-gallery`, the source snapshots `extractGallerySource` writes from an installed pack leave out the licence 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.

382f36c: **BREAKING:** `INDUSTRIAL_THEME` is now a `ThemeManifest` (`kind: 'treatment'`), and a new `./register` subpath adds it to the Tome theme registry. **Migration:** read `name` instead of `themeAttribute` (both `'industrial'`) and `label` instead of `name`; `slug` and `tags` are gone (the package keywords carry the tags). `styledBlocks` is unchanged. `ThemeMeta` is a deprecated alias of `ThemeManifest` for one minor. To list the treatment in the admin theme switcher, add `import '@wabbit/tome-blocks-industrial-theme/register'` on the server (needs the optional `@wabbit/tome-core` `>=1.20.0` peer). - The stylesheet moved to `treatments/catalog-lms.css`; `./styles.css` imports it, so the import path is unchanged. - The course card's white background now reads a private `--industrial-surface` token (from `--pc-white`, default `#fff`) instead of a hard-coded literal; rendering is unchanged unless a site defines `--pc-white`. - The test suite runs the theme conformance check for treatments: every selector scoped to the theme attribute, public hooks only, and no raw colour literal outside the private `--industrial-*` tokens.

• 382f36c: **BREAKING:** `INDUSTRIAL_THEME` is now a `ThemeManifest` (`kind: 'treatment'`), and a new `./register` subpath adds it to the Tome theme registry. **Migration:** read `name` instead of `themeAttribute` (both `'industrial'`) and `label` instead of `name`; `slug` and `tags` are gone (the package keywords carry the tags). `styledBlocks` is unchanged. `ThemeMeta` is a deprecated alias of `ThemeManifest` for one minor. To list the treatment in the admin theme switcher, add `import '@wabbit/tome-blocks-industrial-theme/register'` on the server (needs the optional `@wabbit/tome-core` `>=1.20.0` peer). - The stylesheet moved to `treatments/catalog-lms.css`; `./styles.css` imports it, so the import path is unchanged. - The course card's white background now reads a private `--industrial-surface` token (from `--pc-white`, default `#fff`) instead of a hard-coded literal; rendering is unchanged unless a site defines `--pc-white`. - The test suite runs the theme conformance check for treatments: every selector scoped to the theme attribute, public hooks only, and no raw colour literal outside the private `--industrial-*` tokens.

917b77a: CSS files are copied to `dist/` by a post-build script instead of a tsup `onSuccess` hook, whose output the type-declaration phase can remove.

• 917b77a: CSS files are copied to `dist/` by a post-build script instead of a tsup `onSuccess` hook, whose output the type-declaration phase can remove.

0836ef5: 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.

• 0836ef5: 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.
• 637db74: README brought to the package contract (install, Public API, posture, decisions) and a node:test smoke suite added (descriptor/manifest tier agreement, every claimed block has a scoped rule, no selector escapes the theme scope). Closes the two CI gate failures the package shipped with.
• 73081e6: 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.

Initial release: industrial theme pack — safety-yellow accents, charcoal type, motorsport-italic chrome for catalog/LMS blocks. Extracted from the client-era styling that used to ship inside blocks-lms-pack (CourseCard) and blocks-catalog-pack (ProductGrid, CategoryStrip). Owns no blocks; restyles the neutral packs through their public .tome-_ BEM hooks, scoped under [data-tome-theme='industrial'] so it wins on specificity regardless of stylesheet order and can be applied per-section. Prefers legacy --pc-_ tokens when the consumer defines them.

• Initial release: industrial theme pack — safety-yellow accents, charcoal type, motorsport-italic chrome for catalog/LMS blocks. Extracted from the client-era styling that used to ship inside blocks-lms-pack (CourseCard) and blocks-catalog-pack (ProductGrid, CategoryStrip). Owns no blocks; restyles the neutral packs through their public .tome-_ BEM hooks, scoped under [data-tome-theme='industrial'] so it wins on specificity regardless of stylesheet order and can be applied per-section. Prefers legacy --pc-_ tokens when the consumer defines them.