[buxuku]

#580 records four abnormal exits during Vulkan transcription on a Radeon 780M, while #581 reports that CPU mode works. The bundle has no native stack, selected Vulkan device or AMD driver version, so it cannot identify the underlying failure.

Add an explicit Whisper diagnostic to the export dialog on Windows/Linux. Users can compare an installed model on Vulkan/CPU and toggle VAD using the bundled short speech sample. Each run loads the addon in a disposable utility process, with cancellation and a three-minute deadline, so native diagnostic crashes leave the application available to export evidence. The last six reports include the addon, execution phase, native device messages, stderr tail and exit classification in addon.json; Windows adapter driver versions are included in gpu.json. Native text in JSON snapshots is sanitized before export.

This adds diagnostic isolation only. Normal transcription, acceleration settings and crash-breaker policy are unchanged; it does not claim to fix the Radeon driver/backend failure or add automatic CPU retries. A completed short-sample test is not a guarantee for all inputs. Windows exit-code precision loss remains explicitly marked and can be correlated with crash events/dumps.

Validation:

• yarn typecheck, yarn check:i18n, yarn build
• yarn test:gpu-enumeration plus the AMD driver propagation test
• yarn test:crash (22 suites), including report redaction/export and diagnostic lifecycle coverage
• yarn jest --runInBand renderer/components/__tests__/DiagnosticsDialog.test.tsx (10 tests)
• node scripts/crash/smoke.mjs whisper-probe: real Electron/native access-violation on macOS arm64; main process survives and a subsequent diagnostic runs
• The existing Windows/Linux/macOS crash workflow now exercises the new native diagnostic scenario; Windows GPU CI checks the actual PowerShell driver query. Radeon 780M reproduction still requires the affected hardware.

Refs #580, #581.