2 Commits

Author	SHA1	Message	Date
Jake	26c7307607	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>	2026-05-13 12:38:03 +01:00
Jake	fdab77776c	docs(area-a): storage error inventory + proposed typed taxonomy ... Pre-migration survey for engine-slop residuals Area A. Catalogues every MagnotiaError::StorageError construction site in the storage crate (78 total across database.rs and migrations.rs), groups by failure mode, proposes a typed magnotia_storage::Error enum with a serde- friendly MagnotiaError::Storage { kind, operation, detail } variant on top, and flags 6 ambiguities + 3 migration risk classes. Key findings the residuals plan did not capture: - StorageError is a String variant on MagnotiaError, not a separate enum — there is nothing called StorageError in the storage crate. - Actual site count is 78, not the ~25 the residuals plan estimated. - Tauri commands stringify every error before crossing into the frontend (Result<T, String>), so MagnotiaError's Serialize impl is presently unused at the FE/BE boundary. Area E owns that fix. - Zero Other(String) sites in storage — already cleaned in db654de. No code changes. Migration awaits decisions on the 6 ambiguous cases in §"Ambiguous cases / decisions needed". Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-12 22:39:27 +01:00