docs: make controlled-alpha onboarding executable - #62
Merged
Conversation
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
Why
The controlled-alpha image was publicly pullable, but a newcomer still had to invent PostgreSQL wiring, runtime configuration, the first API call, and the recovery exercise. Existing scenario articles demonstrate use cases but do not provide an executable onboarding path.
Impact
A user with Docker can now complete a deterministic durable Run without local Node.js, BytePlus credentials, or model spend. The same Compose path is exercised against each release candidate in CI. Kertas integration remains limited to the versioned public API and event protocol.
Verification
Fixes #61