wiki-federatelisted

# wiki-federate The federation client side of v1.12. v2.8.0/v2.9.0 made a kata serve itself over MCP; v2.10.0 (this skill) makes a kata **consume** other kata MCP servers — query them, merge results, preserve provenance. ## When to use - A query in kata A would benefit from kata B / C's content too ("how do other projects handle X?", "is there a prior decision on Y in the patterns kata?") - Authoring a new spec in kata A that may overlap with prior specs in federated peers - Cross-team / cross-project knowledge surfacing without forcing bulk-import Skip if: - Only one kata exists on this machine - The federation peer isn't trusted (don't add to `.federation.yaml` in the first place — PRD D2.3 trust-is-explicit) - You want to ingest the peer's content as first-class A pages — use `wiki-import` against the peer's filesystem path instead (PRD D1.6) ## Configuration Each wiki has its own `.federation.yaml` at the wiki root (PRD D2.1 per-wiki, not per-machine): ```yaml # {wiki_path}/.federation.yaml peers: - name: necallkit wiki_id: 7b52f6df-d7cf-47ab-b980-6042cf3a675c endpoint: stdio command: - "py" - "-3" - "C:/path/to/kata/plugin/scripts/mcp_server.py" - "--wiki" - "~/.llm-wiki/NECallKit" description: "NECallKit project wiki" enabled: true timeout_seconds: 5 ``` **Quote every command token.** The kata-stdlib YAML subset parser treats bare colons as mapping separators, so on Windows the `C:/...` drive co