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

[github-actions]

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

[Git-on-my-level]

Thanks for keeping the Windows release metadata in sync.

I reviewed the current head (f11a44f632e69a6d0cba65738b411cf2136f8720) statically. The PR only updates desktop/windows/package.json from 1.0.23 to 1.0.25, and the v1.0.25-windows GitHub release exists with the expected Windows installer/update assets.

I do not see a code or dependency-install change in this diff. I’m not formally approving because this is release/version metadata with [skip ci] and most checks were skipped, so a human maintainer should confirm this is the intended release-sync commit 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 keeping the Windows release metadata in sync. This PR is now superseded: main already has desktop/windows/package.json at 1.0.29, and newer Windows releases exist after v1.0.25-windows (including v1.0.30-windows). Merging this head would move the package version backward to 1.0.25.\n\nClosing this stale release-sync PR so the queue reflects the current Windows release state.

[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!