Skip to content

fix(skills): keep fragmentation attribution inside selected range - #191

Merged
codeasier merged 1 commit into
mainfrom
fix/issue-180
Oct 3, 2026
Merged

codeasier merged 1 commit into
mainfrom
fix/issue-180

Conversation

@codeasier

Copy link
Copy Markdown
Owner

Summary

Use the range-filtered peak event for fragmentation attribution, including default start_id=0 and lower-bound-only scopes. Stop on unusable peaks; retain blocks allocated before the window but live at the event. Allow unfiltered reports only as explicitly requested independent comparisons. Preserve setup readiness and collection routing guidance during integration.

Fixes #180

Validation

  • Original full pytest: 1194 passed
  • Latest-main provenance, skills, bounded CLI/SQLite attribution and bundled checks passed
  • Ruff, Black, basedpyright (0 errors), diff check passed
  • Real CLI regression coverage for distinct scoped/full peaks and empty/NULL/synthetic cases.

@codeasier
codeasier merged commit 26071ae into main Oct 3, 2026
6 checks passed
@codeasier
codeasier deleted the fix/issue-180 branch October 3, 2026 19:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[DOCS] fragmentation skill 的 optional report 会越出限定事件范围

1 participant