Repository navigation
(4/8) fix(setup): atomic policy writes, unique preinstall temps, cheap status polls - #144
Merged
Merged
Conversation
…us polls Policy and update-state writes now go through a unique temp file plus rename, so a power loss or concurrent POSTs from two tabs can never leave a torn file that the catch-all reader turns into defaults (silently disabling schedules). Preinstall records get the same random-suffix plus wx treatment, so overlapping writers no longer interleave JSON and trigger redundant reinstalls. The harness status() read defaults to cheap (no CLI probes); authenticated verdicts refresh in the background on a 15-minute TTL and after mutations.
Contributor
Author
This was referenced Nov 14, 2026
Merged
Merged
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.
Auto-update policy and preinstall records now use unique temporary files and atomic replacement, so overlapping writes or an interrupted write cannot leave torn JSON that silently disables schedules or repeats installs.
Status polling reads current local installation, lifecycle and native connection settings. Expensive authentication probes are cached for 15 minutes, refreshed after Setup mutations, and made due when an installation or credential source changes locally. A warm cache no longer hides a switch between T3 Code's own Codex connection and its managed CLI sign-in.
Cached sign-in verdicts stay tied to the same executable, version and credential surface. An inconclusive probe for a new installation cannot reuse the old installation's signed-in verdict. Slow local reads retain the last known snapshot with a stale flag and diagnostics, within the existing request budget.
Validation:
git diff --checkare clean.Original reliability and polling improvements contributed by @0libote; maintainer review fixes preserve fresh local facts between authentication checks.