codebase-architecture-audit

# Codebase Architecture Audit Bundled commands use `$PLUGIN_ROOT` (`$env:PLUGIN_ROOT` in PowerShell; same path suffix) for the plugin root. Set it once: use the host's plugin-root variable when defined (Claude Code: `PLUGIN_ROOT="$CLAUDE_PLUGIN_ROOT"`), otherwise the absolute path of this plugin's root directory. Use to inspect the architecture that exists in code, not the architecture people intend it to have. ## Inputs Gather repository guidance, product/domain context, top-level structure, entry points, manifests, ownership files, architecture docs, ADRs, API contracts, schemas, runtime/deployment evidence, tests, observability hooks, and recent changes. Run the probe when useful: ```bash python3 "$PLUGIN_ROOT/scripts/architecture_probe.py" <repo-path> --json python3 "$PLUGIN_ROOT/scripts/architecture_probe.py" <repo-path> --json --git-history python3 "$PLUGIN_ROOT/scripts/architecture_probe.py" <repo-path> --json --policy <policy.json> ``` ## Lenses - System shape: monolith, modular monolith, service system, plugin, app/backend, library, CLI, data pipeline, mixed. - Boundaries: module purpose, public APIs, ownership, dependency direction, leakage. - Domain/data: bounded contexts, language, data ownership, transaction boundaries, anti-corruption layers. - Coupling/cohesion: cycles, hubs, framework bleed, shared mutable state, duplicated domain rules, change amplification. - Structure metrics: fan-in/out, instability, dependency cycles, co-change hotspots, intent fi...