ki-binding-chezmoilisted

# The chezmoi render path for the KI MCP binding You are governing **one render path**: how the canonical MCP single source becomes the file-editable surfaces that run the servers, through chezmoi. This is a **governance skill** and a **composition skill** — it sits on top of two siblings and adds a delta over them, never forking their shared modes (`ADR-KI-HARNESS-SKILLS-004`, the composition-for-backends corollary: a render path is its own skill, not a `--backend` flag on `ki-binding`). The two composed layers: - **`ki-binding`** owns the portable canonical source and mcporter evidence; runtime adapters own their native client surfaces. - **`ki-repo-dotfiles-chezmoi`** is the house standard for any chezmoi source repo — naming prefixes, templating, `chezmoi apply`, surgical-patch reverse-merge — with no knowledge of MCP. This skill's **delta** is the render contract that ties them together — the `mcp-servers-json` template, its source-data wiring, and the `chezmoi apply` that generates the surfaces `ki-binding` audits. That contract belongs to neither sibling: `ki-binding` owns no renderer, and `ki-repo-dotfiles-chezmoi` covers only generic dotfile templating. The full model is in [the standard](references/standards-chezmoi-mcp-rendering.md); the checkable criteria are in [the generated rubric](references/rubric.md); provenance is in [the sources list](references/sources.md). ## Operating modes Like every governance skill it carries the universal **AUDIT · CONFORM · E