Repository navigation
Conversation
|
This was referenced Nov 18, 2026
harsh62
previously approved these changes
Nov 18, 2026
xyos
force-pushed
the
docs/readme-native-sdks
branch
from
November 18, 2026 22:50
ec9ca11 to
38ccfb7
Compare
xyos
force-pushed
the
docs/readme-native-sdks
branch
from
November 19, 2026 06:30
38ccfb7 to
9509fcc
Compare
… constructor and error tables The SDK README's `build.yaml` step showed a `spec:` option the builder does not read; it now says the builder applies itself, turns every `*.spec.json` into `*.blocks.dart`, and reads only `fail_on_collision` and `native_package_opt_out`. "Requirements" said Dart 3.3+ and Flutter "for the demo app"; the packages require Dart 3.11, only `blocks_runtime_flutter` needs Flutter (3.41+), and `example/` holds end-to-end tests, not a demo Flutter app. The "Using Auth" section had the same text in the SDK README and in the `blocks_runtime` README; it is kept in the `blocks_runtime` README, and the SDK README keeps the heading, six rules (one says what each platform passes to `signIn`, one that a sign-in ending without a redirect throws `OidcCancelledException`) and a link to it. The SDK README documents the generated `Blocks` constructor under "Configuration". "Errors" keeps the `BlocksException` table and states the name-matching, HTTP status and 401-retry rules as lists; it adds that a 401 without an `authProvider` is not retried, what a missing result throws for a method whose result is not nullable, and which errors an `OidcClient` throws outside the taxonomy. The `blocks_runtime` README documents the `BlocksClient` constructor, how to pass a `BlocksClient` to a generated API class (the generated `Blocks` takes none), the `OidcClient` members with their return types, and what each call throws: the four `OidcException` subclasses, `ApiException` and `TransportException` for `restore()`, `signOut()` and a token refresh, and the `StateError`, `ArgumentError`, `FormatException` and `TypeError` cases. The `blocks_codegen` README has a table of CLI flags and `build.yaml` options. For an Android emulator the SDK README said to rewrite `localhost` to `10.0.2.2`; it now says to forward the port with `adb reverse` first, because the identity provider's redirect URI is built from the base URL. The `blocks_runtime_flutter` README lists the three ways `FlutterBrowserLauncher` ends a sign-in with `OidcCancelledException` and says a desktop app calls `signIn` without a launcher. The example README says the backend has four `Auth` blocks, not three, lists `rest_tuple_params_test.dart`, no longer calls the OIDC suite local only, and says the suite also signs in through the loopback listener. "How it works", "What you get", "Project structure" and "How the codegen works" are removed from the SDK README; the typed OIDC provider details are in the `blocks_runtime` and `blocks_codegen` READMEs, which the SDK README links.
…EADME "Workflow After Codegen Changes" was the last section and repeated the command of each check; it is now the first section and links to the section that holds each command. The Swift and Kotlin compile checks were single paragraphs of more than 400 characters; each is now a list of what the check compiles, what it skips or treats as advisory, what it needs and which CI job runs it. The live `Auth` fixture check is a table of fixture, what it mirrors and what is compared, for fixtures 18, 23 and 37. The sentence saying `dart/` can hold `codegen-error.txt` is now part of the `dart/` entry in the structure list.
…ckend README for setup The Android and KMP example READMEs said to run `npm install`, `npm run dev` and `npm run spec` from `example/typescript/aws-blocks`, whose `package.json` has no such scripts; both now link to the backend README's "Running" section. Both also said there is no fake-user fallback for sign-in; they now name the two ways to sign in that the backend README documents, the stub IdP and a Google OAuth client. The KMP README said `App` constructs `Blocks()`; it constructs `Blocks` with `Blocks.defaultServer`, and the README says so. The SDK README drops a badge that said Kotlin 2.2.10 (the build uses 2.2.21), gains an "Errors" section for `ApiException`, `TransportException`, `ClientClosedException`, the four `OidcException` subclasses and `FileTransferException`, and splits "Generated types" into "Open records", "Unions" and "Names" with one rule per list item or table row. The backend README presents the stub IdP before the Google setup and states the `userId`-keyed table upgrade as one present-tense line under "Running".
…en the demo README The SDK README said the backend writes the `x-blocks-type-name` hint for a TypeScript type alias and referred to a pull request number and "an older backend"; it now states what the generator produces with and without the hint, and lists a name that isn't a Swift identifier as a third reason for a nested `Input` with a warning. The demo README told a reader with a physical device to deploy and "regenerate" without a command; it now names `BLOCKS_SPEC_STAGE=production npm run spec`, because plain `npm run spec` reads the dev server's configuration. `Blocks(server:session:tokenStore:)` is documented under "Configuration" as a table of parameters and defaults, followed by "Lifetime"; "Features" is now "Generated types" with one rule per list item; the launcher options are a table, and the errors `signIn` throws are a table of the eight `OIDCError` cases and `CancellationError`. The demo README replaces the four "Option" sections for code generation with the CLI command the demo uses, the two generated files the demo target compiles, and two list items: the Xcode command plugin run on the `BlocksDemo` project, and the build plugin with what the demo target needs for it. `swift package generate-code-from-blocks-spec` is no longer listed for the demo: from `native/swift/` it generates into the package's own test targets. An out-of-date per-file tree becomes two lines. The demo README's step 1 says the published `@aws-blocks/blocks` cannot build the backend until a release includes `Auth`, and how to run the backend against the checkout. The demo backend README says it is the backend of the Swift demo, lists `npm run spec` under "Commands" and states the docs pointer once. The "Lifetime" list says realtime channels and file transfers use sessions of their own, shared by every instance: realtime sockets have a `URLSession` separate from the one for file transfers. # Conflicts: # native/swift/Demo/README.md # native/swift/README.md
…en the demo README The SDK README said the backend writes the `x-blocks-type-name` hint for a TypeScript type alias and referred to a pull request number and "an older backend"; it now states what the generator produces with and without the hint, and lists a name that isn't a Swift identifier as a third reason for a nested `Input` with a warning. The demo README told a reader with a physical device to deploy and "regenerate" without a command; it now names `BLOCKS_SPEC_STAGE=production npm run spec`, because plain `npm run spec` reads the dev server's configuration. `Blocks(server:session:tokenStore:)` is documented under "Configuration" as a table of parameters and defaults, followed by "Lifetime"; "Features" is now "Generated types" with one rule per list item; the launcher options are a table, and the errors `signIn` throws are a table of the eight `OIDCError` cases and `CancellationError`. The demo README replaces the four "Option" sections for code generation with the CLI command the demo uses, the two generated files the demo target compiles, and two list items: the Xcode command plugin run on the `BlocksDemo` project, and the build plugin with what the demo target needs for it. `swift package generate-code-from-blocks-spec` is no longer listed for the demo: from `native/swift/` it generates into the package's own test targets. An out-of-date per-file tree becomes two lines. The demo README's step 1 says the published `@aws-blocks/blocks` cannot build the backend until a release includes `Auth`, and how to run the backend against the checkout. The demo backend README says it is the backend of the Swift demo, lists `npm run spec` under "Commands" and states the docs pointer once. The "Lifetime" list says realtime channels and file transfers use sessions of their own, shared by every instance: realtime sockets have a `URLSession` separate from the one for file transfers.
xyos
force-pushed
the
docs/readme-native-sdks
branch
from
November 19, 2026 14:25
9509fcc to
c8a5818
Compare
This branch has not been deployed
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.
Problem
The READMEs of the Dart, Kotlin and Swift SDKs had setup steps that do not work and long paragraphs that hold many rules each (48 prose lines over 400 characters in 13 files, 17 of them in
native/swift/README.md).native/dart/README.mdset aspec:option inbuild.yamlthat the builder does not read, and required Dart 3.3+ where the packages require 3.11.native/dart/README.mdand innative/dart/packages/blocks_runtime/README.md.npmscripts fromexample/typescript/aws-blocks, whosepackage.jsonhas none.BlocksorBlocksClient, or the return types and exceptions of theOidcClientmembers; the Kotlin README had no list of the exceptions a call throws.Issue #, if available:
Changes
Dart (
native/dart)README.md: the builder applies itself (packages/blocks_codegen/build.yaml:5-6) and reads onlyfail_on_collisionandnative_package_opt_out(packages/blocks_codegen/lib/builder.dart:9-15). Requirements are Dart 3.11+ (pubspec.yaml:9of both packages) and Flutter 3.41+ forblocks_runtime_flutteronly.example/is described as end-to-end tests, not a demo Flutter app.README.md: "Using Auth" is the heading, six rules (two of them fail without an error when skipped; one says what each platform passes tosignIn; one says a sign-in that ends without a redirect throwsOidcCancelledException) and a link to the same section of theblocks_runtimeREADME.README.md: new "Configuration" with the generatedBlocksconstructor (packages/blocks_codegen/lib/src/generator.dart:875,881). On an Android emulator it says to forward the port withadb reversefirst:rewriteLocalhostgives the identity provider a redirect URI on10.0.2.2, because the client builds it from the base URL (packages/blocks_runtime/lib/src/oidc_client.dart:223-235,517).README.md: "Errors" is a section of its own. It holds theBlocksExceptiontablemainhas (packages/blocks_runtime/lib/src/blocks_exception.dart:16-111), the rules for matching an error by name as a list, and the HTTP status and 401 retry rules as a list (packages/blocks_runtime/lib/src/blocks_client.dart:84-89,181-209). Two items are new: a 401 without anauthProvideris not retried, and a result that is missing for a method whose result is not nullable throws aTypeError, or aTransferableExceptionfor an unbound or declared native transferable (native/codegen-fixtures/17-transferables/dart/client.dart:59,27-declared-transferable-bindings/dart/client.dart:100,packages/blocks_runtime/lib/src/transferable_descriptor.dart:11-15). "How it works", "What you get", "Project structure" and "How the codegen works" are removed; the typed OIDC sample is in theblocks_runtimeREADME, which is linked.packages/blocks_runtime/README.md: "Using Auth" keeps the sample and rules it has onmain, "Federated sign-in on each platform" included; its two opening paragraphs are lists, and thesignOut()rule lists its four outcomes as sub-items. NewBlocksClientconstructor table (lib/src/blocks_client.dart:32-40,109-121) and a sample that passes aBlocksClientto a generated API class, because the generatedBlockstakes none (packages/blocks_codegen/lib/src/generator.dart:875-892). New "OidcClient" section: a member table with return types (lib/src/oidc_client.dart:77,153,159,259,308,432,650,866,986) and anOidcExceptiontable of four rows (lib/src/oidc_exception.dart:13-44).restore(),signOut()and a token refresh throwApiExceptionandTransportException(lib/src/oidc_client.dart:797-808,887-894,1011-1055), which the list above the table says.packages/blocks_codegen/README.md: table of CLI flags andbuild.yamloptions (bin/blocks_codegen.dart:9-32); the arm-naming rules are a list.packages/blocks_runtime_flutter/README.md: the paragraph on howFlutterBrowserLauncherends a sign-in is a list of its three cases (lib/src/flutter_browser_launcher.dart:87-96,102-107,123-132), and one list item says a desktop app callssignInwithout a launcher.example/README.md: fourAuthblocks, not three (test-apps/native-bindings/aws-blocks/index.ts:65,77,109,138); the suite list gainsrest_tuple_params_test.dart(bin/e2e_test.dart:28); the OIDC suite is not local only (bin/e2e/oidc_test.dart:141) and also signs in through the loopback listener (bin/e2e/oidc_test.dart:341).Fixtures (
native/codegen-fixtures/README.md): "Workflow After Codegen Changes" is first and links to each check; the Swift and Kotlin compile checks are lists; the liveAuthcheck is a table; thecodegen-error.txtsentence is part of thedart/list entry.Kotlin (
native/kotlin)README.md: the Kotlin 2.2.10 badge is removed (gradle/libs.versions.toml:3is 2.2.21). New "Errors" table:ApiException,TransportExceptionandClientClosedExceptionfromruntime/src/commonMain/kotlin/com/aws/blocks/kotlin/BlocksClient.kt:55,70-136and the generated null-result guard (codegen/src/main/java/com/aws/blocks/kotlin/generator/KotlinCodeGenerator.kt:1964-1971); the fourOidcExceptionsubclasses (runtime/src/commonMain/kotlin/com/aws/blocks/kotlin/oidc/OidcException.kt:5-17) andFileTransferException(runtime/src/commonMain/kotlin/com/aws/blocks/kotlin/exceptions/FileTransferException.kt:13). "Generated types" is split into "Open records", "Unions" and "Names". "Support by Target" is one sentence.example/android/README.md,example/kmp/README.md: "Prerequisites" links to the backend README's "Running" section (the scripts are inexample/typescript/package.json:12-37). Sign-in names the stub IdP and a Google OAuth client. KMP:AppconstructsBlockswithBlocks.defaultServer(composeApp/src/commonMain/kotlin/com/aws/blocks/example/App.kt:40).example/typescript/README.md: the stub IdP comes before the Google setup; the upgrade note is one line under "Running". The sentence saying the published package cannot build the backend is kept as onmain.Swift (
native/swift)README.md:x-blocks-type-nameis described by what the generator reads (Sources/BlocksCodegen/CodegenModelBuilder.swift:274-287), without a pull request number.Blocks(server:session:tokenStore:)is a table under "Configuration" (Sources/BlocksCodegen/SwiftCodeGenerator+EntryPoint.swift:85-96,Sources/BlocksRuntime/BlocksClient.swift:59-80), followed by "Lifetime", which says realtime channels and file transfers use sessions of their own (Sources/BlocksRuntime/BlocksRuntimeSession.swift:13-34). "Features" is "Generated types" in seven sections; "Transferables" holdsmain's item on how a realtime subscription ends, unchanged. The launcher options are a table, and the errorssignInthrows are a table of the eightOIDCErrorcases andCancellationError(Sources/BlocksRuntime/OIDC/OIDCClient.swift:858-873). Comparisons with the other SDKs and statements about earlier releases are removed.Demo/README.md: step 1 says the published@aws-blocks/blockscannot build the backend until a release includesAuth, and lists the three steps that run it against a checkout of this repository. Step 4 keeps the CLI command, names the two files the demo target compiles, and has two list items: the Xcode command plugin run on theBlocksDemoproject (Plugins/BlocksCodegenCommandPlugin/Plugin.swift:96-113) and the build plugin with what the demo target needs for it.swift package generate-code-from-blocks-specis not listed for the demo: it covers the package's own targets (Plugin.swift:31). ThePackage.swiftsnippet is in the Swift README. A device needsBLOCKS_SPEC_STAGE=production npm run spec(packages/core/src/scripts/generate-spec.ts:1128-1130,packages/core/src/scripts/deploy.ts:385). The folder tree is two lines.Demo/typescript-demo/README.md: says what the backend is for; "Commands" gainsnpm run spec.native/codegen-fixtures/README.mdnative/dart/README.mdnative/dart/example/README.mdnative/dart/packages/blocks_codegen/README.mdnative/dart/packages/blocks_runtime/README.mdnative/dart/packages/blocks_runtime_flutter/README.mdnative/kotlin/README.mdnative/kotlin/example/android/README.mdnative/kotlin/example/kmp/README.mdnative/kotlin/example/typescript/README.mdnative/swift/Demo/README.mdnative/swift/Demo/typescript-demo/README.mdnative/swift/README.mdChangesets: one for
aws-blocks-kotlinand one foraws-blocks-swift, eachpatch. The Dart SDK has no changeset directory, and no package underpackages/changes, so there is no other changeset.Look hardest at:
native/dart/README.mdand tonative/dart/packages/blocks_runtime/README.md; feat(native-dart): sign in on desktop through a loopback listener #1499, feat(native-dart)!: let a sign-in browser launch be cancelled #1571 and feat(native-dart)!: one shared error taxonomy for the Dart client #1574 then edited both copies the same way. This change keeps it once, in the runtime README, and leaves in the SDK README the heading, six rules and a link to it. That reverses part of four merged changes, so a maintainer should confirm it; restoring the second copy is a one-file change.Blocks,BlocksClient,OidcClient,OidcException, codegen options): every cell is new text derived from the source. The member table leaves outrefresh(),getAccessToken()andonAuthFailure(). TheBlocksExceptiontable in "Errors" ismain's, unchanged.native/dart/README.mdkeepsmain's sentence "Every error the runtime throws is aBlocksException" and lists beside it the cases where that does not hold: aTypeErrorfrom the generated cast for a missing result (native/codegen-fixtures/41-void-methods/dart/client.dart:32), and theStateError,ArgumentError,FormatExceptionandTypeErroranOidcClientthrows (packages/blocks_runtime/lib/src/oidc_client.dart:358,445,468,599-601,719,726,736,packages/blocks_runtime/lib/src/loopback_session_io.dart:108-113).spec:option, every*.spec.jsonbecomes*.blocks.dart.native/swift/Demo/README.mdgoing from 132 to 97 lines: the Xcode steps for both plugins are derived from the plugin sources and the project file, and were not run in Xcode.native/swift/Demo/README.mdwere run onmainea7108832: withoutnpm installand with the link,npm run devserved the API on port 3001 andnpm run specwrote a spec with the local server. On that first start Vite, which serves the web frontend, logged a dependency-scan error for theaws-blockspackage, which the dev server generates the client for while starting.Not changed on purpose: the sample and the rules of "Using Auth" as they are on
main, and the two Flutter samples;build_runner: ^2.4.0and "Node.js 22+" in the Dart README; the version in the Swift quick start; "Xcode 26+"; the Kotlin "Requirements" list; the.changeset/README.mdandfixture-stubs/README.mdfiles.Open questions:
mainno source writesx-blocks-type-nameinto a spec; only the Swift generator reads it. fix(native-dart)!: one shared AuthActionInput for every Auth block #1599 makes core write it, and with the hint the generator marksAuthApi.SetAuthState.Inputdeprecated. Whichever of the two merges second switches the "UsingAuth" sample toAuthActionInput?.OidcClient.signInDirectreports a state mismatch as aStateError(oidc_client.dart:358). A 2xx answer of the authorize-params route that is not the expected JSON is aFormatExceptionor aTypeError(oidc_client.dart:599-601), although the doc comment ofsignInsays it is aTransportException(:430-431). A 2xx exchange answer whoseuseror tokens have the wrong type is aTypeError(:719,726,736). The README documents what the code does. The review's answer: the Kotlin client wraps these in itsOidcExceptionsubclasses with acause, and Dart doing the same is a runtime change;OidcCallbackExceptiontakes nocauseyet (oidc_exception.dart:36-38).mainsays every error the Dart runtime throws is aBlocksException, whilesignInandsignInDirectstill throwStateError(oidc_client.dart:358,445,468), asignInwithout a launcher throwsArgumentErrorfor an authorize URL that is neitherhttpsnorhttpon a loopback host (loopback_session_io.dart:108-113), andBlocksClient.callthrowsArgumentError(blocks_client.dart:74-80). The READMEs keep the sentence and list the exceptions.relayTo; the doc comment ofsignInrequires a custom-scheme URI (oidc_client.dart:407-408). Not changed.build_runnerfloor is^2.16.2.Answered in review, no change:
native/swift/README.mdpins.upToNextMinor(from: "0.2.0")while the newest tag of the Swift package is 0.1.1. 0.2.0 is the next release (31 pendingminorchangesets undernative/swift/.changeset), and the README documents what that release contains.native/swift/Demo/README.mdrequires Xcode 26+ whileswift-demo/project.ymlsaysxcodeVersion: "15.0". The README is right:native/swift/Package.swiftdeclaresswift-tools-version: 6.2. The value inproject.ymlis for a separate change.Changed after review:
main. The Swift demo README gains the same statement for its backend, which importsAuththe same way.OidcExceptionsubclasses andFileTransferException.TypeError, or aTransferableExceptionwhen the result is an unbound or declared native transferable. The other items the first review round asked for (no HTTP status check, anullresult for a gateway's own error body) are gone, becausemainnow checks the status and throws aTransportException.blocks_runtimeandblocks_runtime_flutterREADMEs: the statements that a sign-in the user backs out of does not complete are gone, because onmainFlutterBrowserLauncherthrowsOidcCancelledExceptionin that case andcancel:works with a launcher.OIDCErrorcase.XcodeCommandPluginextension (Plugins/BlocksCodegenCommandPlugin/Plugin.swift:96-113) that readsswift-demo/blocks.spec.jsonand writesswift-demo/Generated/, the two files the project compiles. The build plugin item says what the demo target needs.adb reversefirst on an Android emulator.blocks_runtimeREADME: the generatedBlockstakes no client.aws-blocks/index.ts".Auth" sample: unchanged, see the first open question.Carried from
main: six changes merged after this pull request was opened are applied to the revised text.mainchanged are redone onmain's text, and every error, cancellation and sign-in statement of the revision is checked again againstblocks_client.dart,blocks_exception.dart,transport.dart,oidc_client.dart,oidc_exception.dartandflutter_browser_launcher.dart.main's item is under "Transferables", unchanged, and the "Lifetime" line about realtime and file-transfer sessions follows the new source.kotlinx.serializationplugin line in the Kotlin quick start (fix(kotlin): document the kotlinx.serialization plugin requirement #1595) is kept..cdk-blocks-sandbox(refactor!: rename .blocks-sandbox to .cdk-blocks-sandbox, served path included #1644): five lines ofnative/kotlin/example/typescript/README.md.Related pull requests: this supersedes none. Open pull requests that touch the same files:
native/dart/README.md: docs: fix dart README.md dependencies #167, docs(native-dart): sample app that stays signed in across launches #1526, feat(native-dart)!: keep sessions across launches by default #1575, feat(native-dart)!: report how a realtime subscription ended, and keep it alive #1578native/dart/packages/blocks_runtime/README.md: fix(dart): time out stalled HTTP requests #1524, feat(dart): stream file uploads and downloads #1525, docs(native-dart): sample app that stays signed in across launches #1526, feat(dart): add a BlocksConfig configuration object #1527, feat(native-dart)!: keep sessions across launches by default #1575native/dart/packages/blocks_runtime_flutter/README.md: docs(native-dart): sample app that stays signed in across launches #1526, feat(native-dart)!: keep sessions across launches by default #1575native/dart/packages/blocks_codegen/README.md: docs(native-dart): sample app that stays signed in across launches #1526, feat(dart): add a BlocksConfig configuration object #1527, fix(native-dart): format generated clients #1631native/dart/example/README.md: docs(native-dart): sample app that stays signed in across launches #1526native/kotlin/README.md: refactor!: rename the scaffolded backend folder to cdk-blocks #1630native/kotlin/example/typescript/README.md: feat(core, blocks, hosting, create-blocks-app, admin-ui, bb-database)!: rename the hidden .blocks folder to .cdk-blocks and consolidate local data under it #1607, refactor!: rename the scaffolded backend folder to cdk-blocks #1630native/kotlin/example/android/README.md,native/kotlin/example/kmp/README.md: refactor!: rename the scaffolded backend folder to cdk-blocks #1630native/swift/README.md: fix(native-dart)!: one shared AuthActionInput for every Auth block #1599, refactor!: rename the scaffolded backend folder to cdk-blocks #1630native/swift/Demo/README.md,native/swift/Demo/typescript-demo/README.md: refactor!: rename the scaffolded backend folder to cdk-blocks #1630Whichever merges second rebases.
Part of a set of README revisions: #1635 (core), #1636 (hosting and pipeline), #1637 (bb-agent and bb-knowledge-base), #1638 (bb-auth and auth-common), #1639 (the storage blocks), #1640 (compute, jobs, realtime, email and observability), #1641 (the guide, the scaffolder and its templates), #1643 (contributor docs). Each merges on its own.
Validation
Run on this branch alone at
9509fcc60, onmain8940cfd2f, with Node 22. All pass:npm run buildpackages/blocks(readme-links,docs-pointers,doc-snippets,imports-reference)packages/blockssandbox-dir-coverage(no tracked file names the old directory.blocks-sandbox)packages/corereadme-policies(the IAM policy JSON)packages/bb-authreadme-recipes,first-admin,multi-block-snippets,users-cli,gate-diagnosticspackages/auth-commonui.react-typespackages/bb-kv-storereadme.generated(every README snippet compiled) andlegacy/runtimepackages/create-blocks-appnpm testnpm run sync-docs:checknpm run check:importschangeset-guard.ts validate-structurechangeset-guard.ts verify-coveragechangeset-guard.ts verify-umbrellachangeset-guard.ts block-major#anchorin the changed files, and every link into them from another Markdown file, resolves (checked with a script)Run once on all the README branches of this set combined, as they were on an earlier
maincommit (e1e484465), and not run again after the rebases:packages/coreunit suite,packages/blocksunit suite,packages/bb-kv-storeunit suite,packages/bb-authunit suite,packages/auth-commonunit suite,npm run lint,npm run lint:depsandnpm run check:api. All passed.Not run locally: the full
npm testacross all workspaces,npm run test:e2e:localand the sandbox e2e suites. CI runs them.No test was added: the tests listed above already read these READMEs, and the remaining statements are checked against the source by review.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.