chore(sync): reconcile the #524 and #525 ledger entries - #526
Merged
Conversation
The four entries written during this run carried `pending-merge` in both `pr` and `b24ui_sha`, because the entry goes in with the port before its PR has a number or a squash SHA. Both PRs have now merged: - `9c99bf16`, `9d46fc7e`, `20c1954d` → #524 / `1e33c0a2` - `e791d302` → #525 / `0a8c87ca` Bookkeeping only — no entry is added, the cursor does not move, and no decision changes. This is also the first run through the corrected ordering guard from #524, which allows a pending suffix and now sees it emptied.
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
2 participants
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.
Bookkeeping for #524 and #525.
The entry goes into
.sync/nuxt-ui.jsonin the same commit as the port, soprandb24ui_shacannot be known yet — they go in aspending-mergeand are reconciled once the PR squash-merges. Both have now merged:9c99bf16—chore(deps): update all non-major dependencies524/1e33c0a29d46fc7e—chore(deps): update tiptap to ^3.30.5524/1e33c0a220c1954d—chore(deps): update dependency reka-ui to v2.10.4524/1e33c0a2e791d302—fix(Select/SelectMenu): add responsive text size525/0a8c87caScope
Eight lines in
.sync/nuxt-ui.json, nothing else. No entry is added,cursordoes not move, nodecisionorsummarychanges, and no.sync/log/*.mdfile is touched.Worth noting
This is the first run through the corrected ordering guard from #524. Its previous form asserted that no entry carries
pending-mergeat all, which §6 step 4 requires them to — it went red on the very next port and would have blocked this exact sequence. The corrected form allows a pending suffix and fails only when a pending entry sits behind a reconciled one, i.e. when a bookkeeping PR was skipped. It stayed green through the port with a four-entry tail, and now sees that tail emptied.Verification
sync-ledger·dep-parity·commit-parses— 100 tests, 3 files.grep -c pending-merge .sync/nuxt-ui.jsonis 0.Generated by Claude Code