Skip to content

feat(workflow): mechanical merge-conflict fixups keep review coverage - #2270

Closed
timothyfroehlich wants to merge 2 commits into
mainfrom
feat/mechanical-resolution-review-exception
Closed

timothyfroehlich wants to merge 2 commits into
mainfrom
feat/mechanical-resolution-review-exception

Conversation

@timothyfroehlich

Copy link
Copy Markdown
Owner

Summary

  • Extends spec §8.12: a merge-conflict resolution or migration renumbering keeps prior review coverage when the commit carries a Mechanical-Resolution: <what you resolved> trailer attesting no logic changed — previously any manual conflict resolution broke coverage and forced a fresh review round, even for trivial import-path or migration-number collisions.
  • Trust boundary is the trailer itself: the owning agent attests mechanical-only, nothing here diffs content semantically; a false attestation is traceable to a name in git log.
  • Updates scripts/workflow/_pr-gates.sh (_has_mechanical_trailer, extended _is_pure_merge_from_main), docs/feature-specs/pr-lifecycle-monitoring.md §8.12 + changelog, REVIEW.md, AGENTS.md, scripts/workflow/AGENTS.md, and .agents/skills/pinpoint-pr-workflow/SKILL.md.

Test plan

  • bash -n scripts/workflow/_pr-gates.sh
  • pnpm run check (pre-existing unrelated warnings only)
  • Manual test of _has_mechanical_trailer against a synthetic repo (trailered vs. untrailered commit)
  • CI

🤖 Generated with Claude Code

… (PP-8.12)

Extends the §8.12 pure-merge-from-main exception: a merge-conflict
resolution or migration renumbering keeps prior review coverage when
every such commit carries a `Mechanical-Resolution: <what you
resolved>` trailer attesting no logic changed. Manual conflict
resolution previously always broke the tree-match check and forced a
fresh review round even for trivial import-path or migration-number
collisions.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@vercel

vercel Bot commented Sep 26, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
pin-point Ready Ready Preview Sep 26, 2026 10:18pm UTC

Request Review

@coderabbitai

coderabbitai Bot commented Sep 26, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

Comment @coderabbitai help to get the list of available commands.

…solution

The suffix text changed from "pure merge from main" to "pure merge or
mechanical resolution from main"; update the five test_pr_gates.py
assertions that pinned the old wording.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@timothyfroehlich

Copy link
Copy Markdown
Owner Author

Closing per Tim: superseded by #2436, which implements the §8.12 wording Tim approved (#2434) and keeps coverage only for verified migration-renumber merges instead of a self-attested trailer. —Claude-SessionOrchestrator

This branch was successfully deployed

1 active deployment
Preview — 79acb17e Deployed Sep 26, 2026 by vercel[bot]
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