Replace the provider-only modal with an extensible Settings experience

[fhemmerrelias]

Parent

#70

What to build

Replace the current provider checkbox modal with a settings window that can host General, Accounts, Alerts, Appearance, Widgets, and About sections. This slice must deliver global refresh controls, account navigation, credential status, reset behavior, and extension points for the remaining parity features.

Acceptance criteria

• Settings has navigable General, Accounts, Alerts, Appearance, Widgets, and About sections
• Auto Refresh supports Off, 1, 5, 15, 30, and 60 minute choices
• Accounts can be added, edited, enabled, disabled, and removed through the account model
• Credential availability and secure-store failures are visible without exposing secrets
• Reset Accounts requires confirmation and removes accounts and credentials safely
• Keyboard navigation, persistence, and cancellation paths are tested
• All repository quality gates pass

Blocked by

• Introduce account-scoped provider configuration with migration #73
• Move API keys and tokens into Windows secure credential storage #74

[HemSoft]

Mission hard-block proof for #91.

This issue is not implemented or delivered. Its declared prerequisite chain is held on #73. The dependency graph was checked against each issue body, not inferred from issue age.

Direct prerequisites: #73, #74.

The missing external requirement is connected Codex review capacity for requester HemSoft. Delivery of the foundation cannot proceed without its required real current-head review. Two distinct self-service paths failed:

1. Automatic review returned an explicit account quota refusal. It was also refused on PR114 and PR115.
2. One explicit request received the same refusal. That is shared requester-capacity evidence, not a clean review of revised code.

No safe repository-code default supplies that required review. Unreviewed foundation delivery, replacing the reviewer, buying credits or waiving the policy is not authorized. Restoring connected Codex capacity is the exact next need. Any alternative policy requires explicit owner authority. Subsequent implementation remains agent work after prerequisites are delivered, not a claim that the owner must write code.

This issue stays open. The final revisit and item-by-item incomplete-run report are recorded in the mission ledger. No lifecycle-completion notification has been sent for unfinished work.