context/impact: --in in a multi-language repository is checked against one language's graph, so a path another language holds is refused or ignored #1584

Symptom

In a repository indexed in several languages (one graph per language), a path scope is checked against the first language's graph only. A path that only another language's graph holds is refused or ignored:

• axiomcode context "<task>" --in plugins/x → no indexed file has 'plugins/x' in its path, offering only the first graph's scopes, although the Python graph indexes plugins/x/… (the same query without --in lists those files in its Python section). Adding --lang python gives the same refusal.
• axiomcode context "<task>" --in tests (MCP in_path=tests) answers only from the TypeScript graph, matching tests as a substring of parser/src/test/…, and leaves out the Python graph whose tests/*.py files are the ones meant.
• axiomcode impact run --in plugins/x/mcp answers for TypeScript declarations under graph/test/…, all outside the scope, and not for the Python run inside it.

CLI and MCP give the same answers.

Expected

With a scope, every language graph is asked, and each keeps only the files under that path. A path is refused only when no graph holds it. A scope matches by path prefix, not by a substring of a directory name.

Repro

A repository with TypeScript under src/ and Python under tools/py/ (both indexed): axiomcode context "anything" --in tools/py refuses. Without --in, the Python section lists tools/py/….