Refactor/s3 hardware detect

[natashaannn]

Closes #22

Summary

• Adds HardwareProfile type and detectHardware(): Promise<HardwareProfile> to scripts/config/hardware.ts
• Derives encoder profile from process.platform / process.arch: macOS → videotoolbox, Linux x64 → nvenc, all else → libx264
• 21 unit tests covering all three hardware paths via mocked platform/arch values

Test plan

• npm test — 205 passing, 0 failures
• tsc --noEmit — clean
• macOS (darwin/arm64) smoke test — detectHardware() returns encoderProfile: "videotoolbox", supportsVideoToolbox: true
• Windows manual test — needs reviewer on Windows machine (see below)
• Linux/NVIDIA — covered by unit test mock; real hardware not available

Windows manual test instructions

On a Windows machine, check out the branch and run:

git checkout refactor/s3-hardware-detect

Create a test file hw-test.ts in the repo root:

import { detectHardware } from './scripts/config/hardware.ts';
const p = await detectHardware();
console.log(JSON.stringify(p, null, 2));

Run it:

npx tsx hw-test.ts

Expected output:

{
  "platform": "win32",
  "arch": "x64",
  "supportsVideoToolbox": false,
  "supportsCuda": false,
  "encoderProfile": "libx264"
}

Delete the test file when done: del hw-test.ts

Key things to confirm: supportsVideoToolbox and supportsCuda are both false, encoderProfile is "libx264".

Notes

• Phase 1 only: no FFmpeg integration, no nvidia-smi probe. The Linux/x64 → CUDA heuristic will be refined with a real probe in a later phase.
• Downstream issues (Add typed FFmpeg command builder #23 FFmpeg command builder) will import detectHardware() and HardwareProfile from this file.

🤖 Generated with issue-pilot skill

[natashaannn]

Hi @victoria-lo , opening this PR first because it requires testing on a Windows machine. I technically could use my Windows to test but best would be to check with yours as it is intended to work on your hardware - opening the PR early so you can take your time to test when able!

[natashaannn]

@victoria-lo Pinging again so you know to review this when you have time!

[victoria-lo]

Confirmed the script runs as expected and outputs expected JSON