chore(sync): reconcile the #509 ledger entries with their merged PR - #511
Merged
Merged
Conversation
`a494a97d`, `3d2de0ce` and `ae243116` were written while their port was still open, so all three carried `pending-merge` in both `pr` and `b24ui_sha`. #509 squash-merged as `7203420b`; this points them at it. Bookkeeping only — no ledger entry is added, the cursor does not move, and no decision changes.
IgorShevchik
force-pushed
the
chore/sync-ledger-509
branch
from
August 29, 2026 05:42
ca0f7a7 to
0580150
Compare
IgorShevchik
pushed a commit
that referenced
this pull request
Aug 30, 2026
A routine sync check turned up two drifts in `.sync/nuxt-ui.json` that no guard could see, because both are only visible when the whole file is tallied rather than diffed one entry at a time. `decision` had two spellings for one verdict: 50 entries `no-op`, 14 `noop`, interleaved across the same period. That is not cosmetic — the ledger is queried by decision when answering "what did we skip, and why", and a query written against one spelling silently omits the rest. The 14 are normalised, and §6 step 4 now writes the vocabulary down as closed: `port`, `no-op`, `skip`, `n/a`. `pr` was a number in all 277 older entries and a string in exactly the three #511 added, which is this session's own error; `vue-tsc` caught it the moment the file was typed at all. Those three are now numbers. `b24ui_sha` splits the same way — 155 abbreviated, 125 full — and is left split on purpose: both resolve under `git show`, which is the field's only use, so the guard checks for a value that resolves to *nothing* rather than for a uniformity worth 280 rows of diff. `test/utils/sync-ledger.spec.ts` holds all of it, plus the invariants that were unenforced either way: full-SHA keys, a `cursor` that is one of the processed commits, no entry still carrying `pending-merge`, and a non-empty `summary`. Ten mutations verified, each failing exactly one assertion. Two findings from the same audit are deliberately not fixed here and are recorded in PORTING.md: four entries at the very start of the ledger have no `.sync/log/<sha>.md`, predating the convention by one commit, and writing that reasoning now would be reconstruction rather than record.
IgorShevchik
added a commit
that referenced
this pull request
Aug 30, 2026
…pe (#515) A routine sync check turned up two drifts in `.sync/nuxt-ui.json` that no guard could see, because both are only visible when the whole file is tallied rather than diffed one entry at a time. `decision` had two spellings for one verdict: 50 entries `no-op`, 14 `noop`, interleaved across the same period. That is not cosmetic — the ledger is queried by decision when answering "what did we skip, and why", and a query written against one spelling silently omits the rest. The 14 are normalised, and §6 step 4 now writes the vocabulary down as closed: `port`, `no-op`, `skip`, `n/a`. `pr` was a number in all 277 older entries and a string in exactly the three #511 added; `vue-tsc` caught it the moment the file was typed at all. Those three are now numbers. `b24ui_sha` splits the same way — 155 abbreviated, 125 full — and is left split on purpose: both resolve under `git show`, which is the field's only use, so the guard checks for a value that resolves to nothing rather than for a uniformity worth 280 rows of diff. `test/utils/sync-ledger.spec.ts` holds all of it, plus the invariants that were unenforced either way: full-SHA keys, a `cursor` that is one of the processed commits, no entry still carrying `pending-merge`, and a non-empty `summary`. Ten mutations verified, each failing exactly one assertion.
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 #509.
.sync/PORTING.mdhas the ledger entry written in the same commit as the port, which meansprandb24ui_shacannot be known yet — they go in aspending-mergeand are reconciled once the PR squash-merges. #509 merged as7203420b, so the three entries it recorded now point at it:a494a97d—fix(Form): omit method attribute on nested formspending-merge509/7203420b3d2de0ce—fix(Slider): emit a number for a single thumbpending-merge509/7203420bae243116—docs: refactor with nuxt-agent-discovery modulepending-merge509/7203420bScope
Six lines in
.sync/nuxt-ui.json, nothing else. No entry is added,cursordoes not move, nodecisionorsummarychanges, and no.sync/log/*.mdfile is touched — those never carried the placeholder.grep -rn pending-merge .sync/is now empty, which is the state the ledger is supposed to be in between ports.Verification
test/utils/commit-parses.spec.tsandtest/utils/dep-parity.spec.ts— the two suites that read this file — pass: 90 tests, 2 files.Generated by Claude Code