fix(nix): drop Windows AudioCapture from non-Windows bundle resources

[daschinmoy21]

Summary

Nix package build failed with:

resource path \`bin/AudioCapture-x86_64-pc-windows-msvc.exe\` doesn't exist

That helper is Windows-only and no longer in git (#17). It was still listed in main `tauri.conf.json` resources, so every Linux/Nix build required a dummy file.

Changes

• Main `tauri.conf.json`: only `src/audio/transcription/*`
• New `tauri.windows.conf.json`: transcription + AudioCapture (Windows merge)
• Drop CI dummy-touch steps that existed only for the bad main config

Test plan

• `nix build` / `nix profile add .` (or install from flake) on NixOS succeeds past tauri build-script
• Linux CI cargo check green without dummy exe
• Windows still bundles helper when binary is produced by `bun run build:audio`

Note

`nix profile install` warns it is a deprecated alias of `nix profile add`.

[daschinmoy21]

Manual audit

Root cause matches the failure log: tauri-build requires every `bundle.resources` path to exist; the Windows AudioCapture exe was removed from the tree but still listed for all platforms.

• Windows-only config is the right Tauri 2 pattern
• Windows conf keeps transcription + helper so array replace does not drop transcription
• CI dummy steps no longer needed on Linux

Verdict: merge when CI green.

[coderabbitai]

Warning

Review limit reached

@daschinmoy21, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 19 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 67f62914-21f7-4a0a-acb5-d3a66168c515

📥 Commits

Reviewing files that changed from the base of the PR and between 0d98f1a and 3d5ffe1.

📒 Files selected for processing (4)

• .github/workflows/ci.yml
• .github/workflows/main.yml
• src-tauri/tauri.conf.json
• src-tauri/tauri.windows.conf.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/nix-no-windows-audio-resource

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}