Repository navigation
test(workbook): qualify verified terminal persistence - #7
Open
rudycelekli wants to merge 1 commit into
Open
rudycelekli wants to merge 1 commit into
rudycelekli wants to merge 1 commit into
Conversation
Signed-off-by: Rudy Celekli <47457359+rudycelekli@users.noreply.github.com>
3 of 4 tasks
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
Persist terminal workbook cell outcomes before the worker-owned ORM session closes. False conditions and missing AI/research prompts now commit their existing receipt and row status after the existing run fence, preventing old COMPLETE values from surviving into later hydration.
This owned-fork PR runs the unchanged four-job qualification workflow for the candidate.
Verification
Boundaries
Only terminal result durability changes. Existing condition evaluation, terminal statuses and run-state checks are preserved. No HTTP authentication, tenancy, provider authorization or model/network behavior is claimed by the local SQLite proof. Hosted PostgreSQL/frontend qualification passed on this replacement commit.
Checklist
Signature correction
The prior owned-fork validation PR #5 used a DCO-signed commit without a cryptographic signature. This replacement uses explicit SSH signing; GitHub commit verification is
verified=true, reasonvalid, on84735689b1af0e7911a293ae20a8c8d996920813. 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
84735689b1af0e7911a293ae20a8c8d996920813: backend SQLite 2,105 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.