@vendian/cli 0.0.6 → 0.0.8

package/README.md

@@ -6,6 +6,8 @@ Command-line tools for signing in to Vendian and running local agent workflows.
 npm install -g @vendian/cli
 vendian
 vendian login
+vendian init --output-dir ./agents
+vendian create "My Agent" --output-dir ./agents
 vendian cloud local serve --agents-dir ./agents
 ```
 
@@ -16,6 +18,11 @@ vendian
 vendian login
 vendian doctor
 vendian update
+vendian init --output-dir ./agents
+vendian create "My Agent" --output-dir ./agents
+vendian validate ./agents/my-agent --runtime
+vendian test ./agents/my-agent --dry-run --mock-credentials
+vendian models
 vendian cloud local serve --agents-dir ./agents
 ```
 
@@ -32,6 +39,13 @@ managed runtime without changing your agents.
 After login, regular `vendian cloud ...` commands are forwarded to the managed
 runtime installed by the CLI.
 
+Agent authoring commands are also forwarded to the managed Python SDK CLI.
+`vendian init` writes the current SDK-owned authoring docs into `.vendian-docs/`,
+and `vendian create` scaffolds agents from the SDK templates. Updating the
+managed runtime refreshes these docs and templates with the Python SDK. The CLI
+remembers workspaces initialized with `vendian init` and refreshes their
+`.vendian-docs/` automatically after `vendian update` or a managed auto-update.
+
 ## Local Data
 
 Vendian stores its managed runtime and CLI state under your user profile:

package/bin/vendian.cjs

@@ -1,2 +1,6 @@
 #!/usr/bin/env node
-require('../cli-wrapper.cjs');
+import('../cli-wrapper.mjs').catch((error) => {
+  const message = error && typeof error.message === 'string' ? error.message : String(error);
+  console.error(`[vendian] ${message}`);
+  process.exitCode = 1;
+});