The "sol identity" agent-name field reset to "sol" when the owner pressed Enter. Its form's only button ("reset to default") had no `type`, so it defaulted to `type="submit"`, and pressing Enter in the lone text input triggered an implicit form submission that clicked it — firing the reset-to-default handler and persisting the reset server-side (`onsubmit="return false;"` cancels only navigation, not the dispatched click). The agent-name input was also the one settings text input without a `data-section`, so it was excluded from the generic Enter-to-save handler — which is why Enter didn't commit here like it does in every other box. - Give all three untyped settings-form buttons an explicit `type="button"` (resetAgentName, createPersonalBtn, redactAddBtn) so Enter can never fire an implicit submit. redactAddInput keeps its own dedicated Enter→add handler, so Enter-to-add there is unaffected. - Add an Enter→blur handler to the agent-name input so Enter commits the typed name via the existing change-listener save path, matching every other settings text box. - Regression guard: an HTMLParser-based test asserts no button inside a settings-form lacks an explicit `type`, plus targeted tests pinning the agent-name and redact Enter behaviors. Reported by a Linux tester (batch #9). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>