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-pipeline.md

@@ -13,7 +13,7 @@ last_verified: 2026/05/09
 
 ## At a glance
 
-- Crate: `magnotia-ai-formatting`
+- Crate: `lumotia-ai-formatting`
 - Path: `crates/ai-formatting/src/pipeline.rs`
 - LOC: 211
 - Public surface:
@@ -21,7 +21,7 @@ last_verified: 2026/05/09
   - `pub enum FormatMode { Raw, Clean, Smart }` (`:20`)
   - `impl FormatMode { pub fn parse(&str) -> Self }` (`:27`)
   - `pub fn post_process_segments(segments: &mut Vec<Segment>, options: &PostProcessOptions, llm: Option<&LlmEngine>)` (`:38`)
-- External deps that matter: `magnotia_core::constants::SMART_PARAGRAPH_GAP_SECS`, `magnotia_core::types::Segment`, `magnotia_llm::LlmEngine`. Internal modules: `llm_client`, `rule_based`, `to_plain_text`.
+- External deps that matter: `lumotia_core::constants::SMART_PARAGRAPH_GAP_SECS`, `lumotia_core::types::Segment`, `lumotia_llm::LlmEngine`. Internal modules: `llm_client`, `rule_based`, `to_plain_text`.
 - Tauri command that calls this (slice 2, best guess): three call sites, all in slice 2:
   - `src-tauri/src/commands/transcription.rs:196`, `:317`, `:386` — the file-import and historical-transcript paths.
   - `src-tauri/src/commands/live.rs:891` — the live dictation path.
@@ -103,7 +103,7 @@ Vec<Segment>  +  PostProcessOptions  +  Option<&LlmEngine>
 - **LLM cleanup collapses the segment list.** A 50-segment transcript becomes one segment after a successful LLM call. Any downstream feature that assumes per-segment timing on the LLM-cleaned text needs to skip the LLM stage or run it after a fresh re-segmentation. Cleanup output's `start` and `end` cover the original range, but anything inside is opaque.
 - **LLM error path is silent (eprintln) but visible to the user.** The rule-based output stays; the user sees rule-based text where they expected LLM-cleaned text. There is no surfacing back up to the Tauri layer beyond the eprintln. Worth a structured error if "did the LLM run" becomes user-visible.
 - **Dictionary terms only flow through the LLM path.** The rule-based filters do not see `dictionary_terms`. A user-defined custom spelling that the rule-based BRITISH_REPLACEMENTS table contradicts will get re-Britished. The LLM cleanup prompt includes the terms explicitly to override that.
-- **`SMART_PARAGRAPH_GAP_SECS` lives in `magnotia-core`, not here.** Slice 5 owns the constant. Look there to tune the long-pause threshold.
+- **`SMART_PARAGRAPH_GAP_SECS` lives in `lumotia-core`, not here.** Slice 5 owns the constant. Look there to tune the long-pause threshold.
 
 ## See also