Conversation
weekwood
marked this pull request as ready for review
August 21, 2026 08:53
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.
Summary
lastUsedTimepersistence as best-effort so a valid token remains usable when profile storage is read-onlyRoot cause
Configstorereceived an empty defaults object, which rewrote the config during construction. In addition,ensureAuth()always persistedlastUsedTime. In sandboxed or otherwise read-only environments, either write failed and the CLI surfacedE1005, even though the stored token was valid.Verification
bun test— 186 passed, 0 failedbun run typecheckbun run buildzentao --versionand an authenticatedzentao story 326 --format=jsonboth reuse the existing token without another login