Fix Windows SQLite lifecycle for deterministic qualification - #115
Merged
blackmore-technology-group merged 2 commits intoOct 1, 2026
Merged
Conversation
blackmore-technology-group
deleted the
remediation/btdu-sqlite-lifecycle-20261001
branch
October 1, 2026 15:06
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
Closes SQLite handles deterministically across BTDU, profiles, global infrastructure, passports, provenance and rights stores so Windows qualification can clean temporary databases without WinError 32 file-lock teardown failures.
Evidence
This is resource-lifecycle hardening. It does not change protocol origin, authority, rights, settlement semantics, economic entitlement, or the immutable v3.4.3 tag.