Add enhanced WolfEQ device scanner

[audioslayer]

Adds a standalone Windows x64 device scanner for Retro Nano/WolfEQ hardware debugging.

Includes:

• PnP, USB, sound device, MMDevices registry, and PnP property dumps
• HID interface enumeration with VID/PID, strings, usage page/usage, report lengths
• read-only feature report attempts for report IDs 0..15
• USBPcap detection and optional --capture mode
• timestamped Desktop output folder plus zip bundle for Discord upload

Published latest test build to assets/wolfeq-test-builds/WolfEQDeviceScanner-Latest.zip.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a4d41841b9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Resolve USBPcapCMD from PATH before declaring it missing

FindUsbPcapCmd uses File.Exists on the literal "USBPcapCMD.exe", which only checks the current working directory and not %PATH%. In environments where USBPcapCMD is installed outside the two hardcoded folders (or only discoverable via PATH), this returns null, so --capture is disabled even though the command is runnable.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Keep USBPcap capture interactive instead of fully redirected

The capture process is configured with redirected stdin/stdout/stderr, but the code never relays USBPcap’s prompts or reads its output. If USBPcap asks for interface selection (as the preceding console instructions anticipate), users cannot see/respond to that prompt, so capture can stall or fail to start.

Useful? React with 👍 / 👎.