architecture-ownership-topologylisted

# Architecture Ownership Topology Bundled commands use `$PLUGIN_ROOT` 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 when the question involves ownership, team boundaries, review paths, CODEOWNERS, OWNERS files, shared modules, Conway-style alignment, or coordination risk across modules/services. ## Inputs - Ownership sources: `.github/CODEOWNERS`, `CODEOWNERS`, `OWNERS`, `OWNERS_ALIASES`, `MAINTAINERS`, `GOVERNANCE.md`, `CONTRIBUTING.md`. - Architecture sources: package/module layout, ADRs, architecture docs, service boundaries, public APIs, dependency rules. - Coupling evidence: static imports, build/package graph, runtime integrations, deployment/IaC, data ownership, co-change history. - Governance evidence: branch protection, review rules, release ownership, exception paths, waivers. - User-provided organization facts, only when explicitly provided. Do not infer actual communication, staffing, workload, or review enforcement from repository files alone. ## Probe ```bash python3 "$PLUGIN_ROOT/scripts/architecture_probe.py" <repo-path> --json ``` Use `ownership_topology` for ownership sources, top-level coverage, ownerless areas, and cross-owned static dependency edges. The parser is conservative: no GitHub API, org membership lookup, branch-protection proof, or full CODEOWNERS semantics. ## Lenses - Coverage: sig