@naturali/sdk 0.46.0 → 0.47.0

package/dist/index.cjs

@@ -1063,7 +1063,7 @@ var Channels = class {
 	/**
 	* List the channel's conversations
 	*
-	* A cursor page of the channel's conversations, newest first. A conversation is one contact's dialogue on the channel — the continuity anchor that resumes the same runtime session instead of starting fresh per message — so this is the read path for who has talked to the channel and which actor/session their dialogue resolved to.
+	* A cursor page of the channel's conversations, newest first. A conversation is one address's dialogue on the channel — the continuity anchor that resumes the same runtime session instead of starting fresh per message — so this is the read path for who has talked to the channel and which actor/session their dialogue resolved to.
 	* Conversations are created by the inbound path (the WhatsApp webhook, the Discord gateway worker) when a real message arrives; there is no way to create one directly.
 	*
 	*/
@@ -1095,159 +1095,6 @@ var Channels = class {
 		});
 	}
 };
-var Contacts = class {
-	/**
-	* List contacts
-	*
-	* A cursor page of the project's contacts, newest first.
-	* `channel` + `identifier` (supplied together) is the identity lookup — "who is this phone number?" — and returns at most one contact, following the merge pointer to whoever holds the identifier today. `external_id` asks the same question from the customer's side of the mapping. Contacts merged away are omitted unless `include_merged` asks for them.
-	*
-	*/
-	static listContacts(options) {
-		return (options.client ?? client).get({
-			url: "/v1/projects/{project_id}/contacts",
-			...options
-		});
-	}
-	/**
-	* Create a contact
-	*
-	* Record a contact the customer already knows about, optionally with the identifiers it is expected to arrive at.
-	* Optional by design — the inbound path creates contacts on its own. This is for the embedder who has a user in their own system and wants naturali to agree about who that is before the first message, which is what makes `external_id` (and, through it, a session's `tool_context`) useful. No runtime actor is created here; the contact gets one on first need.
-	*
-	*/
-	static createContact(options) {
-		return (options.client ?? client).post({
-			url: "/v1/projects/{project_id}/contacts",
-			...options,
-			headers: {
-				"Content-Type": "application/json",
-				...options.headers
-			}
-		});
-	}
-	/**
-	* Erase a contact
-	*
-	* **Erasure (C4/LGPD).** Not a soft delete and not reversible: the contact's sessions — with their messages and media — its runtime actor, its memory container and every identifier it was reachable at are removed, along with the merge records that reference it.
-	* The upstream deletes happen first, so a failure there aborts before the local pointers are dropped and a retry can still find what is left. A contact that was merged into another cannot be erased directly: its data lives with the survivor, so erase that one.
-	*
-	*/
-	static deleteContact(options) {
-		return (options.client ?? client).delete({
-			url: "/v1/projects/{project_id}/contacts/{contact_id}",
-			...options
-		});
-	}
-	/**
-	* Get a contact
-	*/
-	static getContact(options) {
-		return (options.client ?? client).get({
-			url: "/v1/projects/{project_id}/contacts/{contact_id}",
-			...options
-		});
-	}
-	/**
-	* Update a contact
-	*
-	* Retune the customer-owned fields. At least one is required. Identities are attached and detached through their own sub-resource, because each one is a claim about reachability rather than a property of the record.
-	*
-	*/
-	static updateContact(options) {
-		return (options.client ?? client).patch({
-			url: "/v1/projects/{project_id}/contacts/{contact_id}",
-			...options,
-			headers: {
-				"Content-Type": "application/json",
-				...options.headers
-			}
-		});
-	}
-	/**
-	* Attach an identity
-	*
-	* Attach a `(channel, identifier)` pair — the manual half of what the inbound path does automatically, and the way a customer tells naturali that a number it has never seen belongs to a user it already knows. The identifier must be free (C3).
-	*
-	*/
-	static createContactIdentity(options) {
-		return (options.client ?? client).post({
-			url: "/v1/projects/{project_id}/contacts/{contact_id}/identities",
-			...options,
-			headers: {
-				"Content-Type": "application/json",
-				...options.headers
-			}
-		});
-	}
-	/**
-	* Detach an identity
-	*
-	* Detach an identifier attached in error. Refused with `identity_in_use` once a dialogue hangs off it: dropping an identifier with history is erasure wearing a smaller name, and erasure has its own route that actually removes the messages instead of orphaning them.
-	*
-	*/
-	static deleteContactIdentity(options) {
-		return (options.client ?? client).delete({
-			url: "/v1/projects/{project_id}/contacts/{contact_id}/identities/{identity_id}",
-			...options
-		});
-	}
-	/**
-	* List the contact's conversations
-	*
-	* Every dialogue the contact has, across channels, newest first. The channel-scoped list answers "who has talked to this number?"; this one answers "where has this human talked to us?" — the read that makes a merge visible, since both channels' rows then appear under one contact.
-	*
-	*/
-	static listContactConversations(options) {
-		return (options.client ?? client).get({
-			url: "/v1/projects/{project_id}/contacts/{contact_id}/conversations",
-			...options
-		});
-	}
-	/**
-	* Merge another contact into this one
-	*
-	* Fold `source_contact_id` into this contact — "same human, two identifiers" (C4).
-	* What moves: every identity and every conversation, so the survivor's history is the union of both. What is *shared* rather than moved: agent memory — the runtime hangs it off the actor, so the source's actor is re-pointed at the survivor's memory container and both keep answering with one recollection. Existing sessions keep working, which is the point of not rewriting them.
-	* The source is not deleted: it stays as a tombstone pointing at the survivor, and the returned merge record lists exactly what moved, so the merge can be audited and reverted.
-	*
-	*/
-	static mergeContact(options) {
-		return (options.client ?? client).post({
-			url: "/v1/projects/{project_id}/contacts/{contact_id}:merge",
-			...options,
-			headers: {
-				"Content-Type": "application/json",
-				...options.headers
-			}
-		});
-	}
-	/**
-	* List the contact's merges
-	*
-	* The contact's merge history, newest first, from both sides: the merges it absorbed and the one that absorbed it. The audit half of C4.
-	*
-	*/
-	static listContactMerges(options) {
-		return (options.client ?? client).get({
-			url: "/v1/projects/{project_id}/contacts/{contact_id}/merges",
-			...options
-		});
-	}
-	/**
-	* Revert a merge
-	*
-	* Undo a merge (C4). Replays the record backwards: the identities and conversations it lists go back to the source, the source's actor is re-pointed at the memory it had before, and the tombstone becomes a contact again. Anything that arrived *after* the merge stays with the survivor — it was never the source's.
-	* Only the merge still in force can be reverted; a source that has since been merged somewhere else has to be unwound from the top (`merge_superseded`).
-	*
-	*/
-	static revertContactMerge(options) {
-		return (options.client ?? client).post({
-			url: "/v1/projects/{project_id}/contacts/{contact_id}/merges/{merge_id}:revert",
-			...options
-		});
-	}
-};
 var Generations = class {
 	/**
 	* List an agent's generations
@@ -2171,7 +2018,6 @@ var NaturaliClient = class {
 	auth;
 	boards;
 	channels;
-	contacts;
 	generations;
 	knowledge;
 	models;
@@ -2198,7 +2044,6 @@ var NaturaliClient = class {
 		this.auth = bindResource(Auth, this.http);
 		this.boards = bindResource(Boards, this.http);
 		this.channels = bindResource(Channels, this.http);
-		this.contacts = bindResource(Contacts, this.http);
 		this.generations = bindResource(Generations, this.http);
 		this.knowledge = bindResource(Knowledge, this.http);
 		this.models = bindResource(Models, this.http);
@@ -2218,7 +2063,6 @@ exports.Assistant = Assistant;
 exports.Auth = Auth;
 exports.Boards = Boards;
 exports.Channels = Channels;
-exports.Contacts = Contacts;
 exports.Generations = Generations;
 exports.Knowledge = Knowledge;
 exports.Models = Models;