Repository navigation
CI: drift avoids items the round edited on the sending side - #259
Merged
Merged
Conversation
An edit to the receiving side's copy of an item the round also edited on the sending side is a change on both sides, which the sync rightly reports as a conflict. Drift now picks from the other items, so it grades a target-only change (seed 467216964, round 3, hit Posts #113 / #15). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
5PK
added a commit
that referenced
this pull request
Nov 3, 2026
…side (#260) #259 only skipped items the round edited with content/edit. A list swap saves both items it moves (new versions), and so do publishes, so drift could still pick a copy of one and grade a change on both sides (seed 799975145, round 1: list swap of Posts #112, drift on its copy #16). Drift now skips the copies of every content item named by the round's content and ordering changes. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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.
Harness-only fix (
ci/permutation/) for the live sync test that gates the publish. No CLI code changes.The
v1.3.0-beta.1tag run (run 41674024760) failed one check, so nothing was published. In round 3 a source-sidecontent/editchanged Posts #113, and the drift edit then picked its target copy (#15). That's a change on both sides, so the CLI correctly reported a conflict, and the drift check, which expects a target-only change kept with a warning, failed. #258 already kept the conflict edit off the drift item; this does the same for the round's other edits.The fix: drift skips the receiving side's copies of items the round edited on the sending side.
Tested: a replay of the failed run (same seed
467216964, beta tier, fresh dev instances) passed every check in all 5 rounds.After this merges,
v1.3.0-beta.1gets re-pointed at the new main commit to re-run the gated publish.🤖 Generated with Claude Code