Add regression coverage for RouteTableEntry failure handling

[thlpkee20-wq]

Evidence

• src/services/kyc/KycRouter.ts:41 contains throw new Error('Invalid route table signature. Fails closed.');.
• src/services/kyc/KycRouter.ts:58 contains throw new Error(Jurisdiction ${jurisdiction} not supported. Fails closed.);.
• src/services/kyc/KycRouter.ts:63 contains throw new Error(Configured provider ${providerName} not registered.);.

Problem

RouteTableEntry contains an explicit failure or empty-result path that needs a regression suite to prevent silent behavior changes.

Required change

Exercise the branch evidence in src/services/kyc/KycRouter.ts, assert the returned value or error contract, and add tests for the neighboring normal path and boundary inputs.

Acceptance criteria

• Cover the named behavior with focused automated tests, including the relevant success and failure paths.
• Preserve the existing public contract unless the change includes an explicit compatibility plan.
• Make error and boundary behavior observable and deterministic.

Validation

• Run the focused test file and the surrounding suite.
• Run the repository's configured lint, type, build, or contract checks.
• Include the exercised cases and results in the pull request description.

[odesanyataiwo2017-crypto]

@odesanyataiwo2017-crypto has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

HI, please let me fix this issue!

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

[habeebullahabubakar61-debug]

@habeebullahabubakar61-debug has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hello maintenance, I can work on this issues plz give me.

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

[eteonninob-arch]

@eteonninob-arch has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hello boss, Please assign this issue to me. i checked it out and I am confident i will solve it
my eta is 4 hours

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

[drips-wave]

Congratulations, @odesanyataiwo2017-crypto! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.

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

[drips-wave]

This issue has been completed by @odesanyataiwo2017-crypto as part of the Stellar Wave Program's 9th Wave 🥳

😎 @odesanyataiwo2017-crypto: You earned 100 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.