SDK drift: `ServerManagerOptions` type is never re-exported from the TypeScript package root, unlike sibling options types

[realfishsam]

Drift

sdks/typescript/pmxt/server-manager.ts lines 13-17 define export interface ServerManagerOptions { baseUrl?; maxRetries?; retryDelayMs?; }, used as the constructor parameter type at line 58. sdks/typescript/index.ts line 37 only re-exports the class: export { ServerManager } from "./pmxt/server-manager.js"; — there is no export type { ServerManagerOptions }. This is inconsistent with every sibling constructor-options interface in the same package, which are all re-exported: ExchangeOptions/SuiBetsOptions (index.ts line 32), RouterOptions (line 36), FeedClientOptions (line 34). Confirmed via grep that ServerManagerOptions is referenced nowhere else in the TS SDK.

TypeScript SDK

sdks/typescript/pmxt/server-manager.ts:13-17 (definition), sdks/typescript/index.ts:37 (export site, missing the type export).

Python SDK

N/A — ServerManager.__init__ takes a plain base_url: str (already tracked as #1327), so there's no equivalent typed options structure to export or omit.

Expected

If ServerManagerOptions is part of the public constructor contract, it should be exported from the package root like its siblings, so consumers can type-annotate variables (const opts: ServerManagerOptions = {...}) without reaching into the internal ./pmxt/server-manager.js submodule path.

Impact

Minor but real DX/API-surface inconsistency — TS consumers lose type-checking ergonomics for ServerManager construction that they get "for free" with every other exchange/router/feed-client class.

---

Found by automated SDK cross-language drift audit