Qiu Yuzhou effae048b8 feat(settings): remove holistic preferences reset ...

Not every preference warrants a reset; future resets are per
configuration item, added only where a field truly needs one (tracked
in #69). The whole chain goes: the 恢复默认 button and its confirmation
alert in SettingsView, the SettingsWorkflow reset/confirm/cancel
commands and the confirmation machinery they existed for (the
SettingsConfirmation enum had a single case), the
SettingsCommitting.resetPreferences seam entry, the runtime
resetPreferences() and ProxySettingsFileStore.reset() with its
file-rollback helpers and the rollbackFailed store error.

CONTEXT.md drops the three stale reset phrases and now records the
domain decision: no restore-all-factory-defaults action for
preferences; a reset, where it exists, is scoped to one configuration
item. ADR-0004/0005/0011 carry amendment notes since their reset
sentences describe a removed capability (0004's also predate the
PAC removal).

2026-09-27 13:29:32 +08:00

..

adr

feat(settings): remove holistic preferences reset

2026-09-27 13:29:32 +08:00

agents

docs(agents): require explicit --repo on gh (fork has upstream remote)

2026-09-20 03:42:53 +08:00

research

feat(proxy): remove PAC and accept ACL system proxy path

2026-09-26 21:58:12 +08:00