/**
 * PostgresDataAccessor — interface stub for cloud-sync backend.
 *
 * SCAFFOLD ONLY (T9062). This file defines the type surface and namespacing
 * contract for the PostgreSQL-backed DataAccessor. Full implementation
 * (sync commands, migration, multi-tenant namespacing, auth) is deferred
 * to T9062 child tasks.
 *
 * Architecture overview (ADR-TBD — cloud-sync):
 *   - CLEO is local-first SQLite for portability and offline operation.
 *   - A PostgresDataAccessor provides an engine-neutral drop-in replacement
 *     for SqliteDataAccessor — same DataAccessor interface, different engine.
 *   - Multi-tenant namespacing: each CLEO project maps to a Postgres
 *     "tenant namespace" (schema or row-level tenant key) inside a shared
 *     cluster. Cross-tenant isolation is enforced at the DB layer.
 *   - Sync model: pull/push with last-write-wins per row (initial design).
 *     CRDT merge (cr-sqlite) is opt-in per ADR from T947.
 *   - Auth: each tenant identified by SignalDock identity (Ed25519 keypair).
 *     Push receipts signed with the same primitive as llmtxt/sdk receipts.
 *
 * Engine-neutral proof:
 *   The DataAccessor interface in @cleocode/contracts carries `engine: 'sqlite'`.
 *   PostgresDataAccessor will carry `engine: 'postgres'`. Both satisfy the
 *   same interface contract, proving the abstraction from T9050 is real.
 *
 * @task T9062
 * @epic T9048
 * @see packages/contracts/src/data-accessor.ts (DataAccessor interface)
 * @see packages/contracts/src/postgres-sync-spec.ts (sync semantics spec)
 * @see docs/adr/ (ADR-TBD: cloud-sync architecture — to be authored in T9062)
 */
export {};
//# sourceMappingURL=postgres-data-accessor.js.map