refactor(operator-trend): collapse persistence/churn hotspot selectors onto a parametrized base (T3-2 phase 7a)#91
Merged
Conversation
…s onto a parametrized base (T3-2 phase 7a) Pivot the fractal collapse to operator_resolution_trend.py (22K LOC). Collapse the 4 reset-reentry persistence/churn hotspot selectors (reset_reentry / rebuild_reentry / restore / rerestore) onto one `_hotspots_base` + `_HotspotsTierSpec` + 4 specs. They were exact structural clones differing only in the per-tier age / persistence / churn keys, the `just-*` mode token, and the holding/sustained status set; the churn-watch fallback set is identical across tiers and stays inline. Proven byte-identical by an exhaustive branch differential (real vs base+spec over a 9-class grouping / filter / sort / cap corpus across all three modes per tier). This file has no composer-golden coverage, so the differential plus the full suite (which exercises these via the public resolution-trend API) are the gates. Net -260 lines. Verification: pytest 2539 passed / 2 skipped; mypy clean; ruff check clean.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
refactor(operator-trend): collapse persistence/churn hotspot selectors onto a parametrized base (T3-2 phase 7a)
Pivot the fractal collapse to operator_resolution_trend.py (22K LOC).
Collapse the 4 reset-reentry persistence/churn hotspot selectors
(reset_reentry / rebuild_reentry / restore / rerestore) onto one
_hotspots_base+_HotspotsTierSpec+ 4 specs. They were exactstructural clones differing only in the per-tier age / persistence / churn
keys, the
just-*mode token, and the holding/sustained status set; thechurn-watch fallback set is identical across tiers and stays inline.
Proven byte-identical by an exhaustive branch differential (real vs
base+spec over a 9-class grouping / filter / sort / cap corpus across all
three modes per tier). This file has no composer-golden coverage, so the
differential plus the full suite (which exercises these via the public
resolution-trend API) are the gates.
Net -260 lines. Verification: pytest 2539 passed / 2 skipped; mypy clean;
ruff check clean.