@uru-intelligence/cli 0.3.53 → 0.3.55

package/README.md

@@ -13,7 +13,12 @@ bun src/index.ts whoami --json
 bun src/index.ts switch <workspace-id>
 ```
 
-The CLI is registry-backed. Dedicated Gem/Library/Dataset commands are thin adapters over the same platform tools used by MCP and the web UI; broader workspace, automation, prompt/persona/context, sharing, web/file, business SQL, secret/env/token operations are exposed through the generated operation registry while dedicated UX commands continue to mature. The CLI does **not** reimplement Gem lifecycle sequencing client-side.
+The CLI is registry-backed. Dedicated Gem/Library/Dataset/Automation commands
+are thin adapters over the same platform tools used by MCP and the web UI;
+broader workspace, prompt/persona/context, sharing, web/file, business SQL,
+secret/env/token operations remain exposed through the generated operation
+registry while dedicated UX commands continue to mature. The CLI does **not**
+reimplement Gem lifecycle sequencing client-side.
 
 ## Current commands
 
@@ -49,11 +54,29 @@ bun src/index.ts gems write 'library/Golden Gems/My Gem.gem' main.html --file ./
 bun src/index.ts library ls library
 bun src/index.ts library search revenue
 bun src/index.ts library mkdir 'library/Golden Gems'
-bun src/index.ts datasets query revenue_rows --limit 50 --json
+bun src/index.ts library read 'library/Contexts/Client Brief.md'
+bun src/index.ts library write 'library/Contexts/Client Brief.md' --file ./brief.md --create
+bun src/index.ts library write 'library/Prompts/Sales Email.md' --content "Draft the follow-up." --create
+bun src/index.ts library patch 'library/Prompts/Sales Email.md' --stdin
+bun src/index.ts library cp 'library/Notes/Brief.md' 'library/Archive/Brief.md'
+bun src/index.ts library mv 'library/Notes/Draft.md' 'library/Notes/Final.md'
+bun src/index.ts library rm 'library/Notes/Old.md'
+bun src/index.ts library restore 'library/Notes/Old.md'
+bun src/index.ts datasets query revenue_rows --limit 50 --response-format concise --json
 bun src/index.ts datasets get --params-json '{"dataset_id":"revenue_rows"}'
 bun src/index.ts datasets rows-upsert --params-json '{"dataset_id":"revenue_rows","rows":[{"name":"Acme"}]}'
 bun src/index.ts datasets manage-create --params-json '{"title":"Revenue Rows","data_schema":{"properties":[]}}'
 
+# Automation helpers over the platform tool surface.
+bun src/index.ts automations ls --status active --view summary
+bun src/index.ts automations get <automation-id>
+bun src/index.ts automations create "Daily revenue digest" --status draft
+bun src/index.ts automations enable <automation-id>
+bun src/index.ts automations trigger <automation-id> --input-message "Run now"
+bun src/index.ts automations runs ls <automation-id> --scope workspace --limit 20
+bun src/index.ts automations runs tail <run-id> --level warn
+bun src/index.ts automations runs cancel <run-id> --yes
+
 # Raw platform-tool escape hatch for diagnostics and parity.
 bun src/index.ts tools ls
 bun src/index.ts tools schema gem_control_plane --json
@@ -81,8 +104,9 @@ Gem version commands create immutable, build-backed versions through
 `gem_control_plane` `op=version_upload`, then deploy those version ids through
 `op=version_deploy`. Provider-internal flags such as `--runtime-provider` are
 not accepted: runtime routing is compiled server-side from the Gem contract.
-Gradual rollout percentages below 100 still fail with an explicit error until
-split traffic routing is enabled.
+Non-100 rollout percentages are accepted only with `--skip-promote` to stage
+rollout intent; live promote/rollback remains fail-closed until weighted link
+routing is enabled.
 
 The scaffold defaults to the production API (`https://api.uruintelligence.com`).
 Use `--api-url`, `URU_API_BASE`, or `URU_API_URL` to point it at staging or a local backend:
@@ -110,6 +134,8 @@ Headless environments can use device login or explicit token/API-key paths:
 - linked project state: `.uru/project.json` with `{workspaceId, gemId, libraryPath}`
 - no credentials are written to `.uru/project.json`
 - Gem-scoped deploy tokens for CI use `uru tokens create|ls|revoke`
+    - `uru tokens create` requires `--name` plus exactly one lifetime flag:
+      `--expiry <duration>` or `--expires-at <iso timestamp>`
     - created tokens default to the server-enforced `gem:deploy` scope
     - custom `--scope`/`--scopes` values must include `gem:deploy` before the token
       can operate Gem deploy/query/control routes
@@ -158,4 +184,8 @@ bun --filter=@uru-intelligence/cli run smoke:binaries          # dry-run matrix
 ```
 
 The updater command is intentionally conservative: `uru update` prints the exact
-`npm install -g @uru-intelligence/cli@latest` command instead of self-mutating the installation.
+`npm install -g @uru-intelligence/cli@latest` command instead of self-mutating
+the installation. Interactive text-mode commands also perform a bounded
+once-per-24h npm version check and write a single stderr notice when a newer CLI
+is available. The notifier is disabled for JSON/streaming output, CI,
+`NO_UPDATE_NOTIFIER`, and `URU_NO_UPDATE_NOTIFIER`.