docs: fold shipped specs into the architecture docs and delete them

A spec was a promise; sixteen of them had become descriptions of code that
already shipped, sitting beside four that describe work still outstanding, with
nothing in the file telling the two apart. Half the statuses were also wrong —
audio-equalizer read "Accepted" with the EQ live on both platforms, the native
video spec said the flag stays off after the default was flipped on.

The shipped designs move into docs/architecture, which is the maintained
description of the build, and the spec files go. Git history keeps the
originals; what a future change still needs is carried across:

- 01-rust-backend: favourites rewritten (the old section named a file that no
  longer exists and called shipped buttons "planned"), domain vocabulary owned
  by Rust (SearchScope, exclusions, the bitrate ladder), background workers
- 02-svelte-frontend: app shell and chrome, library mosaic, series/episode
  navigation, downloaded browse, safe-area insets, native-video store, logging
- 03-data-flow: locally-indexed search
- 05-platform-backends: audio settings on ExoPlayer, the equalizer's band
  vocabulary, native video compositing, the background-audio handoff
- 06-downloads-and-offline: one storage model, offline catalog visibility
- 09-security: path confinement and input binding

docs/specs/README.md now says what the directory is for and where each shipped
design went. Deferred work the specs recorded is kept beside the code it
concerns rather than lost: season-bounded autoplay, the two dead search
commands, why indexing is a full crawl.

requirements.md had fourteen stale statuses — Android audio parity still read
"Linux only", DR-150 still said the native-video default was off, DR-190 was
Proposed after DR-196 implemented it, and five tooling requirements were
Proposed after landing. Three unbuilt specs suggested requirement ids that have
since been allocated to other work; each now carries a warning.

docs/specs/playback-backend-unification.md

@@ -3,7 +3,10 @@
 **Status:** Accepted (analysis; no code changes)
 **Requirements:** IR-004, UR-031, UR-032, UR-033 — revises the "Platform Playback Backend Parity" issue in requirements.md
 **UX spec:** n/a
-**Supersedes / revises:** informs [android-native-video-spike.md](android-native-video-spike.md), [android-audio-settings-parity.md](android-audio-settings-parity.md), [windows-native-audio-backend.md](windows-native-audio-backend.md)
+**Supersedes / revises:** informed the Android native-video and audio-parity
+work (both since shipped — see
+[05-platform-backends.md](../architecture/05-platform-backends.md)) and
+[windows-native-audio-backend.md](windows-native-audio-backend.md), still open
 
 ## Summary
 
@@ -167,9 +170,9 @@ rewrite, not the bindings.
 2. **Android native video is worth a bounded spike anyway** — not for
    unification, but because ExoPlayer's `SurfaceView` path already exists and
    would restore hardware decode plus ASS/SSA subtitles. See
-   [android-native-video-spike.md](android-native-video-spike.md).
+   [05-platform-backends.md](../architecture/05-platform-backends.md#native-video-compositing-android).
 3. **Audio parity is the real gap** and is achievable without touching any of the
-   above. See [android-audio-settings-parity.md](android-audio-settings-parity.md)
+   above. See [05-platform-backends.md](../architecture/05-platform-backends.md)
    and [windows-native-audio-backend.md](windows-native-audio-backend.md).
 4. **Migrate the dead libmpv pin** regardless of any of this. See
    [libmpv2-migration.md](libmpv2-migration.md).