fix(agent-client): normalize path joining in HttpRequester

[Scra3]

Summary

• When api_endpoint has no trailing slash (e.g. https://example.com/backoffice/v1) and action endpoints have no leading slash (e.g. forest/actions/my-action), HttpRequester produces broken URLs like /backoffice/v1forest/actions/...
• Extract a buildUrl() method that ensures the path always starts with / before concatenation
• Applied to both query() and stream() methods

Test plan

• All 282 agent-client tests pass
• New test verifies path without leading slash is normalized
• Verify action execution works with Ruby backend endpoints

🤖 Generated with Claude Code

Note

Normalize path joining in HttpRequester to prevent malformed URLs

Extracts URL construction into a private buildUrl(path) method in http-requester.ts that ensures paths always have a leading / before joining with baseUrl. Both query and stream now use this helper instead of inline concatenation. A test covering paths without a leading slash is added in http-requester.test.ts.

^{Macroscope summarized 125d71d.}

[qltysh]

Coverage Impact

This PR will not change total coverage.

Modified Files with Diff Coverage (1)

Rating	File	% Diff	Uncovered Line #s
	packages/agent-client/src/http-requester.ts	100.0%
	Total	100.0%

🚦 See full report on Qlty Cloud »

🛟 Help

• Diff Coverage: Coverage for added or modified lines of code (excludes deleted files). Learn more.

• Total Coverage: Coverage for the whole repository, calculated as the sum of all File Coverage. Learn more.

• File Coverage: Covered Lines divided by Covered Lines plus Missed Lines. (Excludes non-executable lines including blank lines and comments.)

  • Indirect Changes: Changes to File Coverage for files that were not modified in this PR. Learn more.