chore(windows): sync release v1.0.21 to main [skip ci]

[github-actions]

Auto-generated: stamps desktop/windows/package.json to v1.0.21 to match the v1.0.21-windows release.

[Git-on-my-level]

Thanks for the automated Windows release sync. I reviewed the current head statically.

This PR only changes desktop/windows/package.json from 1.0.20 to 1.0.21, and that matches the published v1.0.21-windows release tag (Omi for Windows 1.0.21 (beta)). I do not see a code-level blocker in the diff itself.

I’m leaving this as maintainer-review rather than approval because it is a release/package-version sync with [skip ci]: please have a human maintainer confirm that main should be stamped to this Windows release and that the skipped CI is intentional before merge.

---

by AI on behalf of David — if you need David’s attention urgently, please @Git-on-my-level and escalate with need human response.

[Git-on-my-level]

Thanks for the automated Windows release sync. I re-checked this head against the current main state before taking action.

This PR is now superseded: main already has desktop/windows/package.json at 1.0.23, while this branch still stamps it to 1.0.21, and newer Windows releases (v1.0.22-windows through at least v1.0.26-windows) have been published. GitHub also reports the PR as not mergeable (dirty). Merging this stale sync would risk moving the Windows package version backward rather than bringing main up to date.

Closing this as superseded rather than requesting more work from the bot. If a release-sync PR is still needed, it should be regenerated from the current main for the latest intended Windows release.

---

by AI on behalf of David — if you need David’s attention urgently, please @Git-on-my-level and escalate with need human response.

[github-actions]

Hey @github-actions[bot] 👋

Thank you so much for taking the time to contribute to Omi! We truly appreciate you putting in the effort to submit this pull request.

After careful review, we've decided not to merge this particular PR. Please don't take this personally — we genuinely try to merge as many contributions as possible, but sometimes we have to make tough calls based on:

• Project standards — Ensuring consistency across the codebase
• User needs — Making sure changes align with what our users need
• Code best practices — Maintaining code quality and maintainability
• Project direction — Keeping aligned with our product principles and locked invariants

Before your next PR, please skim:

• PRODUCT.md — product north star
• Product invariants — locked rules (shared chat, memory tiers, agent control plane, integrations, brand)

If this was declined for direction or taste, maintainers should cite an invariant ID or open a proposed one — ask if that citation is missing.

Your contribution is still valuable to us, and we'd love to see you contribute again in the future! If you'd like feedback on how to improve this PR or want to discuss alternative approaches, please don't hesitate to reach out.

Thank you for being part of the Omi community!