@toloka-platform/sdk 0.1.0-preview.5 → 0.1.0-preview.7

package/README.md

@@ -44,21 +44,16 @@ toloka init
 
 ## Install
 
-The package is not published to npm yet. Install it from a checkout of this repository:
-
-```sh
-cd packages/sdk && bun link
-cd /path/to/your/project && bun link @toloka-platform/sdk
-```
-
-Once the hosted installer is deployed, install the bytecode-cached CLI and add the SDK to the project:
+Install the bytecode-cached CLI and add the Preview SDK to the project:
 
 ```sh
 curl -fsSL https://platform.toloka.ai/cli/install.sh | sh
 bun add @toloka-platform/sdk@preview
 ```
 
-The installer requires Bun 1.4.0, installs `@toloka-platform/sdk` globally, and exposes `toloka` through Bun's global binary directory. The published CLI includes matching precompiled bytecode. The project install makes SDK imports resolvable.
+The installer requires Bun 1.4.0, installs `@toloka-platform/sdk` globally, and exposes `toloka` through Bun's global binary directory. The project install makes SDK imports resolvable.
+
+For a guided first run, start a fresh coding-agent session and ask it to follow the [agent onboarding guide](https://platform.toloka.ai/onboarding.md).
 
 ## Documentation
 
@@ -66,6 +61,7 @@ The installer requires Bun 1.4.0, installs `@toloka-platform/sdk` globally, and
 | -------------------------------------------- | ---------------------------------------------------------------------------- |
 | [Getting started](./docs/getting-started.md) | install, sign in, adopt an existing project or author a new one, first apply |
 | [Authoring](./docs/authoring.md)             | the typed graph API: fields, node constructors, ports, assembly, identity    |
+| [Testing](./docs/testing.md)                 | `toloka check`, typed node tests, Task UI scenarios, and pipeline flows      |
 | [Nodes](./docs/nodes.md)                     | which node to reach for, what lives inside a human-work node, pricing floors |
 | [Datasets](./docs/datasets.md)               | columns, immutable schemas, loading rows, what plan refuses                  |
 | [CLI](./docs/cli.md)                         | every command, flag, exit code, and the reconcile loop                       |
@@ -83,7 +79,7 @@ Each example is a complete project you can read end to end. See [examples](./exa
 
 ## How it works
 
-The CLI treats your source tree as the desired state. `toloka plan` reads the source, reads live platform state, and prints the difference. `toloka apply` makes the platform match. Running `plan` again should print `No changes.`
+The CLI treats your source tree as the desired state. `toloka check` runs project types, automatic Task UI types, and required typed node and pipeline-flow tests without platform credentials. `toloka plan` reads the checked source and live platform state and prints the difference. `toloka apply` reruns the complete local gate before making the platform match. Running `plan` again should print `No changes.`
 
 Identity lives in `toloka.json`, written when the CLI binds the directory to a platform project. It maps your source directories and dataset names to platform IDs so later runs reconcile the same resources instead of creating new ones. Do not hand-edit it.
 
@@ -94,7 +90,7 @@ Two rules the platform enforces and the SDK will not paper over:
 
 ## Agent support
 
-`toloka init` initializes the current directory with one managed `<toloka>` Agent Bootstrap block in `AGENTS.md` plus minimal pointers to it: a Claude skill at `.claude/skills/toloka-bootstrap/SKILL.md` and, when `.cursor/rules/` exists, an always-applied Cursor rule at `.cursor/rules/toloka-bootstrap.mdc`. It does not require a selected platform project. When one is already selected, it also writes `toloka.json`. Re-running it refreshes only SDK-owned content and removes only Toloka-generated legacy entry points. Then open your coding agent in that directory and ask it to create the project you need; the bootstrap directs the agent to `toloka --help` and the bundled Skill Catalog (`toloka skill search`, `toloka skill install`), and the installed skill guides project creation, authoring, validation, planning, and apply.
+`toloka init` initializes the current directory with one managed `<toloka>` Agent Bootstrap block in `AGENTS.md` plus minimal pointers to it: a Claude skill at `.claude/skills/toloka-bootstrap/SKILL.md` and, when `.cursor/rules/` exists, an always-applied Cursor rule at `.cursor/rules/toloka-bootstrap.mdc`. It does not bind a checkout from the machine registry's current project. Pass `--project-id`, set `TOLOKA_PROJECT_ID` / `POTATO_PROJECT_ID`, or run `toloka project create` first when `init` must write `toloka.json`. For an existing project, run `toloka import <projectId>` before `init`. Re-running `init` refreshes only SDK-owned content and removes only Toloka-generated legacy entry points. Then open your coding agent in that directory and ask it to create the project you need; the bootstrap directs the agent to `toloka --help`, skill discovery, and the installed skill.
 
 ## Agent evals