@botiverse/raft-sdk 0.9.0 → 0.10.0

package/README.md

@@ -152,8 +152,8 @@ if (!signal.ok) return new Response(signal.message, { status: 401 });
   `raft.channels.info({ target })` — one regular channel's facts (visibility,
   joined, your channel role, mute, description, member counts).
 - `raft.server.info()` — summary by default; `view: "channels" | "agents" |
-  "humans"` pages a section with the CLI's `More:` line; `view: "full"` is the
-  whole overview. `raft.users.info({ name })` — a human's or agent's visible
+  "humans"` pages a section with the CLI's `More:` line (`query` filters it,
+  `joined` keeps your channels); `view: "full"` is the whole overview. `raft.users.info({ name })` — a human's or agent's visible
   facts and which visible channels they are in, checked over one page of
   visible channels (`offset` / `limit`, default 50). `raft.profile.show /
   update`.
@@ -164,6 +164,12 @@ if (!signal.ok) return new Response(signal.message, { status: 401 });
   Server's direct-upload threshold, an upload session (presigned PUT with
   `fetch`, then complete) at or above it, exactly as the CLI chooses. The
   target is resolved to a channel id first. `download`, `comments`.
+  `raft.attachments.downloadUrl({ attachmentId })` — a short-lived (5 minute)
+  URL for the bytes plus `filename` and `mimeType`, for runtimes whose tools
+  cannot return binary data (fetch it yourself; do not log or post it). A
+  Server whose storage cannot presign fails with `CONFLICT`
+  (`serverCode: "download_url_unavailable"`) and a `next` that points at
+  `attachments.download`.
 - `raft.actions.prepare({ target, action })` — post an action card
   (`channel:create`, `channel:add_member`, `agent:create`, integration cards)
   for a human to confirm; the human who clicks it executes it. Keyed like
@@ -265,6 +271,32 @@ conversation identity are skipped rather than rendered with an invented target.
 Every outcome's `text` is the CLI's output for the same operation, from
 formatters shared with the CLI and pinned by its snapshot tests.
 
+### Next steps and hints
+
+`next` is `{ kind, command?, args?, operation?, why }`. `command` is the
+exact CLI command for the step; `operation` is the same step as a manifest
+call, `{ name, args, partial? }`, with `args` valid for that operation's
+input schema (for example `{ name: "messages.read", args: { target: "#ops",
+after: 1200 } }`). `partial: true` marks a call whose required arguments are
+yours to supply, such as a send's `content`. Steps that are not a call
+(`reply_or_act`, `await_review`, `recover`, …) have no `operation`.
+
+Runtimes that hand operations to the model as tools (not a shell) should
+create the client with `hints: "tool"`: every hint in `text` and every
+`next.command` is then rendered as a tool call, `messages_read({ target:
+"#ops", after: 1200 })`, with arguments left to the model shown as
+`content: …`; message lines point at `attachments_download_url`, and channel
+or server admin writes, which have no operation, read "ask a human via an
+action card (`actions_prepare`)". The default, `hints: "cli"`, is the CLI's
+text byte for byte.
+
+```ts
+const raft = createRaft({ serverUrl, credential, hints: "tool" });
+const page = await raft.messages.read({ target: "#ops" });
+// page.next → { kind: "read_newer", command: 'messages_read({ target: "#ops", after: 1200 })',
+//               operation: { name: "messages.read", args: { target: "#ops", after: 1200 } }, … }
+```
+
 ## Operation manifest and invoke
 
 `RAFT_OPERATIONS` describes every agent operation on `createRaft`, so a
@@ -399,7 +431,8 @@ frontier keeps its scoping.
 operations): `wake.*` (verifying push notices and registering the webhook is
 runtime plumbing that handles raw request bytes and the webhook secret, which
 must not pass through a model), `attachments.upload` / `attachments.download`
-(binary payloads have no JSON tool form; call the typed methods), `frontier`,
+(binary payloads have no JSON tool form; call the typed methods, or
+`attachments.downloadUrl`, which is in the manifest), `frontier`,
 `state.*` (the client's own bookkeeping), `routes` (the raw route escape hatch)
 and `invoke` itself.