Repository navigation
Conversation
ancongui
marked this pull request as ready for review
October 3, 2026 21:00
This branch has not been deployed
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.
Operators can now register existing container destinations, inspect current resources, review and approve immutable deployment plans, and apply them through an outbound runner. Studio and the CLI share the scoped API; provider credentials and component/image limits remain at the destination. Docker Compose supports trusted-template deployment; Kubernetes and Azure Container Apps support bounded changes to existing resources. Cluster provisioning remains external.
Worker controls now show dated presence, active leases, and available capacity, and support revision-checked drain/resume without revoking active work. Deployment jobs use renewable fenced leases, current authorization, exact revisions, and explicit reconciliation for uncertain provider outcomes. Studio includes target and deployment wizards, mobile layouts, and manual recovery of uncertain requests without duplicate application.
Adds migrations
0029_deploymentsand0030_worker_presence, API/SDK/CLI contracts, an illustrated runner/deployment guide, and alpha12 package metadata. Existing workflow roles do not acquire infrastructure authority; API/scheduler remains a singleton.Validation: all 17 normal release gates passed on Python 3.12, including 3,562 core unit/contract tests, 56 Agentic tests, 29 Files tests, lint/types/docs, package builds, and clean installed artifacts. Studio has 626 unit tests and focused desktop/mobile interaction coverage; the complete browser suite and real-backend release gates are still running. Owned Studio → API → runner → Docker acceptance, Kubernetes conditional-update acceptance, all three CLI setup paths, and Azure read-only observation passed. Live Azure mutation acceptance is not claimed by this PR.