Fix persistent priority reversion after process startup

[PrimeBuild-pc]

Root cause

ThreadPilot treated a completed CPU-priority write as success without verifying that the process still reported the requested priority. Processes that reset their own priority shortly after startup could therefore end at Normal while Activity Log reported a successful persistent-rule apply.

Fix

The persistent-rule lifecycle is now:

apply → immediate verify → delayed verification → detect revert → one retry → final verify

• Verifies the OS-observed priority after the initial write.
• Detects a post-start reversion with two bounded delayed checks.
• Allows at most one retry per PID and rule signature.
• Cancels pending retry state and clears runtime keys when the process exits.
• Skips retry for exited, access-denied, or protected processes.
• Adds no continuous polling and no executable-specific behavior.
• Attributes internal priority writes and logs initial apply, verification, reversion, retry, final verification, and failure separately.

Automated validation

• dotnet clean ThreadPilot_1.sln
• dotnet restore ThreadPilot_1.sln
• dotnet build ThreadPilot_1.sln --configuration Release --no-restore
• Official test command with coverage: 555 passed, 0 failed
• Release build: 0 warnings, 0 errors

Real-world validation

A private diagnostic build was tested by the reporting user against a real process that resets priority shortly after startup. The logs confirmed initial High, reversion to Normal, exactly one scheduled retry, successful retry verification as High, and a final stable High priority. The implementation is general and contains no RimWorld-, Unity-, or Steam-specific logic.

Fixes #32

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

❌ Patch coverage is 70.49608% with 113 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
...vices/PersistentRulePriorityVerificationService.cs	62.25%	59 Missing and 18 partials ⚠️
Services/ProcessService.cs	11.11%	16 Missing ⚠️
Services/PersistentProcessRuleJsonStore.cs	30.76%	3 Missing and 6 partials ⚠️
Services/PersistentRuleAutoApplyService.cs	88.70%	3 Missing and 4 partials ⚠️
Services/PersistentRulesEngine.cs	97.18%	0 Missing and 2 partials ⚠️
Services/PersistentRuleRuntimeKeys.cs	75.00%	0 Missing and 1 partial ⚠️
ViewModels/ProcessViewModel.Behaviors.partial.cs	50.00%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!

[Focaccina-Ripiena37]

Reviewed the bounded retry lifecycle, cancellation, protected/exited-process guards, write attribution, release metadata, and automated validation.