Repository navigation
Reassess preparation incrementally from verified dependencies - #32
Merged
Merged
Conversation
dkropachev
marked this pull request as ready for review
October 25, 2026 06:01
dkropachev
force-pushed
the
incremental-preparation
branch
6 times, most recently
from
October 26, 2026 11:22
3d013c9 to
3b78a1a
Compare
Repeated preparation rebuilds conclusions when their inputs are unchanged. Track complete Git entries and governing evidence with stable conclusion IDs, reuse proven unchanged analysis without model calls, and reassess affected conclusions and their dependents in one batch. Require explicit impact decisions for unmapped changes and preserve unknown evidence. Retain immutable snapshots and verified lineage, support full reassessment and separate v1 migration, and recheck parsed inputs and every consumed ancestor before publication. Guard activation against competing parents. Preserve reviewer order through refresh and cleanup even after descriptor aliases disappear, while retaining exact cohort and review coverage gates. Document the response contract, exercise CLI refresh and migration, and cover dependency, evidence, publication and reconciliation regressions. Synchronize the plugin manifests and owned provenance at version 1.2.0.
Incremental preparation can retain paths containing arbitrary Git bytes. Carry them through reviewer handoffs, session coverage, findings, reports and router output without losing bytes or changing ordinary Unicode hashes. Escape reconciliation payloads so cleanup analyses survive UTF-8 provider transport unchanged, preserving retained review evidence and cycle budgets. Decode Git-quoted paths when collecting context and validating findings. Use paginated file metadata for complete filename records, retain Unicode line separators within filenames, and distinguish headers from added text. Exercise real unusual filenames through ordinary, series and large patches, pinned review delivery, cleanup reconciliation, coverage persistence, statistics and compact, full and paged CLI results.
dkropachev
force-pushed
the
incremental-preparation
branch
from
October 26, 2026 13:52
e6c2905 to
fa51190
Compare
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.
Issue
Refreshing PR preparation repeats analysis even when the relevant code and governing evidence are unchanged. Reusing conclusions needs an explicit dependency record and verified evidence so changes cannot silently invalidate review boundaries or workflow guidance.
Fix
Introduce preparation v2 with runtime-owned conclusion IDs, complete Git tree-entry comparison, and exact governing-evidence fingerprints. Select changed conclusions and their transitive dependents for one batched reassessment, and require explicit impact assessment for new or unmapped inputs. Identical inputs and supported operational changes preserve analysis with zero model calls.
Retain immutable evidence snapshots and parent lineage, support explicit full reassessment and one full fallback, and migrate v1 artifacts through fresh analysis. Check inputs again before atomic publication and require the expected active parent when registering a child, preventing concurrent refreshes from overwriting one another.
Preserve configured-reviewer coverage, exact review-session identities, Decisions synchronization, CI gates and iteration budgets. Document the refresh contract and synchronize the plugin version at 1.2.0.