@abloatai/ablo 0.3.0 → 0.3.1

package/CHANGELOG.md

@@ -11,7 +11,7 @@ Capability fields shed their redundant `allowed` prefix to match the surrounding
 ### Added
 
 - `DefineSchemaOptions.identityRoles?: readonly IdentityRole[]` — open registration of identity-anchored sync-group roles on `defineSchema(...)`. Each `IdentityRole` declares `{ kind, template, extract }`: a diagnostic label, a `'<prefix>:{id}'` template, and a pure extractor function from an opaque identity context to zero-or-more ids. No closed enum; consumers fully control both the template strings and the extraction logic.
-- `composeIdentitySyncGroups(identity, schema)` exported from `@ablo/sync-engine/schema` — walks the schema's registered `identityRoles`, calls each extractor, and substitutes ids into templates. Stable, deduped output. Returns `[]` when no roles are registered.
+- `composeIdentitySyncGroups(identity, schema)` exported from `@abloatai/ablo/schema` — walks the schema's registered `identityRoles`, calls each extractor, and substitutes ids into templates. Stable, deduped output. Returns `[]` when no roles are registered.
 - `Schema.identityRoles: readonly IdentityRole[]` — the registered list, accessible on every `defineSchema(...)` result.
 - New exported types: `IdentityRole`, `IdentityContext`.
 
@@ -47,7 +47,7 @@ Declarative props absorb every class of lifecycle glue; the status hook returns
 
 ### Added
 
-- `<AbloProvider>` — umbrella provider at `@ablo/sync-engine/react`. Props include data config (`schema`, `url`, `userId`, `organizationId`), auth (`capabilityToken` / `apiKey` / session cookie fallback), declarative behavior (`preventUnsavedChanges`, `lostConnectionTimeout`, `postBootstrap`), callbacks (`onSessionExpired`, `onError`, `resolveUsers`), and DI escape hatches.
+- `<AbloProvider>` — umbrella provider at `@abloatai/ablo/react`. Props include data config (`schema`, `url`, `userId`, `organizationId`), auth (`capabilityToken` / `apiKey` / session cookie fallback), declarative behavior (`preventUnsavedChanges`, `lostConnectionTimeout`, `postBootstrap`), callbacks (`onSessionExpired`, `onError`, `resolveUsers`), and DI escape hatches.
 - `<SyncGroupProvider id="matter:...">` + `useSyncGroup()` — per-entity scope context.
 - `<ClientSideSuspense fallback={...}>` — gate renders until the engine reports `connected`. Phase-1 non-Suspense; phase-2 upgrades to real Suspense.
 - `useSyncStatus()` rewritten as a tagged union: `{ name: 'initial' | 'connecting' | 'connected' | 'reconnecting' | 'disconnected' | 'needs-auth', ... }`. Impossible states are unrepresentable.
@@ -155,7 +155,7 @@ The SDK covers exactly three integration shapes. Each has a canonical example in
 
 ### Ergonomics (package-wide)
 
-- **`Ablo` class** — `import Ablo from '@ablo/sync-engine'` / `new Ablo({ schema })`. Matches `new Stripe()` / `new OpenAI()` / `new Anthropic()` pattern. `createMesh(opts)` stays available as the functional alias.
+- **`Ablo` class** — `import Ablo from '@abloatai/ablo'` / `new Ablo({ schema })`. Matches `new Stripe()` / `new OpenAI()` / `new Anthropic()` pattern. `createMesh(opts)` stays available as the functional alias.
 - **Model-scoped joins** — `ablo.matters.join(id, { label })` desugars to the generic `join`. Proxy-based so the namespace adapts to any schema. Collisions with reserved admin fields (`roles`, `members`, `audit`, `capabilities`) throw at construction time.
 - **Flat scope form** — `scope: { matters: id }` alongside the array form.
 - **`as` alias** — `{ as: session({...}) }` replaces the security-jargon `onBehalfOf`; both still accepted.
@@ -199,7 +199,7 @@ Initial release.
 - **AI Agent SDK**: `SyncAgent` for backend/AI agent participation as first-class sync citizens
 - **Pluggable auth**: `AuthProvider` interface with built-in API key, JWT, and session providers
 - **Security**: IndexedDB cleanup on session expiry and sync group revocation
-- **Testing utilities**: `@ablo/sync-engine/testing` subpath with mocks, fixtures, and harness
+- **Testing utilities**: `@abloatai/ablo/testing` subpath with mocks, fixtures, and harness
 
 ### Test Coverage
 

package/README.md

@@ -13,7 +13,7 @@ schema -> ablo.<model>.create/load/edit/update(...)
 ## Install
 
 ```bash
-npm install @ablo/sync-engine
+npm install @abloatai/ablo
 ```
 
 Requires Node 22+ and TypeScript 5+.
@@ -33,8 +33,8 @@ provider. Do not ship `ABLO_API_KEY` in a browser bundle.
 ## Quick Start
 
 ```ts
-import Ablo from '@ablo/sync-engine';
-import { defineSchema, model, z } from '@ablo/sync-engine/schema';
+import Ablo from '@abloatai/ablo';
+import { defineSchema, model, z } from '@abloatai/ablo/schema';
 
 const schema = defineSchema({
   weatherReports: model({

package/docs/api-keys.md

@@ -3,14 +3,14 @@
 Trusted runtimes authenticate with an API key.
 
 ```ts
-import Ablo from '@ablo/sync-engine';
+import Ablo from '@abloatai/ablo';
 
 const ablo = Ablo({ apiKey: process.env.ABLO_API_KEY });
 ```
 
 The key identifies the Ablo account. Application code does not pass an organization id; Ablo derives scope from the credential.
 
-Use the root `@ablo/sync-engine` import with a schema for app clients.
+Use the root `@abloatai/ablo` import with a schema for app clients.
 
 ## Server-Side API Keys
 

package/docs/api.md

@@ -7,8 +7,8 @@ agents, read [Integration Guide](./integration-guide.md).
 
 
 ```ts
-import Ablo from '@ablo/sync-engine';
-import { defineSchema, model, z } from '@ablo/sync-engine/schema';
+import Ablo from '@abloatai/ablo';
+import { defineSchema, model, z } from '@abloatai/ablo/schema';
 
 const schema = defineSchema({
   tasks: model({
@@ -171,7 +171,7 @@ Use `dataSource(...)` only when the customer's app database remains canonical
 and Ablo should call a signed endpoint instead of storing customer rows itself.
 
 ```ts
-import { dataSource } from '@ablo/sync-engine';
+import { dataSource } from '@abloatai/ablo';
 import { schema } from './ablo.schema';
 
 export const POST = dataSource({

package/docs/capabilities.md

@@ -104,7 +104,7 @@ behalf-of).
 ## Create
 
 ```ts
-import Ablo from '@ablo/sync-engine';
+import Ablo from '@abloatai/ablo';
 
 const admin = Ablo({ apiKey: process.env.ABLO_API_KEY });
 

package/docs/client-behavior.md

@@ -5,8 +5,8 @@ This page covers the SDK behavior around options, errors, retries, and runtimes.
 ## Constructor
 
 ```ts
-import Ablo from '@ablo/sync-engine';
-import { defineSchema, model, z } from '@ablo/sync-engine/schema';
+import Ablo from '@abloatai/ablo';
+import { defineSchema, model, z } from '@abloatai/ablo/schema';
 
 const schema = defineSchema({
   tasks: model({
@@ -152,7 +152,7 @@ All SDK errors extend `AbloError` and carry a stable `type`.
 | `AbloBusyError` | Active intent conflicted with `ifBusy: 'fail'` or a busy wait timed out. |
 
 ```ts
-import { AbloBusyError } from '@ablo/sync-engine';
+import { AbloBusyError } from '@abloatai/ablo';
 
 try {
   await ablo.tasks.update('task_123', { status: 'done' }, { wait: 'confirmed' });
@@ -192,10 +192,10 @@ request bodies that may contain customer data.
 
 Only these imports are public SemVer surface:
 
-- `@ablo/sync-engine`
-- `@ablo/sync-engine/schema`
-- `@ablo/sync-engine/react`
-- `@ablo/sync-engine/testing`
+- `@abloatai/ablo`
+- `@abloatai/ablo/schema`
+- `@abloatai/ablo/react`
+- `@abloatai/ablo/testing`
 
 `dataSource(...)` is exported from the root package for customer-owned storage
 adapters. Everything outside the four import paths is internal to Ablo-owned

package/docs/data-sources.md

@@ -13,7 +13,7 @@ app to commit it.
 Use the SDK with an API key:
 
 ```ts
-import Ablo from '@ablo/sync-engine';
+import Ablo from '@abloatai/ablo';
 import { schema } from './ablo.schema';
 
 export const ablo = Ablo({
@@ -82,7 +82,7 @@ ABLO_DATA_SOURCE_SIGNING_SECRET=whsec_...
 
 ```ts
 // app/api/ablo/source/route.ts
-import { dataSource } from '@ablo/sync-engine';
+import { dataSource } from '@abloatai/ablo';
 import { schema } from '@/ablo.schema';
 import { db } from '@/db';
 

package/docs/examples/agent-human.md

@@ -18,8 +18,8 @@ Use the same schema client the app uses. The worker loads the task, checks activ
 intents, and writes through `ablo.tasks.update(...)`.
 
 ```ts
-import Ablo from '@ablo/sync-engine';
-import { defineSchema, model, z } from '@ablo/sync-engine/schema';
+import Ablo from '@abloatai/ablo';
+import { defineSchema, model, z } from '@abloatai/ablo/schema';
 
 const schema = defineSchema({
   tasks: model({
@@ -58,7 +58,7 @@ not the first integration path.
 ```tsx
 'use client';
 
-import { useAblo } from '@ablo/sync-engine/react';
+import { useAblo } from '@abloatai/ablo/react';
 
 export function TaskRow({ task: serverTask }: Props) {
   const data = useAblo((ablo) => ablo.tasks.retrieve(serverTask.id)) ?? serverTask;

package/docs/examples/ai-sdk-tool.md

@@ -3,8 +3,8 @@
 Use AI SDK for the loop and Ablo for the state boundary inside the tool.
 
 ```ts
-import Ablo from '@ablo/sync-engine';
-import { defineSchema, model, z as schemaZ } from '@ablo/sync-engine/schema';
+import Ablo from '@abloatai/ablo';
+import { defineSchema, model, z as schemaZ } from '@abloatai/ablo/schema';
 import { streamText, tool } from 'ai';
 import { z } from 'zod';
 

package/docs/examples/existing-python-backend.md

@@ -27,7 +27,7 @@ Create a schema for the records that need realtime coordination.
 
 ```ts
 // web/ablo.schema.ts
-import { defineSchema, model, z } from '@ablo/sync-engine/schema';
+import { defineSchema, model, z } from '@abloatai/ablo/schema';
 
 export const schema = defineSchema({
   tasks: model({
@@ -41,7 +41,7 @@ export const schema = defineSchema({
 
 ```ts
 // web/ablo.ts
-import Ablo from '@ablo/sync-engine';
+import Ablo from '@abloatai/ablo';
 import { schema } from './ablo.schema';
 
 export const ablo = Ablo({
@@ -57,7 +57,7 @@ model resources without importing server credentials.
 // web/app/providers.tsx
 'use client';
 
-import { AbloProvider } from '@ablo/sync-engine/react';
+import { AbloProvider } from '@abloatai/ablo/react';
 import { schema } from '@/ablo.schema';
 
 export function Providers({ children }: { children: React.ReactNode }) {
@@ -73,7 +73,7 @@ subscribe to the same model resource Ablo writes through.
 ```tsx
 'use client';
 
-import { useAblo } from '@ablo/sync-engine/react';
+import { useAblo } from '@abloatai/ablo/react';
 
 export function TaskRow({ task: serverTask }: { task: Task }) {
   const task = useAblo((ablo) => ablo.tasks.retrieve(serverTask.id)) ?? serverTask;

package/docs/examples/nextjs.md

@@ -64,7 +64,7 @@ rejects. The action can re-fetch and ask the user to retry.
 ```tsx
 'use client';
 
-import { useAblo } from '@ablo/sync-engine/react';
+import { useAblo } from '@abloatai/ablo/react';
 
 export function TaskEditor({ task: serverTask }: Props) {
   const data = useAblo((ablo) => ablo.tasks.retrieve(serverTask.id)) ?? serverTask;

package/docs/examples/server-agent.md

@@ -4,8 +4,8 @@ Most server agents should import the app schema and use the same model methods
 as the product UI.
 
 ```ts
-import Ablo from '@ablo/sync-engine';
-import { defineSchema, model, z } from '@ablo/sync-engine/schema';
+import Ablo from '@abloatai/ablo';
+import { defineSchema, model, z } from '@abloatai/ablo/schema';
 
 const schema = defineSchema({
   tasks: model({

package/docs/index.md

@@ -87,7 +87,7 @@ query-shaped sync).
 
 ## Runtime builds
 
-- `@ablo/sync-engine` — schema-powered sync client for typed model operations, realtime, intents, and receipts.
+- `@abloatai/ablo` — schema-powered sync client for typed model operations, realtime, intents, and receipts.
 - `Ablo({ apiKey })` — advanced resource client for runtimes that intentionally cannot import a schema.
 
 ## More

package/docs/integration-guide.md

@@ -40,8 +40,8 @@ together, behind one client.
 The normal integration is one client:
 
 ```ts
-import Ablo from '@ablo/sync-engine';
-import { defineSchema, model, z } from '@ablo/sync-engine/schema';
+import Ablo from '@abloatai/ablo';
+import { defineSchema, model, z } from '@abloatai/ablo/schema';
 ```
 
 Declare the models Ablo coordinates, then read and write through
@@ -106,7 +106,7 @@ offline-heavy local cache behavior.
 
 ```ts
 // src/ablo.schema.ts
-import { defineSchema, model, z } from '@ablo/sync-engine/schema';
+import { defineSchema, model, z } from '@abloatai/ablo/schema';
 
 export const schema = defineSchema(
   {
@@ -176,7 +176,7 @@ Trusted runtimes can use `ABLO_API_KEY`.
 
 ```ts
 // src/ablo.ts
-import Ablo from '@ablo/sync-engine';
+import Ablo from '@abloatai/ablo';
 import { schema } from './ablo.schema';
 
 export const ablo = Ablo({
@@ -192,7 +192,7 @@ server API key in the bundle.
 // app/providers.tsx
 'use client';
 
-import { AbloProvider } from '@ablo/sync-engine/react';
+import { AbloProvider } from '@abloatai/ablo/react';
 import { schema } from '@/ablo.schema';
 
 export function Providers({ children }: { children: React.ReactNode }) {
@@ -259,7 +259,7 @@ In React, selector `useAblo` is the public read API:
 ```tsx
 'use client';
 
-import { useAblo } from '@ablo/sync-engine/react';
+import { useAblo } from '@abloatai/ablo/react';
 
 export function TaskRow({ task: serverTask }: { task: Task }) {
   const task = useAblo((ablo) => ablo.tasks.retrieve(serverTask.id)) ?? serverTask;
@@ -369,7 +369,7 @@ Use a Data Source when your app database remains the source of truth.
 
 ```ts
 // app/api/ablo/source/route.ts
-import { dataSource } from '@ablo/sync-engine';
+import { dataSource } from '@abloatai/ablo';
 import { schema } from '@/ablo.schema';
 import { db } from '@/db';
 

package/docs/quickstart.md

@@ -9,7 +9,7 @@ Ablo-managed state versus a Data Source that calls your existing API service.
 ## 1. Install
 
 ```bash
-npm install @ablo/sync-engine
+npm install @abloatai/ablo
 ```
 
 ## 2. Set a Sandbox Key
@@ -26,8 +26,8 @@ provider with a scoped capability/session route, not a bundled API key.
 ## 3. Declare a Schema
 
 ```ts
-import Ablo from '@ablo/sync-engine';
-import { defineSchema, model, z } from '@ablo/sync-engine/schema';
+import Ablo from '@abloatai/ablo';
+import { defineSchema, model, z } from '@abloatai/ablo/schema';
 
 const schema = defineSchema({
   weatherReports: model({

package/docs/react.md

@@ -1,6 +1,6 @@
 # React
 
-The React bindings for `@ablo/sync-engine`. Use them when you want live
+The React bindings for `@abloatai/ablo`. Use them when you want live
 data on the client without writing fetch + WebSocket plumbing yourself.
 
 For the full app structure, including server loads, existing backends, and
@@ -11,7 +11,7 @@ agents, start with [Integration Guide](/docs/integration-guide).
 The React bindings ship with the main package — no extra install.
 
 ```ts
-import { useAblo } from '@ablo/sync-engine/react';
+import { useAblo } from '@abloatai/ablo/react';
 ```
 
 ## useAblo — model resource
@@ -19,7 +19,7 @@ import { useAblo } from '@ablo/sync-engine/react';
 ```tsx
 'use client';
 
-import { useAblo } from '@ablo/sync-engine/react';
+import { useAblo } from '@abloatai/ablo/react';
 
 export function TaskView({ task: serverTask }: { task: { id: string; title: string } }) {
   const task = useAblo((ablo) => ablo.tasks.retrieve(serverTask.id)) ?? serverTask;

package/docs/roadmap.md

@@ -8,7 +8,7 @@ What is shipped, what is next, and what we will not build.
 - **Capability tokens** — Biscuit-signed, scoped, attenuable, hot-revocable.
 - **Audit log** — hash-chained per principal, with `delegationChainRoot`.
 - **MCP transport** — HTTP server at `/api/mcp`.
-- **TypeScript SDK** — `@ablo/sync-engine`, with React bindings.
+- **TypeScript SDK** — `@abloatai/ablo`, with React bindings.
 - **Dashboard** — keys, audit, metrics, allowed origins.
 
 ## In flight

package/examples/README.md

@@ -1,11 +1,11 @@
-# @ablo/sync-engine Examples
+# @abloatai/ablo Examples
 
 The examples teach the same path as the README and docs: declare a schema,
 create or load typed models, and write through `ablo.<model>`.
 
 ```ts
-import Ablo from '@ablo/sync-engine';
-import { defineSchema, model, z } from '@ablo/sync-engine/schema';
+import Ablo from '@abloatai/ablo';
+import { defineSchema, model, z } from '@abloatai/ablo/schema';
 
 const schema = defineSchema({
   weatherReports: model({

package/llms.txt

@@ -7,8 +7,8 @@ Use AI SDK for the agent loop. Use Ablo when agent reads and writes must persist
 ## Use this API
 
 ```ts
-import Ablo from '@ablo/sync-engine';
-import { defineSchema, model, z } from '@ablo/sync-engine/schema';
+import Ablo from '@abloatai/ablo';
+import { defineSchema, model, z } from '@abloatai/ablo/schema';
 
 const schema = defineSchema({
   tasks: model({
@@ -108,7 +108,7 @@ Every schema model has a backing store. By default, Ablo stores rows for declare
 Use `dataSource` from the root import:
 
 ```ts
-import { dataSource } from '@ablo/sync-engine';
+import { dataSource } from '@abloatai/ablo';
 ```
 
 ## Sandboxes
@@ -133,10 +133,10 @@ two-writer stale/intent smoke test.
 
 Import from these public paths only:
 
-- `@ablo/sync-engine` — `Ablo`, errors, typed model resources, intents, `dataSource`, and advanced protocol resources.
-- `@ablo/sync-engine/schema` — schema DSL.
-- `@ablo/sync-engine/react` — React provider and hooks.
-- `@ablo/sync-engine/testing` — test harnesses and mocks.
+- `@abloatai/ablo` — `Ablo`, errors, typed model resources, intents, `dataSource`, and advanced protocol resources.
+- `@abloatai/ablo/schema` — schema DSL.
+- `@abloatai/ablo/react` — React provider and hooks.
+- `@abloatai/ablo/testing` — test harnesses and mocks.
 
 Do not teach `/api`, `/agent`, `/ai-sdk`, `/core`, `/realtime`, `/source`, or internal subpaths.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@abloatai/ablo",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "description": "State control API for AI agents and collaborative apps.",
   "license": "Apache-2.0",
   "type": "module",