docs: remove completed roadmap + release-gate docs

The ROADMAP files are fully shipped/retrospective and the smoke-test and
signing guides are retired at the maintainer's request. resources/bin/README.md
is kept (documents bundled-binary setup + license obligations).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

docs/SIGNING.md

@@ -1,77 +0,0 @@
-# AeroFetch — Windows code signing
-
-Unsigned builds run, but Windows SmartScreen shows a blue **"Windows protected your PC"**
-prompt the first time each user runs the installer (they must click *More info → Run anyway*).
-This is the single biggest first-run friction when sharing AeroFetch. Code signing removes it
-(EV certificates remove it immediately; OV certificates build reputation over time/installs).
-
-**This step needs a certificate that can't live in the repo**, so it isn't wired on by default.
-The build is otherwise ready for it — electron-builder picks the cert up from environment
-variables with no `electron-builder.yml` changes required.
-
-## What you need
-
-- An **Authenticode code-signing certificate** for Windows:
-  - **OV (Organization Validation)** — cheaper; SmartScreen reputation accrues as more users
-    install, so early downloads still see the prompt.
-  - **EV (Extended Validation)** — pricier, usually on a hardware token / cloud HSM; clears
-    SmartScreen immediately. Token-based EV can't be fed as a plain `.pfx` (see "HSM/EV" below).
-- The cert as a password-protected `.pfx`/`.p12` (for OV), or an HSM/cloud-signing setup (EV).
-
-## Signing an OV `.pfx` locally
-
-electron-builder reads these env vars automatically:
-
-```bash
-# PowerShell
-$env:CSC_LINK = "C:\path\to\codesign.pfx"   # or a base64 string of the .pfx
-$env:CSC_KEY_PASSWORD = "<pfx password>"
-npm run build:win
-```
-
-```bash
-# bash / CI
-export CSC_LINK="$(base64 -w0 codesign.pfx)"   # base64 is convenient for CI secrets
-export CSC_KEY_PASSWORD="$PFX_PASSWORD"
-npm run build:win
-```
-
-electron-builder then signs `AeroFetch Setup <ver>.exe`, the portable `.exe`, and the app
-binary. No changes to `electron-builder.yml` are needed; if `CSC_LINK` is unset, the build
-proceeds **unsigned** (current behavior).
-
-## CI (GitHub Actions sketch)
-
-Store the cert + password as encrypted secrets and export them before the build:
-
-```yaml
-- name: Build (signed)
-  env:
-    CSC_LINK: ${{ secrets.WINDOWS_CSC_LINK }}          # base64 of the .pfx
-    CSC_KEY_PASSWORD: ${{ secrets.WINDOWS_CSC_KEY_PASSWORD }}
-  run: npm run build:win
-```
-
-## HSM / EV certificates
-
-EV certs (and many newer OV certs) ship on a hardware token or cloud HSM and can't be exported
-to a `.pfx`. Sign via a custom signing hook instead — set `win.sign` in `electron-builder.yml`
-to a script that invokes your provider's tool (Azure Trusted Signing, DigiCert KeyLocker,
-SSL.com eSigner, or `signtool` with the token). Each provider documents the exact `signtool`
-invocation; electron-builder calls your hook once per artifact with the file path.
-
-## Verifying a signature
-
-```powershell
-Get-AuthenticodeSignature ".\dist\AeroFetch Setup <ver>.exe" | Format-List
-# Status should be 'Valid'; SignerCertificate should be your cert.
-signtool verify /pa /v ".\dist\AeroFetch Setup <ver>.exe"
-```
-
-## Notes
-
-- The LGPL ffmpeg + yt-dlp binaries shipped in `resources/bin` are third-party; signing the
-  AeroFetch artifacts doesn't (and needn't) re-sign them.
-- Timestamp the signature (electron-builder does by default) so it stays valid after the cert
-  expires.
-- Signing does **not** replace the smoke test — see [SMOKE-TEST.md](SMOKE-TEST.md).

docs/SMOKE-TEST.md

@@ -1,61 +0,0 @@
-# AeroFetch — manual smoke-test checklist
-
-Some features can only be exercised against a **real install** (or a real yt-dlp run) —
-they're main-process / Electron / OS-integration code that the Vite browser preview and the
-unit suite can't reach. They're implemented and typecheck/test/build clean, but the roadmaps
-flag them as needing a hands-on pass. Run this checklist after building
-(`npm run build:win`) and installing the NSIS artifact (or launching the portable `.exe`).
-
-Mark each ✅/❌ and note anything surprising.
-
-## Downloads & post-processing (Phases A, L, M)
-
-- [ ] **Basic download** — paste a URL, Fetch, pick a format, Download → file lands in
-      Documents\Video (or your folder), progress + speed update, "Completed".
-- [ ] **Trim / cut** (Phase L) — set a section like `0:10-0:20`, download → output is ~10s and
-      starts/ends near the cut points (`--download-sections` + `--force-keyframes-at-cuts`).
-- [ ] **Split by chapters** (Phase L) — on a video with chapters, enable it → per-chapter files
-      appear alongside the full file.
-- [ ] **Pause / resume** (Phase M) — start a large download, Pause (process stops, `.part`
-      stays), Resume → it **continues** from where it stopped, not from 0% (yt-dlp `--continue`).
-- [ ] **Scheduling** (Phase M) — schedule a download a couple of minutes out → it sits "Saved /
-      Scheduled", then auto-starts at the time (only while the app is running).
-
-## Access & networking (Phase B, P)
-
-- [ ] **Cookies — sign-in window** — Settings → Cookies → "Sign-in window", log into a site,
-      close it → "cookies saved" with a timestamp; a members-only/age-gated video then downloads.
-- [ ] **Cookies — from browser** — pick an installed browser → a gated video downloads.
-- [ ] **Proxy** — set a working proxy → downloads route through it (verify via the proxy logs).
-- [ ] **aria2c** — drop `aria2c.exe` into `resources/bin`, enable it → multi-connection download
-      works; remove it → silently falls back to yt-dlp's downloader.
-- [ ] **YouTube client / PO token** (Phase P) — set `youtubePlayerClient` (e.g. `web_safari`) →
-      the run includes `--extractor-args youtube:player_client=web_safari` (check Terminal/Preview).
-
-## OS integration (Phase E, J, O)
-
-- [ ] **`aerofetch://` protocol** — from a browser, open `aerofetch://download?url=<encoded>` →
-      AeroFetch focuses and the URL appears in the "Link received" banner.
-- [ ] **Explorer "Send to AeroFetch"** — drag a tab to the desktop to make a `.url`, right-click →
-      Send to → AeroFetch → the link is received.
-- [ ] **Scheduled sync** (Phase J) — Settings → enable the daily sync → a Windows Task Scheduler
-      task exists; run it (or `AeroFetch.exe --sync`) → watched sources index and new items enqueue.
-- [ ] **RSS fast-check** (Phase J) — "Check for new" on a watched channel → newly-posted videos
-      show as new without a full re-index.
-- [ ] **System tray** (Phase O) — enable "Keep running in the tray", close the window → it hides
-      to the tray; tray click reopens; tray → Quit actually exits.
-- [ ] **Taskbar progress** (Phase O) — during downloads the taskbar icon shows a progress bar;
-      it turns red if one fails and clears when the queue goes idle.
-- [ ] **Jump list** (Phase O) — right-click the taskbar icon → "Open AeroFetch" focuses the app.
-
-## Terminal (Phase N)
-
-- [ ] Enable "Run custom commands", open Terminal, run `--version` → the version prints; run
-      `-F <url>` → the format table streams in; Stop cancels a long run.
-
----
-
-If anything here fails, capture the Settings → Diagnostics "Copy full report" output and the
-exact steps. These items have no automated coverage, so this checklist is the release gate for
-them. See also [SIGNING.md](SIGNING.md) for the code-signing step that removes the SmartScreen
-prompt for end users.