[Chore] Record Roomote 0.4.2 on develop after main hotfix

[roomote-roomote]

Opened on behalf of Matt Rubens. Follow up by mentioning @roomote-roomote, in the web UI, or in Slack.

Related issue

Companion to the production hotfix PR #302.

Why this PR exists

• A maintainer explicitly invited this PR in the linked issue or discussion
• I am a maintainer / this is internal Roomote work

What changed

Records product version 0.4.2 and the matching changelog bullet on develop after the main-only Slack setup hotfix so the next normal develop release does not try to re-use the v0.4.2 tag.

No product code changes — package.json + CHANGELOG.md only. The #299 code is already on develop.

⚠️ Merge order (required)

1. First merge and ship #302 to main so v0.4.2 is tagged from the main-only hotfix tree.
2. Only after that tag exists, squash-merge this PR into develop.

If this lands while v0.4.2 is still untagged, the develop release workflow could freeze the full develop tip as 0.4.2 by mistake. Do not merge early.

How it was tested

• Diff is version/changelog-only against develop
• Pre-push lint:fast / check-types:fast / knip passed

Related PRs

• 0.4.2 production hotfix

Checklist

• The PR title follows the repo convention: [Fix], [Feat], [Improve], [Refactor], [Docs], or [Chore] followed by a user-facing description
• This PR is small and scoped to one change
• pnpm lint and pnpm check-types pass locally
• I added tests or included a clear manual validation note above
• I removed secrets, tokens, private keys, and customer data from code, logs, and screenshots
• If this change should appear in the changelog, I ran pnpm changeset

[roomote-roomote]

No code issues found. Version/changelog-only sync: package.json 0.4.1 → 0.4.2 plus a matching ## 0.4.2 changelog entry, consistent with the existing release format. See task

_{Reviewed d091fb5}