Motir

The CUT for the @scope material layer. This card opens no pull request and changes no file. Its whole deliverable is a tag, the run that tag fires, and the evidence that a stranger can fetch what the run published. The consumer half — the motir-marketing re-pin — is the sibling card the re-plan created; the version bump is the sibling before it.

What to do

1. Confirm the bump is on main — this is the step that protects the version. git fetch origin --tags, then git show origin/main:packages/design-system/package.json must read 0.1.3; take the commit from git log origin/main --format=%H -1. The lane's guard catches a tag whose version disagrees with package.json; it does NOT catch a tag on an unmerged branch, which would publish from a commit main never saw and leave npm ahead of the repository for good.
2. Tag and push — git tag design-system-v0.1.3 <that commit> && git push origin design-system-v0.1.3. This is the irreversible act: npm will not accept a second 0.1.3, and recovery is another bump and another release.
3. Watch the lane — gh run watch the Release @motir/design-system run the tag fired (gh run list --workflow=release-design-system.yml). Read the JOB, not the check title: the publish step is conditional on already == 'false', so a version already on npm produces a GREEN run that published nothing. Confirm the Publish to npm step actually ran.
4. PULL IT AS THE CONSUMER, anonymously — npm pack @motir/design-system@0.1.3 from a directory with no .npmrc and no credential. A green lane is not evidence; the pull is.
5. Read the TARBALL, not the repo — unpack what you just pulled and check the @scope rewrite is in it (criterion 4).

Acceptance criteria

• Tag design-system-v0.1.3 exists on origin, its commit is an ancestor of origin/main, and packages/design-system/package.json at that commit reads 0.1.3.
• The run the tag fired is quoted by id, its event is push on that tag, and its Publish to npm step RAN rather than being skipped as already-published.
• npm pack @motir/design-system@0.1.3 succeeds with no credential, and the resulting shasum is quoted on this card.
• In that tarball — not in the repository — package/theme.css carries @scope ([data-style= as 69 blocks and no bare [data-style='X'] <descendant> rule outside the four .style-vignette … > .sv-canvas ones. Show the count from a script over the unpacked tarball, not from a grep -c over a tree you have been editing, and quote both commands.
• This card opens NO pull request, so nothing moves its status automatically: transition it by hand on the evidence above, and paste that evidence in a comment.
• ORDERING — every criterion reads on a tag and on a registry, both of which exist only after the bump card has MERGED. That is why the bump is a blocked_by edge and not a step here. Nothing reads on motir-marketing; the re-pin is the sibling card blocked by this one.