onetaskgraph-sdk

The typed Python client for onetaskgraph. Its request vocabulary, response models, and method surface are generated from the JSON Schema and command help emitted by the real binary; the workspace's just lint rejects committed output that has drifted.

import asyncio
from onetaskgraph_sdk import Client

tasks = asyncio.run(Client().task_list(status=["todo"]))

Each async call runs one binary subprocess and validates its JSON response. The executable is resolved in this order: the binary= constructor argument, the ONETASKGRAPH_SDK_BINARY environment variable, then the onetaskgraph executable supplied on PATH by the packaged binary distribution. Pass cwd= to select the directory from which configuration is discovered. Partial query exit status 4 is parsed and returned, so callers can inspect each typed SourceFailure; other non-zero statuses raise OnetaskgraphError with the exit code, and with the failure document the binary wrote as its failure — so a caller branches on failure.kind — or None when it wrote none.

Every call 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 raises with exit code 2. template_render(file, search_path=..., answers={...}, var=[...]) hands the answers mapping to the binary on standard input, and each var (NAME=VALUE) outranks it.

task_create(source, project, title, template=..., answers={...}) and document_create(...) create an item from a template file — or from template_loader= (the path of a loader document naming what to render), or from a plain body= — and answer as task_show and document_show do; the item records its onetaskgraph.template provenance, which TemplateProvenance reads. task_render(id, ...) and document_render(id, ...) regenerate one in place from its stored answers, with answers, var and unset laid over them, and answer with a Regenerated; task_answers(id) and document_answers(id) answer with the stored TemplateAnswers. template_variables and template_render take template_loader= 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 raises TypeError instead.