Extension v1.5.0 release package contains wrong manifest version (still 1.4.1)

[luohui1997]

Title:

Extension v1.5.0 release package contains wrong manifest version (still 1.4.1)

Body:

### Bug Description
After upgrading CLI to v1.5.0, `opencli doctor` reports:

[OK] Daemon: running on port 19825
[OK] Extension: connected (v1.4.1)
⚠ Extension version mismatch: extension v1.4.1 ≠ CLI v1.5.0

The extension packaged in `opencli-extension.zip` from the v1.5.0 release has `manifest_version: "1.4.1"` instead of `"1.5.0"`.

### Steps to Reproduce
1. `npm install -g @jackwener/opencli` → CLI reports v1.5.0
2. Download `opencli-extension.zip` from v1.5.0 release
3. Load as unpacked extension in Chrome
4. Run `opencli doctor` → extension still shows v1.4.1

### Expected Behavior
Extension version should match CLI version (both v1.5.0).

### Environment
- CLI: v1.5.0
- Extension manifest: v1.4.1
- Node.js: v24.14.0
- OS: Windows

### Additional Context
The v1.5.0 changelog mentions "Zero onboarding: extension version check and update notifier (#479)" — this feature is correctly detecting the mismatch. The release package likely needs to be rebuilt with the updated manifest.

---