memory: record Kimi K3 gateway wiring (temp=1 + reasoning-model constraints)

persistent-memory.md

@@ -128,6 +128,8 @@ _As of 2026-07-25 — **DONE: infra-ops Worldtree config-as-code repo BUILT + PU
 
 ## Recent decisions
 
+- `[2026-07-25]` **Kimi K3 (Moonshot) wired into the LiteLLM gateway** (operator-directed). `model_name: kimi-k3` → `openai/kimi-k3` @ `https://api.moonshot.ai/v1` (OpenAI-compatible paid passthrough, same shape as the z.ai GLM entries). Key `MOONSHOT_API_KEY` in the compose env block + server `.env` (NOT committed) + `.env.example` placeholder. Verified live through the gateway :4000 (17+25→"42", "PONG"). **Two Moonshot constraints (config-pinned + commented):** K3 accepts ONLY `temperature=1` (else 400 "only 1 is allowed"), and it's a REASONING model (CoT in `reasoning_content`, answer in `content` → tiny `max_tokens` returns EMPTY content). Reachable by any gateway key spanning all proxy models (incl. the shared all-agents key `sk-eA_XOd…` → spends Moonshot credits). Siblings not wired: kimi-k2.6 / kimi-k2.7-code / kimi-k2.7-code-highspeed. eshpfi `edaa9a9` (pushed).
+
 - `[2026-07-25]` **infra-ops Worldtree config-as-code repo SHIPPED — `vh/worldtree-instance-configs` (private) built, pushed, validated.** Dir-per-instance (`demo/`, `personal/`; `pinned/` = README stub, out-of-scope — no bind-mount, config frozen in image `446e5807`). Seeded byte-exact from live `/opt/<instance>/config`; 5 files each (defaults/policies/model_roles/providers/matrix). `scripts/deploy-wt-config` = diff / deploy / capture, with in-run host backup → install(vh:vh,644) → restart api+matrix → health-gate api `/health` → auto-rollback. All verbs live-tested (in-sync, capture round-trips zero-diff, pinned refused, dry-run no-ops). Gitea repo created via ana-docker localhost API with vh creds (operator-authorized one-time); pushed over internal git-SSH `10.250.50.70:222` (nh3-dev 403s gitea HTTP). Boundary AGREED by worldtree-dev (althing `01KYCAECRW…`): they stop hand-editing `/opt/<instance>/config`, route config deltas to infra-ops; three-layer model (image baseline → repo per-instance truth → host bind-mount deploy target); carve-out = their admin-API DB mutations (key mint / tier / retirement) stay in-band, not config edits. By-design deltas (personal `agent_architect` + `ratatoskr-affect-full-allow`; demo `#308` metrics + grants) preserved verbatim. → `persistent-memory.d/2026-07-25-infra-ops-wt-config-repo.md`, auto-memory `reference_worldtree_instance_configs_repo`
 
 - `[2026-07-23→25]` **Worldtree #376 config-divergence arc CLOSED — per-instance config ruled BY DESIGN.** wyrd `session.history.write` demo grant was the one real bug (demo-intended grant not on demo; fixed via wholesale `policies.yaml` replace + restart). The b131 drift guard then surfaced broader divergence = legitimate live-bridged per-instance deltas; operator ruled deltas are the design not rot; guard demoted to INFO (b132); infra-ops drift-watcher built then retired same day. → `persistent-memory.d/2026-07-25-wt-376-per-instance-config-arc.md`, auto-memory `reference_worldtree_perinstance_config`