# @happyvertical/smrt-svelte
## Board
`@happyvertical/smrt-svelte/board` provides a generic, accessible Svelte 5
Kanban-style board. It has no project, sales, or support dependency: supply
your own cards, columns, card-to-column getter/setter, and typed card snippet.
`cards` is controlled; `defaultCards` enables local state. `onmove` receives a
typed intent and can be async—rejections restore the previous view. Set
`optimistic` to present controlled moves while persistence is pending.
Set `allowSameColumnReorder={false}` when an adapter persists only lane/status
transitions rather than a position within a lane.
```svelte
card.stage}
setCardColumnId={(card, stage) => ({ ...card, stage })}
getCardLabel={(card) => card.subject}
card={cardSnippet}
onmove={({ card, target }) => save({ ...card, stage: target.columnId })}
/>
```
The same primitive can represent support queues (`card.queue`) or a sales
pipeline (`opportunity.stage`) without importing `@happyvertical/smrt-projects`.
Svelte 5 component library for the s-m-r-t framework. Provides UI components, browser AI integration (STT/TTS/LLM with warm cache), a theme system, permission-aware rendering, and module UI registry for agent admin panels.
## Installation
```bash
pnpm add @happyvertical/smrt-svelte
```
## Data-surface browser bridge security
The browser bridge is a transport adapter, not an authentication system.
Configure it only with a session/source binding established by the server and
use a transport that supplies verified peer metadata. It accepts commands only
from the configured server peer and emits acknowledgements/events only on the
bound route; wire `sessionId` and `source` fields must never be treated as
proof of identity.
The adapter canonicalizes requests and applies the shared identifier limit
from `@happyvertical/smrt-ui/data-surface` along with bounded envelopes before
calling the registry. The registry remains the authority for command
authorization and execution. Command IDs are idempotent while their bounded
replay entries are retained; concurrent same-signature requests coalesce, a
conflicting signature is rejected, and replay-capacity exhaustion is reported
explicitly. Malformed requests and unauthenticated peers are ignored before an
acknowledgement; valid requests that expire or encounter disconnect and
transport failures produce bounded protocol outcomes without exposing registry
state.
## Usage
### Query-backed data surfaces
Use the web binding when a table should render one remote page instead of
hydrating its whole collection. It exposes `rows`, `page`, `total`,
`loading`, `refreshing`, `stale`, `error`, `retry`, `lastUpdated`, and the
latest applied `result`. The result getter also follows query-scoped live
replacements, so consumers can keep envelope metadata in sync with the rows.
```svelte
{#if view.loading}Loading…
{/if}
{#each view.rows as row (row.id)}{row.name}
{/each}
```
### Provider Setup
```svelte
{@render children()}
```
The Provider can own generated WebMCP tools for the same lifecycle. Its policy
is identical to `registerWebMcpTools`; omitted `effects` exposes reads only:
```svelte
{@render children()}
```
This controls capability exposure, not authorization. Tool execution still
crosses the authenticated REST boundary and must retain its auth and tenancy
guards. The `effects`, `filter`, and `filterTool` policy applies to generated
data/model tools only; the fixed mounted-UI adapter has the separate controls
described below.
WebMCP test doubles and polyfills should implement the browser's
promise-returning `document.modelContext.registerTool()` contract; declare the
function `async` when migrating older void-returning fixtures.
### Mounted UI through WebMCP
`` registers six fixed `smrt_ui_*` tools for the mounted UI:
list, inspect, and execute for form controls and data surfaces. The tool set does
not change as components mount and unmount; each call reads the current
transport-neutral registries instead of inspecting or simulating the DOM.
Forms automatically join the Provider's control registry. An explicit Form
`interactionRegistry` still takes precedence. Pass the same data-surface
registry used by `DataTable` or `CollectionToolbar` when those mounted surfaces
should be discoverable:
```svelte
{@render children()}
```
The default prefix is `smrt_ui_`. Configure `ui.prefix` when multiple Providers
must coexist in one document; the same prefix cannot be registered twice. The
six derived names are reserved through the document-global tool-name lock, so
a generated model tool, a view intent, or a `useWebMcpTool` tool that would
take one of them under your prefix fails at registration with a message naming
the tool and its current owner, rather than being silently dropped by the
browser.
`ui: false` disables only the fixed UI adapter while leaving generated model
tools enabled. For compatibility, an object config that omits `ui` continues to
enable only generated model tools; use `webmcp={true}` or provide `ui: {}` to
enable the mounted-UI adapter.
Form commands always run with `source: 'agent'`. WebMCP input cannot assert
confirmation: staging is allowed by the registry policy, while apply, clear,
and undo require a separate human-confirmed path. Secret control values and
hidden data-surface columns are not serialized. Read responses are marked as
untrusted content. Bespoke `useWebMcpTool` and `