feat: deliver Python workflow client
This commit is contained in:
@@ -22,6 +22,15 @@ The durable product path is now `wf-rpc-server` plus neutral `wf_config` /
|
||||
`wf_server` composition. The old `wf-mcp` script remains a legacy/special-purpose
|
||||
MCP entrypoint and compatibility surface.
|
||||
|
||||
Completed: the async `wf_client` Python slice is verified against the real
|
||||
JSON-RPC ASGI application. It covers capability discovery, local graph
|
||||
authoring, remote validation, immutable artifact save, deployment selection,
|
||||
and durable run execution. Rich client objects have bounded, secret-safe
|
||||
`repr()` and `_repr_html_()` views that never perform remote I/O. Draft
|
||||
workspaces remain a separate server/admin surface and are not part of the
|
||||
client; server registration is explicit so the artifact -> deployment -> run
|
||||
path does not require draft storage.
|
||||
|
||||
## Active Initiative: Workflow Console And Defense Demo
|
||||
|
||||
The next product-facing push is a local-first web console and defense demo that
|
||||
|
||||
Reference in New Issue
Block a user