…rm-independent)

The issue was that when multiple detection clusters had overlapping onset
lookback windows, the same pop could be counted twice. For example:
- Cluster A detected at frame 30, looks back and finds onset at frame 28
- Cluster B detected at frame 32, looks back and finds onset at frame 30
- Both get reported, even though they're the same pop

Fix: Deduplicate by true_idx AFTER onset lookback, not before.
This ensures overlapping lookbacks don't create duplicate events.

- Add windows-x64-smoke-test job after windows-build
- Add windows-arm64-smoke-test job after windows-arm64-build
- Both jobs install OBS, install plugin, launch OBS with logging
- Verify plugin loads without errors by parsing OBS logs
- Ensures plugin is loadable on both architectures

- Remove docker image dependency (Windows builds don't use Docker)
- Add 3 explicit assertions per smoke test:
  1. Plugin DLL loaded (check for c64stream.dll in logs)
  2. Plugin registered (check for source registration)
  3. No critical errors (check error patterns)
- Combine stdout and stderr for complete log coverage
- Increase startup wait time to 10s for reliable plugin loading
- Add clear pass/fail messages for each assertion

- Create windows-smoke-test.yaml reusable workflow
- Eliminate 200+ lines of duplicated test code
- Both x64 and ARM64 smoke tests now call the same workflow
- Pass architecture-specific parameters (runner, artifact pattern, etc.)
- Maintains all assertions and functionality

- OBS 31.1.1 installers no longer available (404 error)
- Update to latest OBS 32.0.4
- Fix ARM64 suffix: -arm64 (lowercase) not -ARM64

- ARM64 has no installer, only zip file
- x64 uses installer as before
- Extract ARM64 zip directly to Program Files

- OBS crashes when --portable flag used without config dir
- Create obs-portable/config/obs-studio directory structure
- Set working directory to portable dir when launching OBS

OBS was failing with sentinel file directory errors in portable mode.
Switch to normal mode with --disable-shutdown-check flag.

OBS was failing to create sentinel file in AppData\Roaming\obs-studio.
Pre-create the directory to avoid the error.

Start-Process with RedirectStandardOutput wasn't capturing logs.
Switch to cmd /c with background start and output redirection.

OBS is a GUI app that never exits - it was hanging the tests.
Now start OBS async, monitor log for plugin loading activity,
and kill OBS once we detect plugins are loaded (or timeout).

Monitor logs specifically for c64stream plugin.
Only terminate OBS when:
- c64stream is detected without errors/warnings, OR
- 30 second timeout is reached

Provides progress updates every 5 seconds.

- Print OBS log output in real-time as it's generated
- Track file size and only print new content
- Prefix monitoring messages with [Monitor] for clarity
- Remove duplicate log output after completion
- Makes debugging much easier by seeing logs as they happen

OBS doesn't write to stdout/stderr when launched as GUI app.
Instead, it creates log files in $APPDATA/obs-studio/logs/.

Changes:
- Remove RedirectStandardOutput (doesn't capture OBS logs)
- Find the most recent .txt file in obs-studio/logs directory
- Wait 3 seconds for OBS to start and create log file
- Monitor the actual OBS log file for c64stream plugin loading

OBS creates its own log file with its own timestamp format,
not the one we pre-generate. The fix:

1. Start OBS without pre-generating a log filename
2. Poll the logs directory for up to 10 seconds
3. Find the most recent .txt file (created in last 15 seconds)
4. Monitor that file for c64stream plugin loading

This matches the approach used in Linux e2e tests (e2e.py:1828-1850).

Fixed missing '}' and uninitialized variables that caused parser error.

Converted multi-line here-string to single-line string literal
to avoid YAML parser confusion with colons in C# attributes.

- Set working directory to C:\Program Files\obs-studio\bin\64bit before LoadLibrary
- Install plugin to C:\ProgramData\obs-studio\plugins per Windows x64 instructions
- Use SetDllDirectory to add OBS bin to DLL search path
- Add detailed diagnostics for dependency resolution
- Verify obs.dll and w32-pthreads.dll are present before LoadLibrary

This fixes LoadLibrary error 126 (ERROR_MOD_NOT_FOUND) by ensuring the
Windows DLL loader can find obs.dll and other OBS runtime dependencies.

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Change header format for Windows (ARM64 - Experimental) section.

Updated Linux compatibility information to include Fedora 40 and Arch Linux.

Updated verification information for Linux distributions.