@arbidocs/cli 0.4.74 → 0.4.76

package/CHANGELOG.md

@@ -1,5 +1,39 @@
 # Changelog
 
+## v0.4.76
+
+[compare changes](https://github.com/arbicity/ARBI-frontend/compare/v0.4.75...HEAD)
+
+### 🚀 Enhancements
+
+- **blocks:** Linked workflows through step signals ([25280c1e6](https://github.com/arbicity/ARBI-frontend/commit/25280c1e6))
+
+### 💅 Refactors
+
+- **blocks:** Use the generated TaskPlanStep.signals ([b1cfb26ec](https://github.com/arbicity/ARBI-frontend/commit/b1cfb26ec))
+
+### 🏡 Chore
+
+- Merge main into feat/workflow-signals ([974839985](https://github.com/arbicity/ARBI-frontend/commit/974839985))
+- Regenerate OpenAPI schema ([ad642fedf](https://github.com/arbicity/ARBI-frontend/commit/ad642fedf))
+
+## v0.4.75
+
+[compare changes](https://github.com/arbicity/ARBI-frontend/compare/v0.4.74...HEAD)
+
+### 🚀 Enhancements
+
+- **databases:** Notion/Airtable-style databases page on @arbidocs/blocks ([a3ba6b7f5](https://github.com/arbicity/ARBI-frontend/commit/a3ba6b7f5))
+- **databases:** Global Databases row behind the custom_databases experiment ([78e8f5178](https://github.com/arbicity/ARBI-frontend/commit/78e8f5178))
+
+### 🩹 Fixes
+
+- **databases:** Keep the add-column button in view and scroll to a new column ([cac1e5a09](https://github.com/arbicity/ARBI-frontend/commit/cac1e5a09))
+
+### 🏡 Chore
+
+- Update OpenAPI schema (databases) ([13ae57efd](https://github.com/arbicity/ARBI-frontend/commit/13ae57efd))
+
 ## v0.4.74
 
 [compare changes](https://github.com/arbicity/ARBI-frontend/compare/v0.4.73...HEAD)

package/SKILL.md

@@ -61,7 +61,7 @@ Scripting notes:
 
 ## For Automations / AI Agents
 
-- **Structured output (`--json`)**: supported on `status`, `config show`, `health`, `models`, `workspaces`, `workspace users`, `workspace current`, `docs`, `convo` (or `convo list`), `tags` (or `tags list`), `contacts` (or `contacts list`), `find`, `settings get`, `task list` / `task status` / `task result`, `agent list`, `session list`, `dm list`, `notifications list`, `local ls` / `local find` / `local cat` / `local tree`, `update --check`, `register --non-interactive`, `ask -b`, `upload`, `watch`. Use it whenever parsing output. `docs` also supports `--csv`, `--ids`, and `--count`. `arbi ask --json` without `-b` errors out — streaming mode is prose, not JSON; pass `-b` to get a background task ID, then `arbi task result --json`.
+- **Structured output (`--json`)**: supported on `status`, `config show`, `health`, `models`, `workspaces`, `workspace users`, `workspace current`, `docs`, `convo` (or `convo list`), `tags` (or `tags list`), `contacts` (or `contacts list`), `find`, `settings get`, `task list` / `task status` / `task result`, `agent list`, `session list`, `dm list`, `notifications list`, `local ls` / `local find` / `local cat` / `local tree`, `update --check`, `register --non-interactive`, `ask -b`, `upload`, `watch`, `workflow list` / `create` / `run` / `update`, `run start` / `run steps` / `run step`. Use it whenever parsing output. `docs` also supports `--csv`, `--ids`, and `--count`. `arbi ask --json` without `-b` errors out — streaming mode is prose, not JSON; pass `-b` to get a background task ID, then `arbi task result --json`.
 - **Human table output is lossy**: table rows may contain status glyphs (`●`, `🟩`, etc.) and emoji, and column widths truncate content. Never parse tables — always pass `--json`.
 - **Exit codes**:
   - `0` success
@@ -149,9 +149,9 @@ Footnote-style rendering at the end of the answer is currently not supported —
 - **Persistent agents**: `arbi agent create --name <n> -w <ws-id>` creates a child identity the parent can delegate to (printed email+password). Share workspace IDs via `-w` rather than the interactive picker when running non-interactively.
 - **Agent-create errors**: `agent-create` rejects non-`agent-*` emails with a clear message. If you see "No verification record found" the account probably already exists — use `arbi login` instead.
 
-## Workspace automations
+## Workflows
 
-`arbi automation` is an alias for `arbi workflow`. Triggers are run now (no trigger flags), a schedule (`--run-at` or `--rrule`), or a notification (`--event-kind`, optional `--event-filter` JSON). `run <wfl-id>` starts any saved action now. Scheduled document actions require an assistant with standing workspace access (`--agent <agt-id> --auth-mode scheduled_permanent`). Do not silently grant that access.
+A workflow starts by hand (no trigger flags), on a schedule (`--run-at` or `--rrule`), on an event (`--event-kind`, optional `--event-filter` JSON), or after a task (`--after <con-id>`). It runs a prompt, a skill, a document action, or named steps (`--steps <file>`). `arbi automation` is an alias for `arbi workflow`. `run <wfl-id>` starts any saved workflow now. Scheduled document actions require an assistant with standing workspace access (`--agent <agt-id> --auth-mode scheduled_permanent`). Do not silently grant that access.
 
 ```bash
 # Daily annotation review of documents currently carrying a label.
@@ -163,7 +163,44 @@ arbi automation runs wfl-example --json
 arbi automation update wfl-example --file changes.json
 ```
 
-Document actions return `execution_id` and do not require a conversation. Execution history includes status, selected documents, a run label, errors and result metadata. Annotation answers/citations remain document annotation fields; emails report delivery metadata. Chat/prompt actions retain their linked conversation history. `--overwrite` regenerates existing annotation answers; the default preserves them. Label selection is resolved at execution time rather than frozen when creating the rule. `arbi task` still refers to local background ask requests, not workspace automations.
+Document actions return `execution_id` and do not require a conversation. Execution history includes status, selected documents, a run label, errors and result metadata. Annotation answers/citations remain document annotation fields; emails report delivery metadata. Chat/prompt actions retain their linked conversation history. `--overwrite` regenerates existing annotation answers; the default preserves them. Label selection is resolved at execution time rather than frozen when creating the rule. `arbi task` still refers to local background ask requests, not workflows.
+
+### Stepped workflows (forms, agent steps, reviews)
+
+A stepped workflow's steps are a list in the API's `TaskPlanStep` shape, in a `.json`, `.yaml` or `.yml` file (a list, or an object with `steps`). Fields: `id` (lowercase, `[a-z][a-z0-9_-]*`), `title`, `kind` (`form` | `upload` | `agent` | `review`), `after` (step ids it waits for; default the step before it, `[]` = at the start), `prompt` or `skill` (agent steps only; `{{field}}` fills from the run's inputs), `inputs` (a skill step's input templates), `branch` (agent steps), `ui` (what the app shows: a form's `fields` as `{name, type, label, required}`, a review's `instructions`). The CLI checks the file before sending it and lists every problem (`steps[1].kind: must be one of …`).
+
+```yaml
+# steps.yaml
+- id: brief
+  title: Brief
+  kind: form
+  ui:
+    fields:
+      - { name: client, type: text, label: Client, required: true }
+      - { name: topic, type: longtext, label: What to cover }
+- id: draft
+  title: Draft the note
+  kind: agent
+  prompt: Write a short client note for {{client}} about {{topic}}.
+- id: approve
+  title: Approve the note
+  kind: review
+  ui: { instructions: Check the note before it goes out }
+```
+
+```bash
+arbi workflow create --name 'Client note' --steps steps.yaml --json   # add --rrule/--event-kind/--after to trigger it
+arbi workflow update wfl-example --steps steps.yaml                   # replace its steps
+arbi workflow run wfl-example                                         # prints the run's thread id (con-…)
+arbi run steps con-example --json                                     # each step: pending | ready | running | done | skipped | failed
+arbi run step con-example brief complete --input client=Acme --input topic='Q3 results'
+arbi run steps con-example --watch --answers                          # poll while an agent step runs, print its answer
+arbi run step con-example approve complete                            # a review: completing it approves
+arbi run step con-example draft skip                                  # skip any step (e.g. a failed agent step)
+arbi run start --steps steps.yaml --title 'Acme note' --input client=Acme   # a one-off run, no saved workflow
+```
+
+`arbi run steps --json` gives `waiting_on` (`person` | `agent` | `finished` | `stuck`) and per step `state`, `after`, `answer_id` (a done agent step's message in the thread) and `error`; with `--answers` each done agent step also has `answer` (its text). `--watch` polls (`--interval`, default 3s) until the run stops waiting on an agent step (`--timeout`, default 600s; `timed_out` in the JSON). A form step's required fields are checked before completing it. Agent steps run themselves: they can only be skipped.
 
 In the terminal UI: `/automations` lists rules; `/automation view|run|runs|pause|resume|delete <wfl-id>` manages them; `/automation create <JSON>` and `/automation update <wfl-id> <JSON>` accept the same request bodies as the SDK.