@hsuite/smart-engines-sdk 4.1.0 → 5.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +23 -0
- package/dist/index.d.ts +432 -346
- package/dist/index.js +59 -10
- package/dist/index.js.map +1 -1
- package/dist/nestjs/index.d.ts +1261 -1176
- package/dist/nestjs/index.js +59 -10
- package/dist/nestjs/index.js.map +1 -1
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,28 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 5.0.0 — 2026-06-27
|
|
4
|
+
|
|
5
|
+
### Breaking changes
|
|
6
|
+
|
|
7
|
+
- **Root `CreateAccountRequest` / `CreateTokenRequest` now refer to the BaaS shapes.** These exports previously pointed to the legacy validator-direct request types used by `SmartEngineClient.createAccount` / `createToken`. They now point to the BaaS request types consumed by `BaasClient.entities`. If you need the validator-direct request types, import `ValidatorCreateAccountRequest` and `ValidatorCreateTokenRequest` from the SDK root.
|
|
8
|
+
- **`EntityCreationResult.agentId` is now required.** The field was optional in 4.2.0; it is now guaranteed on normalized results and is backfilled from `entityId` when the host response omits it. Callers constructing this type directly must now include `agentId`.
|
|
9
|
+
|
|
10
|
+
### Added
|
|
11
|
+
|
|
12
|
+
- **Exported client interfaces:** `IBaasClient`, `IEntitiesClient`, and `IRulesClient` are now part of the public surface.
|
|
13
|
+
- **Exported `BatchInnerTransaction`** as an alias for `PreparedTransaction`.
|
|
14
|
+
- **BaaS and validator-direct request types are re-exported from the root.** This includes `CreateAccountRequest`, `CreateTokenRequest`, `CreateAgentRequest`, `CreateTopicRequest`, `ValidatorCreateAccountRequest`, and `ValidatorCreateTokenRequest`.
|
|
15
|
+
- **`EntitiesClient` response normalization.** `getById`, `getByRuleRef`, `lookup`, and create/prepare methods now normalize host responses to the stable `EntityInfo` and `EntityCreationResult` shapes.
|
|
16
|
+
|
|
17
|
+
## 4.2.0 — 2026-06-26
|
|
18
|
+
|
|
19
|
+
### Added
|
|
20
|
+
|
|
21
|
+
- **Two-phase EXECUTABLE-agent surface (additive, non-breaking).** Reflects the host change that promotes a payer-funded XRPL agent into an executable AGENT record during the execute-create/finalize half. Lets the app-as-proxy consumer drive the full prepare → fund → execute agent flow type-safely.
|
|
22
|
+
- **`EntityCreationResult.agentId?: string` + `status?: string`.** The host now merges `{ agentId, status }` additively onto the execute-create envelope once the funded entity is promoted to an agent record (`executeCreateAgent`, and the convenience `createAgent` on payer-funded chains). Present ONLY on the agent execute/finalize path; undefined for non-agent entity types and on the prepare half. Field names + `string` types match the host controller's `executeCreate` return (`apps/smart-host/.../entities.controller.ts`) verbatim.
|
|
23
|
+
- **`CreateAgentRequest.rulesConfig?: Record<string, unknown>` + `capabilities?: string[]`.** Carried through `prepareCreateAgent` (which already forwards the whole request body) so the host can stash them VERBATIM on the PENDING registry row at prepare and recover them at execute to mint the agent record — avoiding a `rulesHash` divergence from re-deriving them from the bound rule. Field names + types mirror the host `PrepareCreateDto` / `entity-registry.schema.ts` verbatim. Optional/additive; ignored by the legacy synchronous `createAgent` and by non-agent entity types.
|
|
24
|
+
- **App-as-payer `fundWith` documented.** `CreateAgentRequest.fundWith` now documents that a smart-app may supply a SERVER-SIDE `fundWith` that signs the prepared payer `Payment` with the app's OWN treasury key and sets `payerAccountId` to that treasury account. No new method — the existing `prepareCreateAgent` → `fundWith` → `executeCreateAgent` sequence already supports an app funding an agent on a customer's behalf.
|
|
25
|
+
|
|
3
26
|
## 4.1.0 — 2026-06-25
|
|
4
27
|
|
|
5
28
|
### Added
|