(motir-marketing) Re-pin `@motir/design-system` to 0.1.2 — ten palette tiles resolve ten accents on `/design`, light and dark
Opened by Zhu Yue ·
The consumer half of the release. motir-marketing pins "@motir/design-system": "0.1.1" (package.json, origin/main), which is the tarball that predates MOTIR-3933 — so motir.co/design renders ten identical palette tiles no matter what motir-core's source says. This card moves the pin to 0.1.2 and proves the 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.1"→"0.1.2". An exact pin, not a caret — the repo pins both@motir/*packages exactly today (@motir/brandreads0.2.0), and a caret here would make the built site's contents depend on when the image was built.pnpm installto regeneratepnpm-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/designheadlessly against it, put<html>on a NON-BASE palette — the case MOTIR-3933 fixed — and read the ten palette tiles' resolved accent in light AND dark. Ten distinct values, twice. 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.csscarries@source '../node_modules/@motir/*/dist'lines without which Tailwind emits none of the packages' classes and the page paints unstyled with no error, andapp/layout.tsxruns the package'sthemeInitScriptblocking in<head>. Neither should change — confirm they still hold on the built output.
Acceptance criteria
package.jsonpins exactly0.1.2, andpnpm-lock.yamlis regenerated in the same commit — no other dependency moves.pnpm lint,pnpm format:check,pnpm typecheck,pnpm buildandpnpm testall 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 palette active, the ten palette tiles resolve TEN DISTINCT accents in light AND dark. 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. Its harness controls read the registries and the token blocks directly, so a token that moved shows up there rather than in a screenshot./designis unchanged in every other respect — the nav entry, the type axis 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-3965 is
done:pnpm installcannot resolve a version that has not been published, so the lockfile itself is unobtainable until then. That is what theblocked_byedge 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-3965 — the cut that publishes the version this card pins.
- Not blocked on MOTIR-3947 (style-axis isolation) or MOTIR-3931 (a design-asset fix in this repo that touches no code). 3947 will owe its own publish and its own re-pin after this one; that is the accepted cost of shipping the colour fix now.
Discussion
No comments yet.
Adding to this discussion signs you in on app.motir.co and brings you back to this request.