mycocanopy-manifest-driven-tool-resolutionlisted

# Canopy Manifest-Driven Tool Resolution Architecture Canopy's manifest-driven tool resolution provides a single source of truth for determining which symbiont tools constitute file reads, enabling consistent path extraction across hooks, database queries, and analytics. This architecture eliminates hardcoded per-symbiont assumptions and makes adding new symbionts require only manifest declarations, not code changes. ## Prerequisites - Understanding of symbiont manifest structure in `packages/myco/src/symbionts/manifests/` - Familiarity with Canopy's pre/post tool-use hooks in `packages/myco/src/hooks/` - Knowledge of the activity database schema and drilldown query patterns - Access to test infrastructure for validating tool resolution changes ## Procedure A: Add canopyReadTools to Symbiont Manifest Define which tools constitute file reads using the `capabilities.canopyReadTools` discriminated union in the symbiont's YAML manifest. ### For Structured Tools (e.g., Claude Code) When the symbiont exposes named tools with structured arguments: ```yaml # packages/myco/src/symbionts/manifests/claude-code.yaml capabilities: canopyReadTools: mode: structured tool: Read filePath: file ``` - **mode: structured** - Tool has named fields for arguments - **tool** - Exact tool name that triggers Canopy injection - **filePath** - Field name containing the file path ### For Shell-Pattern Tools (e.g., Codex) When the symbiont uses shell commands with regex-based pa