[cursor]

Summary

Prevent the TUI from silently recreating config.json and keyring-backed settings after Settings reset. A reset now marks the running app as needing restart, blocks subsequent Settings/layout persistence in that session, and reports reset failures.

Crate(s)

• romm-api
• romm-cli
• romm-tui
• docs / CI only

Checklist

• cargo fmt --check passes
• Both cargo clippy runs pass (--all-features and --no-default-features, -D warnings)
  • Ran scoped check: cargo +stable clippy -p romm-tui --all-targets -- -D warnings
• cargo test --workspace passes (or scoped tests with reason)
  • Scoped tests: cargo +stable test -p romm-tui
• PR title uses Conventional Commits with the right scope for the changelog
• No secrets, tokens, or personal config in the diff
• User-facing changes documented in the relevant docs/*.md if needed
  • Not needed: preserves existing Settings reset message/behavior, but prevents stale in-memory persistence until restart.