Cherry-pick the still-relevant fixes from recent draft PRs without pulling in stale release/docs changes:
- serialize dashboard data loads to avoid concurrent config self-heal writes
- preserve valid per-model default blocks during dashboard model self-heal
- pass structured humanizeError results directly to toast for model import scan failures
- align frontend kernel isLatest with suffix-aware recommended version ordering
Verification:
- node --test tests/*.test.js
- npm run build
OpenClaw 2026.5.18/2026.5.19 still uses Gateway WS protocol v4
(PROTOCOL_VERSION=4, MIN_CLIENT_PROTOCOL_VERSION=4), so there is no v5
handshake to implement. The compatibility break is the hello payload
shape: current upstream sends the runtime version at `hello.server.version`
while ClawPanel only read the old flat `hello.serverVersion` field.
Read both shapes so latest kernels keep populating wsClient.serverVersion,
which in turn keeps Dashboard display, kernel snapshot feature gates and
isLatest checks working after the WebSocket handshake succeeds.
Also bump the recommended OpenClaw targets to the current npm latests:
- official: 2026.5.19
- chinese: 2026.5.18-zh.1
Verification:
- node --test tests/kernel.test.js
- npm run build
- manual module check: simulated both hello.server.version and legacy
hello.serverVersion payloads, both report serverVersion and protocol v4
- Fix MiniMax API base URL from api.minimax.chat to api.minimax.io
- Add MiniMax model presets (M2.7, M2.7-highspeed, M2.5, M2.5-highspeed)
with correct context window sizes (1M for M2.7, 204K for M2.5)
- Update MiniMax description to reflect latest M2.7/M2.5 model series
- Add MiniMax to README provider tables (Chinese + English)
- Add 12 unit tests for model presets validation
Co-authored-by: PR Bot <pr-bot@minimaxi.com>
