docs: refresh user-facing guides and examples

- Clarify current integration, media review, and Anki behavior
- Remove obsolete AI translation and configuration references
- Standardize headings and prose across docs

docs-site/architecture.md

@@ -20,7 +20,7 @@ Within the desktop app, `src/main.ts` is a composition root that wires small run
   - services compose through explicit inputs/outputs
   - orchestration is separate from implementation
 
-## Project Structure
+## Project structure
 
 ```text
 launcher/                 # Standalone CLI launcher wrapper and mpv helpers
@@ -33,7 +33,6 @@ plugin/
                           #   state · messages · hover · ui · options · environment · log
                           #   binary · session_bindings · version)
 src/
-  ai/                      # AI translation provider utilities (client, config)
   main-entry.ts           # Background-mode bootstrap wrapper before loading main.js
   main.ts                  # Entry point - delegates to runtime composers/domain modules
   preload.ts               # Electron preload bridge
@@ -86,7 +85,7 @@ src/
   anki-integration/        # AnkiConnect proxy server + note-update enrichment workflow
 ```
 
-### Service Layer (`src/core/services/`)
+### Service layer (`src/core/services/`)
 
 - **Overlay/window runtime:** `overlay-manager.ts`, `overlay-window.ts`, `overlay-visibility.ts`, `overlay-bridge.ts`, `overlay-runtime-init.ts`, `overlay-content-measurement.ts`
 - **Shortcuts/input:** `shortcut.ts`, `overlay-shortcut.ts`, `overlay-shortcut-handler.ts`, `shortcut-fallback.ts`, `numeric-shortcut.ts`
@@ -98,7 +97,7 @@ src/
 - **Config/runtime controls:** `config-hot-reload.ts`, `runtime-options-ipc.ts`, `cli-command.ts`, `startup.ts`
 - **Domain submodules:** `anilist/*` (token/update queue/updater), `immersion-tracker/*` (storage/session/metadata/query/reducer)
 
-### Renderer Layer (`src/renderer/`)
+### Renderer layer (`src/renderer/`)
 
 The renderer keeps `renderer.ts` focused on orchestration. UI behavior is delegated to per-concern modules.
 
@@ -136,12 +135,12 @@ src/renderer/
     platform.ts            # Layer/platform capability detection
 ```
 
-### Launcher + Plugin Runtimes
+### Launcher + plugin runtimes
 
 - `launcher/main.ts` dispatches commands through `launcher/commands/*` and shared config readers in `launcher/config/*`. It handles mpv startup, app passthrough, Jellyfin helper commands, and playback handoff.
 - `plugin/subminer/main.lua` is the mpv entrypoint: it sets up the module path and loads `init.lua`, a thin shim that boots the modular Lua files: `bootstrap.lua` (startup), `lifecycle.lua` (connect/disconnect), `process.lua` (process management), `state.lua` (shared state), `messages.lua` (IPC), `hover.lua` (hover-token highlight rendering), `ui.lua` (OSD rendering), `options.lua` (config), `environment.lua` (detection), `log.lua` (logging), `binary.lua` (path resolution), `session_bindings.lua` (configurable session keybindings), `version.lua` (version metadata). AniSkip intro detection lives in the SubMiner app (`src/main/runtime/aniskip-runtime.ts`), which drives mpv chapters and the skip key over the IPC socket.
 
-## Flow Diagram
+## Flow diagram
 
 The main process orchestrates a single primary overlay window plus modal surfaces: `main.ts` delegates to composition modules that wire together domain services. Subtitle layers (primary + secondary bar) are rendered in the same overlay renderer process, connected through `preload.ts`. External runtimes (launcher CLI and mpv plugin) operate independently and communicate via IPC socket or CLI passthrough.
 
@@ -224,7 +223,7 @@ flowchart TB
   style ExtRt fill:#363a4f,stroke:#494d64,color:#cad3f5
 ```
 
-## Composition Pattern
+## Composition pattern
 
 Most runtime code follows a dependency-injection pattern:
 
@@ -261,14 +260,14 @@ Additional conventions in the current code:
 - Domain barrels in `src/main/runtime/domains/*` re-export runtime handlers + main-deps builders, while composers in `src/main/runtime/composers/*` assemble larger runtime clusters.
 - Many runtime handlers accept `*MainDeps` objects generated by `createBuild*MainDepsHandler` builders to isolate side effects and keep units testable.
 
-### IPC Contract + Validation Boundary
+### IPC contract + validation boundary
 
 - Central channel constants live in `src/shared/ipc/contracts.ts` and are consumed by both main (`ipcMain`) and renderer preload (`ipcRenderer`) wiring.
 - Runtime payload parsers/type guards live in `src/shared/ipc/validators.ts`.
 - Rule: renderer-supplied payloads must be validated at IPC entry points (`src/core/services/ipc.ts`, `src/core/services/anki-jimaku-ipc.ts`) before calling domain handlers.
 - Malformed invoke payloads return explicit structured errors (for example `{ ok: false, error: ... }`) and malformed fire-and-forget payloads are ignored safely.
 
-### Runtime State Ownership (Migrated Domains)
+### Runtime state ownership (migrated domains)
 
 For domains migrated to reducer-style transitions (for example AniList token/queue/media-guess runtime state), follow these rules:
 
@@ -278,7 +277,7 @@ For domains migrated to reducer-style transitions (for example AniList token/que
 - Reducer boundary: when a domain has transition helpers in `src/main/state.ts`, new callsites should route updates through those helpers instead of ad-hoc object mutation in `main.ts` or composers.
 - Tests for migrated domains should assert both the intended field changes and non-targeted field invariants.
 
-## Playback Startup Flow
+## Playback startup flow
 
 Before the app boots, something has to launch mpv, inject the plugin, and bring the overlay up. SubMiner-managed launches own this step - the `subminer` launcher, the app's own playback, and the packaged Windows shortcut all follow the same path. The launcher reads `config.jsonc`, spawns mpv with the IPC socket and the bundled plugin, and passes runtime settings as `--script-opts`. The plugin never reads a config file: the shipped `subminer.conf` is intentionally empty so command-line opts always win.
 
@@ -315,7 +314,7 @@ flowchart TB
 
 The runtime sockets in this flow are detailed in [IPC + Runtime Contracts](./ipc-contracts#runtime-sockets).
 
-## Program Lifecycle
+## Program lifecycle
 
 - **Module-level init:** Before `app.ready`, the composition root registers protocols, sets platform flags, constructs all services, and wires dependency injection. `runAndApplyStartupState()` parses CLI args and detects the compositor backend.
 - **Startup:** If `--generate-config` is passed, it writes the template and exits. Otherwise `app-lifecycle.ts` acquires the single-instance lock and registers Electron lifecycle hooks.
@@ -387,7 +386,7 @@ flowchart TB
   style Loop fill:#363a4f,stroke:#494d64,color:#cad3f5
 ```
 
-## Subtitle Prefetch Pipeline
+## Subtitle prefetch pipeline
 
 SubMiner can pre-tokenize upcoming subtitle lines before they appear on screen. When an external subtitle file (SRT, VTT, or ASS) is detected on the active track, the `SubtitlePrefetchService` parses all cues via the subtitle cue parser (`subtitle-cue-parser.ts`), identifies a priority window of upcoming lines based on the current playback position, and tokenizes them in the background through the same pipeline used for live subtitles. Results are stored directly into the `SubtitleProcessingController` cache, so when a subtitle actually appears during playback, it hits a warm cache and renders in ~30-50ms instead of ~200-320ms.
 
@@ -417,7 +416,7 @@ flowchart TB
   style Render stroke-width:2px
 ```
 
-## Why This Design
+## Why this design
 
 - **Smaller blast radius:** changing one feature usually touches one service.
 - **Better testability:** most behavior can be tested without Electron windows/mpv.
@@ -428,7 +427,7 @@ flowchart TB
 - **Split MPV service layers:** MPV internals are separated into transport (`mpv-transport.ts`), protocol (`mpv-protocol.ts`), and properties/render metrics modules for maintainability.
 - **Config by domain:** defaults, option registries, and resolution are split by domain under `src/config/definitions/*` and `src/config/resolve/*`, keeping config evolution localized.
 
-## Extension Rules
+## Extension rules
 
 - Add behavior to an existing service in `src/core/services/*` or create a focused runtime module under `src/main/runtime/*`; avoid ad-hoc logic in `main.ts`.
 - Add new cross-process channels in `src/shared/ipc/contracts.ts` first, validate payloads in `src/shared/ipc/validators.ts`, then wire handlers in IPC runtime modules.