managed-codebase-contextlisted

# Managed Codebase Context ## When to use Use when a persistent codebase-context MCP server is available and the task requires broad architectural context, symbol inventory, or cross-file navigation that would be expensive to reconstruct from scratch on each turn. ## Requirements / Checks - Check MCP transport type: stdio (local, one-off) vs HTTP (requires a running server). - Do not run `npx -y` or start server processes without user approval. - Verify server `cwd`, env variables, timeout, and workspace path scope. - Confirm cleanup behavior for spawned stdio processes before starting long-running tasks. ## Workflow 1. **Select transport**: - **stdio**: suitable for local, ephemeral sessions started per task. - **HTTP**: use only when a local server is already confirmed to be running. 2. **Connect with timeout** — set a connection timeout; do not let the agent hang indefinitely if the server never initializes. 3. **Retrieve context** — fetch the current codebase map, symbol index, or architectural summary as available. 4. **Validate freshness** — a map is stale if any of the following are true: - Map timestamp predates the last `git commit` that touched relevant files. - Map references files that no longer exist. - Map is missing files present in the current workspace. - The user reports recent significant refactoring. 5. **Refresh when stale** — trigger a context refresh only when the map is demonstrably stale. Do not refresh on every request — ref