Increase SDK CraftClient test coverage to all public methods

[temma02]

Description

packages/sdk/tests/client.test.ts covers the core auth and template methods but getDeploymentHealth, getDeploymentAnalytics, cancelSubscription, and getSubscription have no tests. SDK consumers rely on these methods being correct.

Requirements and context

• Must be secure, tested, and documented where applicable
• Should stay reviewable and fit the current monorepo structure
• Relevant files: packages/sdk/src/client.ts, packages/sdk/tests/client.test.ts

Suggested execution

• Create branch: issue-025-sdk-client-full-method-coverage
• Keep changes scoped to the issue and reference the task IDs in the PR

Implement changes

• Add tests for getDeploymentHealth, getDeploymentAnalytics, cancelSubscription, getSubscription
• Use the existing mockFetch helper to simulate success and error responses
• Assert that CraftApiError is thrown with the correct status code on non-2xx responses

Test and commit

• Run vitest run packages/sdk and confirm 100% method coverage
• Include request/response examples for each new test case
• Edge case: setAccessToken not called before a protected method — should throw CraftApiError with 401

Example commit message

test(sdk): add full coverage for all CraftClient public methods

Guidelines

• Prefer small, reviewable PRs
• Keep naming and data contracts consistent with the spec docs

[Ekenesamuel8]

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

I will like to work on this issue

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

[dot-enny]

@dot-enny has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

I would like to work on this.

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

[drips-wave]

Congratulations, @dot-enny! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

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