Extract model catalog into a single models.md; point chat + API docs at it

infrastructure.md

@@ -100,38 +100,14 @@ Questions about the Git itself? Write to info@inference.coop.
 
 ## Models and providers
 
-The co-op serves models from multiple providers, named `provider/model-name` so
-members can choose both *which* model and *where* it runs. Each provider carries
-a value you can route by:
+The co-op serves models from multiple providers (Tinfoil for privacy, GreenPT
+for renewable energy, PublicAI coming soon). See the [model list](models.md) for
+the current catalog — that's the single source of truth for which models are
+available and how they're named.
 
-| Provider | Value | How it works |
-|---|---|---|
-| **Tinfoil** | *private* | Models run inside hardware enclaves (TEEs); request/response bodies are encrypted end-to-end (EHBP), so even Tinfoil's infrastructure can't read them. Verifiable via remote attestation. |
-| **GreenPT** | *green* | Models served on 100% renewable energy in the EU. Standard (non-enclave) hosting — cleaner energy, but privacy is a policy commitment, not architectural. |
-| **PublicAI** | *public* | (coming soon — publicly developed models.) |
-
-Five models are currently exposed:
-
-- **DeepSeek V4.1 Flash** (`deepseek-v4-1-flash`) — default, agentic tasks. *(Tinfoil)*
-- **GPT-OSS 120B** (`gpt-oss-120b`) — lightweight fallback. *(Tinfoil)*
-- **GLM-5.3 Flash** (`glm-5-3-flash`) — fast, efficient. *(Tinfoil)*
-- **Green-R** (`greenpt/green-r`) — reasoning, renewable energy. *(GreenPT)*
-- **Green-L** (`greenpt/green-l`) — lightweight, renewable energy. *(GreenPT)*
-
-The three Tinfoil models currently use their bare names (no `tinfoil/` prefix);
-they'll be renamed to `tinfoil/…` in an upcoming, announced change.
-
-A local Tinfoil proxy sidecar handles the enclave encryption on our side of the
-gateway.
-
-The honest caveat: only **Tinfoil** offers architectural privacy. The other
-providers are chosen for their value (renewable energy, public models) but do
-not run in enclaves — prompts and responses pass through them in the ordinary
-way. Your **chat history** is also stored on our server so you can revisit it,
-and that stored history is not encrypted in a way that prevents us from
-technically reading it — we commit not to. The full distinction — what's
-architecturally private versus what's a policy commitment — is in the
-[Privacy Policy](privacy-policy.md).
+One infra detail worth knowing: a local Tinfoil proxy sidecar handles the
+enclave encryption on our side of the gateway — only Tinfoil traffic goes
+through it; the other providers are called directly.
 
 ## Security posture (plain language)