@yansirplus/client
v0.6.4
Published
<!-- generated by packages/cli/src/generate/generate-docs.mjs; edit docs/surface.json and docs/packages/client.md -->
Readme
@yansirplus/client
Purpose
Framework-neutral agent client store contract, typed command surface, and optional React/Svelte subpath bridges.
Public API Status
0.6.x active development. Public exports are listed in PUBLIC_API.md to prevent accidental exports; the package owns the transport-neutral root client state machine and optional React/Svelte subpaths.
Audience
| Entrypoint | Audience | Capability |
| --------------------------------------- | ---------------------------------- | ------------------------------------------------------------------------------------ |
| @yansirplus/client | default-direct | transport-neutral client store and runtime ledger stream decoder |
| @yansirplus/client/react | default-direct | React client adapter |
| @yansirplus/client/svelte | default-direct, generated-only | Svelte client adapter |
| @yansirplus/client/product-shell-client | default-direct | product-shell client composition for product commands plus runtime ledger projection |
| @yansirplus/client/workspace-agent | generated-only | generated workspace agent client |
Invariant
The package root owns transport-neutral state and command orchestration. It
consumes runtime-protocol Recorded projections and injected transports; it does
not import React, Svelte, AG-UI framework adapters, or product UI code. React
and Svelte bridges live only behind @yansirplus/client/react and
@yansirplus/client/svelte.
Minimal Usage
import { createAgentClient, selectAgentClientSnapshot } from "@yansirplus/client";
const agent = createAgentClient({ streamSource, rpcInvoker });
const status = selectAgentClientSnapshot(agent, (snapshot) => snapshot.run.status);Framework consumers import explicit subpaths:
import { useClientStore } from "@yansirplus/client/react";
import { selectClientReadable } from "@yansirplus/client/svelte";The store contract is the bridge point for framework subpaths. The client root
owns reconnect/replay state, Recorded runtime-event snapshots, symbolic
ContinuationRef/InputRequestRef lifecycle, and a generic command invoker; browser
direct transports and server bridges supply only streamSource and rpcInvoker.
Verification
cd packages/client
vp test run