6 Commits

Include renames

Author	SHA1	Message	Date
molluskandClaude Fable 5	af7a42a049	ci: remove zombie workflows from the per-push pipeline ... cargo-deny.yml (runs-on: ubuntu-latest) and windows-build.yml (runs-on: windows-latest) target runner labels no registered runner advertises, so every push queued two runs Gitea auto-cancelled ~24h later — the Actions page has shown 2 cancelled runs per push since the runner went live. - cargo-deny.yml: deleted; redundant with ci.yml's deny step, which now runs `cargo deny --locked check` to preserve the locked-tree stance. - windows-build.yml: kept but workflow_dispatch-only until a Windows runner exists; restore instructions in the header comment. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-16 23:46:56 -04:00
molluskandClaude Opus 4.8	3a74fd0230	ci: drop concurrency block (Gitea 1.26 dropped runs with it set) ... A push that only changed Cargo.lock failed to create any Actions run while the concurrency group was present; removing it restores reliable push triggering. Single-dev CI doesn't need run-cancellation. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-29 16:02:15 -04:00
molluskandClaude Opus 4.8	83e5881768	ci: cancel superseded in-progress runs (concurrency group) ... Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-29 15:51:31 -04:00
molluskandClaude Opus 4.8	8424b44dec	ci: add Gitea Actions workflow (self-hosted host-mode runner) ... CI runs on a self-hosted host-mode gitea-runner on the desktop (label `arch`), so the cheap gitbutter VPS only queues jobs while all compile/test compute runs locally. Pipeline on push-to-main / PR / manual dispatch: cargo fmt --check, clippy --all-targets -D warnings, cargo test --all-targets + doc tests, cargo deny check, cargo audit. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-29 15:43:35 -04:00
molluskandClaude Opus 4.8	85b12a26c9	Windows port Phase 0: platform-select the audio backend ... Make the tree compile for Windows without touching core logic, by confining all Linux/PipeWire assumptions behind cfg gates and a single platform-selected backend alias. No new dependencies — the cpal/WASAPI backend lands in Phase 1; this ships a no-op stub. - Cargo.toml: move pipewire + rfd(xdg-portal) under cfg(unix); add a cfg(windows) rfd using the Win32 dialog backend. - audio: gate pipewire_impl to unix, add a cpal_impl stub for windows, and select between them via the new PlatformAudioBackend alias. - core: use PlatformAudioBackend instead of the concrete PipeWireBackend. - lib: gate the unix-only 0o600 log-file mode code (+ its test); Windows logs inherit the directory ACL. - audio_probe: gate this PipeWire diagnostic to unix with a stub main. - app: open URLs via rundll32 on windows, xdg-open on unix (shell-free). - ci: add .gitea/workflows/windows-build.yml (M1) — build + lib tests for x86_64-pc-windows-msvc, with CMAKE_POLICY_VERSION_MINIMUM=3.5 for the vendored libopus build. Needs a windows act_runner to actually run. Linux build/clippy/tests green (316/316). The Windows path is verified by inspection only (no local Windows toolchain); CI is the real gate. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-18 16:47:13 -04:00
molluskandClaude Opus 4.8	e4767be210	ci: enforce cargo-deny supply-chain policy on push and PRs ... Adds a Gitea Actions workflow that runs `cargo deny --locked check` on every push to main and every PR, so the deny.toml policy (advisories, bans, licenses, sources) is enforced automatically rather than by hand. Runs on a locked tree so the pinned versions in Cargo.lock are what get audited; a poisoned dependency release can't reach CI until Cargo.lock is deliberately updated. cargo-deny is pinned to 0.19.9 via a prebuilt binary. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-18 16:00:36 -04:00