task: Architecture — workspaces, cross-repo, worktrees, benchmarks (6 issues)

[DeusData]

Scope

Umbrella tracker for larger feature requests / architectural proposals that don't map to a single bug. Each item here typically needs a small design discussion before implementation.

Sub-issues

• Cross-crate call graphs stop at boundaries #56 — Cross-crate call graphs stop at boundaries (Rust workspaces)
• Workspace support: package.json#workspaces, pnpm-workspace.yaml, and [workspace] in Cargo.toml — proposal #271 — Workspace support: package.json#workspaces, pnpm-workspace.yaml, [workspace] in Cargo.toml — proposal
• Feature Request: Automatic deletion of project when underlying folder is deleted #286 — Feature Request: Automatic deletion of project when underlying folder is deleted
• Protocol-aware cross-repo intelligence: gRPC + typed-message + attribute-route matching (design proposal) #292 — Protocol-aware cross-repo intelligence: gRPC + typed-message + attribute-route matching (design proposal)
• Support efficient indexing for Git worktree-based agent development workflows #351 — Support efficient indexing for Git worktree-based agent development workflows
• Add new benchmark with memtrace-public #356 — Add new benchmark with memtrace-public

PR #369 (workspace imports + SvelteKit filesystem routes) is a partial implementation of #271 / #56's TypeScript-monorepo half — please review there before scoping further.

Acceptance

Per item:

1. A short design note (or rejection with rationale) in this issue or a sub-issue.
2. If in scope: implementation tracked in its own follow-up issue or PR.

Why one task

These are not bugs — they're feature/architecture asks. Triaging them together prevents them from drifting into the backlog uncategorized.