@toloka-platform/sdk 0.1.0 → 0.2.0-preview.2

package/dist/cli/toloka.js.jsc.sha256

@@ -1 +1 @@
-b3ff8750d4254e81d4dccbba6db162057e702b7b823d76d6adc2e6b122212251  toloka.js.jsc
+4bc560d638ddf49386ccbb12f7eeaaa0922fd26ab13c69065cbb8540c27cbe50  toloka.js.jsc

package/dist/cli/toloka.js.sha256

@@ -1 +1 @@
-122b2c1f1afe960176a8f8f5557f847da14ed454809f44d8ed4a5212be6ace2a  toloka.js
+e7e688bae427a1230ea0cbcacf81224527dc592f0e9087d584462d5ab3ec2059  toloka.js

package/docs/cli-v2.md

@@ -64,7 +64,7 @@ Highest wins:
 2. `TOLOKA_PROJECT_ID` (keep accepting `POTATO_PROJECT_ID` until we rename the rest of the env surface)
 3. `toloka.json` in the discovered checkout (walk up from cwd, or `--source-root`)
 4. `current` in the machine registry
-5. Fail: `No project selected. Run toloka project add, or cd into a checkout.`
+5. Fail: `No project selected. Run toloka project create for a new project, toloka project add for an existing project, or cd into a checkout.`
 
 A checkout wins over the machine default so a repo is self-describing for agents and CI. Flags and env still win over both, same as PostHog (`POSTHOG_CLI_PROJECT_ID`) and Windmill (`--workspace`).
 

package/docs/cli.md

@@ -88,6 +88,8 @@ toloka project untrack <pipeline|dataset> <name> [--confirm]
 
 `project untrack` removes one pipeline or dataset binding from `toloka.json` without deleting the live resource. It previews the name and id in a terminal; outside a terminal, pass `--confirm` after reviewing the state file.
 
+`list` prints `CURRENT`, `ID`, `NAME`, and `ALIAS` columns. `*` marks the selected project and `-` marks an unselected project or missing alias.
+
 `url` fetches the selected project to resolve its team and prints only its platform UI URL to stdout, making the output safe to capture in scripts and agent workflows.
 
 ## login
@@ -199,7 +201,7 @@ Runs the complete Local Check Gate, then makes the platform match source.
 toloka apply
 ```
 
-Checks run before credentials are resolved or any platform request is made. A failed or missing required check exits `1`; a checker infrastructure error exits `2`. After a pass, the preflight refuses before any write when a pipeline or dataset is removed from source, a project secret is missing, or a dataset field schema conflicts. On success it prints `No changes.` or `Applied N writes to project <projectId>.`
+Checks run before credentials are resolved or any platform request is made. A failed or missing required check exits `1`; a checker infrastructure error exits `2`. After a pass, the preflight refuses before any write when a pipeline or dataset is removed from source, a project secret is missing, or a dataset field schema conflicts. On success it prints `No changes.` or reports both the number of approved planned changes and the lower-level platform writes used to apply them.
 
 ## secret set
 

package/docs/getting-started.md

@@ -37,7 +37,7 @@ CI does not need `login`. Set `POTATO_API_KEY` and the stored file is ignored. S
 
 ## Start with an agent
 
-For a guided first run, start a fresh coding-agent session and ask it to follow `https://platform.toloka.ai/onboarding.md`. The guide takes the agent through installation, credentials, project selection, local tests, plan approval, apply, cost review, and a bounded sample run.
+For a guided first run, start a fresh coding-agent session and ask it to follow `https://platform.toloka.ai/agents/data-labeling.md`. The guide takes the agent through installation, credentials, project selection, local tests, plan approval, apply, cost review, and a bounded sample run.
 
 Initialize the current directory and install the Agent Bootstrap. No platform project needs to be selected yet.
 

package/docs/limitations.md

@@ -2,7 +2,7 @@
 
 What this Beta SDK does not do yet, stated plainly so you can decide what to depend on.
 
-`@toloka-platform/sdk` is `0.1.0`. This is a Beta: the authoring API, the CLI surface, and the generated source layout can change before general availability. Pin an exact version. Do not depend on this in production yet.
+`@toloka-platform/sdk` is `0.2.0-preview.2`. This is a Beta: the authoring API, the CLI surface, and the generated source layout can change before general availability. Pin an exact version. Do not depend on this in production yet.
 
 ## Local checks do not certify deployability
 
@@ -15,7 +15,7 @@ What this Beta SDK does not do yet, stated plainly so you can decide what to dep
 | Training course content, when Training is enabled | platform validation  | nothing                |
 | labeler UI validation receipt                     | platform validation  | nothing                |
 
-The typed client can list, start, and poll Remote Node Checks. `toloka check` does not start them: it validates the authored source and its local tests. A `not_ran_node_check` result from `toloka validate` describes remote state, not missing local evidence.
+The typed client can list, start, and poll Remote Node Checks. `toloka check` does not start them: it validates the authored source and its local tests. A `not_ran_node_check` result from `toloka validate` describes remote state rather than missing local evidence. Its severity is check-specific: lint checks report a blocking error, while other checks can report a warning.
 
 Python code nodes have executable behavior checks but no useful static Python typecheck yet. Their generated `Inputs` and `Outputs` aliases are currently `dict[str, Any]`; adding Pyright or mypy before those aliases become field-derived `TypedDict` contracts would provide little protection.
 

package/docs/testing.md

@@ -112,4 +112,4 @@ File pickers, video upload/recording, and other hardware-backed fields cannot be
 
 ## Final gate
 
-`toloka check` loads every authored pipeline, runs the project TypeScript compiler, typechecks every Task UI against declarations bundled with the installed SDK, runs Vitest, and requires passing `test.code`, `test.ui`, and `test.pipeline` evidence. `missing`, `failed`, `partial`, and `infrastructure_error` are distinct blocking outcomes. `toloka apply` reruns this complete gate before resolving credentials or writing platform state. Platform source/spec errors from `toloka validate` remain separate; `not_ran_node_check` describes a Remote Node Check and does not replace local evidence.
+`toloka check` loads every authored pipeline, runs the project TypeScript compiler, typechecks every Task UI against declarations bundled with the installed SDK, runs Vitest, and requires passing `test.code`, `test.ui`, and `test.pipeline` evidence. `missing`, `failed`, `partial`, and `infrastructure_error` are distinct blocking outcomes. `toloka apply` reruns this complete gate before resolving credentials or writing platform state. Platform validation remains separate: a `not_ran_node_check` describes Remote Node Check state rather than missing local evidence, but lint checks report it as a blocking remote error while other checks can report it as a warning.

package/examples/face-image-collection/README.md

@@ -30,7 +30,7 @@ toloka plan
 # ~ Node changed in pipelines/face-image-collection: annotate_faces (...)
 
 toloka apply
-# Applied 1 write to project pp.0190abcd-abcd-7abc-8abc-abcdefabcdef.
+# Applied 1 planned change with 1 platform write to project pp.0190abcd-abcd-7abc-8abc-abcdefabcdef.
 ```
 
 `apply` creates the named dataset and missing required columns before it binds the pipeline. It never reconciles dataset items. Upload items explicitly as JSONL: