Tracking issue for cross-language edges — arguably the most important v2 capability. CLDK's supported languages are exactly the polyglot-enterprise stack (TS frontends, Java services, Python glue/workers), and no tool today links fetch("/api/users") in TypeScript to @GetMapping("/api/users") in Java.

Boundary edges are canonical Edges with structural confidence by construction, which is what keeps cross-language reachability honest.

Depends on: Epic A (canonical schema + URIs), the fluent query core (#155), and the deeper per-language semantics landing in the codeanalyzer-* backends (their domain).

Children

• rfc: boundary-edge taxonomy (http/rpc/queue) as canonical edges #223
• feat(xlang): normalized provides/consumes facts across languages #224
• feat(xlang): heuristic HTTP linker v1 (TS fetch/axios <-> Java/Python routes) #225
• feat(xlang): CLDK.workspace() multi-language composition #226
• test(xlang): polyglot fixture app (TS + Java + Python) as executable spec #227