get_architecture should honor path scope

[noamsiegel]

Summary

On v0.8.1, get_architecture appears to ignore or under-apply the path parameter. Asking for a subdirectory/package architecture returns the same whole-repo node totals and global package list as the root project.

Environment

• codebase-memory-mcp: 0.8.1
• OS: macOS Darwin arm64
• Project: large monorepo
• Indexed project name: Users-noam.siegel-Documents-GitHub-monorepo

Reproducer

Root architecture:

codebase-memory-mcp cli get_architecture '{"project":"Users-noam.siegel-Documents-GitHub-monorepo"}'

Scoped architecture:

codebase-memory-mcp cli get_architecture '{"project":"Users-noam.siegel-Documents-GitHub-monorepo","path":"apps/hoa"}'

Observed

Both responses reported the same whole-project totals:

{
  "root_total_nodes": 305560,
  "scoped_total_nodes": 305560
}

The scoped response also started with the same global package list as the root response, e.g. Django, Pillow, PyMuPDF, Pygments, Requests, instead of an architecture summary constrained to apps/hoa files/modules.

Expected

When path is provided, get_architecture should scope the analysis to nodes whose file_path is under that subdirectory/package, including totals, clusters, top nodes, entry points, routes, hotspots, and package/module summaries.

For monorepos, this is important because whole-repo architecture output is too broad to answer questions like "explain the architecture of apps/hoa".

Duplicate check

I found related but not duplicate issues:

• task: Architecture — workspaces, cross-repo, worktrees, benchmarks (6 issues) #398 is a broad architecture/workspace tracker.
• task: Windows platform issues (8 bugs) #394 covers Windows platform/path issues.
• ES/TS module specifiers produce zero IMPORTS edges — pipeline resolves by name only #180 covers TypeScript import edges affecting architecture quality.

I did not find an existing issue specifically for get_architecture returning whole-repo output when a path scope is supplied.