Parent: #4
Objective
Evaluate the upstream v0.10.x agent-integration work and adopt the integrations that can be generated and maintained from this fork's actual MCP tool registry and instruction contract.
Upstream references
Fork requirements
- Generate schemas and tool profiles from the fork's current registry, including project selection and cross-repository search.
- Replace only content inside the CBM instruction markers.
- Preserve unrelated user configuration and agent instructions.
- Do not advertise an integration until install, detection, configuration, restart guidance, and smoke tests exist.
- Keep unsupported upstream integrations explicitly listed rather than inflating the supported-agent count.
Acceptance criteria
- Produce an adoption matrix: adopted, already equivalent, deferred, or rejected, with a reason for each upstream integration.
- Generated tool schemas match the MCP registry in CI.
- Installer regression tests cover every adopted agent on its supported platforms.
- Installed instructions explain single-file Zova operation and selected/all-project search correctly.
v0.10.3–v0.10.8 additions
- a154d18a — repair the Pi default-export contract.
- 63f26f4c — forward CBM_CACHE_DIR to Codex-spawned servers.
- 20ad3e5b — forward CBM_RUNTIME_DIR where daemon adoption requires it.
- 1e6825f9 — update the OpenCode config file that already exists.
- 0374af14 — configure only explicitly selected clients.
- 2bb94372 — keep installed skill YAML valid for strict readers.
- b54998d2 and 33d1ecea — accept real client YAML/annotated entries and repair entries written by older releases.
Generated instructions must continue to describe single-file Zova and cross-repository project selection, not upstream per-project databases.
Parent: #4
Objective
Evaluate the upstream v0.10.x agent-integration work and adopt the integrations that can be generated and maintained from this fork's actual MCP tool registry and instruction contract.
Upstream references
Fork requirements
Acceptance criteria
v0.10.3–v0.10.8 additions
Generated instructions must continue to describe single-file Zova and cross-repository project selection, not upstream per-project databases.