Release notes: OpenClaw 2026.5.4

[github-actions]

Generate release notes markdown for OpenClaw 2026.5.4 following our release notes guidelines.

Upstream GitHub Release:

• https://github.com/openclaw/openclaw/releases/tag/v2026.5.4

Guidelines:

• release-notes/GUIDELINES.md (in this repo)

Tasks:

• Pull changes/changelog from upstream OpenClaw release/tag v2026.5.4
• Draft a release-notes/ markdown file in zh-TW
• Follow guidelines (分類：功能更新/安全性提升/錯誤修復；每項標註⭐；含用途/解決問題/影響)
• Include ## ⚠️ 升級前必讀 section with Breaking Changes table and 新功能亮點 (required if release has breaking changes; omit if none)
• Include link(s) to the upstream GitHub Release

Acceptance:

• New md file committed in claw-info under release-notes/
• 升級前必讀 section present if release has breaking changes
• Issue closed via PR

[zhudage-agent]

Quick reviewer notes for drafting v2026.5.4 release notes:\n\n1) Please explicitly check whether this release introduces any breaking behavior around messaging visibility and tool/profile constraints, and include only if such breaking changes are confirmed in upstream notes/PRs.\n2) For each major item, keep the guideline triad clear: 用途 / 解決問題 / 影響 (especially operator-impacting config changes).\n3) Prioritize concrete migration guidance over feature listing, e.g. exact config knobs to verify post-upgrade.\n4) Include direct upstream links for the release and high-impact PRs/issues to keep the note auditable.\n\nIf you want, I can do a second-pass review focused on upgrade-risk clarity once the draft PR is up.

[zhudage-agent]

已 review 對應 PR #587，內容涵蓋 breaking changes 與主要更新，結構符合 GUIDELINES.md。若 maintainer 確認無其他 blocking check，可優先合併並關閉本 issue。

[zhudage-agent]

這題的內容目前也被 PR #590 覆蓋（含 2026-05-04）。若維持一次整併策略，建議 merge #590 後關閉本 issue。\n\n另外，2026-05-04 涉及多項 breaking/behavior change，建議在 release notes 開頭加一段『升級前 60 秒檢查清單』，降低誤升級風險。