chore: rebrand from Kon/Corbie to Magnotia
Replace all instances of the legacy product names "Kon" and "Corbie" with "Magnotia" across user-facing copy, code identifiers, package names, bundle ids, file paths, and documentation. Preserves the unrelated "konsole" (KDE terminal) reference and the parent CORBEL company name. - Renames 10 Rust crates (kon-* → magnotia-*) and the tauri binary - Updates package.json, tauri.conf.json (productName + identifier) - Renames CSS classes (kon-rh-* → magnotia-rh-*) and animations - Renames brand and roadmap docs - Regenerates Cargo.lock and package-lock.json Verified: svelte-check passes; pure-rust crates compile under new names.
This commit is contained in:
@@ -27,7 +27,7 @@ call returns `Err`, and post-call `SELECT COUNT(*) FROM poison_marker`
|
||||
fails with "no such table" while `MAX(schema_version)` remains at 8.
|
||||
|
||||
SQLite DDL participates in transactions, so this is sufficient for the
|
||||
Kon schema. If any future migration needs a statement that implicitly
|
||||
Magnotia schema. If any future migration needs a statement that implicitly
|
||||
commits (`VACUUM`, `REINDEX`, `ATTACH`) — none do today — it must be
|
||||
split into its own non-transactional migration. Reviewer's job to flag.
|
||||
|
||||
@@ -43,7 +43,7 @@ split into its own non-transactional migration. Reviewer's job to flag.
|
||||
|
||||
## Fix scope
|
||||
|
||||
Medium. Wrap each migration in `pool.begin()` / `tx.commit()`. The version update and the migration statements all execute on the same `Transaction` handle. Needs careful review of any migration that uses implicit commits (SQLite `VACUUM`, `REINDEX`, `ATTACH` — none of which Kon currently uses, but the review pattern should guard against future additions).
|
||||
Medium. Wrap each migration in `pool.begin()` / `tx.commit()`. The version update and the migration statements all execute on the same `Transaction` handle. Needs careful review of any migration that uses implicit commits (SQLite `VACUUM`, `REINDEX`, `ATTACH` — none of which Magnotia currently uses, but the review pattern should guard against future additions).
|
||||
|
||||
## Dependencies
|
||||
|
||||
|
||||
Reference in New Issue
Block a user