agent: lumotia-rebrand — docs, scripts, root config, residuals

Phase 9 of the rebrand cascade. Sweep covers everything the Phase 8
frontend pass deliberately skipped: docs/, root markdown, scripts,
Cargo.toml descriptions, code comments that survived earlier
word-boundary sed, plus a handful of identifiers caught on the final
verify pass.

transcription-app changes:
- README.md, HANDOVER.md, KNOWN-ISSUES.md, run.sh — magnotia/Magnotia
  -> lumotia/Lumotia.
- docs/ — sweep across all subdirs except docs/handovers/ (preserved
  as immutable audit trail). Includes architecture-map references
  to magnotia_core::*, magnotia_storage::*, etc. now pointing at
  lumotia_*; dev-setup.md tracing output examples (lumotia_startup
  target); brief/ + superpowers/ + issues/ + whisper-ecosystem/ +
  audit/.
- Cargo.toml descriptions on 9 crates (core, audio, cloud-providers,
  hotkey, llm, mcp, plus referenced others).
- crates/core/src/{error,hardware,recommendation,paths}.rs +
  crates/audio/src/wav.rs + crates/llm/src/model_manager.rs +
  crates/cloud-providers/src/keystore.rs + crates/mcp/src/lib.rs —
  doc comments and a model-manager user-agent string.
- Caught on final pass: BroadcastChannel("magnotia_task_sync") -> ...
  ("lumotia_task_sync"); magnotia_locale i18n localStorage key
  renamed + migration shim added; CSS keyframe names
  magnotiaPulse / magnotiaBar / magnotiaFade renamed in the design-
  system kit; magnotia_viewer_item / magnotia_viewer_mode handoff
  keys renamed in HistoryPage + viewer/+page.svelte; src/assets/
  wordmark.svg text.
- src-tauri/src/lib.rs comment cleanup ("magnotia era" was sed'd
  to "lumotia era" earlier — restored).

Preserved (intentional):
- crates/core/src/paths.rs — keeps "magnotia" / "Magnotia" / ".magnotia"
  legacy detection strings in legacy_and_target_paths() so the
  migration shim can still find user data from the magnotia era.
- src/lib/stores/{page,focusTimer}.svelte.ts + src/lib/i18n/index.ts
  — migration call sites reference the legacy magnotia keys
  deliberately.
- docs/handovers/ — historical audit trail.

cargo build --workspace passes. npm run check: 0 errors / 0 warnings
(3958 files). cargo test --workspace: 339 pass / 0 fail.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

docs/architecture-map/04-llm-formatting-mcp/formatting-correction-learning.md

@@ -13,12 +13,12 @@ last_verified: 2026/05/09
 
 ## At a glance
 
-- Crate: `magnotia-ai-formatting`
+- Crate: `lumotia-ai-formatting`
 - Path: `crates/ai-formatting/src/correction_learning.rs`
 - LOC: 229
 - Public surface:
   - `pub fn extract_corrections(original_text: &str, edited_text: &str, existing_terms: &[String]) -> Vec<String>` (`crates/ai-formatting/src/correction_learning.rs:131`)
-  - Re-exported at crate root as `magnotia_ai_formatting::extract_corrections` (`crates/ai-formatting/src/lib.rs:7`).
+  - Re-exported at crate root as `lumotia_ai_formatting::extract_corrections` (`crates/ai-formatting/src/lib.rs:7`).
 - External deps that matter: none — pure CPU, pure stdlib.
 - Tauri command that calls this (slice 2, best guess): `commands::profiles.rs:14` imports it; the actual call is at `src-tauri/src/commands/profiles.rs:165`. The wrapper command is named in `profiles.rs` (likely `learn_corrections_*_cmd` — check slice 2's profiles page).
 
@@ -105,7 +105,7 @@ which then appears as PostProcessOptions.dictionary_terms in the next pipeline r
 - **Casing is preserved in the output.** The dedupe set is lowercased (so two corrections that differ only in casing collapse to one), but the kept variant is whatever case the user typed. If a user types `Sinead` and `SINEAD` in the same edit, the first one wins.
 - **`existing_terms` should pass the user's full custom dictionary.** The function lowercases internally; the caller can pass any casing. Filling this in correctly is the difference between "we keep suggesting CORBEL the user already added" and "we only suggest new terms".
 - **Substitutions only — no insertions or deletions.** A user inserting a new word that the ASR did not pick up at all is not a "correction" to anything; it is content. The aligner correctly leaves it as `(None, Some(_))` and the subsequent matcher ignores those.
-- **No language awareness.** The function does not know about morphological variants. `"organize" → "organise"` is correctly detected as a 1-character substitution (because `to_british_english` would have done it earlier in the pipeline), but if a user edits a transcript Magnotia did not Britanise, the function will happily learn `organise` as a new term — duplicating work.
+- **No language awareness.** The function does not know about morphological variants. `"organize" → "organise"` is correctly detected as a 1-character substitution (because `to_british_english` would have done it earlier in the pipeline), but if a user edits a transcript Lumotia did not Britanise, the function will happily learn `organise` as a new term — duplicating work.
 - **`find_edited_region` heuristic floor is 30%.** Below that match-score, the function gives up alignment and returns the whole edited text, which is then very likely to fail the rewrite-ratio gate. Effectively a graceful "I don't know what changed, skip it" path.
 
 ## See also