Custom connections are gone: the CLI talks to the LLeMbas server it is logged in to

LLeMbas CLI 2.0 is LLeMbas-server-specific (CLI rule 2). Removed: the
anthropic, gemini, ollama and responses clients, context discovery and
llama-swap unloading (discover.ts), the Connection schema with its dialect,
auth, key_cmd, discover, unload_url and one_model_at_a_time, the model
`fallback` (it only ever moved to another server), effort_map and cache, and
the multi-connection refs. Kept: openai-chat, http, sse, think, effort,
tokens and all of src/lembas.

- connections.yaml holds the login (`type: webui`, as lembas login writes
  it). A custom entry from 1.x is read past with a warning that says how to
  log in, so an old file still starts; with several logins left, the latest
  is used and the others named.
- A model's ref is the id the server serves it under; the older forms
  (`<login>/<id>`, `<login>/<model>`) still resolve and config.yaml is
  rewritten once. Without a login there is no model, and the error (and the
  first-run screen, now the sign-in alone) says `lembas login <address>`.
- A login to another server signs this machine out of the previous one.
- The window is the server's word (no discovery); a capacity group comes
  from the server's `capacity.group` alone; embeddings use the server's
  /v1/embeddings.
- `lembas models` lists the server's models; install.sh's starter files, the
  README and the JSON schemas say the same.

Tests: every fixture is a login now (the fake server lists models, answers
other GETs with 404, and can hand one model to another script, as a server
with several backends); the dialect suites and the cross-connection tests are
gone with their code.

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

README.md

@@ -4,12 +4,11 @@
 
 # LLeMbas CLI
 
-A terminal coding agent and project manager: the `lembas` command. It talks to any LLM API
-(OpenAI-compatible servers such as llama.cpp, vLLM or LM Studio, the OpenAI Responses API,
-Anthropic, Gemini, Ollama), works in your project with four permission modes and a git snapshot of
-every turn, remembers what it learns across sessions, and can sign in to a
-[LLeMbas](https://github.com/LLeMbas/LLeMbas) server to use its models, library and search — and
-let its web UI work the same sessions. Linux, x64 and arm64.
+A terminal coding agent and project manager: the `lembas` command. It signs in to a
+[LLeMbas](https://github.com/LLeMbas/LLeMbas) server and uses its models, memory and search, works
+in your project with four permission modes and a git snapshot of every turn, keeps its own notes,
+knowledge bases and skills on your machine, and lets the server's web UI work the same sessions.
+Linux, x64 and arm64.
 
 ## Install
 
@@ -24,12 +23,12 @@ checksum before installing anything ([SECURITY.md](SECURITY.md) shows how to che
 ## First steps
 
 ```sh
-cd your-project && lembas              # the TUI
-lembas login https://your-server       # sign in to a LLeMbas server and use its models
+lembas login https://your-server       # sign in to your LLeMbas server
+cd your-project && lembas              # the TUI, on the server's models
 ```
 
-Without a server, add a connection to `~/.config/lembas/connections.yaml` and set `model:` in
-`~/.config/lembas/config.yaml`.
+From 2.0 the CLI talks only to the LLeMbas server it is logged in to; the custom connections of 1.x
+(`dialect:` entries in `connections.yaml`) are gone.
 
 `lembas` updates itself (`lembas update` does it now); `lembas uninstall` removes it, and
 `--purge` takes settings and sessions too.