From a327f4d882f52e18ccbbc29b18ae93e7a448dc0e Mon Sep 17 00:00:00 2001 From: Jake Date: Fri, 24 Apr 2026 14:17:56 +0100 Subject: [PATCH] docs(handover): note CI red-state + Cargo.lock policy decision as open TODO --- HANDOVER.md | 1 + 1 file changed, 1 insertion(+) diff --git a/HANDOVER.md b/HANDOVER.md index 32d643e..cf42ca4 100644 --- a/HANDOVER.md +++ b/HANDOVER.md @@ -77,6 +77,7 @@ Compared the branch against current main: ## Still deferred (not session-actionable) +- **CI green-up + Cargo.lock policy decision** — four jobs on the 2026-04-24 evening push (three `cargo check` matrix legs + `svelte build + lint`) went red, but a clean reproduction locally (`git archive HEAD | tar -x`, fresh `npm ci`, `cargo check --workspace --all-targets`) is green. Root cause likely one of: (a) crate version drift because `Cargo.lock` is in `.gitignore` so CI resolves fresh every run (a binary workspace should normally commit its lockfile), (b) Swatinem/rust-cache bad entry, (c) transient CI-runner environment issue. Next steps before restarting CI: pull the actual failing-step log text from the GitHub Actions UI, and decide whether to start committing `Cargo.lock` (recommended for a Tauri binary). - **RB-08 verification** — needs macOS hardware access. Gates v0.1 tag. One concrete open item. - **Kon → Corbie codebase rename** — Jake handles repo rename (Gitea + GitHub); coordinated codebase sweep (package name `kon@0.1.0` → `corbie@0.1.0`, crate prefixes `kon-*` → `corbie-*`, desktop file, binary name, install paths `~/.local/share/kon/` → `~/.local/share/corbie/`, database filename `kon.db`, window titles, README body) should follow the repo rename so artefact names match. Will need a migration shim to keep existing users' data alive across the path change. - **npm audit residuals** — see §1 above. Re-visit when `@sveltejs/kit` bumps its cookie pin, or when an i18n replacement is chosen.