docs: sync from Docs-dev main — workspaces, API-key model, CLI 0.6.0 surface - #62
Open
zeshi-du wants to merge 1 commit into
Open
docs: sync from Docs-dev main — workspaces, API-key model, CLI 0.6.0 surface#62zeshi-du wants to merge 1 commit into
zeshi-du wants to merge 1 commit into
Conversation
….6.0 surface Mirrors the four Docs-dev PRs that landed after sync #61 was merged: workspace/API-key documentation (#29), CI-CD reachability and CLI path (#27), GitHub-native CI output (#30), and rerun pricing on V3 (#28). 11 files, one of them new (web-portal/admin/workspaces.mdx). After this commit the tree matches Docs-dev main exactly — verified with `git diff docsdev/main HEAD` returning empty.
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.
Sync #61 was merged at 2026-08-13T01:49Z, but Docs-dev
mainmoved again at 05:00Z. This closes that gap — 11 files, 1 new page.Why it matters
The public portal is currently missing the docs for things that already shipped:
web-portal/admin/workspaces.mdxdoes not exist publicly at all (new page). There is no published explanation of what a workspace is, personal vs. shared, or which balance work draws on.web-portal/admin/api-keys.mdxstill documents the old single-kind key model. The published page does not mention thatsk-user-personal keys can no longer be minted and that every key created today is ask-member-workspace key bound to the workspace whose page minted it — which is the first thing a user hits when they create a key and it behaves differently than the page says.@testsprite/testsprite-cli@0.6.0:cli/concepts/key-terms.mdx,cli/core/authentication.mdx,cli/getting-started/installation.mdx,cli/integrations/ci-cd.mdx.What is in it
Mirrors four Docs-dev PRs that landed after #61: workspace/API-key documentation (#29), CI-CD reachability and CLI path (#27), GitHub-native CI output (#30), rerun pricing on V3 (#28).
Verification
git diff docsdev/main HEADis empty — the branch tree matches Docs-devmainexactly.sk-user-abcd1234efgh5678ijklinide-configuration-issues.mdxis a placeholder inside a config example, and theamazonaws.comURL indocs.jsonis the existing public font asset.