samva 0.2.0 → 0.4.0

package/AGENTS.md

@@ -6,7 +6,7 @@ required.
 
 Effect applications should import Pascal-cased domain modules from focused subpaths such as
 `samva/effect/email` and provide `Client.layerFetch` from `samva/effect/client`. Install the optional
-peer `effect@4.0.0-beta.102` when using those entrypoints. Keep that exact beta pinned. Tagged API
+peer `effect@4.0.0-rc.112` when using those entrypoints. Keep that exact release candidate pinned. Tagged API
 failures remain in the Effect error channel and can be handled with `Effect.catchTag`.
 
 Treat exported request and response types as the API contract. Do not import package-internal files

package/README.md

@@ -65,7 +65,7 @@ const messages = await client.messages.list({
 Install `effect` next to `samva` when using the Effect entrypoint:
 
 ```bash
-bun add samva effect@4.0.0-beta.102
+bun add samva effect@4.0.0-rc.112
 ```
 
 ```typescript
@@ -114,6 +114,10 @@ const client = createClient({
 
 For terminal workflows (`samva login`, `samva org use`, `samva email send --dry-run`), see the [`@samva/cli` README](https://github.com/AryaLabsHQ/samva/tree/main/packages/cli).
 
+The Promise and Effect clients identify their public SDK surface and package version with the
+advisory `x-samva-client` request header. Supply your own value in `headers`, or set the header to
+`null` in Promise request options or `undefined` in Effect client configuration to omit it.
+
 ## Service Surface
 
 The Promise client exposes:
@@ -124,6 +128,7 @@ The Promise client exposes:
 - `conversations`
 - `design`
 - `email`
+- `media`
 - `messages`
 - `operations`
 - `organizations`
@@ -139,6 +144,7 @@ The Effect SDK exposes Pascal-cased domain modules with lower-camel operations:
 - `Conversations`
 - `Design`
 - `Email`
+- `Media`
 - `Messages`
 - `Operations`
 - `Organizations`
@@ -148,6 +154,11 @@ The Effect SDK exposes Pascal-cased domain modules with lower-camel operations:
 
 Effect operations take direct parameter objects: body, path, and query fields are not wrapped in `payload` or `params` envelopes. Import the modules you use from `samva/effect/<lower-kebab>` and provide `Client.layerFetch` once at the program boundary. `Client.raw` exposes the underlying generated client for advanced access, but ordinary workflows do not require it.
 
+Email attachments use organization-owned media. Call `media.create`, upload the bytes with the
+returned instruction, call `media.complete`, and pass the ready `mediaId` to `email.send` or
+`messages.send`. A message accepts at most 10 attachments totaling 25 MiB of raw bytes; the same
+budget covers inline base64 content and owned media references. Remote URL attachments are not.
+
 Effect failures carry Samva's real tagged errors (`RateLimitedError`, `ValidationError`, `PaymentRequiredError`, …) directly in the error channel, so `Effect.catchTag("RateLimitedError", …)` works against any operation without enumerating status codes, and each error exposes its own fields (no wrapper `cause`). The SDK also exports category helpers such as `isRetryable`, `isTransient`, `catchAuthError`, and `catchTransient`. Success values decode to domain types: annotated absolute instants become `Date`, sensitive fields become `Redacted`, and unannotated wire timestamps remain strings.
 
 ### Default-on retry
@@ -369,8 +380,8 @@ subclass for failures declared by OpenAPI. Network and malformed-response failur
 const result = await client.raw.messages.send({
   body: {
     to: [{ contactId: "contact-id" }],
-    channel: "sms",
-    sms: { text: "Hello" },
+    channel: "email",
+    email: { subject: "Hello", text: "Hello" },
   },
 });