Repository navigation
test(workbook): qualify verified complete migration - #6
Open
rudycelekli wants to merge 2 commits into
Open
rudycelekli wants to merge 2 commits into
rudycelekli wants to merge 2 commits into
Conversation
Signed-off-by: Rudy Celekli <47457359+rudycelekli@users.noreply.github.com>
3 tasks done
Signed-off-by: RudyCelekli <rudycelekli@gmail.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.
What & why
Snapshot every matching legacy lead during workbook migration. Read source pages of 500 and flush row batches of 50, then commit the complete snapshot and storage marker together. A later-page failure rolls back so retry can finish.
This owned-fork PR runs the existing four-job qualification workflow for the candidate.
Verification
Boundaries
No proof of a consistent snapshot while source leads change concurrently, or repair of previously completed partial migrations. HTTP auth, PostgreSQL and frontend qualification belong to the existing hosted workflow. The existing enrichment map retains its memory behavior.
Checklist
Signature correction
The prior owned-fork validation PR #4 used a DCO-signed commit without a cryptographic signature. This replacement uses explicit SSH signing; GitHub commit verification is
verified=true, reasonvalid, on8fd7c20d99f7c59a7d624f1e582dd3a444cf940f. Its complete Git tree and source/test/diff hashes match the previously reviewed patch. The prior receipts remain preserved; this PR reruns the unchanged full workflow on the verified head. No upstream publication.Hosted qualification
Unchanged four-job workflow passed at
8fd7c20d99f7c59a7d624f1e582dd3a444cf940f: backend SQLite 2,099 passed/134 skipped/3 deselected; PostgreSQL integrity and tenancy 18 passed; frontend lint/build and 63 Bun tests passed; mounted browser regressions 3 passed. GitHub verifies the commit signature as valid.