matevip 0141b00270 docs(agent): document per-agent primary knowledge base binding (1.5.0) ... Add the user-facing and API-reference docs that explain how an employee can declare a primary knowledge base, what the runtime fallback chain looks like, and how the binding is driven from the API. agents.md (zh + en) - New section "Knowledge base binding (per-agent primary KB)" right after the tool-binding section, with a 1.5.0 New In badge - Lays out the design intent explicitly: KBs stay workspace-shared, the binding only chooses a default target, multiple agents may pick the same KB as primary - Documents the runtime resolution order used by wiki tools: explicit kbName/kbId, agent.primaryKbId, most-recently-updated workspace KB - Migration note about the legacy kb.agent_id to agent.primary_kb_id backfill and the visibility change for anyone who relied on the old one-to-one isolation api.md (zh + en) - Under Agents: document the primaryKbId field with the three-state PUT semantics (omit / null / value) and example curl calls - Under LLM Wiki: document GET /api/v1/wiki/knowledge-bases/bindable and the explicit warning that PUT /api/v1/wiki/knowledge-bases/{id} no longer processes the agentId field		2026-05-29 06:33:46 +08:00
..
en	docs(agent): document per-agent primary knowledge base binding (1.5.0)	2026-05-29 06:33:46 +08:00
zh	docs(agent): document per-agent primary knowledge base binding (1.5.0)	2026-05-29 06:33:46 +08:00