chore(cli): release 0.2.0

[hsskey]

Why

The merged per-side stroke-width feature (PR#5) needs a semver minor bump so owners can publish @hsskey/tokenloom@0.2.0 to npm. Published 0.1.0 predates that capability.

What changed

• apps/cli/package.json: version 0.1.0 → 0.2.0
• apps/cli/test/installed-package.test.ts: fixed packed-manifest version assertion to 0.2.0

No implementation, docs, or historical evidence rewrites.

How I checked

pnpm build
pnpm --filter @hsskey/tokenloom test
pnpm typecheck
pnpm lint

pnpm --filter @hsskey/tokenloom test exit 0 (298 passed, including installed-package.test.ts and direct-input.test.ts stroke cases).

Fresh offline Node v22.23.2 packed-install validation of hsskey-tokenloom-0.2.0.tgz (sha256 93c526d2eec99e71529bd69ced5fc8247e557da74b859a526facbf640abe004c): uniform, per-side, unequal, unknown, unknown --strict, and no-width stroke behaviors all match expected receipts.

CI on this PR: fast passed; full skipped (not a failure).

npm whoami returns ENEEDAUTH in the current context — publication not performed.

What I left alone

• No npm publish, credential changes, or Figma/plugin updates
• No weakened gates, no vitest -u, no rewritten committed evidence
• No blanket version replacement across docs or lock metadata beyond the installed-package test assertion

Separate merge and publication approval are required. Publish the validated tarball (hsskey-tokenloom-0.2.0.tgz, sha256 above) or rebuild with pnpm build && npm pack and re-verify after merge; do not publish from an unverified stale dist/.