channelReconciler.ts: Refactor reconciliation loop to separate concerns

[Kingsman-99]

Description

src/channelReconciler.ts mixes data fetching, diffing, and persistence in a single function. This makes the reconciliation logic hard to test in isolation. Separate the three concerns into distinct functions called by the main loop.

Acceptance Criteria

• fetchChannelState(), diffChannelState(), and persistChannelDiff() are extracted as standalone, testable functions
• The main reconciliation loop delegates to these three functions
• All existing tests still pass without modification
• Unit tests pass

Context

• Target file: src/channelReconciler.ts
• The public reconcile() function signature must not change

[chideraisiguzor]

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

I’m a software developer with experience in JavaScript, TypeScript, React, Node.js, Rust, and blockchain development, and I’m particularly interested in contributing to open-source projects where I can solve real problems, learn from experienced contributors, and give back to the developer community.

I have reviewed the issue and believe I can contribute effectively by [briefly describe what you intend to implement/fix]. My approach would be to first understand the existing implementation and project conventions, reproduce the issue where necessary, implement the required changes, and add or update tests to ensure the solution works correctly without introducing regressions.

I’m comfortable working with Git and GitHub, including creating branches, making focused commits, submitting pull requests, responding to review feedback, and making improvements based on maintainer recommendations.

I would be grateful for the opportunity to work on this issue and contribute to the project. I’m also happy to discuss my proposed approach before beginning implementation if that would be helpful.

Thank you for your time and for maintaining this open-source project. I look forward to contributing.

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

[drips-wave]

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

🧑‍💻 @chideraisiguzor: 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 as part of the Third Campaign campaign!

@chideraisiguzor's PR #710 was approved and merged by @Kingsman-99.

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

👏 Great work, @chideraisiguzor! Keep contributing to Stellar-split.

[drips-wave]

This issue has been completed by @chideraisiguzor as part of the Stellar Wave Program's 8th Wave 🥳

😎 @chideraisiguzor: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.