Jake
26c7307607
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>
3.1 KiB
3.1 KiB
name, description, type, tags, created, status, author
| name | description | type | tags | created | status | author | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Phase 10a manual dogfood notes | Runtime dogfood findings captured during the 2026/05/10 Phase 10a walkthrough. | audit |
|
2026/05/10 | in-progress | Hermes Agent with Jake Sames |
Phase 10a — Manual Dogfood Notes
Environment
- Launched via
./run.shfrom/home/jake/Documents/CORBEL-Projects/transcription-app. - Dev server: Vite on
localhost:1420. - Tauri binary:
/home/jake/Documents/CORBEL-Projects/transcription-app/target/debug/lumotia. - Launch visible to Jake after restarting under PTY.
Results
| Check | Result | Notes |
|---|---|---|
| App launches visibly | PASS | Tauri app visible after PTY launch. |
| History row export | PASS | Row-level History export opens the native save dialog and works as intended. |
| File Transcription multi-format export | PASS after fix | Initially failed across all export types. Fixed by routing desktop exports through Tauri native save dialog + write_text_file_cmd; Jake retested and confirmed it works as intended. |
| Bulk History export | PASS | Selected 3 history rows, bulk toolbar appeared, “Export selected” wrote one .md per row and behaved as expected. |
| Tag one History row | BLOCKED / CRASH | Initially showed “LLM not loaded. Download an AI model in Settings.” After LLM load attempt, dev process exited during llama.cpp load with GGML_ASSERT(strncmp(n->name, LLAMA_TENSOR_NAME_FGDN_AR "-", prefix_len) == 0) failed while loading Qwen3.5-4B-Q4_K_M.gguf. Treat as release-blocking LLM compatibility/setup issue before LLM-dependent tagging can pass. |
2026/05/12 — re-validation pass after engine slop residuals + Area A
Context: residuals B (184214b), hotkey tracing finishing (48c4838), and Area A storage-error typing (52565ea + a36ae7e) landed today. Launched lumotia under RUST_LOG=info,lumotia=debug,lumotia_lib::commands::live=debug to validate that the new tracing + storage-error semantics held up in a real session.
| Check | Result | Notes |
|---|---|---|
| Native window visible on Dictation | PASS | Confirmed by Jake. |
| Settings opens in native window | PASS | Confirmed by Jake. |
| Record start/stop or clear prerequisite/error | PASS | Confirmed by Jake. |
| No obvious WARN/ERROR toast or crash on smoke | PASS | Confirmed by Jake. |
| Longer-form dogfood (transcribe + LLM cleanup + tagging) | NOT RUN | Hermes session crashed before the longer pass could start. The LLM tagging crash from the 2026/05/10 entry above remains the outstanding release-blocker. |
Observability check — tracing pipeline confirmed working under the new default filter (lumotia=info,lumotia_lib=info,lumotia_audio=info,lumotia_startup=info,lumotia_hotkey=info,lumotia_ai_formatting=info). Per-chunk speech-gate skip + dispatch events show under lumotia_lib::commands::live=debug as intended.
Storage-error semantics: no opportunity to exercise typed storage failures this session (no FK violation, NotFound, or migration replay path was hit). Re-validation deferred to next dogfood pass when a path that produces a real storage error can be triggered deliberately.