Expand description
Command-neutral health execution options and runners.
Modules§
- ownership
- Ownership risk analysis for hotspot files.
- scoring
- styling_
score - Styling-health score: a SECOND health axis derived purely from the structural
CSS analytics (
CssAnalyticsReport), orthogonal to the JS/TS code-health score. Mirrors the code-score shape (vital_signs::compute_health_score): start at 100, subtract capped per-category penalties, map the result to a letter grade via the sharedletter_grade. The code score is never touched.
Structs§
- Complexity
RunOptions - Normalized programmatic complexity / health inputs shared by API, NAPI, and engine-backed runners.
- Complexity
Section Options - Input for deriving effective programmatic complexity sections.
- Derived
Complexity Options - Derived section selection for programmatic health / complexity runs.
- Derived
Health Sections - Derived section selection for health runs.
- Health
Analysis Result - Typed health analysis result shared by CLI, API, NAPI, and future embedders.
- Health
Coverage Inputs - Command-neutral Istanbul coverage inputs for health CRAP scoring.
- Health
Execution Options - Command-neutral inputs needed to execute a health analysis.
- Health
Gate Options - Command-neutral health exit gate options.
- Health
Pipeline Inputs - Discovery / parse inputs the CLI resolves before calling the engine.
- Health
RunOptions - Normalized health inputs shared by CLI, API, NAPI, and future runners.
- Health
RunOptions Input - Command-neutral inputs used to normalize a health run before it reaches a concrete runner.
- Health
Scope Inputs - Scope inputs the CLI resolves before calling the engine.
- Health
Seams - CLI-supplied callbacks the command-neutral health pipeline needs.
- Health
Section Options - Input for deriving effective health sections from command-neutral flags.
- Health
Shared Parse Data - Pre-parsed health input reused from another analysis in the same process.
- Health
Threshold Overrides - Command-neutral threshold overrides for health complexity findings.
- Runtime
Coverage Options - Command-neutral runtime coverage input for health analysis.
- Runtime
Coverage Seam Input - Inputs the runtime coverage seam needs from the analysis core.
- Styling
Analysis Artifacts - Session-owned styling inputs that can be reused by health, audit, and future editor surfaces without rebuilding every source reference corpus.
Enums§
- Health
Sort - Command-neutral sort criteria for health complexity findings.
- NoGroup
Resolver - Placeholder grouping resolver for runs without
--group-by(the programmatic API path). Constructed only asNone, so its methods are never invoked.
Traits§
- Health
Group Resolver - Command-neutral grouping resolver contract for
--group-byhealth output.
Functions§
- derive_
complexity_ sections - Derive effective programmatic health / complexity section flags.
- derive_
health_ run_ options - Normalize health run inputs into the engine-owned run contract.
- derive_
health_ sections - Derive effective health section flags for CLI and embedders.
- execute_
health_ inner - Run the command-neutral health analysis pipeline.
- run_
ungrouped_ health - Run health analysis without a presentation grouping resolver.
- run_
ungrouped_ health_ with_ session - Run health analysis from an existing analysis session.
- run_
ungrouped_ health_ with_ session_ artifacts - Run health analysis from an existing analysis session and retained dead-code artifacts.
- shared_
parse_ data_ from_ artifacts - Build health shared parse data from retained dead-code artifacts.
- should_
precompute_ dead_ code_ analysis - Return true when health sections will need dead-code analysis artifacts.
- validate_
coverage_ root_ absolute - Validate that a coverage-data root is absolute under Unix or Windows path conventions.
- validate_
health_ churn_ file - Validate an explicit
--churn-fileup front so a malformed import is a loud hard error rather than a silent hotspot skip. Runs before the pipeline, and only when churn would actually be consumed (--hotspots/--targets;--ownershipis subsumed because the dispatch layer setshotspots = hotspots || ownershipbefore buildingHealthExecutionOptions), so an inert--churn-fileon a non-churn run is not penalized.
Type Aliases§
- Runtime
Coverage Analyzer - Runtime coverage analysis seam.