Fix account locks, proxy egress and Builder Event auto-claim - #12
Merged
Merged
Conversation
Recover abandoned account-store locks and expose CLI unlock. Strip ambient proxy settings and keep explicit CAPTCHA egress scoped to its own requests. Use current ZCode routes, client configs, app version and gateway error codes. Enable campaign auto-claim and prefer Builder Event tokens while continuing to poll for new campaigns. Remove unused prompt and test artifacts, and clean up private audit references in comments.
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.
Fix abandoned account-store locks and expose
accounts unlock. Strip ambient proxy settings from managed processes and scope explicit CAPTCHA proxies to CAPTCHA requests. Update routing, public client config requests, app version and gateway error codes to the current ZCode source.Enable campaign auto-claim by default and prefer Builder Event token plans. Keep polling for new campaigns while an earlier plan is held. Stop the scheduler during proxy shutdown. Remove unused prompt/test artifacts and private audit references from comments.
Closes #10
Closes #11
Validation: 164 focused proxy tests and 94 root integration/regression tests passed on the final tree. The full suites previously retained one IPv6-loopback timeout and one unavailable child-process start-time check in this environment. No live Builder Event claim was performed; support uses the kit's existing preview/claim API, which the current public ZCode source does not expose.