Repository navigation
Unify qBtGuard protection with tested opt-in enforcement and quiet logging - #1
Merged
Merged
Conversation
mc4bbs
changed the title
mc4bbs
marked this pull request as ready for review
October 19, 2026 13:15
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.
Replace overlapping Windows audit/protection engines with one PowerShell 5.1 engine for prohibited-extension and extensionless inspection, completed MKV header checks, configurable PIA recovery, forwarded-port synchronization and VPN/binding-gated restart. Installation defaults to audit mode and corrective policies remain opt-in. Add a shared action gate, bounded API/native calls, cooldown state, installation lock, scoped fixture targeting and quiet calendar-cutoff heartbeat.
Validation: engine f9fc69e passed Windows syntax checks and 84 Pester 3.4.0 tests (0 failed/skipped/pending) in CI and on the pilot machine. Live tests exercised restart, port synchronization, revised unattended recovery and scoped torrent/data deletion for prohibited-extension, extensionless and invalid-MKV fixtures. Fixture files were independently checked absent. The pilot cut over to a single task October 15; the October 19 check showed a recent successful task result, expected future schedule, both legacy tasks disabled and successful heartbeats without recorded errors/findings. See QA.md for exact evidence and limitations.
Current finalization commit changes documentation only. The installed engine remains unchanged. The pilot keeps invalid-MKV deletion disabled. MKV checks validate headers, not full video integrity. Quiet logging does not establish every intervening task succeeded. Clean-machine and other-version portability remain unverified; defaults remain conservative. Personal configuration, credentials, task exports and logs are excluded.
Rollback installation/task backups are retained privately. Local retirement of legacy tasks/files is pending a final path and ownership inventory.