@toloka-platform/sdk 0.1.0-preview.9 → 0.2.0-preview.1

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

@@ -1 +1 @@
-92bbe68b3e86c7e0a8d7d66dfc8277f682402c5513db4a58844ba6173975afd1  toloka.js.jsc
+19983b733a3e06f8b57ec971da718a2d169e6afe9c45a37ba02cf4a30a6bc6f1  toloka.js.jsc

package/dist/cli/toloka.js.sha256

@@ -1 +1 @@
-16b1b42414dbde194d20e05efb359538bae80906bba75e1af3e0b8638a82ec43  toloka.js
+e9731d96ceea4fa47b10bf5b846240437fe966e231929ed5f02a586aa886c22a  toloka.js

package/docs/authoring.md

@@ -37,19 +37,24 @@ The name is a bare identifier. When a field is a pipeline **input**, its name mu
 
 ## Node constructors
 
-Five constructors cover the whole palette. Each takes a name, a settings object, and optional `{ id }`.
+Four work-node constructors take a name, settings, and optional `{ id }`: `code`, `generation`, `quorum`, and `match`. `root` is the single pipeline boundary and takes only settings plus optional `{ id }`.
 
 ### root
 
 Defines the pipeline's input and output contract. `started` is what each item carries in from the dataset; `completed` is what gets written back.
 
 ```ts
-import { root } from "@toloka-platform/sdk";
+import { optional, root } from "@toloka-platform/sdk";
 
-export const collection = root({ started: [imageUrl], completed: [annotations] });
+export const collection = root({
+  started: [imageUrl],
+  completed: [optional(annotations)],
+});
 ```
 
-Pass `{ field, optional: true }` instead of a bare field to make a binding optional.
+Pass a bare field for a required binding. Use `optional(field)` for new optional bindings. The explicit `{ field, optional }` form remains supported and may appear in imported source.
+
+`root()` deliberately has no name argument: a pipeline has exactly one boundary, and its default wire id is `root`.
 
 ### code
 

package/docs/cli-v2.md

@@ -1,6 +1,6 @@
 # CLI v2: project as the root
 
-How `toloka` should work in the next version. Preview is unreleased, so this is a clean cutover, not a compatibility layer.
+How `toloka` should work in the next version. Beta remains a clean cutover rather than a compatibility layer.
 
 The platform object is a **project** (`pp.…`, today's pipeline project). Windmill calls the same role a workspace. PostHog calls it a project. We keep **project** so the CLI matches the API and the console.
 
@@ -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`).
 
@@ -212,7 +212,7 @@ Do not add those groups until the resource exists. The rule is already fixed: th
 | `toloka runs` / `cost` / `cancel` / `results` | `toloka pipeline …`                                                |
 | root = `toloka.json` or `pipelines/`          | root = `toloka.json` only                                          |
 
-No shims. Preview callers update.
+No shims. Beta callers update.
 
 ## Out of scope
 

package/docs/cli.md

@@ -2,7 +2,7 @@
 
 The `toloka` CLI reads TypeScript source as the desired state, compares it with the live platform state, and reconciles the two.
 
-This CLI is Preview software. Commands, flags, and output can change without a major version bump.
+This CLI is Beta software. Commands, flags, and output can change before general availability.
 
 `toloka` requires Bun 1.4.0. The published package ships matching CLI bytecode; the launcher falls back to TypeScript source in a development checkout when the bytecode is absent.
 
@@ -61,6 +61,14 @@ The CLI is resource-first: `toloka <resource> <action>`. A Base Action has one m
 
 Resources may also expose specialized actions beyond the Base Actions, such as `pipeline cost`, `skill search`, and `skill install`.
 
+## version
+
+Print the SDK/CLI version. `toloka version --json` also prints build provenance: the build commit when the bytecode bundle recorded one, the install channel (`global-registry`, `linked`, or `project-local`), and the local package path for linked installs. `toloka -v` and `toloka --version` remain semver-only for scripts.
+
+```sh
+toloka version [--json]
+```
+
 ## project
 
 Register and select the platform project later commands use.
@@ -73,9 +81,14 @@ toloka project current
 toloka project url
 toloka project remove <alias>
 toloka project create [alias] [--name <name>] [--team-id <id>]
+toloka project untrack <pipeline|dataset> <name> [--confirm]
 ```
 
-`add`, `switch`, `remove`, and `create` write the machine registry in the credentials file. They refuse `--api-key` / `--base-url` / `POTATO_*` when those would select a different key or platform than the stored file. `create` reuses the only visible team when every listed project shares one; otherwise pass `--team-id`.
+`add`, `switch`, `remove`, and `create` write the machine registry in the credentials file. They refuse `--api-key` / `--base-url` / `POTATO_*` when those would select a different key or platform than the stored file. `project list` prints project id, name, and team id. `create` reuses the only visible team when every listed project shares one; otherwise pass `--team-id`.
+
+`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.
 
@@ -188,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

@@ -4,11 +4,11 @@ Install the SDK, sign in, and get a pipeline project reconciling from source in
 
 ## Install
 
-Install the bytecode-cached CLI globally and declare the Preview SDK in the project:
+Install the bytecode-cached CLI globally and declare the Beta SDK in the project:
 
 ```sh
 curl -fsSL https://platform.toloka.ai/cli/install.sh | sh
-bun add @toloka-platform/sdk@preview
+bun add @toloka-platform/sdk@latest
 ```
 
 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.
@@ -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.
 
@@ -140,4 +140,4 @@ Exit code `0` means the run reached a successful terminal state, `1` a failed on
 - [Nodes](./nodes.md) — which node to reach for, and the pricing floors you must clear
 - [CLI](./cli.md) — every command and flag
 - [Troubleshooting](./troubleshooting.md) — the failures you will hit
-- [Limitations](./limitations.md) — Preview status and what this SDK does not do yet
+- [Limitations](./limitations.md) — Beta status and what this SDK does not do yet

package/docs/limitations.md

@@ -1,8 +1,8 @@
 # Limitations
 
-What this Preview SDK does not do yet, stated plainly so you can decide what to depend on.
+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-preview.9`. This is a Preview: the authoring API, the CLI surface, and the generated source layout can change without a major version bump. Pin an exact version. Do not depend on this in production yet.
+`@toloka-platform/sdk` is `0.2.0-preview.1`. 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 Preview SDK does not do yet, stated plainly so you can decide what to
 | 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: