Orphaned options/ folder — manifest has no options page, AccountsSection is dead code

[Loule95450]

Context

The directory extension/src/options/ looks like an options-page implementation (it has components/, an api.ts, a styles.css). It is not. The components are all re-imported by SettingsScreen.tsx (which renders the in-popup settings flow), and there is no entrypoints/options/ and no options_ui/options_page in wxt.config.ts. The folder naming misleads readers and contributors.

Problem / Observation

• extension/wxt.config.ts:11-39 declares only popup/content/background entrypoints; no options page.
• extension/src/entrypoints/ only contains background.ts, content.ts, popup/.
• extension/src/options/api.ts is a one-line re-export of shared/api.ts (export { BackgroundError, send } from "../shared/api.js";), 100% duplicated of popup/api.ts:1.
• extension/src/options/styles.css is two lines.
• extension/src/options/components/AccountsSection.tsx (109 lines) is NEVER imported — confirmed via grep -rn "AccountsSection" src/ returning only the definition. Pure dead code.

Proposed approach

Either:

1. Promote it: add extension/src/entrypoints/options/ with an index.html + main.tsx, declare options_ui in wxt.config.ts, and route from the popup's chrome.runtime.openOptionsPage() when desktop screen real estate is available. Bitwarden-style.
2. Demote it: rename src/options/ → src/settings/, delete api.ts and styles.css (the popup already owns these), and delete AccountsSection.tsx.

Option 2 is the smaller surgical change. Pick (1) only if a real options UI is on the roadmap.

Acceptance criteria

• Either an options entrypoint exists and is reachable, OR the folder is renamed to reflect its actual role.
• AccountsSection.tsx is deleted unless wired up.
• extension/src/options/api.ts is removed or its duplicate is justified in a comment.
• Imports across SettingsScreen.tsx etc. are updated.
• npm run typecheck and npm run lint are green.