First 15 minutes

This walkthrough is a release-candidate checklist. It cannot yet be completed using only published packages: dartstream_client 0.3.3 is not yet published. CLI ds_dartstream 0.0.11 is published; backend beta acceptance remains open.

  1. Sign up in the DartStream dashboard and select your workspace.

  2. Create a project. Feature flags and experience belong to that project; database, storage and streaming are workspace-shared.

  3. Create a machine credential for that project with flags:read; copy the one-time secret into your trusted server’s secret storage.

  4. After SDK 0.3.3 is published, create a clean Dart console directory and add dartstream_client: 0.3.3 to its dependencies.

  5. Set the three required server variables in SDK setup and run that complete Dart example against development.

  6. Compare the returned project flag count with the selected project’s Feature Flags page. An empty project legitimately returns no flags.

  7. For CLI initialization, follow Phase 1. For a public game, use trusted backend mediation; never put the machine secret into the game.

Credentials

The intended limit is 10 active credentials per workspace, shared by CLI and app credentials. Revoking frees a slot, disabling does not. Expired credentials stop counting with the #152 backend fix. This behavior requires that fix to be deployed; do not infer it from these candidate docs. Never publish a copied credential or record it in screenshots, source control or test output.

Acceptance before public beta

Run this walkthrough in a clean directory with the actually published SDK/CLI versions and the exact deployed backend build. Development gets a docs preview; https://docs.dartstream.io is updated only by the normal main release. Record those versions and the preview URL on #152. A successful docs build does not establish live user acceptance.