Repository navigation
docs: align HTTP client examples with unified deployment commands - #27
Merged
Merged
Conversation
anycodes
marked this pull request as ready for review
November 11, 2026 01:05
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 README now shows how to deploy, inspect and delete the application used by this HTTP client. It makes the client's existing HTTP scope clear and does not add a cloud lifecycle SDK or another facade.
Validation: both README languages and owner records checked for local links; no implementation or dependency changes. CHANGELOG and
.agents/evidence/verify/2026-11-10-canonical-cli-guidance.mdrecord the documentation scope.Draft pending the coordinated CLI command delivery and repository CI.
Coordination: Alibaba-Agent-Sandbox/agent-sandbox#244. CLI examples explicitly require the current source CLI; no package release is claimed.
Source integration decision — 2026-11-11
The maintainer explicitly requested that the already-pushed content be merged into main now, ahead of the remaining acceptance work. This supersedes the earlier Draft hold for source integration only. It does not assert completion of unrun cloud acceptance, resolve all coordinated issues, qualify changed template identities, or authorize npm/PyPI releases. Historical evidence remains unchanged.
Current reviewed head:
9d965869cfef670e9c8118ccce42f6271712df5c. Exact-head CI is green.Normal GitHub merge is used with the expected head SHA. Repository main has no active branch rules or required review requests. Retain open acceptance issues and the documented gaps; source merge is separate from release and full validation.