docs(versioning): the experimental local model list names the library and agent verbs (#804, #806)

POST /api/local-model/use, DELETE /api/local-model/models and
POST /api/local-model/agent are experimental like the routes beside them,
and so are the install object's library, store and harnesses lists.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>

docs/versioning-policy.md

@@ -88,14 +88,18 @@ decision.
 
 ### Experimental local model routes
 
-`GET /api/v1/local-model`, `POST /api/v1/local-model/install`, `/cancel`, `/resume`
-and `/runtime`, and `DELETE /api/v1/local-model` (and their `/api` aliases) are
+`GET /api/v1/local-model`, `POST /api/v1/local-model/install`, `/use`, `/cancel`,
+`/resume`, `/runtime` and `/agent`, `DELETE /api/v1/local-model` and
+`DELETE /api/v1/local-model/models` (and their `/api` aliases) are
 labeled experimental, so item 3 above applies to them: their paths, their payloads
 (the hardware facts, the verdicts and reasons, the candidate fields, the `install`
-object with its states, steps, error codes and actions, the 409 conflict shape and
+object with its states, steps, error codes and actions, its `library`, `store` and
+`harnesses` lists, the 409 conflict shape and
 every English sentence) and their behavior may change or be removed in a MINOR or
 PATCH release. They look at the Mac the server runs on, say which local model fits,
-and install, start, stop and remove one ([local-models.md](local-models.md)).
+install, start, stop and remove one, keep a library of installed models to switch
+between or delete, and install one more coding agent beside an installed model
+([local-models.md](local-models.md)).
 
 They are not behind a setting. Reading changes nothing; an install starts only on an
 explicit request that carries the size the person confirmed. All of them are admin