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

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

@@ -1 +1 @@
-bbe06fffb8a659ebc2903d962ff2b4a225fe3abc691e607a01258350163c36c7  toloka.js.jsc
+2e4e22afc766a0a267262fe07718505b43f1cdf364e402a990279e224ad92923  toloka.js.jsc

package/dist/cli/toloka.js.sha256

@@ -1 +1 @@
-43e152b2ae5342013785dd1c89843bead8b68039ea6576ae5a8bea5944263127  toloka.js
+842c3cdfb47d5a899375c288cefa8ba550c22301dbd47d99d224a8b34acd01a2  toloka.js

package/docs/cli.md

@@ -202,6 +202,31 @@ toloka pipeline results <runId> [--limit <n>] [--failed]
 
 `pipeline status` reports the latest run of that pipeline. `pipeline runs` lists recent runs (default 10). `pipeline cost` forecasts what a run would bill. `pipeline cancel` and `pipeline results` take a run id.
 
+## base-model
+
+Inspect the global, read-only Base Model Catalog.
+
+```sh
+toloka base-model list [--json]
+toloka base-model get <id> [--json]
+```
+
+Human-readable output is the default. `base-model list` prints aligned ID, name, provider, and upstream-model columns; `base-model get` prints labeled fields including the pinned revision. Pass `--json` for machine-readable output.
+
+## model
+
+Manage Model metadata in the selected project.
+
+```sh
+toloka model list [--json]
+toloka model get <name-or-id> [--json]
+toloka model versions <name-or-id> [--json]
+toloka model create <name> --base <base-model-id> [--description <text>] [--json]
+toloka model archive <name-or-id> [--json]
+```
+
+`model create` creates project-owned Model metadata linked to one catalog Base Model; it does not create a Model Version. Human-readable output is the default for every command in this group. Pass `--json` for machine-readable objects or arrays. Weight upload, validation, download, and Model Version creation are deferred.
+
 ## dataset
 
 Catalog and row commands for datasets in the selected project. Name or id is accepted; duplicate names must be addressed by id.
@@ -219,7 +244,7 @@ toloka dataset upload <name> <file>
 
 `dataset load` starts a platform export, waits for it (default 60s; pass `--timeout`), downloads the JSON array, and writes JSONL to `--out`. `--limit` slices after download; it still waits for the full export. On timeout the message names the export id. Failed downloads and invalid payloads leave `--out` untouched.
 
-`dataset upload` appends JSONL rows. Field schemas are immutable after the first upload: you can add columns, never alter or remove one. See [datasets](./datasets.md).
+`dataset upload` accepts `.json` arrays, `.jsonl` files with one object per line, and `.csv` files with a header row. The CLI infers the format from the extension and uploads the original bytes without conversion. If the blob transfer or finalization fails, the CLI cancels the started upload before returning the error, so another upload can start immediately and may reuse the same filename. Field schemas are immutable after the first successful upload: you can add columns, never alter or remove one. See [datasets](./datasets.md).
 
 ## report
 

package/docs/datasets.md

@@ -109,17 +109,16 @@ toloka dataset upload face-images data/face_images.jsonl
 
 The command takes two positional arguments and has no flags:
 
-| Argument | Description                          |
-| -------- | ------------------------------------ |
-| `<name>` | Dataset name or id                   |
-| `<file>` | JSONL file, one JSON object per line |
+| Argument | Description                                |
+| -------- | ------------------------------------------ |
+| `<name>` | Dataset name or id                         |
+| `<file>` | `.json`, `.jsonl`, or `.csv` file to append |
 
-Each line is a JSON object with keys matching column names:
+The CLI infers the format from the filename extension and uploads the original bytes without conversion:
 
-```json
-{"image_url": "https://example.com/cat-1.jpg"}
-{"image_url": "https://example.com/cat-2.jpg"}
-```
+- `.json` contains an array of row objects.
+- `.jsonl` contains one row object per non-empty line and is validated locally before upload.
+- `.csv` uses its header row for field names; every value is ingested as a string.
 
 Upload is additive: it appends items and never rewrites existing ones. If the dataset does not exist yet and a pipeline in source declares it, `dataset upload` creates the dataset with the declared columns automatically. If no pipeline declares the dataset, upload stops and asks you to bind a pipeline to it in source so its columns are known, or to upload to an existing dataset. Duplicate live names must be addressed by id.
 

package/docs/limitations.md

@@ -2,7 +2,7 @@
 
 What this Preview SDK does not do yet, stated plainly so you can decide what to depend on.
 
-`@toloka-platform/sdk` is `0.1.0-preview.5`. 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.1.0-preview.6`. 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.
 
 ## The SDK does not certify deployability
 
@@ -39,13 +39,10 @@ A `code` node carries its Python as an inline string in `code.code`. There is no
 
 These are reproduced platform-side issues that affect the SDK path. They are not SDK bugs and cannot be fixed from this package.
 
-| defect                                                                                  | effect on you                                                                                           | workaround                                                        |
-| --------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- |
-| Re-uploading a filename already used in a dataset returns a bodyless `500`              | running the same `toloka dataset upload` twice fails                                                    | use a distinct filename per upload                                |
-| A failed upload leaves a pending upload row, and a pending upload counts as in progress | later uploads to that dataset return `409 Another upload is already in progress`, with no public cancel | load into a new dataset; ask for the pending upload to be cleared |
-| Finalizing a file upload can return a bodyless `500`                                    | `toloka dataset upload` cannot complete on an affected environment                                      | declare columns in source and load rows through a client call     |
-| Rows added through the items endpoint skip column inference                             | `toloka dataset fields` reports no columns for a dataset that holds rows                                | declare columns in source rather than inferring them              |
-| Starting a run intermittently returns a bodyless `500`                                  | `toloka pipeline run` fails with nothing to act on                                                      | check `toloka pipeline runs <name>` for a created run, then retry |
+| defect                                                      | effect on you                                                            | workaround                                                        |
+| ----------------------------------------------------------- | ------------------------------------------------------------------------ | ----------------------------------------------------------------- |
+| Rows added through the items endpoint skip column inference | `toloka dataset fields` reports no columns for a dataset that holds rows | declare columns in source rather than inferring them              |
+| Starting a run intermittently returns a bodyless `500`      | `toloka pipeline run` fails with nothing to act on                       | check `toloka pipeline runs <name>` for a created run, then retry |
 
 ## Not attempted yet
 

package/docs/troubleshooting.md

@@ -51,17 +51,6 @@ A resource exists on the platform but not in your source tree. `apply` reports i
 
 Another writer changed the graph after your source was read. Do not retry blindly: `plan` again to re-read live state, review the new diff, carry any intentional remote change into source, then `apply`.
 
-## Second upload of the same filename fails
-
-Uploading a file whose basename already exists in that dataset fails with a bodyless `500`. `toloka dataset upload` sends the file's basename, so running the same documented command twice reproduces it:
-
-```sh
-toloka dataset upload cat-images ./data/rows.jsonl   # first time: fine
-toloka dataset upload cat-images ./data/rows.jsonl   # second time: 500
-```
-
-Until the platform returns a proper conflict, use a distinct filename per upload — for example `rows-2026-08-13.jsonl`. This is a platform defect, tracked; the SDK cannot detect it in advance.
-
 ## Another upload is already in progress
 
 ```