Document issue inapplicability - STDIO to HTTP migration not relevant to HTTP client library

[Copilot]

After thorough analysis of the repository and Issue #22, I've determined that the Smithery STDIO to HTTP transport migration is not applicable to this codebase.

Repository Analysis

This repository is a TypeScript HTTP client library for the Hevy fitness app API, not a Smithery MCP (Model Context Protocol) server. Key findings:

• Client-side SDK: Generated from OpenAPI specifications using @hey-api/openapi-ts
• Already uses HTTP: All API calls use standard HTTP requests via the fetch API to api.hevyapp.com
• No server components: Contains no server-side code, transport layers, or STDIO mechanisms
• No MCP/Smithery code: No references to Smithery, MCP servers, or STDIO transport found

Issue Context Mismatch

The issue describes migrating Smithery hosted servers from STDIO to Streamable HTTP transport, which requires:

• Server-side code modifications
• Transport layer configuration changes
• MCP server implementation updates

None of these components exist in this repository, as it's purely a client library that already communicates over HTTP.

Recommendation

This issue should be closed as "not applicable" or reassigned to the correct repository containing a Smithery MCP server that requires STDIO to HTTP migration.

Fixes #22.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

@chrisdoc 👋 This repository doesn't have Copilot instructions. With Copilot instructions, I can understand the repository better, work faster and produce higher quality PRs.

I can generate a .github/copilot-instructions.md file for you automatically. Click here to open a pre-filled issue and assign it to me. I'll write the instructions, and then tag you for review.