feat(69): push parity — local moves, tag and assignee diffs reach Fizzy (#33)#50
Merged
Conversation
Four tests on the LWW local-newer branch: a moved card POSTs triage with the new column id; tag edits push EXACT toggle diffs (tag_ids on PUT is rejected live — probe notes); assignee edits toggle symmetrically; no-diff cycles add zero toggle calls (pin). RED: 3 failed, 1 pin passing. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
pushParityDiffs on the LWW local-newer branch: column moves ride POST /triage (only when the remote column is KNOWN and differs — legacy payloads without a column say nothing about placement); tags and assignees push as exact toggle diffs against this cycle's fresh remote state (tag_ids on PUT is rejected live; toggles are not idempotent). Errors collect, never throw. Rider: removes a same-type forced cast warning that rode in with #44 (StepRepository) — restores the zero-warning baseline. Closes the gap found in issue #33 (option A). Full suite green; macOS zero warnings. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
ChrisPelatari
added a commit
that referenced
this pull request
Jun 12, 2026
Co-Authored-By: Claude Fable 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
1 participant
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.
Summary
pushParityDiffson the LWW local-newer branch: column moves push viaPOST /cards/:n/triage(only when the remote column is known and differs); tags and assignees push as exact toggle diffs computed against this cycle's fresh remote state.tag_idson PUT is rejected by the live server (probed — docs/fizzy-api-notes.md); toggles are non-idempotent, hence exact diffing.Test plan
New suite
FizzySyncEnginePushParityTests(4 tests: triage body, exact tag diff incl. the both-sides-match-don't-toggle pin, assignee diff, no-diff zero-toggles pin). Three resilience tests updated… no — they pass unchanged thanks to the known-remote-column guard. Full suite green; macOS zero warnings.Engine chain: A1 ✓ C2 ✓ C4 ✓ C4b/C5/C6 ✓ → C11 remains. Mission: #28 · Status log: #69
🤖 Generated with Claude Code