@vinaverse/client 0.1.0-alpha.10 → 0.1.0-alpha.11

package/README.md

@@ -139,7 +139,8 @@ app comes back to the foreground).
 **Your backend, in two lines** (`@vinaverse/client/backend`): `backendFromFetch({ routes, headers })` is an
 `AgentBackend` over your own routes, sending the person's credentials from `headers`, never in a body.
 `backendRoutes(base)` gives the routes the .NET SDK's `MapVinaverseAgentSessions` serves by default (`session`,
-`refresh`, `status`, `feedback`, `end`, `context`, `delete`); give your own where they differ. Both sides speak
+`refresh`, `status`, `feedback`, `end`, `context`, `delete`, and history's `list` and `read`, answered
+`{ version: 1, page }` as the gateway wrote the page); give your own where they differ. Both sides speak
 `vinaverse.agent-backend/1` (vinaverse-contracts `docs/agent-backend.md`, tested here against its fixture): successes
 wrapped with the version (`{ version: 1, session }`, `{ version: 1, client_secret: { value, expires_at } }`,
 `{ version: 1, status }`, or 204), and one failure body for every route. Every session creation (a first open, a
@@ -192,8 +193,23 @@ For a mock mode and tests, `@vinaverse/client/testing` has a scripted agent:
 `createMockAgent({ script, reply, refuse, welcome })` gives an `AgentBackend` and a WebSocket factory that speaks the
 protocol (`conversation.transport.webSocket`). `script` is the replies in order, one per turn, each with its text, its
 cards or a failure; `reply` answers after it. `mockCards` gives the cards your tools would: `professional`,
-`workspace`, `timeSlots`, `proposal` (pending, confirmed in your app) and `links`. Scripted history comes with the
-runtime's history.
+`workspace`, `timeSlots`, `proposal` (pending, confirmed in your app) and `links`. `history` scripts past
+conversations (`{ id, title, state, items: [{ role, text, refusal? }, { card, proposal_outcome? }] }`): listed, read
+back, continued with their messages, deleted (then `not_found`); a conversation begun in the mock is listed too once
+something was said.
+
+**History** (`@vinaverse/client/history`, an entry of its own): `createAgentHistory({ runtime, mode, scope, agent,
+pageSize })` is the person's past conversations, newest activity first, a page at a time (`refresh`, `loadMore`, and
+`retry` for the page that failed, the first or the next; `failure` says `off` when your backend serves no
+`listConversations`; a cursor the gateway no longer takes, refused `unavailable` with its `invalid_request`, starts the
+list over once, and any other refusal is said); `remove(key, id)` deletes through `runtime.deleteConversation` and drops
+the row, one already gone too. `createAgentTranscript({ runtime, conversationId })` reads one back, the newest page
+first and earlier pages prepended (`load`, `loadEarlier`, `retry`; a stale cursor reads back from the newest page
+once), its items as the kits draw them (`historyItems`: messages
+as sent, a cut-off reply and a guardrail's refusal kept, cards restored and inert, a proposal with the outcome it
+had). `continueKey(conversation, subject)` is the key it continues under (its side and business as bound when it
+started), for `runtime.continue` and `deleteConversation`. Nothing begun before a sign-out lands after it
+(`runtime.epoch()`), nor a page from before a newer read.
 
 The contract's types are exported too (`paths`, `components`, `operations`, `Schemas`): import them instead of copying
 the spec. Design: [docs/architecture/agent-runtime.md](../../docs/architecture/agent-runtime.md).

package/dist/agent/index.cjs

@@ -3126,6 +3126,8 @@ function createAgentRuntime(options) {
     },
     getStatus: () => status?.value ?? null,
     getStatusState: () => statusState,
+    backend,
+    epoch: () => generation,
     getName: () => sessionName ?? status?.value.displayName ?? null,
     subscribe(listener) {
       listeners.add(listener);