release: next release tracking — UI state migration + openclaw + Hermes bumps

[MCERQUA]

Tracking issue for the release after v2026.5.4.

Top 3 priorities

1. refactor: migrate UI state context from user message to workspace file #94 — Migrate UI state context from user message to workspace file (priority promoted)

   • Per-turn state prefixes (canvas, music, tracks, pages, current_user, office_briefing) accumulate in conversation history and waste tokens through compaction
   • PR feat(office): persist clerk_user_id + extend CURRENT_USER with office briefing #297 in v2026.5.4 made this worse by adding two more prefixes (CURRENT_USER + OFFICE_BRIEFING)
   • Migrate all to `workspace/UI_STATE.md` injected via system prompt — refreshes every turn, never accumulates

2. release: bump openclaw pin from 2026.3.24 to 2026.5.2 (latest) #300 — Bump openclaw pin 2026.3.24 → 2026.5.2 (latest)

   • 6 weeks of upstream changes uncaptured
   • Must update all 3 sync points: `docker-compose.yml`, `deploy/openclaw/Dockerfile`, `setup-sudo.sh`
   • Use `bump-openclaw-version.sh`

3. release: bump Hermes Agent plugin from 0.6.0 to 0.12.0 (latest) #301 — Bump Hermes Agent plugin 0.6.0 → 0.12.0 (latest)

   • 6 minor version bumps from Nous Research
   • Voice + 14-provider config + sub-agents need regression testing

Suggested order

1. Bump openclaw + Hermes pins first (smaller, isolated changes — establish a clean baseline)
2. Tackle refactor: migrate UI state context from user message to workspace file #94 on top of the new openclaw — depends on `workspace/UI_STATE.md` injection behavior, which is openclaw bootstrap territory and may have improved upstream
3. Image rebuild + 10-container roll, same release sequence as v2026.5.4 (dev → main → tag → release → npm publish auto)