Repository navigation
docs: use public server a2 in the example and CI - #16
Merged
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.
The documented local agent-loop setup and its real HTTP CI now install exact public agent-sandbox-server 0.4.0a2. Configuration export parity uses the matching release tag. Remove historical source-path setup from the current example instructions while preserving existing dated evidence.
Validation: fresh public Python a2 installation and pip check; npm run typecheck; all 24 npm tests; actual Node example health, command 4, exact downloaded file bytes and SIGTERM process exit; complete configuration-schema comparison. This validates local runtime integration and does not claim cloud lifecycle, model use or Node npm publication.
Requested as part of the coordinated current-release/examples cleanup. Repository decision and new point-in-time evidence are included; no Node runtime/API/package version changes.