mirror of
https://github.com/openclaw/openclaw.git
synced 2026-08-24 19:35:28 -06:00
Peter Steinberger
946e49cb80
* fix(ui): block renaming config map keys that still hold redacted secrets Renaming a map entry whose value is the server redaction sentinel moves the sentinel to a new key. The gateway's exact-key restore then fails closed forever (dead-end draft with a Retry that can never succeed), and when the rename is folded with a delete of the target key inside one autosave window, the restore silently binds the deleted entry's old credential under the new name and drops the intended one — a green Saved with the wrong secret. The rename handler is the only owner that knows a sentinel was moved rather than typed, so it now rejects the rename like the existing duplicate-key guard and explains the retype path via input validity. Plain values rename exactly as before. * chore(ui): record startup JS growth for the redacted-rename guard string The renameRedactedBlocked validity message in the startup en locale adds 65 gzip bytes over the recorded baseline; record the CI-measured size per the established baseline pattern.