dependency-handling

<!-- codex: tool-name mapping applied. See .codex/scripts/session-start.sh --> # Dependency & External API Handling ## Conventions Read capy knowledge base conventions at [shared-capy-knowledge-protocol.md](shared-capy-knowledge-protocol.md). ## Workflow **Mandatory order — lookup before usage.** Do not write, modify, or recommend any call, import, config key, or version specifier involving the dependency until you have completed the lookup cascade below. Guessing a signature or API version and fixing it after the fact is the failure mode this skill exists to prevent. 1. **Extract the dependency identity.** From the calling context, identify the dependency name, the version constraint (declared or inferred), and the specific API surface being used (function, config key, API version, image tag). This is the minimal scope — enough to drive the lookup, not enough to guess the answer. 2. **Capy search.** Search `kk:lang-idioms` and `kk:project-conventions` for previously indexed knowledge about this dependency. 3. **Context7 lookup.** Use the context7 MCP to fetch documentation. The doc version MUST match the declared dependency version. 4. **Web fallback.** Only if context7 has no coverage. 5. **Apply.** With verified knowledge now loaded, write or recommend the call, import, or config. ## Rules 1. **Prefer the latest stable version** when introducing a new dependency. Pin deliberately; don't inherit a stale version by copy-paste. 2. **Never assume how an external depend...