jake/Lumotia

Fork 0

Files

Jake 26c7307607

check / cargo check (macos-latest) (push) Has been cancelled

Details

check / cargo check (ubuntu-22.04) (push) Has been cancelled

Details

check / cargo check (windows-latest) (push) Has been cancelled

Details

check / svelte build + lint (push) Has been cancelled

Details

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

4.4 KiB

Raw Blame History

name, type, slice, last_verified

name	type	slice	last_verified
Cargo feature matrix	architecture-map-page	03-audio-transcription	2026/05/09

Cargo feature matrix

Where you are: Architecture map → Audio + Transcription → Cargo features

Plain English summary. lumotia-audio has no Cargo features. lumotia-transcription has two: whisper (default on, gates whisper-rs, whisper_rs_backend.rs, and load_whisper) and whisper-vulkan (default on, additive Vulkan GPU offload). Parakeet is unconditional. The defaults give a desktop GPU build; non-Vulkan or cloud-only configurations turn features off explicitly.

At a glance

Crate file: crates/transcription/Cargo.toml
Source of [features]: crates/transcription/Cargo.toml:8-21.
Source of conditionals in code: #[cfg(feature = "whisper")] in crates/transcription/src/lib.rs:6 and :10, plus the gated pub mod whisper_rs_backend; and load_whisper re-export. Vulkan check inside WhisperRsBackend::transcribe_sync (crates/transcription/src/whisper_rs_backend.rs:82).

Feature table

Feature	Default	Pulls in	Gates
`whisper`	yes	`whisper-rs 0.16` (optional dep)	`whisper_rs_backend` module, `load_whisper` re-export, the `set_initial_prompt` path
`whisper-vulkan`	yes	`whisper-rs?/vulkan`	Compile-time GPU offload. Runtime gated additionally on `vulkan_loader_available()`

Other deps are unconditional (always present): transcribe-rs 0.3 (Parakeet), lumotia-core, tokio, reqwest, futures-util, sha2, thiserror, tracing. Dev-only: tempfile, num_cpus (used by thread_sweep.rs to label physical vs logical core counts).

Build commands

Default (Whisper + Vulkan):

cargo build -p lumotia-transcription

Whisper without Vulkan (CPU-only desktop, Android without GPU drivers):

cargo build -p lumotia-transcription --no-default-features --features whisper

No Whisper at all (Parakeet only — useful for shrinking the binary and dropping whisper-rs-sys):

cargo build -p lumotia-transcription --no-default-features

The --no-default-features form drops the whisper_rs_backend module entirely, so any sibling code holding a WhisperRsBackend will fail to compile. LocalEngine, SpeechModelAdapter, load_parakeet, and the streaming primitives stay available.

Rationale (from Cargo.toml comments)

whisper exists as a feature so a future Windows non-AVX2 build, or a cloud-only ASR config, can drop whisper-rs-sys entirely (brief item #13). Disabling it also drops the WhisperRsBackend module and the load_whisper entry point.
whisper-vulkan is a separate feature so a non-Vulkan target (Android without GPU drivers, a CPU-only Windows build) can pull in whisper-rs but skip the Vulkan backend.
transcribe-rs is unconditional because today's only second engine (Parakeet) goes through it. Brief item #13's hypothetical "drop both engines" case would need a second feature flag introduced here.

Watch-outs

whisper-vulkan is purely additive. Disabling it does not change whisper's default build except for skipping the Vulkan backend selection. There is no separate "force CPU" or "force GPU" runtime flag; the backend probes vulkan_loader_available() and uses Vulkan if present.
thiserror and tracing are not feature-gated. Comments justify keeping them unconditional (small cost, broad usage).
Reqwest features are pinned. default-features = false, features = ["rustls-tls", "stream"]. There is no native-tls fallback path; --features reqwest/native-tls would rebuild the dep with the wrong TLS backend on Linux.
whisper-rs is default-features = false, optional = true. Whisper-rs's own default features can re-enable backends we don't want; setting default-features = false keeps the dep minimal and lets whisper-vulkan add the one feature we care about.
Switching feature sets between builds invalidates the build cache. A common slow-down for first-time contributors switching --no-default-features builds.

4.4 KiB Raw Blame History

Cargo feature matrix

At a glance

Feature table

Build commands

Rationale (from Cargo.toml comments)

Watch-outs

See also

4.4 KiB

Raw Blame History