Jake
ab5f6ab995
The Magnotia->Lumotia rebrand commit 26c7307 ran a too-greedy
s/magnotia/lumotia/g across comments that already had the correct
legacy/target distinction. The commit author caught one case in
src-tauri/src/lib.rs ("magnotia era" -> "lumotia era" restored) but
missed four others, plus a duplicated word in a Cargo description
from an earlier two-name sed.
Fixed sites:
* crates/storage/src/database.rs — migrate_legacy_setting_keys docstring
* src/lib/utils/localStorageMigration.ts — file-level docstring
* src/lib/utils/settingsMigrations.ts — historical-key comment
* crates/cloud-providers/Cargo.toml — description duplication
* src-tauri/src/lib.rs — data-dir migration log + doc
None of the underlying code paths were wrong; the lies were
docstring-only. Risk: future maintainer reading any of these
comments at incident time could invert the migration direction or
conclude no migration ran.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
17 lines
506 B
TOML
17 lines
506 B
TOML
[package]
|
|
name = "lumotia-cloud-providers"
|
|
version = "0.1.0"
|
|
edition = "2021"
|
|
description = "Provider trait and BYOK cloud STT scaffolding for Lumotia"
|
|
|
|
[dependencies]
|
|
lumotia-core = { path = "../core" }
|
|
|
|
# Async-native trait. async_trait converts async fn into Pin<Box<dyn
|
|
# Future>> at the trait surface so TranscriptionProvider stays
|
|
# object-safe (Arc<dyn TranscriptionProvider>).
|
|
async-trait = "0.1"
|
|
|
|
# Trait types serialise across the Tauri boundary.
|
|
serde = { version = "1", features = ["derive"] }
|