Re-pin @motir/design-system to 0.1.3 — the style gallery isolates under glassmorphism

MOTIR-4052Done

Re-pin @motir/design-system to 0.1.3 — the style gallery isolates under glassmorphism

Opened by Zhu Yue · 31 August 2026

The consumer half of the 0.1.3 release. motir-marketing pins "@motir/design-system": "0.1.2" (package.json, origin/main), the tarball that predates MOTIR-3997's @scope rewrite — so motir.co/design still lets a non-base style leak into every tile. This card moves the pin to 0.1.3 and proves the STYLE gallery on the built site, which is the only evidence that the release actually reached the page.

No source change. StyleVignette, theme.css and app/design/page.tsx are not touched. If the published package turns out to need a fix, that is a different card and this one waits for it.

What to do

package.json: "@motir/design-system": "0.1.2" → "0.1.3". An exact pin, not a caret — the repo pins both @motir/* packages exactly today, and a caret would make the built site's contents depend on when the image was built.
pnpm install to regenerate pnpm-lock.yaml; commit the lockfile in the same commit as the pin.
Run the repo's own lane locally: pnpm lint, pnpm format:check, pnpm typecheck, pnpm build, pnpm test.
Verify the gallery on the BUILT site, not from the version number. Serve the production build (pnpm build && pnpm start) or render /design headlessly against it, put <html> on a NON-BASE style — glassmorphism, the worst case (1/11 before the fix) — and read the eleven style tiles' material properties: the Neo-Brutalism tile computes NO backdrop-filter and the Aurora tile does NOT wear glass. Under warm-editorial the page looks correct either way, so a check run only there proves nothing. Quote the measured values and the command that produced them; "the version bumped" is not this criterion.

⚠️ Two things this repo does that a dependency bump can silently break, both worth re-checking in step 4 rather than assuming: app/globals.css carries @source '../node_modules/@motir/*/dist' lines without which Tailwind emits none of the packages' classes and the page paints unstyled with no error, and app/layout.tsx runs the package's themeInitScript blocking in <head>. Neither should change — confirm they still hold on the built output.

Acceptance criteria

package.json pins exactly 0.1.3, and pnpm-lock.yaml is regenerated in the same commit — no other dependency moves.
pnpm lint, pnpm format:check, pnpm typecheck, pnpm build and pnpm test all pass; the pull request's CI is the authority and its result is quoted in the body.
On the built site, with a non-base style active, the eleven style tiles each render their own material — the Neo-Brutalism tile computes no backdrop-filter, and the Aurora tile does not wear glass. The measured values and the command are in the pull-request body. A screenshot alone is not the measurement.
tests/aaMatrix.test.ts (shipped by MOTIR-1043) passes against the new package.
/design is unchanged in every other respect — the nav entry, the palette and type axes, and the AA matrix all still hold.
ORDERING — every criterion reads on THIS branch, against a version that is already on npm. It cannot be started before MOTIR-3999 (the cut) is done: pnpm install cannot resolve a version that has not been published, so the lockfile itself is unobtainable until then. That is what the blocked_by edge carries.

Context refs

package.json · pnpm-lock.yaml — the two files this card changes.
app/design/page.tsx · design/marketing/design-showcase.mock.html — the surface and its design asset, both READ and neither edited.
tests/aaMatrix.test.ts · tests/designShowcase.test.tsx · tests/support/themeTokens.ts — the shipped guards this bump runs against.
MOTIR-3999 — the cut that publishes the version this card pins.

Discussion

No comments yet.

Adding to this discussion signs you in on app.motir.co and brings you back to this request.

Add a comment