alex/g3
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove Key findings section from dependency analysis docs

Browse Source
This commit is contained in:
Dhanji R. Prasanna
2026-01-06 12:33:48 +11:00
parent d695f10604
commit 9132c441f1
1 changed files with 0 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
AGENTS.md
View File

@@ -216,11 +216,4 @@ The `analysis/deps/` directory contains static analysis artifacts generated by t
| `hotspots.md` | Coupling hotspots: files/crates with disproportionate fan-in or fan-out (>2× average) | | `hotspots.md` | Coupling hotspots: files/crates with disproportionate fan-in or fan-out (>2× average) |
| `limitations.md` | Known limitations of the static analysis (conditional compilation, macros, re-exports) | | `limitations.md` | Known limitations of the static analysis (conditional compilation, macros, re-exports) |
**Key findings:**
- No cycles detected at crate or file level (strict DAG structure)
- `g3-config` and `g3-providers` are the most depended-upon crates (fan-in: 4)
- `g3-cli` has highest fan-out (5 crate dependencies) as the composition root
- `ui_writer.rs` is the most imported file (11 dependents)
- `g3-core/src/lib.rs` has highest fan-out (25 module declarations)
These artifacts are useful for understanding coupling, planning refactors, and identifying architectural boundaries. These artifacts are useful for understanding coupling, planning refactors, and identifying architectural boundaries.