Spike: Audit which src/*.ts modules are unreachable from src/index.ts and decide removal vs export

[meshackyaro]

Description

This audit found a consistent pattern of source files that exist in src/ but are never reached from the package's actual public entrypoint (src/index.ts) and, in several cases, aren't imported by any other file in src/ either: src/utils.ts (imports missing dependencies), src/utils/cache.ts's SimpleCache, src/utils/logger.ts's SDKLogger, src/utils/validate.ts, src/stellar/horizon.ts's submitTransaction, src/hooks/* (not exported from the root, tracked in #81), and src/errors.ts's TrustFlowError itself (used internally everywhere, but not exported — a different flavor of the same "unreachable from outside" problem). Each of these has its own narrow companion issue in this batch, but there's no single place that decided, module by module, "is this dead code to delete, or a real feature that should be exported and documented" — leaving open the risk that future contributors keep independently rediscovering (or worse, silently reimplementing) functionality that already exists but isn't reachable.

Component

SDK

Difficulty

🟣 Spike — investigation required, scope not yet defined

Tasks

• Enumerate every exported symbol in src/ and trace whether it's reachable from src/index.ts (directly or transitively)
• For each unreachable module/symbol, classify it as "delete" or "export + document"
• Cross-reference against the companion per-module issues already filed in this batch so decisions aren't duplicated
• Produce a short written recommendation and file/close the relevant per-module issues accordingly

Acceptance Criteria

• A written audit listing every currently-unreachable src/ module/symbol and its disposition (delete vs export)
• Follow-up issues filed or closed to match the recommendation

Estimated Time

1-2 days (time-boxed spike)

[dee-john]

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

i’m very conversant in solving problems like this, let me work on it

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

[entitydev30]

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

Kindly assign me to this issue

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

[Johnjnr1]

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

i’m very conversant in solving problems like this, let me work on it

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

[doncross03]

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

Hello Maintainer, I have carefully reviewed the issue and understand the requirements and expected outcome. I am confident in my ability to deliver a clean and effective solution that meets the acceptance criteria. Kindly assign this issue to me.

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

[Sharon-dev-create]

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

I have experience with this, kindly assign the issue to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Sharon-dev-create to this issue.

[Ahbiz]

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

Hi, I'd be glad to work on this issue. I've reviewed the requirements and believe I can implement the fix properly while keeping the existing functionality intact. I'm genuinely interested in contributing to the project, so I'd appreciate the opportunity to take this one. I’ll make sure the PR is focused, tested, and aligned with the project's conventions.

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

[connelevalsam]

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

I like this project and would like to work on this.

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

[drips-wave]

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

🧑‍💻 @connelevalsam: 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 🌊