Lms Ui

• hrefBase="/my/certificates" links each card to /my/certificates/{id}. hrefFor still wins when both are set.
• Passing hrefFor from a Server Component throws in Next.js ("Functions cannot be passed directly to Client Components"), because the list is a Client Component.
• CertificatePass draws its dark card with tome-ui's surface-solid-dark / on-solid-dark pair. It used on-inverse, which is dark text for the white surface-inverse, so the card's text rendered dark on dark.

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.

The default course-player composition now uses the components that already ship: CourseShellLayout (and CourseShell without children, which now renders it) fills the on-this-page rail with OnThisPage while the lesson is accessible (onThisPageSlot={null} leaves it empty); LessonContent's footer renders SuggestedNextPanel; a gated lesson renders PrerequisiteGate or VisibilityGate (with EnrollmentCTA) instead of an inline message, with a new slotOverrides.gate to replace it; and VisibilityGate's expired branch renders ExpiredEnrollmentNotice instead of a placeholder. ExpiredEnrollmentNotice and PrerequisiteGate gain an optional headingLevel (default 3).

All prop changes are additive.

Covers student, enrollment and leaderboard counts and the enrollment, due, expiry and quiz-cooldown dates; the cooldown time now names its zone (UTC). Internal: collection slugs are typed through one package-internal helper instead of inline casts.

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.

Not a floor raise — lms-ui already required React 19. This is the last of the five competing peer shapes collapsing onto the one the platform now uses everywhere (ruled 2026-09-01), so a reader comparing manifests across packages sees one vocabulary instead of five.

The practical difference is that a future React 20 consumer is no longer excluded by punctuation alone.

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.

• blocks-core — the ./categories and ./types entry points are now named in the Public API section; both were published but undocumented.
• core — added /access/orgScoped, /access/vendorScoped, /infra/health and /infra/env-scaffold to the additional-subpaths table, and noted that /auth/collections/roles has a real /auth/collections/Roles case alias in the exports map.
• crowdfund — CROWDFUND_LAYER_VERSION is also published standalone at ./version; the row now says so.
• dispatch — the eight per-block ./blocks/* config subpaths and all eight ./components/* component subpaths are enumerated instead of one "etc." row.
• forms — the peer table now lists @wabbit/tome-core, @wabbit/tome-ui and typescript, which are declared peerDependencies but appeared only in prose (or not at all).
• lms-ui — StudentProfileEditor is flagged @deprecated in the component table, matching the tag its source already carries.

asQuizBlock/asAssignmentBlock returned the block AS-IS and every field read (quiz.questions, quiz.maxAttempts, quiz.showCorrectAnswers, quiz.passingScore, assignment.submissionType, assignment.points, assignment.choices, …) came off the OUTER object, which only carries blockType/blockData — so questions was always undefined, no quiz question ever rendered (students saw only a bare Submit button), and every submit graded 0/n; assignment blocks silently collapsed to the default text submission type regardless of what was authored.

Both narrowing functions now unwrap block.blockData when present, falling back to the block itself when it's absent — the pre-existing flat shape ({ id, title, questions, ... }, still used by every other consumer and by this package's own pre-existing tests) keeps working byte-for-byte. readBlockId on both renderers now also falls back through block.blockData?.id and block.blockID before giving up — EDU's real rows currently carry no id anywhere, so it still returns undefined for them, and the two-step quiz-attempt-start / richer-assignment-submit dispatch paths fall back exactly as they did before (onQuizAttemptStart receives '' via its existing ?? '' guard; onAssignmentSubmitWithBlock is skipped in favor of onAssignmentSubmit since it only fires when an id is truthy) — no d.ts contract change was needed for either.

LessonContent's block dispatcher already routed this shape to both renderers correctly (its blockType lookup handles the 'quizBlock'/'quiz' and 'assignmentBlock'/'assignment' key spellings) — the renderers' own field reads were the only break. New tests cover both shapes side by side (QuizRenderer.blockdata-unwrap.test.tsx, AssignmentRenderer.blockdata-unwrap.test.tsx), including a nested fixture copied verbatim from the verified live EDU row shape, and were demonstrated red against the unfixed source before the fix was applied.

It was already part of CourseShellRoot's public onQuizAttemptStart signature but had no supported import path — consumers had to mirror its shape structurally instead of importing it.

No source change, no behavior change.

@wabbit/tome-lms-ui was the ONLY layer: app package in the monorepo declaring @wabbit/* packages as runtime dependencies. Every sibling — tome-admin, tome-admin-pro, tome-chrome, tome-dispatch, tome-longform, tome-readout — declares its engines as required peers with a workspace:* devDependency twin, and carries no peerDependenciesMeta entry for them.

This package now matches that convention exactly.

Both were declared workspace:^, which pnpm rewrites at pack time — so the published tarball carried a hard ^0.x runtime dependency on the LMS engine. A consumer mounting tome-lms-ui always mounts tome-lms itself (they are one licensable family, learning), so npm was installing and version-resolving a second copy of an engine the consumer already supplies.

The peer declaration lets the consumer's copy satisfy it.

Ranges follow the sibling convention (>=MIN <NEXTMAJOR): @wabbit/tome-ui at >=0.9.0 <1.0.0, matching tome-chrome/tome-dispatch/tome-longform/tome-readout/tome-admin verbatim. @wabbit/tome-lms at >=0.12.0 <1.0.0 — deliberately holding the floor the published tarball already carried rather than raising it to the current 0.14.0, so this change alters the KIND of dependency without narrowing the version contract consumers already rely on.

(tome-sc declares the same engine at >=0.9.0 <1.0.0; the higher floor here is the conservative choice, not a conflict.)

Both peers are REQUIRED (no peerDependenciesMeta entry), which is the honest declaration and matches the sibling packages:

• @wabbit/tome-lms is statically value-imported in exactly one place — src/server/active-quest.ts imports getActiveEnrollments/getLessonChain from @wabbit/tome-lms/server, reachable via the ./server subpath. Everything else referencing the engine is a comment or a deliberately re-declared type (see src/types.ts, which re-declares CertificationAwardData specifically so consumers "don't have to depend directly on @wabbit/tome-lms types just for the shell"). An optional peer would be dishonest for ./server.
• @wabbit/tome-ui has ZERO imports anywhere in src/ — its only references are prose comments and three CSS files that consume --tome-color-* Layer-2 tokens shipped by @wabbit/tome-ui/tokens. The dependency is real but ambient: the consumer must load those tokens for this package to render correctly. A peer declares that requirement without forcing a runtime install of a module nothing imports, which is precisely what the sibling packages do.

The workspace:* devDependency twins are required, not optional bookkeeping: assert:declared-imports fails a statically-imported internal package that is peer-only ("add a workspace:\* devDependency so pnpm topology orders the build"), because peers are invisible to pnpm's build ordering on cold checkouts. pnpm assert:declared-imports is green after the change.

Guarded going forward by a new assert:app-layer-peers check (repo tooling — no changeset of its own, since it ships no package), wired into platform-discipline CI pre-build alongside the other manifest asserts. It fails any layer: app package that declares a @wabbit/* engine in dependencies, and carries an empty, stale-entry-failing allowlist so a future exception has to be argued rather than assumed.

NOT published here; publishing waits on the irreversible-publish preflight checklist.

• @wabbit/tome-lms@0.14.0

• @wabbit/tome-lms@0.13.0

• @wabbit/tome-lms@0.12.0

• @wabbit/tome-ui@0.11.0

• @wabbit/tome-lms@0.11.0

• @wabbit/tome-ui@0.10.0

• lms-ui: CurriculumSidebar now derives per-row effective access via deriveAccessState (enrollment/tier-aware) instead of disabling every locked-visibility row — enrolled members can navigate locked lessons from the rail, matching what the content pane already grants. CurriculumTree gains an optional resolveLessonAccess prop; without it the visibility-tier fallback (anon/landing behavior) is unchanged.
• lms: the course-completion badge check moved out of onLessonCompletion (it fired per LESSON, awarding course-completion badges on a student's first completed lesson) into a new awardCourseCompletionBadges CourseEnrollment afterChange hook guarded on the status transition into completed — the same guard autoAwardCertification uses. Per-lesson points (and the points-threshold badge cascade inside awardPoints) are unchanged.

• @wabbit/tome-lms@0.10.1

• @wabbit/tome-ui@0.9.8

• @wabbit/tome-lms@0.9.2

@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-ui@0.9.7
• @wabbit/tome-lms@0.9.1

• @wabbit/tome-ui@0.9.6

• @wabbit/tome-ui@0.9.5

• @wabbit/tome-lms@0.9.0

• @wabbit/tome-lms@0.8.0

• @wabbit/tome-lms@0.7.0

• @wabbit/tome-ui@0.9.3

• @wabbit/tome-ui@0.9.2
• @wabbit/tome-lms@0.6.1

• @wabbit/tome-ui@0.8.3

• @wabbit/tome-ui@0.8.2

• @wabbit/tome-ui@0.6.1