codebase-anatomylisted

# Codebase Anatomy (codeweb) Build a structural map of the system. Each function, class, method, or exported symbol is a node. Calls, imports, and inheritance relationships are edges. Each node belongs to a domain. An **overlap graph** identifies separate parts that do the same work. The result is an **evidence-backed restructuring plan**. It identifies the duplicated logic that can move into one defined system and the symbols that must depend on that system. ## When to Use - Restructuring your own codebase and you need to *see* the real dependency web and where it's duplicative before moving code. - Onboarding to a large or legacy system at symbol resolution, including relationships across folders. - Reviewing an **external** repo (a plugin, library, or template you found on GitHub) end-to-end before adopting it — what it does, how it's wired, and whether it's worth committing to. - Hunting cross-cutting duplication that file/module tools miss (the same check coded N times in N domains). ## Two Modes - **internal** — analyze the current project; produce a domain map + overlap graph + restructure recommendations. - **external** — `target` is a git URL or `owner/repo`. Clone it **read-only** to a temp dir, map it the same way, and add an **adoption review** (risk, dependencies, architecture verdict, "should you adopt this?"). Auto-detect: a URL or `owner/repo` ⇒ external; a path or `.` ⇒ internal. `--mode` overrides. ## Non-Negotiable Rules - **Never exe