docs(handover): note CI red-state + Cargo.lock policy decision as open TODO

This commit is contained in:
2026-04-24 14:17:56 +01:00
parent d307722c7a
commit a327f4d882

View File

@@ -77,6 +77,7 @@ Compared the branch against current main:
## Still deferred (not session-actionable) ## 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. - **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. - **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. - **npm audit residuals** — see §1 above. Re-visit when `@sveltejs/kit` bumps its cookie pin, or when an i18n replacement is chosen.