Repository navigation
Bind the remaining provider launches to the selected-account lifecycle - #792
Merged
Merged
Conversation
Stacked on #776 (closed launch lifecycle custody); it is retargeted to main once #776 merges. Second slice of #725. - Bind Grok runs to the selected-account launch lifecycle before the adapter declaration and credential capability are constructed. - Carry admission expiry through process setup and record reference-only lifecycle metadata. - Finalize from confirmed runner outcomes; setup timeouts and tee conflicts are pre-release refusals that release the account, while an unknown child exit keeps custody. - Hold the outer selected-use lease through report teardown. Tests use synthetic material and deterministic child barriers only. Other root providers and the optional catalog lifecycle integration follow separately. Validation: formatting and 18 exact Linux tests passed; Clippy and the full suites run in CI.
Stacked on #787 (desktop launches through the service operation); it is retargeted to main once #787 merges. Final slice of #720. - While a selected account is in use (a held use lease or a service-owned launch operation), operators can change the future selection and modify other accounts of the same provider. - The exact in-use account incarnation stays protected from replacement, deletion and credential changes until its lease ends; unknown lease state fails closed. - Admitted runs no longer require the frozen binding to remain the current selection: once the lease is held, the provider verifiers recheck only that the frozen incarnation is still complete and unreplaced, so a future selection never affects the running child. Validation: formatting, the core and root-crate exact tests and Clippy for both crates passed on Linux; desktop-feature builds and platform suites run in CI.
Meta-Develop
changed the base branch from
codex/secret-lifecycle-executor-20261030
to
main
October 29, 2026 23:44
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.
Stacked on #785 (Grok launches bound to the selected-account lifecycle); it also merges #790 (future selection changes while an account is in use), whose provider verifiers it touches. It is retargeted to main once #785 merges.
Final slice of #725.
Tests use synthetic material and deterministic child barriers only.
Validation: formatting, 52 exact root tests and 4 account manager tests, the whole external-agent and account-authority test modules and Clippy passed on Linux; other platforms run in CI.
Closes #725.