chore(release): prepare 1.3.15-Beta.4

[appergb]

User description

5 文件版本同步 1.3.15-Beta.3 → 1.3.15-Beta.4（package.json / package-lock.json / tauri.conf.json / Cargo.toml / Cargo.lock），版本同步闸门要求。

内容：胶囊样式可选（#887）+ 此前全部合并项。Beta.4 发布前的版本准备。

---

PR Type

Other

---

Description

• Bump app version from 1.3.15-Beta.3 to 1.3.15-Beta.4

• Sync version across package.json, Cargo.toml, and tauri.conf.json

• Prepare the Beta.4 release build

---

File Walkthrough

Relevant files

Configuration changes

package.json Bump npm package version to Beta.4                                              openless-all/app/package.json Bump npm app version from 1.3.15-Beta.3 to 1.3.15-Beta.4 +1/-1      Cargo.toml Bump Rust crate version to Beta.4                                                openless-all/app/src-tauri/Cargo.toml Update Rust crate version from 1.3.15-Beta.3 to 1.3.15-Beta.4 +1/-1      tauri.conf.json Bump Tauri app version to Beta.4                                                  openless-all/app/src-tauri/tauri.conf.json Set Tauri app version to 1.3.15-Beta.4 +1/-1

---

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis 🔶 887 - Partially compliant Compliant requirements: None Non-compliant requirements: None Requires further human verification: Capsule style selector, Classic pill rendering/interaction, and capsuleStyle preference/payload behavior are not part of this release-prep diff and need manual verification in the Beta.4 build. Classic pill click/passthrough handling and audio-thread lock fix need verification through the merged feat(capsule): 录音胶囊样式可选（流光 Siri / Openless 默认）+ 修复 beta 构建破坏 #887 implementation. Build/test gates for the Beta.4 state need confirmation.

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Version Sync The diff bumps the version to 1.3.15-Beta.4 in package.json, Cargo.toml, and tauri.conf.json, but it does not show updates to package-lock.json or Cargo.lock. If those lockfiles still reference 1.3.15-Beta.3, npm ci and cargo build --locked will fail due to version mismatch during the release build. Confirm that the lockfile version sync described in the PR description is actually included in the full PR. "version": "1.3.15-Beta.4",