dataiku-sdk 0.12.6 → 1.0.0

package/dist/src/skill.js

@@ -2,218 +2,16 @@ import { execFileSync, } from "node:child_process";
 import * as fs from "node:fs";
 import * as os from "node:os";
 import * as path from "node:path";
-const SKILL_BODY = `# Dataiku DSS agent CLI
-
-Use \`dss\` when an agent needs to inspect or change Dataiku DSS resources: projects, datasets, recipes, jobs, scenarios, folders, notebooks, SQL, variables, code envs, and connections.
-If the installed \`dss\` binary is unavailable but the repository checkout is the current workspace, prefer \`bun --no-env-file src/cli.ts ...\` or \`bun --no-env-file ./bin/dss.js ...\`. Node users can invoke the same cross-runtime launcher as \`node ./bin/dss.js ...\`; when \`dist/\` has not been built, it delegates to Bun. From another working directory, pass the checkout's absolute \`bin/dss.js\` path to Bun or Node.
-\`--no-env-file\` disables Bun's automatic preloading only; the CLI still applies its documented \`.env\` handling unless \`DATAIKU_DISABLE_ENV=1\` is set.
-
-## Contract
-
-- Command results write exactly one JSON value to stdout, including \`doctor\`, \`batch\`, and \`cleanup\` failure reports; use the exit code and result fields.
-- Dispatch/runtime failures write one JSONL error event to stderr with \`type:"error"\`, \`ok:false\`, \`error\`, \`code\`, and \`exitCode\`, while stdout stays empty.
-- Non-fatal warnings and \`--verbose\` HTTP traces are JSONL stderr events (\`type:"warning"\` / \`type:"trace"\`), never prose.
-- No prompts, help screens, tables, banners, or prose output are part of the contract.
-- Exit codes: 0 success, 1 usage/configuration error, 2 DSS or internal error, 3 transient/retryable DSS error, 4 a failed long-running result or synchronous assertion.
-- Pass \`--json\` for compact single-line JSON on stdout; use it for agent discovery and other JSON results to minimize tokens. Without it, success JSON is pretty-printed.
-- \`--raw\` is the only stdout escape hatch: recipe payload commands emit raw bytes to stdout unless \`--output PATH\` is also set; with \`--output\`, stdout is the JSON string equal to \`PATH\` and the file receives exact raw bytes.
-- \`--fields a,b,c\` projects those fields from object or array-of-objects results; dotted paths (\`a.b.c\`) drill into nested objects, and missing fields become \`null\`; string and scalar results pass through unchanged.
-
-## Discover commands
-
-\`\`\`text
-dss agent contract --fields protocol,agentContractVersion,cli,stdio,planning,compatibility --json
-dss commands run --fields dataset.create --json
-dss commands run --fields dataset.create.usage,dataset.create.description,dataset.create.flags,dataset.create.examples --json
-dss commands run --fields dataset --json
-dss agent contract --fields commands.actions --json
-\`\`\`
-
-Bootstrap with the scoped \`agent contract\` call above: \`protocol,agentContractVersion,cli,stdio,planning,compatibility\` cover protocol/schema compatibility, stderr event semantics, preferred discovery commands, non-JSON escape hatches, planning rules, and compatibility guarantees in ~250 tokens. Request \`schemas\` (the JSON schemas) or \`commands\` (the contract's discovery section) only when you actually need them.
-
-Before choosing command syntax, look the action up in the command registry: \`--fields RESOURCE.ACTION\` returns one complete entry, and appended \`.FIELD\` paths return only the metadata you need. Prefer the four-field projection \`usage,description,flags,examples\` by default — it is the smallest self-sufficient starting point for constructing an invocation. The registry entry is the canonical schema for flags, positional arguments, side effects, auth requirements, output shape, idempotency, dry-run support, structured examples, payload schemas, unsafe outputs, cleanup hints, and exit codes.
-
-\`--fields\` takes a comma-separated list, so request several actions in one call. Each key is echoed exactly as requested (\`--fields dataset.create\` returns \`{"dataset.create": {...}}\`). Enumerate every resource and action with \`dss agent contract --fields commands.actions --json\` (~1k tokens); the hundreds-of-thousands-token unscoped registry is compatibility-only. An unknown resource or action exits with code 1 and a JSON error envelope on stderr containing the valid options.
-Credential lookup order is flags first, then \`DATAIKU_*\` environment variables, then saved credentials.
-Set \`DATAIKU_DISABLE_ENV=1\` when a test must ignore both \`.env\` files and \`DATAIKU_*\` environment variables.
-When \`.env\` loading is enabled, the CLI reads \`.env\` from the command's current working directory first and then the CLI build/root directory; the invocation directory wins on conflicting keys. Put test-specific \`.env\` files in the directory where you invoke \`dss\`.
-For disposable agent tests, set \`DSS_CONFIG_DIR\` to a temporary directory so saved credentials never touch the real profile.
-
-## Planning, safety, and generic inputs
-
-- Before any registry entry with \`sideEffect:"write"\`, run the exact argv with \`--plan\` first. Planning is local: it returns the derived operation without resolving credentials or calling DSS. Check \`destructive\`, \`idempotency\`, \`async\`, \`unsafeOutputs\`, and \`exitCodes\` before execution.
-- Use \`--dry-run\` only when that action's registry entry has \`dryRun:true\`. \`--plan\` explains the operation; \`--dry-run\` exercises the action-specific simulation path. Never add an unsupported flag.
-- When a create/upload action advertises \`--record-cleanup\`, pass \`--record-cleanup cleanup.jsonl\`. \`dss cleanup --file cleanup.jsonl\` previews the recorded cleanup steps in reverse order and does not mutate DSS; add \`--apply\` only after checking the preview.
-- For JSON payload actions, follow \`inputContract\`, \`requiredFlags\`, and \`requiredOneOf\`. Prefer \`--data-file PATH\` or \`--stdin\` when advertised instead of inline \`--data\`; this preserves exact JSON across shells and keeps large or sensitive payloads out of process arguments.
-- Authenticated actions advertise \`--request-timeout MS\` and \`--retries N\`; \`--retries\` applies to idempotent GET requests. Long-running actions separately advertise controls such as \`--timeout MS\`, \`--poll-interval MS\`, and log limits; use only the flags in that action's registry entry.
-- Before live mutation tests, use \`dss fixtures --json\` to discover compatible test resources instead of guessing project objects.
-
-## Authentication
-
-Prefer environment variables for ephemeral agent runs. Use the syntax for the active shell:
-
-POSIX shell:
-
-\`\`\`sh
-export DATAIKU_URL=https://dss.example.com
-export DATAIKU_API_KEY=your-api-key
-export DATAIKU_PROJECT_KEY=MYPROJ
-\`\`\`
-
-PowerShell:
-
-\`\`\`powershell
-$env:DATAIKU_URL = "https://dss.example.com"
-$env:DATAIKU_API_KEY = "your-api-key"
-$env:DATAIKU_PROJECT_KEY = "MYPROJ"
-\`\`\`
-
-Windows Command Prompt:
-
-\`\`\`bat
-set "DATAIKU_URL=https://dss.example.com"
-set "DATAIKU_API_KEY=your-api-key"
-set "DATAIKU_PROJECT_KEY=MYPROJ"
-\`\`\`
-
-To persist credentials for later invocations:
-
-\`\`\`bash
-dss auth login --url https://dss.example.com --api-key YOUR_KEY --project-key MYPROJ
-\`\`\`
-
-The command saves credentials and returns \`{"saved":true,"path":"..."}\`. \`DSS_CONFIG_DIR\` wins when set. Otherwise credentials use \`XDG_CONFIG_HOME/dataiku/credentials.json\`, the \`dataiku/credentials.json\` directory under \`APPDATA\` on Windows, or \`~/.config/dataiku/credentials.json\`.
-\`auth login\` validates by listing accessible projects before saving credentials, so the API key must be allowed to call DSS project-list APIs.
-
-TLS flags: \`--insecure\` disables certificate verification; \`--ca-cert PATH\` adds a PEM CA bundle. Environment equivalents: \`NODE_TLS_REJECT_UNAUTHORIZED\`, \`NODE_EXTRA_CA_CERTS\`.
-
-## Common workflows
-
-\`\`\`text
-dss version
-dss project list
-dss dataset list --project-key MYPROJ
-dss recipe get-payload compute_orders --raw --output code.py --project-key MYPROJ
-dss recipe diff compute_orders --file code.py --project-key MYPROJ
-dss recipe set-payload compute_orders --file code.py --project-key MYPROJ
-dss job build-and-wait orders --include-logs --project-key MYPROJ
-dss sql query --connection analytics --sql "select 1" --project-key MYPROJ
-dss batch --data-file steps.json
-\`\`\`
-For fake-DSS smoke tests, return project lists as JSON arrays such as \`[{"projectKey":"MYPROJ","name":"My Project"}]\` from \`/public/api/projects/\`; recipe payload commands read \`/public/api/projects/<PROJECT>/recipes/<NAME>?includePayload=true\` and expect a JSON object shaped like \`{"recipe":{"name":"<NAME>","type":"python"},"payload":"..."}\`.
-
-## Application release safety
-
-Treat app release as explicit validate, compare, version, successor, verify, and permission gates.
-The public app-manifest \`version\` field is raw metadata: writing it is NOT a publish transaction.
-New instances inherit the template's raw \`version\`; existing instances are never upgraded in
-place — create an additive successor (the old instance is preserved), verify it, then retire the
-old one as a separate guarded step. Never infer private publish/recreate/rename,
-recipient-sharing, or UI-click operations that the public DSS API does not expose.
-
-\`\`\`text
-dss app validate-manifest --project-key APP_TEMPLATE
-dss app compare-manifest APP_ID --project-key RELEASE_INSTANCE
-dss app manifest-version --project-key APP_TEMPLATE
-dss app set-manifest-version --manifest-version 1.4.0 --project-key APP_TEMPLATE
-# targetProjectKey in instance.json must be confirmed absent
-dss app create-instance APP_ID --data-file instance.json --wait --record-cleanup cleanup.jsonl
-dss app create-successor-instance APP_ID --from RELEASE_INSTANCE --to RELEASE_INSTANCE_V2 --copy-permissions --record-cleanup cleanup.jsonl
-dss app verify-instance APP_ID --project-key RELEASE_INSTANCE_V2 --expect-version 1.4.0
-dss cleanup --file cleanup.jsonl
-dss app permissions-snapshot --project-key RELEASE_INSTANCE --output permissions.json
-dss app permissions-diff --project-key RELEASE_INSTANCE --file permissions.json
-dss app permissions-restore --project-key RELEASE_INSTANCE --file permissions.json --dry-run
-\`\`\`
-
-An invalid manifest exits non-zero with the validation result in the structured error details.
-Review the cleanup preview before \`dss cleanup --file cleanup.jsonl --apply\`. Every new entry is
-bound to the canonical DSS URL. App cleanup records a \`creationTag\` hash observed after the DSS
-future identifies its target key; unconfirmed creation stops unresolved. The future target and
-later \`creationTag\` are independent, non-atomic observations because the public API exposes
-neither an immutable project ID joined to the future nor a conditional DELETE. Cleanup rechecks
-type and \`creationTag\` immediately before deletion, rejecting detected key reuse but unable to
-eliminate replacement in the remaining check-to-DELETE gap. Apply validates the full ledger before
-any request and rejects legacy, mixed-server, mismatched-server, or unbound app cleanup entries.
-The successor's cleanup ledger entry targets only the new project key;
-the predecessor is never targeted. Some DSS deployments return 403 for an unknown target project:
-instance creation requires confirmed target absence before POST, so an inaccessible target absent
-from the visible project list is still rejected as unconfirmed rather than risking cleanup against
-a pre-existing project. A definitive create rejection never produces a cleanup entry.
-
-\`app set-manifest-version\` reports
-\`concurrencyControl:"client-side-non-atomic-stale-read-check"\`. \`--expect-hash SHA256\` refuses the
-write when the manifest already changed, but the PUT itself stays unconditional: this command can
-overwrite a writer that commits inside the read-then-write window, and the post-write read cannot
-detect that lost update when this command's payload wins. Never treat the hash as a serializing lock.
-An ambiguous manifest PUT or verification read exits non-zero with \`persisted:null\`,
-\`after:null\`, and \`outcome:"indeterminate"\`; it never claims success or rejection.
-
-The API key authenticates public REST only. \`app verify-instance\` reports \`apiReady:true\`,
-\`status:"API_VERIFIED_UI_PENDING"\`, and \`uiPublicationVerified:false\`. Its \`visual-ui\` gate
-requires a pre-authenticated SSO browser session or dedicated UI test identity and evidence from
-exercising the affected tiles, forms, and actions; the CLI never marks that external gate complete.
-Permission snapshots have an integrity hash bound to the canonical DSS URL, project key, and
-observed concrete project incarnation from \`creationTag\`; diff and restore reject detected server,
-key, or incarnation mismatches. DSS exposes no conditional permission PUT, so these client-side checks
-narrow and detect key-reuse races but cannot serialize the final check with the write. Snapshots
-contain access-control identities; keep them mode \`0600\` and commit them only when repository
-policy permits.
-
-## Confirming mutations
-
-Mutations print a small JSON ack to stdout and exit 0 on success (e.g. \`{"updated":"NAME","resource":"recipe"}\`); on failure they print the error envelope to stderr and exit non-zero. The exit code is the source of truth.
-
-- For portable multi-step writes, prefer \`dss batch\` (payload: a JSON array of argv arrays). It runs fail-fast, returns one envelope with per-step \`ok\`/\`result\`/\`error\`, and exits non-zero if any step fails.
-- If separate processes are required, inspect each exit code and stop before launching the next step. Do not rely on shell chaining: syntax differs between POSIX shells, Windows PowerShell 5.1, PowerShell 7, and Command Prompt.
-- Never pipe a mutation into a command that prints a fixed string or merges stderr: a pipeline may return the helper's exit code and report a failed mutation as success.
-- To branch in code, key off the exit code or the JSON ack on stdout — never a hardcoded label.
-
-## Platform & debugging notes
-
-- Pass code and SQL via \`--file\`/\`--sql-file\`, not inline: shells (especially PowerShell) mangle quotes, \`$\`, and newlines in multi-line snippets.
-- On a non-UTF-8 console (e.g. Windows cp1252), don't print non-ASCII results; write them to a UTF-8 file and read that, or use \`--output PATH\`.
-- Build failures: \`dss job log <id> --errors-only\` surfaces just error/traceback lines, and \`--output PATH\` saves the full log to a file. Logs are one long line with JVM noise; the \`Error in Python process: At line <N>\` marker maps \`<N>\` straight to your recipe payload's source line.
-- Schema changes aren't automatic for code recipes: after changing a python/SQL/prepare recipe's output columns run \`dss dataset refresh-schema\` (or rebuild) before downstream reads, and \`dss dataset validate-build\` to catch file-backed misconfig before launching a build. Exception: \`dss recipe create --type sync\` copies the input schema onto a schemaless dataset output at create time (see \`syncOutputSchemaPropagated\` in the result), so a fresh sync output builds populated without a manual refresh.
-- \`dss dataset download\` is capped (default 100k rows) and returns \`{ path, rows, truncated, limit }\`: check \`truncated\` and raise \`--limit N\` when you need more — treat it as a sample, not a guaranteed full export. Without \`--output\` the file lands in the current working directory (and a \`dataset_download_default_location\` warning names that path); pass \`--output PATH\` to control the destination. For very large tables, aggregate in SQL or read inside a recipe instead.
-- \`dss api-service list-packages SERVICE\` first verifies the parent service through its settings. A \`not_found\` error means the service is missing (verify the service ID and project key); an empty array means the service exists but has no deployable packages. Do not reinterpret \`not_found\` as an empty package list or retry the lower-level packages route.
-- \`dss notebook clear-jupyter-outputs NAME --dry-run\` returns the full \`current\` and \`next\` notebook states. Applying it clears \`outputs\` and resets \`execution_count\` to \`0\` only on code cells, preserving markdown and raw cells unchanged.
-- \`dss sql query ... --dataset PROJECT.NAME\` first queries through the dataset. If DSS rejects that dataset connection as neither SQL nor HDFS, the CLI reads dataset metadata and retries with \`params.connection\` (using its schema or catalog as the database when available). A readable dataset with no usable connection exits with \`validation_failed\` and advises \`--connection\`; dataset metadata \`404\` and \`403\` errors propagate as \`not_found\` and \`permission_denied\`.
-- \`dss sql query ... --start-retries N\` opts the query-start POST into transient retries with exponential backoff. A lost response can cause DSS to execute the SQL more than once, so use it only for SQL whose repetition is safe; ordinary \`--retries N\` remains GET-only.
-
-## Error envelope
-
-For dispatch/runtime failures, parse stderr as JSONL; the final line is an error event:
-
-\`\`\`json
-{
-  "type": "error",
-  "ok": false,
-  "error": "Missing API key.",
-  "code": "usage_error",
-  "category": "usage",
-  "exitCode": 1,
-  "resource": "dataset",
-  "action": "list"
-}
-\`\`\`
-
-\`doctor\`, \`batch\`, and \`cleanup\` report command-level failures on stdout and leave stderr empty. Use the exit code before choosing a stream.
-Use \`code\`, \`category\`, \`exitCode\`, \`retryable\`, \`status\`, and \`details\` for recovery logic. Do not scrape message text when a structured field is available.
-Treat \`details.body\` as sanitized metadata only: it contains at most \`requestId\`/\`request_id\`/\`errorId\`/\`elapsedMs\` plus locally trusted target/timing fields, not the arbitrary DSS response body. \`details.statusText\` is canonical text derived from the numeric status, not a remote reason phrase. Base recovery on top-level \`code\`, \`category\`, \`status\`, \`retryable\`, \`requestId\`, \`hint\`, and \`details.dssCategory\`; never parse or expose assumed server-body fields.
-`;
-const SKILL_FRONTMATTER = `---
-name: dataiku-dss
-description: >-
-  Agent-only JSON CLI for Dataiku DSS. Use to inspect or mutate DSS projects,
-  datasets, recipes, jobs, scenarios, folders, notebooks, SQL, variables,
-  code envs, and connections. Discover scoped command metadata with
-  dss commands run --fields RESOURCE.ACTION --json.
----
-
-`;
+const SKILL_URLS = [
+    new URL("../skills/dataiku-dss/SKILL.md", import.meta.url),
+    new URL("../../skills/dataiku-dss/SKILL.md", import.meta.url),
+];
 function skillContent() {
-    return SKILL_FRONTMATTER + SKILL_BODY;
+    for (const skillUrl of SKILL_URLS) {
+        if (fs.existsSync(skillUrl))
+            return fs.readFileSync(skillUrl, "utf-8");
+    }
+    throw new Error(`Bundled Dataiku skill not found. Checked: ${SKILL_URLS.map((url) => url.pathname).join(", ")}`);
 }
 export const AGENTS = {
     claude: {

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "dataiku-sdk",
-	"version": "0.12.6",
+	"version": "1.0.0",
 	"description": "Dataiku DSS SDK and CLI for programmatic access to DSS REST APIs",
 	"type": "module",
 	"workspaces": [
@@ -13,6 +13,8 @@
 	},
 	"files": [
 		"dist/",
+		"plugin.json",
+		"skills/",
 		"bin/dss.js",
 		"packages/types/dist/"
 	],
@@ -22,9 +24,10 @@
 	},
 	"scripts": {
 		"build": "tsc && tsc -p packages/types/tsconfig.json",
-		"prepack": "tsc && tsc -p packages/types/tsconfig.json",
-		"prepublishOnly": "tsc && tsc -p packages/types/tsconfig.json",
-		"check": "tsc --noEmit",
+		"prepack": "node scripts/sync-plugin-version.mjs --check && tsc && tsc -p packages/types/tsconfig.json",
+		"prepublishOnly": "node scripts/sync-plugin-version.mjs --check && tsc && tsc -p packages/types/tsconfig.json",
+		"check": "tsc --noEmit && node scripts/sync-plugin-version.mjs --check",
+		"version": "node scripts/sync-plugin-version.mjs && git add plugin.json",
 		"lint": "oxlint src/",
 		"lint:fix": "oxlint --fix src/",
 		"format": "dprint fmt",

package/packages/types/dist/index.d.ts

@@ -66,6 +66,7 @@ export declare const DatasetSummarySchema: import("@sinclair/typebox").TObject<{
     managed: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TBoolean>;
     params: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TObject<{
         connection: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
+        uploadConnection: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
         schema: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
         catalog: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
     }>>;
@@ -86,6 +87,7 @@ export declare const DatasetDetailsSchema: import("@sinclair/typebox").TObject<{
     managed: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TBoolean>;
     params: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TObject<{
         connection: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
+        uploadConnection: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
         path: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
         table: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
         schema: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
@@ -111,7 +113,7 @@ export declare const DatasetDetailsSchema: import("@sinclair/typebox").TObject<{
 export type DatasetDetails = Static<typeof DatasetDetailsSchema>;
 export declare const DatasetCreateOptionsSchema: import("@sinclair/typebox").TObject<{
     datasetName: import("@sinclair/typebox").TString;
-    connection: import("@sinclair/typebox").TString;
+    connection: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
     dsType: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
     table: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
     dbSchema: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
@@ -382,8 +384,8 @@ export declare const FlowZoneUpdateOptionsSchema: import("@sinclair/typebox").TO
 export type FlowZoneUpdateOptions = Static<typeof FlowZoneUpdateOptionsSchema>;
 export declare const FolderCreateOptionsSchema: import("@sinclair/typebox").TObject<{
     name: import("@sinclair/typebox").TString;
-    type: import("@sinclair/typebox").TString;
-    connection: import("@sinclair/typebox").TString;
+    type: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
+    connection: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
     path: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
     params: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TRecord<import("@sinclair/typebox").TString, import("@sinclair/typebox").TUnknown>>;
     projectKey: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
@@ -677,6 +679,128 @@ export declare const FlowMapOptionsSchema: import("@sinclair/typebox").TObject<{
     includeRaw: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TBoolean>;
 }>;
 export type FlowMapOptions = Static<typeof FlowMapOptionsSchema>;
+/**
+ * Git working-copy status of a project. Stable fields are documented in the
+ * DSS 14.7.3 source; DSS additionally returns extension fields, which are
+ * preserved by `additionalProperties: true`.
+ */
+export declare const ProjectGitStatusSchema: import("@sinclair/typebox").TObject<{
+    currentBranch: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
+    remotes: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TArray<import("@sinclair/typebox").TObject<{
+        name: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
+        url: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
+    }>>>;
+    trackingCount: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TObject<{
+        ahead: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TNumber>;
+        behind: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TNumber>;
+    }>>;
+    clean: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TBoolean>;
+    hasUncommittedChanges: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TBoolean>;
+    added: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TArray<import("@sinclair/typebox").TString>>;
+    changed: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TArray<import("@sinclair/typebox").TString>>;
+    removed: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TArray<import("@sinclair/typebox").TString>>;
+    missing: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TArray<import("@sinclair/typebox").TString>>;
+    modified: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TArray<import("@sinclair/typebox").TString>>;
+    conflicting: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TArray<import("@sinclair/typebox").TString>>;
+    untracked: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TArray<import("@sinclair/typebox").TString>>;
+    untrackedFolders: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TArray<import("@sinclair/typebox").TString>>;
+    originProjectKey: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
+    trackingCountWithOriginProject: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TObject<{
+        ahead: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TNumber>;
+        behind: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TNumber>;
+    }>>;
+}>;
+export type ProjectGitStatus = Static<typeof ProjectGitStatusSchema>;
+export declare const ProjectGitRemoteSchema: import("@sinclair/typebox").TObject<{
+    url: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
+}>;
+export type ProjectGitRemote = Static<typeof ProjectGitRemoteSchema>;
+/**
+ * Result of a Git mutation. DSS answers with HTTP 200 even for failures, so
+ * `success` is the field callers must inspect before trusting the operation.
+ */
+export declare const ProjectGitActionResultSchema: import("@sinclair/typebox").TObject<{
+    success: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TBoolean>;
+    output: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TUnknown>;
+    logs: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TUnknown>;
+    messages: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TUnknown>;
+}>;
+export type ProjectGitActionResult = Static<typeof ProjectGitActionResultSchema>;
+export declare const ProjectGitTagSchema: import("@sinclair/typebox").TObject<{
+    name: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
+    shortName: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
+    commit: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TUnknown>;
+    annotations: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TUnknown>;
+    readOnly: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TBoolean>;
+}>;
+export type ProjectGitTag = Static<typeof ProjectGitTagSchema>;
+export declare const ProjectGitTagsSchema: import("@sinclair/typebox").TArray<import("@sinclair/typebox").TObject<{
+    name: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
+    shortName: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
+    commit: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TUnknown>;
+    annotations: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TUnknown>;
+    readOnly: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TBoolean>;
+}>>;
+export type ProjectGitTags = Static<typeof ProjectGitTagsSchema>;
+/**
+ * Paginated commit log. `nextCommit` is the cursor DSS expects back to fetch
+ * the following page; entries stay unpinned because commit payloads vary.
+ */
+export declare const ProjectGitLogResultSchema: import("@sinclair/typebox").TObject<{
+    entries: import("@sinclair/typebox").TArray<import("@sinclair/typebox").TUnknown>;
+    nextCommit: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
+}>;
+export type ProjectGitLogResult = Static<typeof ProjectGitLogResultSchema>;
+/**
+ * Diff between two revisions. Stable fields are documented in the DSS 14.7.3
+ * source; DSS additionally returns extension fields, which are preserved by
+ * `additionalProperties: true`.
+ */
+export declare const ProjectGitDiffResultSchema: import("@sinclair/typebox").TObject<{
+    commitFrom: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TUnknown>;
+    commitTo: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TUnknown>;
+    addedLines: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TNumber>;
+    removedLines: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TNumber>;
+    changedFiles: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TNumber>;
+    entries: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TArray<import("@sinclair/typebox").TUnknown>>;
+}>;
+export type ProjectGitDiffResult = Static<typeof ProjectGitDiffResultSchema>;
+export declare const ProjectGitLibrarySchema: import("@sinclair/typebox").TObject<{
+    repository: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
+    login: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
+    pathInGitRepository: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
+    localTargetPath: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
+    checkout: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
+    addToPythonPath: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TBoolean>;
+}>;
+export type ProjectGitLibrary = Static<typeof ProjectGitLibrarySchema>;
+export declare const ProjectGitLibrariesSchema: import("@sinclair/typebox").TArray<import("@sinclair/typebox").TObject<{
+    repository: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
+    login: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
+    pathInGitRepository: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
+    localTargetPath: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
+    checkout: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
+    addToPythonPath: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TBoolean>;
+}>>;
+export type ProjectGitLibraries = Static<typeof ProjectGitLibrariesSchema>;
+/** Handle returned by Git operations that run asynchronously as a DSS future. */
+export declare const ProjectGitFutureResponseSchema: import("@sinclair/typebox").TObject<{
+    jobId: import("@sinclair/typebox").TString;
+}>;
+export type ProjectGitFutureResponse = Static<typeof ProjectGitFutureResponseSchema>;
+export declare const ProjectGitFutureStateSchema: import("@sinclair/typebox").TObject<{
+    jobId: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
+    hasResult: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TBoolean>;
+    result: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TUnknown>;
+    alive: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TBoolean>;
+    aborted: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TBoolean>;
+    abortable: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TBoolean>;
+    unknown: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TBoolean>;
+    startTime: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TNumber>;
+    runningTime: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TNumber>;
+    error: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TUnknown>;
+}>;
+export type ProjectGitFutureState = Static<typeof ProjectGitFutureStateSchema>;
 export declare const ProjectSummaryArraySchema: import("@sinclair/typebox").TArray<import("@sinclair/typebox").TObject<{
     projectKey: import("@sinclair/typebox").TString;
     name: import("@sinclair/typebox").TString;
@@ -689,6 +813,7 @@ export declare const DatasetSummaryArraySchema: import("@sinclair/typebox").TArr
     managed: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TBoolean>;
     params: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TObject<{
         connection: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
+        uploadConnection: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
         schema: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
         catalog: import("@sinclair/typebox").TOptional<import("@sinclair/typebox").TString>;
     }>>;

package/packages/types/dist/index.js

@@ -123,6 +123,7 @@ export const DatasetSummarySchema = Type.Object({
     managed: Type.Optional(Type.Boolean()),
     params: Type.Optional(Type.Object({
         connection: Type.Optional(Type.String()),
+        uploadConnection: Type.Optional(Type.String()),
         schema: Type.Optional(Type.String()),
         catalog: Type.Optional(Type.String()),
     }, { additionalProperties: true, })),
@@ -141,6 +142,7 @@ export const DatasetDetailsSchema = Type.Object({
     managed: Type.Optional(Type.Boolean()),
     params: Type.Optional(Type.Object({
         connection: Type.Optional(Type.String()),
+        uploadConnection: Type.Optional(Type.String()),
         path: Type.Optional(Type.String()),
         table: Type.Optional(Type.String()),
         schema: Type.Optional(Type.String()),
@@ -159,7 +161,7 @@ export const DatasetDetailsSchema = Type.Object({
 }, { additionalProperties: true, });
 export const DatasetCreateOptionsSchema = Type.Object({
     datasetName: Type.String(),
-    connection: Type.String(),
+    connection: Type.Optional(Type.String()),
     dsType: Type.Optional(Type.String()),
     table: Type.Optional(Type.String()),
     dbSchema: Type.Optional(Type.String()),
@@ -393,8 +395,8 @@ export const FlowZoneUpdateOptionsSchema = Type.Object({
 // ---------------------------------------------------------------------------
 export const FolderCreateOptionsSchema = Type.Object({
     name: Type.String(),
-    type: Type.String(),
-    connection: Type.String(),
+    type: Type.Optional(Type.String()),
+    connection: Type.Optional(Type.String()),
     path: Type.Optional(Type.String()),
     params: Type.Optional(Type.Record(Type.String(), Type.Unknown())),
     projectKey: Type.Optional(Type.String()),
@@ -642,6 +644,107 @@ export const FlowMapOptionsSchema = Type.Object({
     includeRaw: Type.Optional(Type.Boolean()),
 });
 // ---------------------------------------------------------------------------
+// Project Git
+// ---------------------------------------------------------------------------
+/**
+ * Git working-copy status of a project. Stable fields are documented in the
+ * DSS 14.7.3 source; DSS additionally returns extension fields, which are
+ * preserved by `additionalProperties: true`.
+ */
+export const ProjectGitStatusSchema = Type.Object({
+    currentBranch: Type.Optional(Type.String()),
+    remotes: Type.Optional(Type.Array(Type.Object({
+        name: Type.Optional(Type.String()),
+        url: Type.Optional(Type.String()),
+    }, { additionalProperties: true, }))),
+    trackingCount: Type.Optional(Type.Object({
+        ahead: Type.Optional(Type.Number()),
+        behind: Type.Optional(Type.Number()),
+    }, { additionalProperties: true, })),
+    clean: Type.Optional(Type.Boolean()),
+    hasUncommittedChanges: Type.Optional(Type.Boolean()),
+    added: Type.Optional(Type.Array(Type.String())),
+    changed: Type.Optional(Type.Array(Type.String())),
+    removed: Type.Optional(Type.Array(Type.String())),
+    missing: Type.Optional(Type.Array(Type.String())),
+    modified: Type.Optional(Type.Array(Type.String())),
+    conflicting: Type.Optional(Type.Array(Type.String())),
+    untracked: Type.Optional(Type.Array(Type.String())),
+    untrackedFolders: Type.Optional(Type.Array(Type.String())),
+    originProjectKey: Type.Optional(Type.String()),
+    trackingCountWithOriginProject: Type.Optional(Type.Object({
+        ahead: Type.Optional(Type.Number()),
+        behind: Type.Optional(Type.Number()),
+    }, { additionalProperties: true, })),
+}, { additionalProperties: true, });
+export const ProjectGitRemoteSchema = Type.Object({
+    url: Type.Optional(Type.String()),
+}, { additionalProperties: true, });
+/**
+ * Result of a Git mutation. DSS answers with HTTP 200 even for failures, so
+ * `success` is the field callers must inspect before trusting the operation.
+ */
+export const ProjectGitActionResultSchema = Type.Object({
+    success: Type.Optional(Type.Boolean()),
+    output: Type.Optional(Type.Unknown()),
+    logs: Type.Optional(Type.Unknown()),
+    messages: Type.Optional(Type.Unknown()),
+}, { additionalProperties: true, });
+export const ProjectGitTagSchema = Type.Object({
+    name: Type.Optional(Type.String()),
+    shortName: Type.Optional(Type.String()),
+    commit: Type.Optional(Type.Unknown()),
+    annotations: Type.Optional(Type.Unknown()),
+    readOnly: Type.Optional(Type.Boolean()),
+}, { additionalProperties: true, });
+export const ProjectGitTagsSchema = Type.Array(ProjectGitTagSchema);
+/**
+ * Paginated commit log. `nextCommit` is the cursor DSS expects back to fetch
+ * the following page; entries stay unpinned because commit payloads vary.
+ */
+export const ProjectGitLogResultSchema = Type.Object({
+    entries: Type.Array(Type.Unknown()),
+    nextCommit: Type.Optional(Type.String()),
+}, { additionalProperties: true, });
+/**
+ * Diff between two revisions. Stable fields are documented in the DSS 14.7.3
+ * source; DSS additionally returns extension fields, which are preserved by
+ * `additionalProperties: true`.
+ */
+export const ProjectGitDiffResultSchema = Type.Object({
+    commitFrom: Type.Optional(Type.Unknown()),
+    commitTo: Type.Optional(Type.Unknown()),
+    addedLines: Type.Optional(Type.Number()),
+    removedLines: Type.Optional(Type.Number()),
+    changedFiles: Type.Optional(Type.Number()),
+    entries: Type.Optional(Type.Array(Type.Unknown())),
+}, { additionalProperties: true, });
+export const ProjectGitLibrarySchema = Type.Object({
+    repository: Type.Optional(Type.String()),
+    login: Type.Optional(Type.String()),
+    pathInGitRepository: Type.Optional(Type.String()),
+    localTargetPath: Type.Optional(Type.String()),
+    checkout: Type.Optional(Type.String()),
+    addToPythonPath: Type.Optional(Type.Boolean()),
+}, { additionalProperties: true, });
+export const ProjectGitLibrariesSchema = Type.Array(ProjectGitLibrarySchema);
+/** Handle returned by Git operations that run asynchronously as a DSS future. */
+export const ProjectGitFutureResponseSchema = Type.Object({
+    jobId: Type.String(),
+}, { additionalProperties: true, });
+export const ProjectGitFutureStateSchema = Type.Object({
+    jobId: Type.Optional(Type.String()),
+    hasResult: Type.Optional(Type.Boolean()),
+    result: Type.Optional(Type.Unknown()),
+    alive: Type.Optional(Type.Boolean()),
+    aborted: Type.Optional(Type.Boolean()),
+    abortable: Type.Optional(Type.Boolean()),
+    unknown: Type.Optional(Type.Boolean()),
+    startTime: Type.Optional(Type.Number()),
+    runningTime: Type.Optional(Type.Number()),
+    error: Type.Optional(Type.Unknown()),
+}, { additionalProperties: true, });
+// ---------------------------------------------------------------------------
 // Array wrappers (for runtime validation of list() responses)
 // ---------------------------------------------------------------------------
 export const ProjectSummaryArraySchema = Type.Array(ProjectSummarySchema);

package/plugin.json

@@ -0,0 +1,15 @@
+{
+	"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+	"name": "dataiku-sdk",
+	"version": "1.0.0",
+	"description": "Dataiku DSS SDK and agent-oriented CLI for programmatic access to DSS REST APIs.",
+	"homepage": "https://github.com/clssck/dataiku-sdk",
+	"repository": "https://github.com/clssck/dataiku-sdk",
+	"license": "MIT",
+	"keywords": [
+		"dataiku",
+		"dss",
+		"cli",
+		"agent-skills"
+	]
+}