docs(custom-model): make the docs match the code, and trim the changeset

More from the review of 5fc391a4, all documentation rather than behaviour.

The changeset was 1602 words of development log, written as the PR grew, with bullets
and loose paragraphs interleaved. That text becomes CHANGELOG.md and the GitHub release
body verbatim, so it is now one user-facing account of what the feature does and what
the real-server work bought, at roughly a fifth the length.

docs/api-reference.md promised a `cmd` field on running-status that the route
deliberately strips (it carries model paths and can carry --api-key).

Two places claimed the apply routes validate `modelId` against the endpoint's
discovered models. Neither does. Dropped the claim rather than adding the check:
discovery can be up to five minutes stale, so a 400 there would refuse a launch that
actually works, and a typo'd id already fails on the CLI's own first request. CLAUDE.md
now says so explicitly, since the absence is the surprising part.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

docs/api-reference.md

@@ -625,7 +625,7 @@ authStyle?, defaultModelId? }` creates one. `id` must match
   `server.ts`), so there is no route for triggering "refresh all" — one
   endpoint being unreachable on a cycle never blocks the others.
 - `GET /api/v1/model-endpoints/:id/running-status` -> `{ isLlamaSwap,
-running: [{model, state, cmd?}], logLine? }`, read-only, no admin gate
+running: [{model, state}], logLine? }`, read-only, no admin gate
   (any session owner who could already point a session at this endpoint can
   equally ask what it currently has loaded). `isLlamaSwap` is
   feature-detected via the endpoint's own `GET /running` — a plain