Repository navigation
Conversation
6 tasks done
This was referenced Nov 15, 2026
- Regenerate Browser/React/Vue/Node guides from restructured source READMEs: shared task-based outline, implementation internals removed, toolbar and CSP guidance restored. - Lead the migration guide with a summary of what changes. - Rewrite v1-shaped and spec-like prose in handbook pages and guides. - Keep the v1 footer on SDK and Next.js pages only; surface the upgrade guide at the top of the SDK overview. - Shorten the scope line to "This page covers SDK v2." and fix bootstrap and event anchors. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Preview
Open the latest GitBook preview
Summary
Use ordinary pages, not GitBook variants:
supported-languages/...URLs.legacy/v1/, rendered by GitBook aslegacy-sdks/v1/....@2commands and upgrade compatibility details are confined to the migration guide.@1; Native keeps links to its supported v1 contracts.sdk/...copies, reference anchors, package/major ownership, deterministic imports and provenance manifests are preserved. Source/version records stay in manifests only; neither current nor legacy SDK pages display generation/provenance notices.gitbook-docs.yaml, live settings/defaults and pre-existing draft spaces are unchanged. This fresh PR supersedes the variants approach in #30; it does not configure a native version picker.Canonical SDK sources
SDK READMEs/source comments in
reflagcom/javascriptremain authoritative. The first-time-reader edits are in small, docs-only source PRs, stacked on the respective v2 feature branches:Merge those source edits into the SDK branches before releasing, so subsequent regeneration retains the first-time-reader wording. The site-only scope line and legacy links are added by the docs importer after copying, based on the package major; every sync reapplies them without changing the source READMEs. No runtime code, package versions or feature-branch working trees were changed.
b4fe5b3d9386b87c6546175c323862d9878e1430ed0e7725719756855c20e939265713914e956b8b81297fbca156feadd3e666188f5141f42e0488ddVerification
import --check) from clean pinned source checkouts; v1/Native output and site configuration unchanged00dd0b4) passed all checks3d3b61e) passed all checks42cf05d): navigation/isolation, all three source rebuilds, matching-SDK example compilation and all GitBook statuses passc35d60b) running for the one-sentence MCP wording update42cf05d(links/layout unchanged by the latest sentence update): cleaned-up prose, both examples, all ten heading targets, SDK-upgrade round trip to the migration section, and the MCP guide link. Removed an incompatible numbered-heading fragment after browser verificationed0e772, #80781297fb; #807's push run failed only in the test-report upload step and passed on rerun)bd9d10a, all four SDK guides, the React reference, Browser feedback and Next.js rendered exactly one scope line and one legacy footer, Migration was last in the rendered sidebar, and current↔legacy round trips workedRelease boundary / publishing
This remains a draft review preview, not permission to merge or publish. Current v2 sources have version
2.0.0-next.0; coordinate matching published SDK/CLI artifacts and required server changes before publishing these default-install pages. Prerelease availability is documented in the migration guide and source versions in manifests, rather than repeated notices on every page.Companion JavaScript #804 replaces whole-tree SDK docs deletion/copy with exact-tagged, actually-released-package imports. Land this docs importer before enabling that workflow. No release workflow was dispatched.
No main merge, SDK publication, deployment, snapshot rebuild or live GitBook setting change was performed.