Skip to content

Clarify worker-owned changes in completion audits - #59

Merged
marvin-bitterlich merged 5 commits into
mainfrom
marvin-bitterlich/pardes/clarify-completion-change-provenance
Jul 11, 2026
Merged

marvin-bitterlich merged 5 commits into
mainfrom
marvin-bitterlich/pardes/clarify-completion-change-provenance

Conversation

@marvin-bitterlich

Copy link
Copy Markdown
Contributor

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

  • Git topology is presented as cooperative evidence, not proof of worker authorship, feature semantics, or conflict-resolution ownership.
  • The total safety diff is explicitly timeout/output bounded; if unavailable, the audit retains known live paths but marks the total incomplete rather than presenting partial data as complete.
  • Stop, auto-stop, and publication safety inspections retain their existing routine behavior.

Callouts

  • Review degraded audit behavior when the total diff exceeds its timeout or output bound.
  • Review first-parent terminology and merge-context wording for accurate reviewer interpretation.

@marvin-bitterlich
marvin-bitterlich merged commit cf35077 into main Jul 11, 2026
1 check passed
@marvin-bitterlich
marvin-bitterlich deleted the marvin-bitterlich/pardes/clarify-completion-change-provenance branch July 11, 2026 19:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant