[Chore] Record Roomote 0.45.1 on develop after production hotfix

[roomote-roomote]

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

What changed

Records product version 0.45.1 and the matching Notion hotfix changelog section on develop after the direct-main production hotfix.

This PR changes only package.json and CHANGELOG.md. The Notion implementation from #1825 is already present on develop, and develop's unrelated pending changesets remain untouched.

Why this change was made

The production hotfix increments main from 0.45.0 to 0.45.1. Recording the same version and release notes on develop prevents the next normal release from trying to reuse the v0.45.1 tag.

Merge and tag instructions

1. First merge production hotfix #1840 into main with a merge commit. Do not squash or rebase it.
2. Wait for the Tag Product Release workflow to succeed and verify the remote tag v0.45.1 exists.
3. Only after v0.45.1 exists, squash-merge this companion PR into develop.
4. Do not merge this PR early. Before the tag exists, a develop push at version 0.45.1 can make the Release workflow freeze the full develop tip as release/v0.45.1 and open an incorrect production Promote PR.

Once the tag exists, the Release workflow sees v0.45.1 and exits without creating a candidate, which is the intended direct-main hotfix behavior.

Validation

• final diff against current origin/develop is exactly package.json and CHANGELOG.md
• hotfix and companion branch tips contain byte-identical package.json and CHANGELOG.md
• develop's existing pending changesets are unchanged
• release-script tests: 16 passed
• repository formatting check passed
• repository pre-push gate passed: oxlint, residual ESLint, fast monorepo typechecks, and knip

Risk and rollback

The only material risk is merge order: this companion must not land before v0.45.1 exists. If needed before merge, close this PR without affecting production. After merge, reverting this version-record commit would make develop's release lineage stale and should only be done together with an explicit release-plan correction.

Related PRs

• Roomote 0.45.1 production hotfix

[roomote-community]

No code issues found. See task

_{Reviewed 6794f47}