Codex MacOS App: Git settings text fields clear or revert after a successful save (stale readback)

Before submitting, I searched for existing app-label issues mentioning Git settings persistence and did not find an obvious duplicate; if I missed one, please point me at it and I will consolidate.

What version of the Codex App are you using (from the About Codex dialog)?
26.415.40636 (1799)

What subscription do you have?
Not specified in this public report; I can share privately if maintainers need it for triage.

What platform is your computer?
Darwin 25.4.0 arm64 arm

What issue are you seeing?
On the Git settings page, several free-text settings can show success feedback after saving, but the field then immediately clears or snaps back to an older value instead of showing the value that was just saved.

Affected fields observed at least:

• Branch prefix
• Commit instructions
• Pull request instructions

What steps can reproduce the bug?

1. Open Codex App → Git settings.
2. Change Branch prefix to a new value such as pr/test.
3. Save and observe the success feedback.
4. Check whether the field still shows pr/test or whether it clears/reverts.
5. Repeat the same flow for Commit instructions and Pull request instructions.
6. Navigate away and back, and/or restart the app, and confirm whether the persisted value matches what was saved.

What is the expected behaviour?
After a successful save, the UI should continue to display the saved value, and navigation or restart should load that same value without reverting to a previous one.

Additional information
Possible cause, though I have not verified the source: the settings UI may clear local draft state immediately after success and then re-render from stale persisted state.

https://github.com/user-attachments/assets/b081e1f9-0777-4777-917b-7fc4ca31e41b

Media: I have a screen recording demonstrating the behaviour and will attach it in a comment if needed.

Regression ideas (non-prescriptive): success should not surface until persistence is complete; a successful save should not be followed by stale readback that clears the field; unchanged drafts should still collapse back to the persisted value correctly.