Expand description
Trimming strategies assign information value to tree nodes.
Each strategy implements domain-specific value scoring. The StrategyResolver maps tool names to strategies via:
- Exact match in TOML overrides
- Hardcoded defaults by tool name
- Strip proxy prefix and retry 1-2
- Fallback to Default strategy
Structs§
- Cascading
Strategy - Cascading trim — chronological decay for comments. Newest comments are most valuable: p(i) = beta^(n-1-i).
- Default
Strategy - Default strategy — uniform value 1.0 for all nodes.
- Element
Count Strategy - Element count trimming — decreasing value by position.
- Head
Tail Strategy - Head+Tail strategy for logs — 30% head, 70% tail with error boost.
- Item
Metadata - Metadata for priority-aware value scoring.
- Priority
Strategy - Priority strategy — composite scorer for issues and MRs.
- Random
Strategy - Random strategy — assigns deterministic pseudo-random values via LCG.
- Reversed
Strategy - Reversed strategy — mirror of ElementCount: last item = 1.0, first = 0.3.
- Size
Proportional Strategy - Size-proportional trimming for diffs — value weighted by file type.
- Strategy
Resolver - Resolves tool names to trimming strategies.
- Thread
Level Strategy - Thread-level trimming for discussions. resolved=0.3, unresolved=1.0; first+last comment always get value boost.
Enums§
- Trim
Strategy Kind - Strategy type identifier.
Traits§
- Trim
Strategy - Trait for assigning information value to tree nodes.
Functions§
- assign_
diff_ values - Assign diff values with explicit file paths.
- assign_
discussion_ values - Assign discussion values with resolved status.
- assign_
priority_ values - Assign priority values with explicit per-item metadata.
- create_
strategy - Create a strategy instance from its kind.