@engram-mem/supabase 0.3.8 → 0.4.1

package/README.md

@@ -1,301 +1,44 @@
 # @engram-mem/supabase
 
-Cloud storage adapter for Engram using Supabase PostgreSQL and pgvector. Enables distributed agents with shared memory.
+> ⚠️ **DEPRECATED** — this package has been renamed to [`@engram-mem/postgrest`](https://www.npmjs.com/package/@engram-mem/postgrest) in v0.4.0. This package is now a thin re-export shim and will be removed entirely in **v0.5.0**.
 
-## Installation
+## Why the rename
 
-```bash
-npm install @engram-mem/supabase
-npm install @engram-mem/core
-npm install @engram-mem/openai  # Optional but recommended
-```
-
-## Setup
-
-### 1. Create a Supabase Project
-
-1. Go to https://supabase.com
-2. Create a new project
-3. Wait for it to provision (~2 min)
-4. Copy your project URL and anon key
-
-### 2. Enable Vector Extension
-
-Run this in the Supabase SQL Editor:
-
-```sql
-CREATE EXTENSION IF NOT EXISTS vector;
-```
-
-### 3. Run Migrations
-
-Get your DATABASE_URL from Supabase settings, then:
+The adapter was always PostgREST under the hood. Engram only ever used the `.from(table)` / `.rpc(fn)` query-builder methods of `supabase-js`, which are themselves a wrapper around `postgrest-js`. The same code worked against any PostgREST endpoint — Supabase-hosted, self-hosted Postgres + PostgREST, anywhere — but the package name made vendor lock-in look mandatory. v0.4.0 fixes that.
 
-```bash
-export SUPABASE_URL="https://your-project.supabase.co"
-export SUPABASE_KEY="your-anon-key"
-
-# Run migrations (instructions below)
-psql $DATABASE_URL < packages/supabase/migrations/001_initial_schema.sql
-psql $DATABASE_URL < packages/supabase/migrations/002_vector_indexes.sql
-```
+## What still works
 
-### 4. Configure in Your App
-
-```javascript
-import { createMemory } from '@engram-mem/core'
-import { supabaseAdapter } from '@engram-mem/supabase'
-
-const memory = createMemory({
-  storage: supabaseAdapter({
-    url: process.env.SUPABASE_URL,
-    key: process.env.SUPABASE_KEY
-  })
-})
-
-await memory.initialize()
-// ... use as normal
-```
-
-## Configuration
+Your existing imports keep working in **v0.4.x** with no code changes:
 
 ```typescript
-interface SupabaseAdapterOptions {
-  url: string        // Supabase project URL (required)
-  key: string        // Supabase anon key (required)
-  schema?: string    // Default: 'engram'
-}
-
-const adapter = supabaseAdapter({
-  url: process.env.SUPABASE_URL,
-  key: process.env.SUPABASE_KEY,
-  schema: 'my_engram'  // Optional custom schema
-})
-```
-
-## Schema Overview
-
-Supabase provides PostgreSQL with pgvector extension for vector search:
-
-```
-TABLES (same structure as SQLite, but with vector columns):
-├── episodes       — With embedding vectors
-├── digests        — With embedding vectors
-├── semantic       — With embedding vectors
-├── procedural     — With embedding vectors
-├── associations   — Edge graph
-├── sensory_snapshots  — JSONB snapshots
-
-INDEXES (HNSW for vector search):
-├── episodes_embedding_idx      — Vector similarity search
-├── semantic_embedding_idx      — Semantic fact search
-├── digest_embedding_idx        — Summary search
-├── associations_source_target_idx  — Graph traversal
-```
-
-## Advantages Over SQLite
-
-### Scalability
-- Handle billions of memories (no single-file size limits)
-- Distributed agents sharing the same memory
-- Horizontal scaling via Supabase infrastructure
-
-### Vector Search
-- HNSW (Hierarchical Navigable Small World) indexes
-- Sub-millisecond vector similarity at scale
-- Better than SQLite FTS5 for semantic search
-
-### Concurrency
-- Built-in row-level security
-- Proper ACID guarantees
-- Multiple writers without conflict
-
-### Durability
-- Automated backups and PITR (point-in-time recovery)
-- Replicas for HA
-- Managed service (you don't maintain it)
-
-## HNSW Index Configuration
-
-HNSW indexes are created automatically on embedding columns:
-
-```sql
-CREATE INDEX episodes_embedding_idx ON episodes
-USING hnsw (embedding vector_cosine_ops)
-WITH (m=16, ef_construction=64);
-```
-
-These settings are good defaults. For massive databases (>10M memories), consider:
-
-```sql
-WITH (m=32, ef_construction=200)  -- Higher accuracy, slower build
-WITH (m=8, ef_construction=32)    -- Lower accuracy, faster build
-```
-
-Adjust via Supabase SQL Editor if needed.
-
-## Cost Estimation
-
-Supabase pricing (as of 2026):
-
-| Component | Cost |
-|-----------|------|
-| Database storage | $0.25 per GB/month |
-| API egress | $0.11 per GB |
-| Realtime (optional) | $10-100/month |
-
-For a typical agent with 100K memories (~500MB):
-- Storage: ~$0.12/month
-- API egress (during consolidation): ~$0.05/month
-- **Total: ~$0.20/month**
-
-This is very economical for distributed multi-agent systems.
-
-## Distributed Agents
-
-One of Engram's killer features: **shared memory between agents**.
-
-```javascript
-// Agent 1
-const memory1 = createMemory({
-  storage: supabaseAdapter({ url: '...', key: '...' })
-})
-
-// Agent 2 (different process, same database)
-const memory2 = createMemory({
-  storage: supabaseAdapter({ url: '...', key: '...' })
-})
-
-// Agent 1 ingests knowledge
-await memory1.ingest({
-  role: 'assistant',
-  content: 'Found that TypeScript strict mode requires...'
-})
-
-// Agent 2 recalls it
-const result = await memory2.recall('TypeScript strict mode')
-// => Finds Agent 1's ingested knowledge
-```
-
-Sessions still partition by sessionId, but facts (semantic/procedural) are shared.
-
-## Level 2 Setup
-
-```javascript
-import { createMemory } from '@engram-mem/core'
-import { supabaseAdapter } from '@engram-mem/supabase'
-import { openaiIntelligence } from '@engram-mem/openai'
-
-const memory = createMemory({
-  storage: supabaseAdapter({
-    url: process.env.SUPABASE_URL,
-    key: process.env.SUPABASE_KEY
-  }),
-  intelligence: openaiIntelligence({
-    apiKey: process.env.OPENAI_API_KEY
-  })
-})
-
-await memory.initialize()
-// Now you have:
-// - Cloud storage (shared between agents)
-// - Vector embeddings (semantic search)
-// - BM25 fallback (keyword search on episodes)
+import { SupabaseStorageAdapter, supabaseAdapter } from '@engram-mem/supabase'
+// ↑ Still works. Both are re-exported from @engram-mem/postgrest.
 ```
 
-## Level 3 Setup (Future)
-
-When auto-consolidation is ready:
-
-```javascript
-const memory = createMemory({
-  storage: supabaseAdapter({ url: '...', key: '...' }),
-  intelligence: openaiIntelligence({
-    apiKey: process.env.OPENAI_API_KEY,
-    intentAnalysis: true,
-    summarization: true
-  }),
-  consolidation: { schedule: 'auto' }
-})
-```
+You'll see:
+- TSDoc deprecation warnings in your IDE
+- `npm WARN deprecated @engram-mem/supabase@... — Renamed to @engram-mem/postgrest` on install
 
-Consolidation will run on a schedule, automatically creating digests and extracting knowledge.
-
-## Row-Level Security (RLS)
-
-By default, Supabase RLS is disabled (anon key has full access). For production:
-
-1. **Enable RLS** on all tables in Supabase dashboard
-2. **Create policies** restricting access by sessionId or agent ID
-
-Example policy:
-
-```sql
-CREATE POLICY episodes_owner_access ON episodes
-FOR ALL USING (auth.uid() = user_id)  -- Restrict to user's own data
-```
-
-This requires setting up Supabase auth and passing user ID during schema setup.
-
-## Backup and Recovery
-
-Supabase handles backups automatically. Access them via:
-
-1. Project settings → Backups
-2. Create new project from backup
-3. Use pg_dump for manual export:
+## Migration
 
 ```bash
-pg_dump $DATABASE_URL > engram_backup.sql
+npm uninstall @engram-mem/supabase
+npm install @engram-mem/postgrest
 ```
 
-## Troubleshooting
-
-**Q: Connection timeout**
-
-A: Check your Supabase project is running and firewall rules allow connections. Verify URL and key are correct.
-
-**Q: Vector index not being used**
-
-A: pgvector queries use indexes automatically for large tables (>10K rows). For testing, check query EXPLAIN PLAN:
-
-```sql
-EXPLAIN (ANALYZE) SELECT * FROM semantic
-ORDER BY embedding <=> '<your-vector>'::vector
-LIMIT 10;
+```diff
+- import { SupabaseStorageAdapter } from '@engram-mem/supabase'
++ import { PostgRestStorageAdapter } from '@engram-mem/postgrest'
 ```
 
-If not using index, run `ANALYZE semantic;` to update statistics.
-
-**Q: High query costs**
+`PostgRestStorageAdapter` is the same class with the same constructor signature. `@engram-mem/postgrest` also re-exports `SupabaseStorageAdapter` as a deprecated alias, so you can rename the package without renaming the class first if you want a two-step migration.
 
-A: Each recall() triggers API calls. For high-frequency agents, consider:
-1. Batch recalls into fewer requests
-2. Use longer consolidation intervals to reduce overhead
-3. Cache results client-side
-
-**Q: Can I migrate from SQLite to Supabase?**
-
-A: Export SQLite and import via pg_load_data (future tooling). For now, do it manually.
-
-**Q: Is Supabase always online?**
-
-A: Supabase runs on AWS with 99.99% uptime SLA. Check status at https://status.supabase.com.
-
-## API Reference
-
-All methods are internal to the StorageAdapter. Use the Memory class API instead. See @engram-mem/core README.
-
-The only public function is:
-
-```typescript
-export function supabaseAdapter(opts: SupabaseAdapterOptions): StorageAdapter
-```
+Same `SUPABASE_URL` / `SUPABASE_KEY` env vars continue to work — they're just strings that get passed to the adapter's `url` and `key` options. The values can point at any PostgREST endpoint (Supabase project URL, your own Docker-hosted PostgREST, etc.).
 
-## Contributing
+Full migration runbook including how to switch from hosted Supabase to self-hosted Postgres + PostgREST:
 
-See [CONTRIBUTING.md](../../CONTRIBUTING.md) at repo root.
+- [`docs/migrations/2026-05-25-supabase-to-postgrest-rebrand.md`](https://github.com/muhammadkh4n/engram/blob/main/docs/migrations/2026-05-25-supabase-to-postgrest-rebrand.md)
 
-## License
+## v0.5.0
 
-MIT
+This package will be removed entirely. Plan to migrate before then.

package/dist/index.d.ts

@@ -1,10 +1,35 @@
-export { SupabaseStorageAdapter } from './adapter.js';
-export type { SupabaseAdapterOptions } from './adapter.js';
-export { getMigrationSQL, MIGRATION_004, MIGRATION_005, MIGRATION_006, MIGRATION_007 } from './migrations.js';
-import { SupabaseStorageAdapter } from './adapter.js';
-export declare function supabaseAdapter(opts: {
-    url: string;
-    key: string;
-    embeddingDimensions?: number;
-}): SupabaseStorageAdapter;
+/**
+ * @engram-mem/supabase — DEPRECATED, renamed to @engram-mem/postgrest in v0.4.0.
+ *
+ * The adapter was always PostgREST under the hood (supabase-js wraps
+ * postgrest-js + auth/realtime/storage; engram only uses the postgrest-js
+ * query builder). The old name made vendor lock-in look mandatory when
+ * it isn't. The new package works against any PostgREST endpoint —
+ * Supabase-hosted, self-hosted Postgres + PostgREST, anywhere.
+ *
+ * This package is now a thin re-export shim. Your existing imports keep
+ * working through v0.4.x and will be removed in v0.5.0.
+ *
+ * Migrate at your convenience:
+ *
+ *   - npm install @engram-mem/supabase
+ *   + npm install @engram-mem/postgrest
+ *
+ *   - import { SupabaseStorageAdapter } from '@engram-mem/supabase'
+ *   + import { PostgRestStorageAdapter } from '@engram-mem/postgrest'
+ *
+ * The class name `SupabaseStorageAdapter` is ALSO re-exported from
+ * `@engram-mem/postgrest` as a deprecated alias, so you can rename the
+ * package without renaming the class first if you want a two-step
+ * migration.
+ *
+ * Full migration runbook (including how to switch from hosted Supabase
+ * to self-hosted Postgres + PostgREST on the same adapter):
+ *   docs/migrations/2026-05-25-supabase-to-postgrest-rebrand.md
+ *
+ * @deprecated Use @engram-mem/postgrest instead. This package will be
+ * removed in v0.5.0.
+ */
+export { PostgRestStorageAdapter as SupabaseStorageAdapter, PostgRestStorageAdapter, createPostgRestAdapter, supabaseAdapter, getMigrationSQL, MIGRATION_004, MIGRATION_005, MIGRATION_006, MIGRATION_007, } from '@engram-mem/postgrest';
+export type { PostgRestAdapterOptions as SupabaseAdapterOptions, PostgRestAdapterOptions, } from '@engram-mem/postgrest';
 //# sourceMappingURL=index.d.ts.map

package/dist/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,sBAAsB,EAAE,MAAM,cAAc,CAAA;AACrD,YAAY,EAAE,sBAAsB,EAAE,MAAM,cAAc,CAAA;AAC1D,OAAO,EAAE,eAAe,EAAE,aAAa,EAAE,aAAa,EAAE,aAAa,EAAE,aAAa,EAAE,MAAM,iBAAiB,CAAA;AAE7G,OAAO,EAAE,sBAAsB,EAAE,MAAM,cAAc,CAAA;AAErD,wBAAgB,eAAe,CAAC,IAAI,EAAE;IAAE,GAAG,EAAE,MAAM,CAAC;IAAC,GAAG,EAAE,MAAM,CAAC;IAAC,mBAAmB,CAAC,EAAE,MAAM,CAAA;CAAE,0BAE/F"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA+BG;AAEH,OAAO,EACL,uBAAuB,IAAI,sBAAsB,EACjD,uBAAuB,EACvB,sBAAsB,EACtB,eAAe,EACf,eAAe,EACf,aAAa,EACb,aAAa,EACb,aAAa,EACb,aAAa,GACd,MAAM,uBAAuB,CAAA;AAE9B,YAAY,EACV,uBAAuB,IAAI,sBAAsB,EACjD,uBAAuB,GACxB,MAAM,uBAAuB,CAAA"}

package/dist/index.js

@@ -1,7 +1,34 @@
-export { SupabaseStorageAdapter } from './adapter.js';
-export { getMigrationSQL, MIGRATION_004, MIGRATION_005, MIGRATION_006, MIGRATION_007 } from './migrations.js';
-import { SupabaseStorageAdapter } from './adapter.js';
-export function supabaseAdapter(opts) {
-    return new SupabaseStorageAdapter(opts);
-}
+/**
+ * @engram-mem/supabase — DEPRECATED, renamed to @engram-mem/postgrest in v0.4.0.
+ *
+ * The adapter was always PostgREST under the hood (supabase-js wraps
+ * postgrest-js + auth/realtime/storage; engram only uses the postgrest-js
+ * query builder). The old name made vendor lock-in look mandatory when
+ * it isn't. The new package works against any PostgREST endpoint —
+ * Supabase-hosted, self-hosted Postgres + PostgREST, anywhere.
+ *
+ * This package is now a thin re-export shim. Your existing imports keep
+ * working through v0.4.x and will be removed in v0.5.0.
+ *
+ * Migrate at your convenience:
+ *
+ *   - npm install @engram-mem/supabase
+ *   + npm install @engram-mem/postgrest
+ *
+ *   - import { SupabaseStorageAdapter } from '@engram-mem/supabase'
+ *   + import { PostgRestStorageAdapter } from '@engram-mem/postgrest'
+ *
+ * The class name `SupabaseStorageAdapter` is ALSO re-exported from
+ * `@engram-mem/postgrest` as a deprecated alias, so you can rename the
+ * package without renaming the class first if you want a two-step
+ * migration.
+ *
+ * Full migration runbook (including how to switch from hosted Supabase
+ * to self-hosted Postgres + PostgREST on the same adapter):
+ *   docs/migrations/2026-05-25-supabase-to-postgrest-rebrand.md
+ *
+ * @deprecated Use @engram-mem/postgrest instead. This package will be
+ * removed in v0.5.0.
+ */
+export { PostgRestStorageAdapter as SupabaseStorageAdapter, PostgRestStorageAdapter, createPostgRestAdapter, supabaseAdapter, getMigrationSQL, MIGRATION_004, MIGRATION_005, MIGRATION_006, MIGRATION_007, } from '@engram-mem/postgrest';
 //# sourceMappingURL=index.js.map

package/dist/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,sBAAsB,EAAE,MAAM,cAAc,CAAA;AAErD,OAAO,EAAE,eAAe,EAAE,aAAa,EAAE,aAAa,EAAE,aAAa,EAAE,aAAa,EAAE,MAAM,iBAAiB,CAAA;AAE7G,OAAO,EAAE,sBAAsB,EAAE,MAAM,cAAc,CAAA;AAErD,MAAM,UAAU,eAAe,CAAC,IAAgE;IAC9F,OAAO,IAAI,sBAAsB,CAAC,IAAI,CAAC,CAAA;AACzC,CAAC"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA+BG;AAEH,OAAO,EACL,uBAAuB,IAAI,sBAAsB,EACjD,uBAAuB,EACvB,sBAAsB,EACtB,eAAe,EACf,eAAe,EACf,aAAa,EACb,aAAa,EACb,aAAa,EACb,aAAa,GACd,MAAM,uBAAuB,CAAA"}

package/package.json

@@ -1,17 +1,12 @@
 {
   "name": "@engram-mem/supabase",
-  "version": "0.3.8",
-  "description": "Supabase storage adapter for Engram — cloud-hosted memory with pgvector and full-text search",
+  "version": "0.4.1",
+  "description": "DEPRECATED — renamed to @engram-mem/postgrest. This package is a thin re-export shim and will be removed in v0.5.0. See README.",
   "keywords": [
     "memory",
     "ai",
     "agents",
-    "cognitive",
-    "embeddings",
-    "recall",
-    "supabase",
-    "postgres",
-    "pgvector"
+    "deprecated"
   ],
   "license": "Apache-2.0",
   "type": "module",
@@ -30,13 +25,12 @@
   },
   "scripts": {
     "build": "tsc",
-    "test": "vitest run",
+    "test": "vitest run --passWithNoTests",
     "typecheck": "tsc --noEmit",
     "clean": "rm -rf dist"
   },
   "dependencies": {
-    "@engram-mem/core": "*",
-    "@supabase/supabase-js": "^2.104.1"
+    "@engram-mem/postgrest": "0.4.1"
   },
   "devDependencies": {
     "typescript": "^6.0.2",

package/dist/adapter.d.ts

@@ -1,51 +0,0 @@
-import type { MemoryType, TypedMemory, SensorySnapshot, SearchResult } from '@engram-mem/core';
-import type { StorageAdapter } from '@engram-mem/core';
-import { SupabaseEpisodeStorage } from './episodes.js';
-import { SupabaseDigestStorage } from './digests.js';
-import { SupabaseSemanticStorage } from './semantic.js';
-import { SupabaseProceduralStorage } from './procedural.js';
-import { SupabaseAssociationStorage } from './associations.js';
-export interface SupabaseAdapterOptions {
-    url: string;
-    key: string;
-    embeddingDimensions?: number;
-}
-export declare class SupabaseStorageAdapter implements StorageAdapter {
-    private client;
-    private _isLegacy;
-    private _episodes;
-    private _digests;
-    private _semantic;
-    private _procedural;
-    private _associations;
-    constructor(opts: SupabaseAdapterOptions);
-    initialize(): Promise<void>;
-    dispose(): Promise<void>;
-    get episodes(): SupabaseEpisodeStorage;
-    get digests(): SupabaseDigestStorage;
-    get semantic(): SupabaseSemanticStorage;
-    get procedural(): SupabaseProceduralStorage;
-    get associations(): SupabaseAssociationStorage;
-    getById(id: string, type: MemoryType): Promise<TypedMemory | null>;
-    getByIds(ids: Array<{
-        id: string;
-        type: MemoryType;
-    }>): Promise<TypedMemory[]>;
-    saveSensorySnapshot(sessionId: string, snapshot: SensorySnapshot): Promise<void>;
-    loadSensorySnapshot(sessionId: string): Promise<SensorySnapshot | null>;
-    vectorSearch(embedding: number[], opts?: {
-        limit?: number;
-        sessionId?: string;
-        tiers?: MemoryType[];
-    }): Promise<SearchResult<TypedMemory>[]>;
-    textBoost(terms: string[], opts?: {
-        limit?: number;
-        sessionId?: string;
-    }): Promise<Array<{
-        id: string;
-        type: MemoryType;
-        boost: number;
-    }>>;
-    private assertInitialized;
-}
-//# sourceMappingURL=adapter.d.ts.map

package/dist/adapter.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"adapter.d.ts","sourceRoot":"","sources":["../src/adapter.ts"],"names":[],"mappings":"AACA,OAAO,KAAK,EAAE,UAAU,EAAE,WAAW,EAAE,eAAe,EAAE,YAAY,EAAE,MAAM,kBAAkB,CAAA;AAC9F,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,kBAAkB,CAAA;AACtD,OAAO,EAAE,sBAAsB,EAAE,MAAM,eAAe,CAAA;AACtD,OAAO,EAAE,qBAAqB,EAAE,MAAM,cAAc,CAAA;AACpD,OAAO,EAAE,uBAAuB,EAAE,MAAM,eAAe,CAAA;AACvD,OAAO,EAAE,yBAAyB,EAAE,MAAM,iBAAiB,CAAA;AAC3D,OAAO,EAAE,0BAA0B,EAAE,MAAM,mBAAmB,CAAA;AAE9D,MAAM,WAAW,sBAAsB;IACrC,GAAG,EAAE,MAAM,CAAA;IACX,GAAG,EAAE,MAAM,CAAA;IACX,mBAAmB,CAAC,EAAE,MAAM,CAAA;CAC7B;AAED,qBAAa,sBAAuB,YAAW,cAAc;IAC3D,OAAO,CAAC,MAAM,CAAgB;IAC9B,OAAO,CAAC,SAAS,CAAiB;IAClC,OAAO,CAAC,SAAS,CAAsC;IACvD,OAAO,CAAC,QAAQ,CAAqC;IACrD,OAAO,CAAC,SAAS,CAAuC;IACxD,OAAO,CAAC,WAAW,CAAyC;IAC5D,OAAO,CAAC,aAAa,CAA0C;gBAEnD,IAAI,EAAE,sBAAsB;IAIlC,UAAU,IAAI,OAAO,CAAC,IAAI,CAAC;IA+B3B,OAAO,IAAI,OAAO,CAAC,IAAI,CAAC;IAS9B,IAAI,QAAQ,IAAI,sBAAsB,CAKrC;IAED,IAAI,OAAO,IAAI,qBAAqB,CAKnC;IAED,IAAI,QAAQ,IAAI,uBAAuB,CAKtC;IAED,IAAI,UAAU,IAAI,yBAAyB,CAK1C;IAED,IAAI,YAAY,IAAI,0BAA0B,CAK7C;IAEK,OAAO,CAAC,EAAE,EAAE,MAAM,EAAE,IAAI,EAAE,UAAU,GAAG,OAAO,CAAC,WAAW,GAAG,IAAI,CAAC;IA8ClE,QAAQ,CAAC,GAAG,EAAE,KAAK,CAAC;QAAE,EAAE,EAAE,MAAM,CAAC;QAAC,IAAI,EAAE,UAAU,CAAA;KAAE,CAAC,GAAG,OAAO,CAAC,WAAW,EAAE,CAAC;IA0D9E,mBAAmB,CAAC,SAAS,EAAE,MAAM,EAAE,QAAQ,EAAE,eAAe,GAAG,OAAO,CAAC,IAAI,CAAC;IAWhF,mBAAmB,CAAC,SAAS,EAAE,MAAM,GAAG,OAAO,CAAC,eAAe,GAAG,IAAI,CAAC;IAYvE,YAAY,CAAC,SAAS,EAAE,MAAM,EAAE,EAAE,IAAI,CAAC,EAAE;QAC7C,KAAK,CAAC,EAAE,MAAM,CAAA;QACd,SAAS,CAAC,EAAE,MAAM,CAAA;QAClB,KAAK,CAAC,EAAE,UAAU,EAAE,CAAA;KACrB,GAAG,OAAO,CAAC,YAAY,CAAC,WAAW,CAAC,EAAE,CAAC;IAoBlC,SAAS,CAAC,KAAK,EAAE,MAAM,EAAE,EAAE,IAAI,CAAC,EAAE;QACtC,KAAK,CAAC,EAAE,MAAM,CAAA;QACd,SAAS,CAAC,EAAE,MAAM,CAAA;KACnB,GAAG,OAAO,CAAC,KAAK,CAAC;QAAE,EAAE,EAAE,MAAM,CAAC;QAAC,IAAI,EAAE,UAAU,CAAC;QAAC,KAAK,EAAE,MAAM,CAAA;KAAE,CAAC,CAAC;IA0BnE,OAAO,CAAC,iBAAiB;CAK1B"}