cliamp moves into the plugin, and the platform loses its last music file

The owner read the code and asked why `plugins/music/api/router.ts` was three
lines importing `@@/api/music/router` — platform code that knows the string
'music'. He was right, and tracing it found the justification was hollow.

The chain: server.tsx:20 imported the cliamp relay's two exports, which are
used only on commented-out lines; so the relay's functions were never invoked;
so its call to getMusicServerWsUrl never ran; and the file's other export,
getMusicServerUrl, had no consumers at all. A dead import held a music-named
file in the platform, and I documented that as a "seam" last night after
checking the import existed and stopping there.

Everything cliamp now lives in plugins/music/cliamp/:

  sidecar/music/{cliamp-ws,pulse-audio}.ts, asoundrc, the test
  api/cliamp/relay.ts
  apps/FileBrowser/{CliampPanel,AudioStreamPlayer}.tsx

src/servers/sidecar/music/, src/servers/api/cliamp/ and src/servers/api/music/
are gone. server.tsx has no cliamp import, provider name, handler entry or
route. The platform contains no file named for music or cliamp.

Two of the things that moved were live, not inert.

The file browser's `Play` context-menu item, on any audio file or folder, set
?play= and rendered a cliamp terminal pointed at /api/cliamp/ws — a route that
upgraded into a handlers entry that was commented out, so handlers[provider]!
asserted non-null on undefined. Using that menu item crashed the socket
handler. Removed: the action, the layout, the panel wiring and both menu
entries. Verified the routes now 404 rather than crash.

That closed the totality drift as a side effect. server.tsx's route table and
its handlers map agree again for the first time since 2026-08-13, and
registry.test.ts now asserts it rather than pinning the hole.

The proxy is built in the plugin now, and its prefix is DERIVED. It was the
literal '/api/music', which the proxy uses to strip characters off the path —
correct only because mountPrefix returns /music for a first-party publisher.
The same plugin published by anyone else mounts at /api/p/<publisher>/music and
would have forwarded /alice/music/stream to a sidecar expecting /stream. A
latent bug only third parties would ever hit, and a quiet violation of the rule
that mountPrefix is the one function allowed to know about provenance. Offscale
has the identical hardcode and still needs it.

Still open there: appName is passed as a literal, because a plugin's router
cannot see its own directory name — the platform imports the module and reads
`router`, so there is nowhere to inject it. The fix is a factory the installer
calls with the plugin's identity.

Plugin backend coupling is down to 7 imports, all of them "a plugin talks to
its host": data-path, sidecar/connect, sidecar/protocol, officer-url, the
manifest type, officerdb/db and the users.id FK. Nothing music-shaped left.

bunx tsgo clean. 797 tests, 787 pass, same 7 pre-existing failures. Verified
live: manifest 200, favorites 200, stream 206, /api/cliamp/ws 404.

plugins/music/manifest.ts

@@ -3,21 +3,21 @@ import type { PluginManifest } from '@@/plugins/manifest';
 // Music — the library, the player, and the phone and tablet apps that stream from it.
 //
 // The second plugin extracted from the platform, on 2026-08-15. Bigger than offscale and, unlike it, not
-// a clean cut: three pieces stay behind deliberately. Each is a documented seam rather than a loose end,
-// and each is recorded in ./PLUGIN.md with what would have to change to close it.
+// a clean cut. It took two passes: the first left three pieces in the platform, and the second moved two
+// of them here after the owner read the code and asked why the platform still had files named for music.
+// He was right — one of the three "seams" turned out to be dead code holding the door open.
 //
-//   api/router.ts     re-exports the platform's music proxy — see that file for why it is not a new one
+//   api/router.ts     the sidecar proxy, built here — thin, and it must never grow music knowledge
 //   sidecar/          the whole /api/music contract: indexing, streaming, per-user state
 //   db/               music_favorites, _playlists, _playlist_items, _now_playing
 //   web/              the library panels; the shell renders the Workspace
 //
-// ── What stayed in the platform, and why ──
+// ── What stayed in the platform, and why ── (one item, down from three)
 //
-// 1. cliamp (`/api/cliamp/ws`, `/api/cliamp/audio/ws`, `sidecar/music/cliamp-ws.ts`, `pulse-audio.ts`,
-//    `asoundrc`). A second playback path — the `cliamp` TUI run on the server with its terminal and its
-//    PulseAudio null sink piped to the browser. Already inert (the routes upgrade into commented-out
-//    handlers) and out of scope by the owner's decision. This sidecar still serves those sockets, so it
-//    imports both modules from `@@/sidecar/music/`.
+// 1. ~~cliamp~~ — MOVED HERE, all of it, into `./cliamp/`. The sidecar halves, the relay, the file
+//    browser's panel and its `Play` action. `src/servers/sidecar/music/`, `src/servers/api/cliamp/` and
+//    `src/servers/api/music/` no longer exist, and `server.tsx` has no cliamp anything. It is PARKED, not
+//    working: bringing it back needs a plugin to own a websocket, which is a platform gap.
 //
 // 2. The dashboard widget (`src/workspaces/widgets/MusicPlayer/`). Plugins cannot contribute widgets and
 //    the mechanism was not worth inventing for one.