Expand description
Typed analysis engine boundary for fallow consumers.
fallow-core remains the internal orchestration backend. This crate owns
the typed boundary that editor, API, and embedding surfaces can depend on
without calling deprecated core entry points directly. Public modules should
expose owned engine runners, typed result structs, or narrowly scoped aliases
instead of broad core re-exports.
Modules§
- baseline
- changed_
files - Changed-file helpers owned by the engine boundary.
- churn
- Git churn helpers and types exposed through the engine boundary.
- codeowners
- CODEOWNERS file parser and ownership lookup.
- cross_
reference - Cross-reference helpers exposed through the engine boundary.
- dead_
code - Dead-code result helpers exposed through the engine boundary.
- discover
- Discovery helpers and types exposed through the engine boundary.
- duplicates
- Duplication result types exposed through the engine boundary.
- flags
- Feature flag analysis owned by the engine boundary.
- guard
- Typed guard report assembly for pre-edit architecture guidance.
- health
- Command-neutral health execution options and runners.
- module_
graph - Module graph contracts owned by the engine boundary.
- plugins
- Plugin registry helpers and types exposed through the engine boundary.
- project_
analysis - Project-level analysis contracts owned by the engine boundary.
- project_
config - Project config resolution owned by the engine boundary.
- session
- Engine-owned analysis session orchestration.
- source
- Source parsing contracts owned by the engine boundary.
- trace
- Read-only trace helpers exposed through the engine boundary.
- trace_
chain - Symbol trace types exposed through the engine boundary.
- validate
- vital_
signs - Vital signs computation and snapshot persistence.
Structs§
- Engine
Error - Error type exposed by the typed engine boundary.
Type Aliases§
- Engine
Result - Result alias for typed engine operations.