Repository navigation
Clarify worker-owned changes in completion audits - #59
Merged
marvin-bitterlich merged 5 commits intoJul 11, 2026
Merged
marvin-bitterlich merged 5 commits into
marvin-bitterlich merged 5 commits into
Conversation
marvin-bitterlich
deleted the
marvin-bitterlich/pardes/clarify-completion-change-provenance
branch
July 11, 2026 19:45
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.
Why?
Completion reports could attribute a large branch-point delta to a worker after merging upstream changes, producing alarming and misleading review signals.
How?
Reuse bounded first-parent provenance to lead with worker-branch non-merge change candidates, while separately labeling merge context, net branch-point delta, and first-parent commit counts.
Decisions
Callouts