5c36bdec28
Two issues with the previous #12 approach, both caught by CI: 1. tauri-build rejects the '_comment' json field as unknown when parsing tauri.windows.conf.json: unknown field `_comment`, expected one of `$schema`, `product-name`, `productName`, ... The schema is strict, so the doc-comment has to live elsewhere. 2. tauri-build's bundle.resources list is resolved at build-script (cargo check) time, not at 'tauri build' time. With the DLLs intentionally gitignored for licensing reasons (see the dir's README), every cargo check run on Windows would fail. Fix: delete tauri.windows.conf.json entirely. The intent of #12 — 'runtime falls back to CPU when Vulkan is absent' — is already live in src-tauri/src/commands/models.rs::detect_active_compute_device, unchanged. Rewrite resources/windows/README.md to document a cargo tauri build --resource ... invocation for the release engineer. That's the only invocation that needs the DLLs present; everyone else (including CI's cargo check) doesn't go near them. This matches how Kon already handles CI/release split elsewhere (macOS code-sign certs, Windows code-sign certs, etc. all stay out of tauri.conf.json for the same reason). Co-authored-by: jars <jakejars@users.noreply.github.com>