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:
Claude
2026-04-30 13:06:55 +00:00
parent 749403697a
commit 89c63891fa
186 changed files with 1297 additions and 1297 deletions

View File

@@ -1,12 +1,12 @@
---
name: Phase 8 — Forgiving gamification (design)
description: Design spec for Corbie Phase 8. Surfaces today's completion count and a 7-day momentum sparkline on the Tasks header. No streaks, no grace days, no loss language.
description: Design spec for Magnotia Phase 8. Surfaces today's completion count and a 7-day momentum sparkline on the Tasks header. No streaks, no grace days, no loss language.
type: spec
tags: [spec, phase-8, corbie, tasks, gamification]
tags: [spec, phase-8, magnotia, tasks, gamification]
created: 2026/04/24
status: approved
phase: 8
roadmap: docs/roadmap/2026-04-23-corbie-feature-complete-roadmap.md
roadmap: docs/roadmap/2026-04-23-magnotia-feature-complete-roadmap.md
author: Wren (CORBEL's resident agent) on behalf of Jake Sames
---
@@ -92,7 +92,7 @@ Query groups matching rows by local-day and then left-joins against a generated
// - window focus (for day rollover while the app stayed open overnight)
```
**Why not hook off `kon:task-completed` alone:** that event only fires on completion, not on uncomplete or delete, and relying on it would leave the badge stale after either of those paths. Refreshing at the mutation-helper level captures every path that can change today's count.
**Why not hook off `magnotia:task-completed` alone:** that event only fires on completion, not on uncomplete or delete, and relying on it would leave the badge stale after either of those paths. Refreshing at the mutation-helper level captures every path that can change today's count.
**`src/lib/pages/TasksPage.svelte` header:**
Stacks to:
@@ -150,7 +150,7 @@ Only the sparkline respects the toggle. The badge is always on.
- Migration v13: applies cleanly against a DB populated at v12; default of `auto_completed = 0` on pre-existing rows verified.
### Frontend (`npm run check` + vitest)
- `completionStats` store refreshes on `kon:task-completed` event.
- `completionStats` store refreshes on `magnotia:task-completed` event.
- `todayCount` derives from the last entry.
- Sparkline renders exactly 7 bars for a populated fixture.
- Sparkline hidden when `showMomentumSparkline === false`.