Implement Stage 1 Container Hosting host, SDK and CLI support - #5893
Draft
cloutiertyler wants to merge 30 commits into
Draft
Implement Stage 1 Container Hosting host, SDK and CLI support#5893cloutiertyler wants to merge 30 commits into
cloutiertyler wants to merge 30 commits into
Conversation
This was referenced Sep 8, 2026
Preserve Stage 1 operation and shutdown ownership while combining complete environment publication with deployment commits. Generate and verify schema-bearing platform modules for container-only databases, and update the CLI and actual runtime regression coverage.
Keep ENV at Wasm10.6 and JS2.2 and authorization at Wasm10.7 and JS2.3. Preserve paired publication cursors, protected submissions, and positive host shutdown ownership. Keep Environment15 and Capabilities16 unchanged. Update the generated v2 system module authorization import and verify exact imports plus rejection of the old prototype namespace. Validated 101 focused publication, storage, lifecycle, CLI and actual host tests, generated-module execution, and strict scoped lint.
cloutiertyler
force-pushed
the
tyler/agent-hosting-proposal-stage-1
branch
from
September 12, 2026 01:18
e52244d to
5ace48e
Compare
cloutiertyler
force-pushed
the
tyler/v10-abi-extensions
branch
from
September 12, 2026 01:18
384c9c0 to
8a1b09e
Compare
cloutiertyler
force-pushed
the
tyler/v10-abi-extensions
branch
from
September 12, 2026 02:06
dee6d8d to
f8684bb
Compare
cloutiertyler
force-pushed
the
tyler/agent-hosting-proposal-stage-1
branch
from
September 12, 2026 02:06
ae9626a to
020fc9e
Compare
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.
Description of Changes
Adds the public host, SDK, and CLI support for Stage 1 Container Hosting: atomic publication, container-only databases, hosted credentials, generation fencing, environment snapshots, and database/container lifecycle integration. Supports local Dockerfile, Railpack, and prebuilt OCI builds. Adds Rust and Node credential discovery, a Node WebSocket transport, and managed credential renewal for Rust and Node connections. Environment-only updates use the publication coordinator; overrides, deletions, and replacement retain their original intent across retries.
Depends on #5892. Companions: private #3943 and website #1352. Stage 1 has no file-storage dependency or user-defined filesystem mounts.
API and ABI breaking changes
Adds container publication and authenticated hosted-client APIs. Uses the prerequisite V10 extensions; no V11 ABI.
Rollback safety impact
Requires #5892. Rollback must preserve deployment records and fence running containers before removing host support.
Expected complexity level and risk
5/5. Couples publication, credential authorization, database lifecycle, and container execution.
Testing
Publication, recovery, authorization, fencing, environment, OCI, and CLI tests. The SDK checkpoint passes 40 Rust and 55 Node tests, scoped lint, type checks, and package builds. The CLI passes 47 publication, image and frontend tests under a permissive umask, plus the protected-storage regression under umask 000. Persistent ENV propagation passes 65 focused tests, 39 deployment regressions, and scoped strict Clippy. Full container acceptance remains in progress.