@cascade-fyi/sati-agent0-sdk 0.3.0 → 0.4.0

package/CHANGELOG.md

@@ -5,6 +5,34 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.4.0] - 2026-02-12
+
+### Breaking Changes
+
+- **`SatiSDK` renamed to `SatiAgent0`** - the old class name is removed entirely. Migration: `import { SatiAgent0 } from "@cascade-fyi/sati-agent0-sdk"`
+- **`SatiSDKConfig` renamed to `SatiAgent0Config`** - same migration pattern
+- **`FeedbackCache` removed** - moved to `@cascade-fyi/sati-sdk` (import from there if needed directly)
+
+### Changed
+
+- Internal delegation to `@cascade-fyi/sati-sdk` convenience methods - `SatiAgent0` is now a thin CAIP-2 type-conversion wrapper over `Sati` class
+- `SatiAgent` internally wraps `SatiAgentBuilder` from sati-sdk for registration and updates
+- Reduced bundle size: duplicated logic (content parsing, schema resolution, cache, slot-to-timestamp) removed in favor of sati-sdk
+
+### Added
+
+- `sdk.sati` accessor - exposes the underlying `Sati` instance for direct access to native Solana types
+
+### Dependencies
+
+- Requires `@cascade-fyi/sati-sdk` >= 0.7.0
+
+## [0.3.1] - 2026-02-12
+
+### Fixed
+
+- SIWS counterparty message schema name corrected from `FeedbackPublic` to `FeedbackPublicV1` in `giveFeedback()` and `prepareFeedback()` - mismatched name caused signature verification failures on-chain
+
 ## [0.3.0] - 2026-02-12
 
 ### Added
@@ -99,6 +127,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Transaction sender support for browser wallet integration
 - Re-exports of agent0-sdk types and SATI constants for consumer convenience
 
+[0.4.0]: https://github.com/cascade-protocol/sati/compare/@cascade-fyi/sati-agent0-sdk@0.3.1...@cascade-fyi/sati-agent0-sdk@0.4.0
+[0.3.1]: https://github.com/cascade-protocol/sati/compare/@cascade-fyi/sati-agent0-sdk@0.3.0...@cascade-fyi/sati-agent0-sdk@0.3.1
 [0.3.0]: https://github.com/cascade-protocol/sati/compare/@cascade-fyi/sati-agent0-sdk@0.2.0...@cascade-fyi/sati-agent0-sdk@0.3.0
 [0.2.0]: https://github.com/cascade-protocol/sati/compare/@cascade-fyi/sati-agent0-sdk@0.1.1...@cascade-fyi/sati-agent0-sdk@0.2.0
 [0.1.1]: https://github.com/cascade-protocol/sati/compare/@cascade-fyi/sati-agent0-sdk@0.1.0...@cascade-fyi/sati-agent0-sdk@0.1.1

package/README.md

@@ -1,8 +1,8 @@
 # @cascade-fyi/sati-agent0-sdk
 
-Agent0-compatible adapter for [SATI](https://github.com/cascade-protocol/sati) - Solana Agent Trust Infrastructure.
+[ERC-8004](https://eips.ethereum.org/EIPS/eip-8004) agent identity and reputation on Solana. Register agents, collect feedback, query reputation, search by capabilities - all on-chain, zero config.
 
-API-compatible adapter for [agent0-sdk](https://github.com/agent0-ai/agent0-sdk) that routes all operations through SATI's Solana infrastructure instead of EVM chains. Same method names and types - write operations return `SolanaTransactionHandle<T>` (compatible with agent0-sdk's `TransactionHandle` via `.hash`, `.waitMined()`, `.waitConfirmed()`).
+API-compatible with [agent0-sdk](https://github.com/agent0-ai/agent0-sdk) - same method names and types, but routes through [SATI](https://github.com/cascade-protocol/sati)'s Solana infrastructure instead of EVM chains. Write operations return `SolanaTransactionHandle<T>` (compatible with agent0-sdk's `TransactionHandle` via `.hash`, `.waitMined()`, `.waitConfirmed()`).
 
 ## Installation
 
@@ -18,11 +18,11 @@ pnpm add @cascade-fyi/sati-sdk @solana/kit @solana-program/token-2022 agent0-sdk
 ## Quick Start
 
 ```typescript
-import { SatiSDK, Outcome } from "@cascade-fyi/sati-agent0-sdk";
+import { SatiAgent0, Outcome } from "@cascade-fyi/sati-agent0-sdk";
 import { generateKeyPairSigner } from "@solana/kit";
 
 const signer = await generateKeyPairSigner();
-const sdk = new SatiSDK({
+const sdk = new SatiAgent0({
   network: "devnet",
   signer,
 });
@@ -55,13 +55,13 @@ The SDK supports three modes depending on your use case:
 
 ```typescript
 // Read-only (no signer) - search agents, read feedback
-const readOnly = new SatiSDK({ network: "devnet" });
+const readOnly = new SatiAgent0({ network: "devnet" });
 
 // Server-side (KeyPairSigner) - full write access
-const server = new SatiSDK({ network: "devnet", signer });
+const server = new SatiAgent0({ network: "devnet", signer });
 
 // Browser wallet (TransactionSender) - wallet-signed writes
-const browser = new SatiSDK({ network: "devnet", transactionSender: walletAdapter });
+const browser = new SatiAgent0({ network: "devnet", transactionSender: walletAdapter });
 ```
 
 ---
@@ -85,7 +85,7 @@ agent.setActive(true);
 agent.setX402Support(true);
 agent.setTrust(true, false, false); // reputation only
 
-// Register on-chain via IPFS (requires pinataJwt in config)
+// Register on-chain via IPFS (zero config - no API keys needed)
 const handle = await agent.registerIPFS();
 console.log(agent.agentId, handle.hash);
 ```