codebase-architecture-auditlisted

# 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> ``` ## AI-Assisted Recovery When Codex, Claude Code, or another coding agent helps recover architecture, treat its map as a hypothesis. Bind important components, responsibilities, edges, and runtime paths to source or command evidence. Explore outward from the focal code through callers, callees, interfaces, subclasses, sibling implementations, importers, shared state, and downstream consumers. Record excluded or inaccessible surfaces and lower confidence instead of claiming whole-repository coverage. Keep explicit architecture in