Add missing "./escrow" subpath export to package.json's exports map

[meshackyaro]

Description

README.md's own "Basic Usage" Quick Start example does import { createEscrow } from '@trustflow/sdk/escrow';. But package.json's "exports" field only declares a single "." condition (types/import/require all pointing at dist/index.*) — there is no "./escrow" entry. Under Node's package-exports resolution, any subpath not explicitly listed is unresolvable, so the documented example fails with ERR_PACKAGE_PATH_NOT_EXPORTED for real consumers of the published package.

Component

SDK

Difficulty

🟢 Easy

Tasks

• Decide whether createEscrow should just be part of the root export (simplest, since src/index.ts already re-exports the ./escrow barrel) or whether a genuine ./escrow subpath build target should be added via tsup.config.ts
• If keeping root-only exports, fix the README example instead (tracked in a companion documentation issue) and don't add the subpath
• If adding the subpath, wire it into tsup.config.ts's entry and package.json's exports map with matching types/import/require conditions
• Verify the chosen import path actually resolves from a built node_modules install, not just from source

Acceptance Criteria

• Every import path shown in README.md and examples/ actually resolves against the published package's exports map
• A CI or test step verifies the built package's subpath resolution

Estimated Time

<1 day

[Salauayo]

I’ll audit the SDK exports against every import path documented in the README and examples, determine the simplest correct export strategy, and update the package configuration or documentation accordingly. I’ll then build and test the package from a clean node_modules install to verify the documented imports resolve correctly and add a CI/test check to prevent future export drift.

[midexol]

@midexol has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi maintainer I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @midexol to this issue.

[Jaydbrown]

@Jaydbrown has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

hello maintainer, kindly assign these issues. i am sure in my expertise in handling them

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Jaydbrown to this issue.

[drips-wave]

Congratulations, @Jaydbrown! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @Jaydbrown: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@Jaydbrown's PR #201 was approved and merged by @meshackyaro.

🏆 @Jaydbrown: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (777 total points). Track your full progress on GrantFox.

👏 Great work, @Jaydbrown! Keep contributing to trustflow-protocol.