fix: preset-mobile peer dep needs republish (0.3.0 → 0.4.0)

[leefanv]

Summary

The 0.4.0 release (#8) updated preset-mobile's peer
@omit-design/engine from ^0.3.0 to ^0.4.0 locally, but I declared
preset-mobile "unchanged" in that PR and didn't republish it. The
npm-published preset-mobile@0.3.0 still demands engine ^0.3.0, so
npx @omit-design/cli@latest init followed by npm install fails:

npm error ERESOLVE unable to resolve dependency tree
npm error While resolving: smoke@0.1.0
npm error Found: @omit-design/engine@0.4.0
npm error peer @omit-design/engine@"^0.3.0" from @omit-design/preset-mobile@0.3.0

Fix

• preset-mobile 0.3.0 → 0.4.0. Only peerDependencies.@omit-design/engine range changed; no source / API change. Per SemVer narrowing a peer range is breaking, so minor (pre-1.0).
• template pin @omit-design/preset-mobile ^0.3 → ^0.4 in templates/init/package.json.tmpl.
• cli 0.4.1 → 0.4.2 carrying the template-pin change. No CLI source change.

Test plan

• bun run --filter @omit-design/cli build — green
• Fresh omit-design init demo → package.json pins preset-mobile ^0.4
• bun install resolves cleanly with file: overrides (mirroring future npm state)
• bun run lint → ✓ no design/*.tsx files yet — nothing to lint exit 0

Publish plan

Order matters (engine peer relationship):

cd packages/preset-mobile && npm publish --access public
cd ../cli                 && npm publish --access public

engine 0.4.0 / dev-server 0.2.0 / eslint-plugin 0.3.0 / figma-plugin 0.1.2 remain unchanged.

🤖 Generated with Claude Code