feat(opapi)!: generate transport-agnostic client code instead of axios

[slvnperron]

What

Bumps @bpinternal/opapi to 2.0.0. The opapi client generator no longer emits axios-based code:

• The generated Client constructor now takes any transport implementing a minimal generated HttpClient interface ({ request: <T>(config: RequestConfig) => Promise<{ data: T }> }) instead of an AxiosInstance, and stores it as httpClient.
• to-axios.ts → to-request.ts: toAxiosRequest → toRequest, returning a RequestConfig ({ method, url, headers, data }) instead of an AxiosRequestConfig. The ClientProps.toAxiosRequest override is now ClientProps.toRequest.
• The generated toApiError and the generated request handler detect http errors structurally (any error carrying response.data) instead of via axios.isAxiosError, so axios-based transports keep working unchanged.

The legacy openapi-generator path (remote typescript-axios template) is untouched.

Why

This lets @botpress/client (and other generated clients) drop axios entirely in favor of a small fetch-based transport — smaller bundles and one less dependency to hoist. The botpress monorepo change consuming this is prepared separately; until @botpress/api ships with opapi 2.0.0 it post-processes the generated output into this exact shape.

Testing

• pnpm build, pnpm check:type pass.
• pnpm test: 25/26 pass; the one failure (server.test.ts bun-types/@types/node lib conflicts) is pre-existing and reproduces on master.

🤖 Generated with Claude Code

[greptile-apps]

Greptile Summary

This PR makes generated opapi clients independent of Axios. The main changes are:

• Adds generated request and HTTP transport interfaces.
• Renames the Axios request mapper to a transport-neutral mapper.
• Replaces Axios-specific error checks with structural checks.
• Publishes the changes as opapi 2.0.0.

Confidence Score: 4/5

Consumer builds and fetch-based error handling can break on the new generated client path.

• Strict TypeScript module settings can reject the generated import.
• Fetch-style transports can return HTTP error bodies as successful results.
• Plain structural HTTP errors lose their response details in generated handlers.

opapi/src/generators/client-node.ts and opapi/src/handler-generator/export-handler.ts

Important Files Changed

Filename	Overview
opapi/src/generator.ts	Renames the generated request helper and calls the matching generator.
opapi/src/generators/client-node.ts	Adds the transport-neutral client contract, with build compatibility and HTTP-status handling bugs.
opapi/src/handler-generator/export-handler.ts	Removes the Axios import, but excludes structurally valid HTTP errors that are not Error instances.
opapi/CHANGELOG.md	Documents the breaking API and provides a fetch-based transport example.
opapi/package.json	Updates the package version to 2.0.0.

_{Reviews (1): Last reviewed commit: "style(opapi): prettier formatting" | Re-trigger Greptile}