[FEATURE] Cross-repo intelligence: link edges across multiple indexed repos

[Wolfvin]

Problem

Microservice and monorepo architectures split code across multiple repos/packages. An agent working on Service A can't trace a call that crosses into Service B or a shared library — the graph just ends at the module boundary.

Proposed Change

Add a --workspace concept that covers multiple root directories under one index:

codelens init --workspace /projects/myapp  # covers services/api, services/worker, lib/shared

• Cross-repo edges become CROSS_CALLS, CROSS_IMPORTS to distinguish them
• trace can follow cross-repo edges with --cross-repo flag
• get_architecture returns a combined service map

Minimum Viable Version

Just support multiple repo_path entries in .codelens/config.json — resolve imports against the combined symbol table from all indexed repos.

[Wolfvin]

Multi-worker analysis: confirmed by 3 worker reports

The cross-repo intelligence proposal is independently confirmed by 3 worker reports, each approaching the problem from a different angle:

Worker	Source file	What they add
Repomix	update!/CodeLens_vs_Repomix_Upgrade_Analysis.md R5	Remote repository processing via --remote <url> flag — fetches GitHub repo tarball via archive API (faster than git clone), supports user/repo shorthand, branch URL, commit URL. Extract to /tmp/codelens-remote-{hash}/, run command, cleanup. MCP tool pack_remote_repository.
Serena	update!/CodeLens_vs_Serena_Upgrade_Analysis.md S14	Cross-package reference for monorepo via LSP additional_workspace_folders (TypeScript only initially). Registers sibling packages as LSP workspace folders so find_referencing_symbols / find_symbol / rename work across package boundaries without explicit import.
CodeGraph	update!/CodeLens_CodeGraph_Upgrade_Analysis.md #29	Multi-repo workspace via projectPath parameter passed to MCP tools. Walk-up parent directory to resolve .codelens/ index. Maintain registry of indexed projects for cross-repo queries.

Recommendation

These target different scopes of "cross-repo":

• CodeGraph feat(types): hybrid type resolution — closes #13 #29 = multi-repo querying within MCP (read-only across pre-indexed projects) — most aligned with this issue's title
• Repomix R5 = one-shot remote fetch + scan (no persistent index) — useful for "analyze a repo I don't have locally"
• Serena S14 = intra-monorepo cross-package (siblings in same repo, different package.json) — actually a narrower problem than this issue

Suggest retitling this issue to "Cross-repo intelligence: query across pre-indexed projects" (CodeGraph #29 scope) and opening 2 sibling issues for the other scopes:

• "Remote repo fetch-and-scan (--remote)" (Repomix R5)
• "Monorepo cross-package reference via LSP workspace folders" (Serena S14, depends on native LSP server issue)

Aggregated from update!/ worker analysis reports by multi-worker triage.

[Wolfvin]

Mengerjakan issue ini -- 2026-07-01T11:58:54Z

[Wolfvin]

PR siap review

PR: #150 -- feat(xrepo): cross-repo intelligence — multi-repo query via --additional-paths (closes #15)
Branch: feat/issue-15-cross-repo-intelligence
Summary: Implementasi MVP dari issue #15 -- engine cross-repo yang merge backend registries dari multiple repos, tag setiap node dengan repo field, re-run resolve_edges() pada combined node set supaya cross-repo calls auto-resolve. Cross-repo edges di-flag dengan cross_repo=True + target_repo + source_repo. Command query dapat --additional-paths flag (backward-compatible: tanpa flag, behavior tidak berubah). MCP tool codelens_query dapat parameter additional_paths. Scope mengikuti rekomendasi CodeGraph #29 dari multi-worker aggregation comment (read-only multi-repo querying across pre-indexed projects).
Tests: 1398 passed (28 test baru di tests/test_crossrepo_engine.py), 80 skipped, 1 failed (pre-existing test_codelensignore::test_actual_target_dir_is_ignored -- gagal juga di clean origin/main, bukan regresi).