The dev -> rc -> main flow left rc ungated: push/pull_request triggers only
listed main and dev, so a release candidate branch could drift without CI
ever running against it. Add rc to both branch lists.
The CI/release workflows still targeted the archived presentation
shells (nuncio-gui, nuncio-tui, nuncio-mcp) and their Tauri/npm
toolchain, so every run failed before the engine crates were even
built.
- ci.yml: run on dev in addition to main, drop the GTK/WebKit/Tauri
apt packages (the engine only needs zbus-based keyring and bundled
sqlite, both pure-Rust/cc), rely on rust-toolchain.toml instead of
dtolnay/rust-toolchain@stable to avoid drift from the pinned 1.97.1
toolchain, and make the coverage job continue-on-error so it stays
informational.
- release.yml / release-nightly.yml: package only nuncio-cli and
nunciod (the shells are gone), and drop the fabricated installer/
Homebrew release notes.
- release-desktop.yml: deleted; the Tauri desktop GUI is being
rebuilt as a separate client repo and no longer belongs here.
Set an explicit top-level permissions block (contents: read for CI;
contents: write for wiki-sync, which pushes to the wiki) so the workflows
follow least-privilege and clear the CodeQL 'workflow does not contain
permissions' findings.
Clippy job now runs 'cargo check-all' (--all-targets), matching the local gate
so CI can no longer pass while the local gate fails. Coverage is now
informational (--summary-only): the former --fail-under-lines 100 excluded all
main.rs and rewarded stub+matching-test theater; a realistic threshold plus a
required mock-server E2E gate lands with Phase 1.C.6.
Refs #142#143