Gap
Core exports and actively uses a NotSupported error class (e.g., both SDKs throw it for operations like fetchClosedOrders/fetchAllOrders when a hosted venue doesn't support them), but core/docs/ERRORS.md's error hierarchy, "HTTP Status Code Mappings" table, and "Error Codes Reference" table list only 12 classes across the 400/401/403/404/429/503 family — no 501/NotSupported appears anywhere in the document.
Core
core/src/errors.ts:152-159 — export class NotSupported extends BaseError { ... }, mapped to HTTP 501, code 'NOT_SUPPORTED'.
TypeScript SDK
Thrown and re-exported — sdks/typescript/pmxt/client.ts:1539 and :1568 (thrown for unsupported operations); sdks/typescript/pmxt/errors.ts:119 (class definition).
Python SDK
N/A checked specifically, but the class exists in core and is part of the shared error taxonomy the doc claims to be exhaustive about.
Evidence
core/docs/ERRORS.md's tables (lines 123-138, 355-370) enumerate every other status/class but never mention 501 or NotSupported, despite core/src/errors.ts defining it alongside the other documented error classes and the TypeScript SDK actively throwing it.
Impact
A reader relying on this doc as an exhaustive error reference has no way to learn about NotSupported — a real, user-facing error class they need to catch when calling operations a given venue doesn't support (a very common occurrence given this repo's per-venue capability variance).
Found by automated Core-to-SDK surface coverage audit
Gap
Core exports and actively uses a
NotSupportederror class (e.g., both SDKs throw it for operations likefetchClosedOrders/fetchAllOrderswhen a hosted venue doesn't support them), butcore/docs/ERRORS.md's error hierarchy, "HTTP Status Code Mappings" table, and "Error Codes Reference" table list only 12 classes across the 400/401/403/404/429/503 family — no 501/NotSupportedappears anywhere in the document.Core
core/src/errors.ts:152-159—export class NotSupported extends BaseError { ... }, mapped to HTTP 501, code'NOT_SUPPORTED'.TypeScript SDK
Thrown and re-exported —
sdks/typescript/pmxt/client.ts:1539and:1568(thrown for unsupported operations);sdks/typescript/pmxt/errors.ts:119(class definition).Python SDK
N/A checked specifically, but the class exists in core and is part of the shared error taxonomy the doc claims to be exhaustive about.
Evidence
core/docs/ERRORS.md's tables (lines 123-138, 355-370) enumerate every other status/class but never mention 501 orNotSupported, despitecore/src/errors.tsdefining it alongside the other documented error classes and the TypeScript SDK actively throwing it.Impact
A reader relying on this doc as an exhaustive error reference has no way to learn about
NotSupported— a real, user-facing error class they need to catch when calling operations a given venue doesn't support (a very common occurrence given this repo's per-venue capability variance).Found by automated Core-to-SDK surface coverage audit