@onetaskgraph/sdk 0.2.45 → 0.2.47

package/README.md

@@ -26,6 +26,22 @@ schemas generated from `onetaskgraph schema` before returning it. Query response
 their `plan` and typed `errors`; exit code 4 therefore resolves to the validated partial
 response instead of discarding the successful sources.
 
+Every invocation also passes `--no-interactive`, so no call ever waits on a prompt: a
+template variable nothing answers takes its default, and a required one left unanswered is
+refused with exit 2. `templateRender(file, { searchPath, answers, vars })` hands `answers`
+to the binary on standard input, and `vars` outrank them as `--var NAME=VALUE`.
+
 Run `bun run --cwd sdks/typescript generate` after changing the binary contract. The gate's
 `./scripts/nx.sh run sdk-typescript:generate-check` target builds the binary and then fails
 naming any generated file that would change.
+
+`taskCreate(source, project, title, { template, answers })` and `documentCreate(...)` create
+an item from a template file — or from `templateLoader` (the path of a loader document naming
+what to render), or from a plain `body` or `bodyFile` — and answer as `taskShow` and
+`documentShow` do; a rendered item records its `onetaskgraph.template` provenance, whose shape
+is the `TemplateProvenance` type. `taskRender(id, ...)` and `documentRender(id, ...)`
+regenerate one in place from its stored answers, with `answers`, `vars` and `unset` laid over
+them; `taskAnswers(id)` and `documentAnswers(id)` answer with the stored `TemplateAnswers`.
+`templateVariables` and `templateRender` take `{ templateLoader }` in place of a file. A
+`body` and `answers` are never passed together — both would go to the binary's one standard
+input — so the call is refused instead.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@onetaskgraph/sdk",
   "//": "llmlint: ignore-file[projects_stay_in_one_js_workspace] This package IS the JS workspace's one member; what the rule reads as a second is the optionalDependency below, which is the published launcher an end user installs beside the SDK and resolves from the registry at their own install. `workspace:*` names nothing there, and npm/cli is not a workspace member for the reason its own manifest records. scripts/set-version.sh writes this number and `--check` refuses any other, under distribution-check. JSON has no comment to scope this to the one line.",
-  "version": "0.2.45",
+  "version": "0.2.47",
   "description": "The TypeScript SDK for onetaskgraph, generated from the binary's own JSON Schema bundle.",
   "license": "MIT",
   "type": "module",
@@ -28,7 +28,7 @@
     "generate:check": "bun scripts/generate.ts --check"
   },
   "optionalDependencies": {
-    "@onetaskgraph/cli": "0.2.45"
+    "@onetaskgraph/cli": "0.2.47"
   },
   "devDependencies": {
     "ajv": "8.17.1",