docs(cli): sync from Docs-dev main — 0.7.0 wave - #64
Open
fyZhang66 wants to merge 1 commit into
Open
Conversation
…rkspace keys, api-key corrections)
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.
Phase 5 mirror for the 2026-08 wave (CLI v0.7.0 is live on npm). Exact-tree commit built with commit-tree on the prod parent — judge by TREE, not git log (mirror commits are never ancestors). Drift check done: zero prod-only content, zero deletions; 11 files updated from Docs-dev authoring (GitHub-native CI output section, workspace-key docs, api-key mint/expiry corrections). After merge, verify prod tree == Docs-dev main tree. Note: schedule/testlist portal pages do NOT exist yet on Docs-dev — separate authoring follow-up, not blocked by this mirror.