Motir

One file, one line, one pull request: packages/design-system/package.json "version": "0.1.1" → "0.1.2". Nothing else changes.

MOTIR-3933's fix is already in the package's SOURCE on origin/main — theme.css returns 13 for grep -c data-appearance-scope and 10 for grep -c ':not(\[data-theme\])', and src/components/theme/StyleVignette.tsx:134 emits the attribute in SCOPED mode (git grep on origin/main at c6409c20c, 2026-08-30). The PUBLISHED 0.1.1 predates it: it was cut from tag design-system-v0.1.1 at c5d11f7f1441 and published 2026-08-29T09:51:55Z, twenty-six hours before 3933 merged (d851bbb32d3f, 2026-08-30T12:55+02:00). The fix is in the source and not in the artifact, and the only thing that closes that gap is a new version number.

Why the bump is its own card. .github/workflows/release-design-system.yml fires on a design-system-v<x.y.z> tag and fails fast unless the tag equals package.json's version; packages/design-system/README.md § Releasing states the procedure as bump → merge → tag. The tag can only be pushed once THIS pull request has merged, which is a human act in manual merge mode — so the cut is MOTIR-3965, not this card, and the boundary between them is a merge.

What to do

1. Bump packages/design-system/package.json 0.1.1 → 0.1.2. PATCH is the right level: the token contract the README calls the public surface (--el-* names, the data-* attribute set, the apply API) is unchanged — 3933 ADDED selectors and one attribute emission and renamed nothing.
2. Nothing else. No source change, no lockfile churn — confirm with git grep '@motir/design-system' -- '*.json' that no workspace dependant pins the version before claiming the diff is one file.
3. Pre-flight the tarball this version will publish, so the release does not discover a packaging gap: pnpm --filter @motir/design-system build, then in packages/design-system run npm pack and read what came out — tar -xzOf motir-design-system-0.1.2.tgz package/dist/components/theme/StyleVignette.js | grep -c data-appearance-scope and the same two greps against package/theme.css. This is evidence for THIS pull request; the PUBLISHED tarball is what MOTIR-3965 checks, and a local pack is not that.

Acceptance criteria

• packages/design-system/package.json reads "version": "0.1.2", and the pull request's diff touches that file and no other.
• The locally packed tarball at this version emits data-appearance-scope in dist/components/theme/StyleVignette.js, and its theme.css carries the same data-appearance-scope and :not([data-theme]) counts as origin/main's source. Quote the counts AND the commands that produced them in the pull-request body.
• pnpm --filter @motir/design-system build and pnpm --filter @motir/design-system test pass locally. Everything suite-wide is the pull request's own CI to report, not this run's to re-run.
• The pull-request body names MOTIR-3965 as the card that cuts the tag once this merges, so whoever merges knows a second step is owed.
• ORDERING — every criterion above reads on THIS branch. Nothing here reads on the tag, on npm, or on motir-marketing.

Context refs

• packages/design-system/package.json — the one file this card edits.
• packages/design-system/README.md § Releasing — the bump → merge → tag procedure; this card is step 1.
• .github/workflows/release-design-system.yml — the TAG_VERSION != pkg_version guard that makes the version and the tag one decision.
• MOTIR-3933 / motir-core#2465 — the fix being carried, merged as d851bbb32d3f.