[RELEASE] Unbreak publishing, and ship Fish Audio (carries #5824 + #5055)

[vivekchand]

Re-cuts the release that silently published nothing, and carries the fix that makes publishing work again.

What rides this: #5824 (pipeline fix, merged) and #5055 (Fish Audio, merged — its [RELEASE] produced no upload).

Why a second release PR exists

release-on-merge.yml runs npm ci in frontend/ and had been failing ERESOLVE since #5376 took vite to ^8.2.2 while @vitejs/plugin-react stayed at ^4.7.0 (peers only to ^7). Two separate dependabot PRs, so nothing evaluated them together.

The failure mode is the dangerous one. npm ci in frontend/ runs only on the release path, so every ordinary PR stayed green while a [RELEASE] merge produced no PyPI upload at all. The Fish Audio [RELEASE] (#5821) merged cleanly, reported success, and shipped nothing. It was caught only because the published version was checked afterwards rather than the merge being taken as proof.

The fix, already on main

@vitejs/plugin-react → ^6.1.0, which peers vite: ^8.0.0. package-lock.json regenerated in the same commit, because npm ci requires both files to agree — bumping package.json alone (all that dependabot #5257 proposed) swaps one npm ci failure for another.

Verified by running the release step's own commands rather than reading them:

before (origin/main):  npm ci        -> exit 1, ERESOLVE
after:                 npm ci        -> exit 0, 86 packages
                       npm run build -> exit 0, bundle emitted

What ships to users

Fish Audio as the 24th chat channel: transcripts ingest from ~/.openclaw/fish-audio/*.jsonl, live events arrive over the gateway tap as fishaudio, /api/channel/* serves the tab. Plus tests/test_channel_four_lists.py, which turns the four-list rule from a review item into a check — proven red against a deliberately half-wired channel.

No-PRD: restores a broken release pipeline and re-cuts an already-merged, already-recorded change.

---

🤖 Generated with Claude Code

https://claude.ai/code/session_01Xb6A5G74JiMe3zHFs1JZEP

[8090-software-factory]

✅ Drift Bot (ClawMetry): no drift detected

Drift Bot analyzed the changed files against this project's blueprints and requirements and found no drift.