Repository navigation
Preserve review follow-up scope and compact coverage reports - #219
Merged
Merged
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
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.
An external-context follow-up for a grouped review could reject a successfully retrieved file because its scope was rebuilt from an unordered set. Preserve the parent scope order while retaining strict binding validation.
The PR305 report also exceeded the publisher's 60,000-byte cap because it repeated JSON coverage rows. Render all obligations in a compact table with a stable evidence index; keep blockers, incomplete states, task/evidence associations, and the full JSON checkpoint. The actual checkpoint now renders to 20,704 bytes rather than 62,777 and passes an offline COMMENT preview with merge=false. The dated evidence record preserves the original incomplete outcome.
Validation: 199 focused engine/report/frozen-runtime/publisher/Actions tests passed; Ruff and diff checks passed. Independent Luna review cleared the exact files. The regression failed before the scope repair and passed under 20 hash seeds afterward. No provider rerun or target publication was performed.