fix: preserve triage scope across sense reloads#639
Draft
ApexWorm wants to merge 1 commit into
Draft
Conversation
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.
Problem
Sense-check content batches correctly use the active triage scope, but post-update plan reloads gave the structure and value batches the full historical plan. On a large tracker this sends an oversized prompt to Codex and aborts the stage before its global checks run.
Fix
Reapply
triage_scoped_planafter each reload and seed the value batch from the already scoped plan. A regression covers a reload that includes a legacy cluster and verifies that the rebuilt structure and value prompts retain only the active cluster.Validation
python3 -m pytest -q desloppify/tests/commands/plan/test_triage_split_modules_direct.py(44 passed)