すべてを、AIエージェントのコンテキストに。

The setting looked saved during the session, but a full relaunch exposed the real problem: save() wrote to a different path from the one load() read.

What you checked

• Activity: SettingsStore.swift in Cursor, Apple's atomic-write reference in Chrome, and the Terminal test run.
• Agent History: Claude Code outlined the checks, Codex diagnosed the path mismatch, and Cursor changed the write path with atomic replacement.
• STM: the three focused tests passed, while the signed staging check remained open.
• LTM: the durable decision is to read and write one Codable payload at one path.

What that suggests

This was a persistence-across-launches issue, not a failure of the setting control itself. The local fix has test evidence, but that does not establish behavior in the signed app.

Next: change the setting in the signed staging build, quit fully, relaunch, and confirm the value before approval.

Resume at the signed staging build. Change the setting, quit the app completely, relaunch, and check the saved value. Record that result in the staging checklist before approval. If it resets, compare the file path the signed build reads with the path it writes; the focused local tests already passed.