# v1.13.18 — codecontext file_path resolver

Fixes a silent failure that caused all four `file_path`-taking codecontext wrappers to return "file not found" whenever the model passed a relative path.

## Why

BooCode's codecontext sidecar (`codecontext_client.ts`) already realpath-resolves `target_dir` before forwarding it to the HTTP shim. It did not do the same for `file_path`. The sidecar's internal file index is keyed on absolute paths, so any relative path from the model produced a JSON error response:

```
{"error":"file not found: apps/server/src/services/inference/turn.ts","result":null}
```

This was observed repeatedly in the 2026-05-22 docker logs (17:56 UTC window) — the model passed relative paths on every `get_file_analysis` tool call and received no useful output, burning tool budget on dead calls.

## Scope

Four wrappers take a `file_path` argument:

- `tools/codecontext/get_file_analysis.ts` — `file_path` required
- `tools/codecontext/get_symbol_info.ts` — `file_path` optional
- `tools/codecontext/get_dependencies.ts` — `file_path` optional
- `tools/codecontext/get_semantic_neighborhoods.ts` — `file_path` optional

Fix lands in one place: `callCodecontext` in `codecontext_client.ts`. A new `resolveProjectPath` helper is inserted at the args-spread site and invoked whenever `file_path` is present and non-empty. All four wrappers benefit automatically; no per-wrapper edits required.

Zod `.trim()` is added to all four `file_path` schema entries so that whitespace-padded paths from the model are cleaned before they reach the resolver.

## Decision: single resolver over per-wrapper edits

Four wrappers, one shared code path. Per-wrapper edits would require four edits and make it easy to miss one. The `callCodecontext` shim already owns `target_dir` validation; `file_path` validation belongs there too for symmetry.

## Non-goals

- No changes to the `target_dir` resolver — it already works correctly.
- No extension to wrappers that do not take `file_path` (`get_codebase_overview`, `get_framework_analysis`, `search_symbols`, `watch_changes`).
- No fix for the unrelated RPC errors and Go map-race warnings visible in the codecontext sidecar logs — those are upstream bugs.