Version 0.20260727.0

[agarny]

No description provided.

[Copilot]

Pull request overview

This PR performs a release/version bump to 0.20260727.0, updates a few build/dependency versions (and corresponding Bun lockfiles), and expands the renderer README with deployment guidance for cross-origin isolation required by libOpenCOR.

Changes:

• Bump package versions to 0.20260727.0 (root + renderer) and update dependency versions (e.g., postcss, tar) with lockfile refreshes.
• Add a “Deployment” section to src/renderer/README.md describing COOP/COEP setup for cross-origin isolation.
• Minor README cleanup (Repobeats image alt text).

Reviewed changes

Copilot reviewed 4 out of 6 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
src/renderer/README.md	Adds deployment documentation and refines usage/props documentation.
src/renderer/package.json	Bumps renderer package version and updates postcss.
src/renderer/bun.lock	Updates lockfile to reflect renderer dependency changes.
README.md	Adjusts Repobeats image alt text.
package.json	Bumps root version and updates postcss/tar.
bun.lock	Updates lockfile to reflect root dependency changes.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 6 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (2)

src/renderer/README.md:78

• The README now states the theme prop is simply "The theme to use", but the implementation applies props.theme once during setup (setTheme(props.theme)) and does not watch for changes. This documentation change makes the API behavior unclear/incorrect for consumers expecting reactivity.

| `theme` | `'light'` \| `'dark'` \| `'system'` | `'system'` | The theme to use.                                                                       |

src/renderer/README.md:65

• The guidance for serving libOpenCOR from a different origin is incorrect: setting Cross-Origin-Embedder-Policy on .js/.wasm subresource responses does not make them loadable under COEP: require-corp. Cross-origin module/wasm loads need to be CORS-enabled (and optionally CORP), otherwise the browser will still block them.

On the other hand, if you serve it from a different path on a different origin, then they need a way to signal that they can be loaded cross-origin under COEP. In practice, a straightforward approach that works across server setups is to set the same `Cross-Origin-Embedder-Policy` header already used on the HTML page. While COEP is semantically a document-level policy, Web browsers ignore it on subresource responses, so setting it here is harmless and avoids subtle server-specific issues with other headers. With Apache, place a `.htaccess` file in the download directory (or one of its parent directories):

```apache
<IfModule mod_headers.c>
    <FilesMatch "\.(js|wasm)$">