feature-status.csv

feature_id,area,surface,feature,source_evidence,user_story,expected_behavior,status,last_tested,test_command,observed_behavior,error_id,fix_commit,retest_status,notes
CORE-001,Core API,HTTP,Server health check,docs/api-reference/openapi.json operationId=healthCheck; core/src/server/app.ts,"As an operator, I want to check whether the local PMXT server is alive so that I can route traffic only to healthy instances.",GET /health returns a successful health payload without exchange credentials.,tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand,Health endpoint test passed: GET /health returns status ok and remains public without auth.,,,pass,
CORE-002,Core API,HTTP,Load markets cache,docs/api-reference/openapi.json operationId=loadMarkets; core/src/BaseExchange.ts:585,"As a developer, I want to load and cache markets from an exchange so that repeated iteration does not drift across API calls.",POST /api/{exchange}/loadMarkets loads all markets into markets and marketsBySlug and returns the cached map on later calls unless reload is requested.,tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/unit/baseExchange.core.test.ts; npm test --workspace=pmxt-core -- --runInBand test/pipeline/core-helper-routes.test.ts,"BaseExchange loadMarkets cache test passed for MockExchange, including id/slug reuse through fetchMarket. HTTP route test passed: POST /api/mock/loadMarkets returns a market map keyed by market id after reload.",,,pass,
CORE-003,Core API,HTTP,Fetch markets,docs/api-reference/openapi.json operationId=fetchMarkets; core/src/BaseExchange.ts:628,"As a market-data user, I want to fetch live markets with filters so that I can discover current tradable questions.","GET /api/{exchange}/fetchMarkets accepts filters such as query, limit, status, slug, marketId, outcomeId, eventId, category, tags, sourceExchange, and returns live UnifiedMarket rows.",fixed_retest_pass,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/mockExchange.core.test.ts core/test/pipeline/http-route-regressions.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; RED: npm test --workspace=pmxt-core -- --runInBand test/pipeline/market-http-routes.test.ts; GREEN: npm test --workspace=pmxt-core -- --runInBand test/pipeline/market-http-routes.test.ts test/pipeline/get-post-parity.test.ts test/unit/baseExchange.core.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand,"Retest caught mock fetchMarkets ignoring documented slug, outcomeId, status, sourceExchange, and exchange-alias filters and single-tag GET queries. After fix, HTTP route coverage passes for marketId, slug, outcomeId, eventId, category, tags, sourceExchange, missing source, and closed-status filters; full core suite passed. Current main later regressed this route/mock behavior; core/test/unit/mockExchange.core.test.ts and core/test/pipeline/http-route-regressions.test.ts caught the drift, and c5253f2 restored mock filters, app-local exchange/router overrides, fetchTrades date normalization, single tags query normalization, and HTTP fetchSeries empty-array behavior. Latest verification passed TypeScript and full core Jest (715 passed, 3 skipped).",CORE-FILTERS-001; CORE-HTTP-REGRESSION-001,a45fcf1; c5253f2,pass,Debugging note saved to docs/knowledge/debugging/2026-06-22-pmxt-market-event-filter-fix.md. Current main route/mock behavior is covered by the consolidated HTTP regression test.
CORE-004,Core API,HTTP,Fetch markets paginated,docs/api-reference/openapi.json operationId=fetchMarketsPaginated; core/src/BaseExchange.ts:673,"As a market-data user, I want stable market pagination so that I can page through a snapshot without result drift.","GET /api/{exchange}/fetchMarketsPaginated creates or reuses an in-memory snapshot, returns data, total, and nextCursor, and slices later pages from the same snapshot.",tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/unit/baseExchange.core.test.ts; npm test --workspace=pmxt-core -- --runInBand test/pipeline/market-http-routes.test.ts,BaseExchange direct and HTTP route tests passed: fetchMarketsPaginated returns stable cursor pages with total count and sequential mock market ids across pages.,,,pass,
CORE-005,Core API,HTTP,Fetch events paginated,docs/api-reference/openapi.json operationId=fetchEventsPaginated; core/src/BaseExchange.ts:743,"As a market-data user, I want stable event pagination so that event pages stay consistent while I browse.","GET /api/{exchange}/fetchEventsPaginated creates or reuses an event snapshot and returns data, total, and nextCursor.",tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/unit/baseExchange.core.test.ts; npm test --workspace=pmxt-core -- --runInBand test/pipeline/market-http-routes.test.ts,BaseExchange direct and HTTP route tests passed: fetchEventsPaginated returns stable cursor pages with total count and sequential mock event ids across pages.,,,pass,
CORE-006,Core API,HTTP,Fetch events,docs/api-reference/openapi.json operationId=fetchEvents; core/src/BaseExchange.ts:809,"As a market-data user, I want to fetch events with optional search so that I can browse grouped markets.","GET /api/{exchange}/fetchEvents returns UnifiedEvent rows and supports filters including query, limit, status, eventId, slug, series, category, tags, and sourceExchange.",fixed_retest_pass,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/mockExchange.core.test.ts core/test/pipeline/http-route-regressions.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; RED: npm test --workspace=pmxt-core -- --runInBand test/pipeline/market-http-routes.test.ts; GREEN: npm test --workspace=pmxt-core -- --runInBand test/pipeline/market-http-routes.test.ts test/pipeline/get-post-parity.test.ts test/unit/baseExchange.core.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand,"Retest caught mock fetchEvents ignoring documented slug, series, status, sourceExchange, and exchange-alias filters and single-tag GET queries. After fix, HTTP route coverage passes for eventId, slug, category, tags, sourceExchange, missing series, and closed-status filters; full core suite passed. Current main later regressed this route/mock behavior; core/test/unit/mockExchange.core.test.ts and core/test/pipeline/http-route-regressions.test.ts caught the drift, and c5253f2 restored mock filters, app-local exchange/router overrides, fetchTrades date normalization, single tags query normalization, and HTTP fetchSeries empty-array behavior. Latest verification passed TypeScript and full core Jest (715 passed, 3 skipped).",CORE-FILTERS-001; CORE-HTTP-REGRESSION-001,a45fcf1; c5253f2,pass,Debugging note saved to docs/knowledge/debugging/2026-06-22-pmxt-market-event-filter-fix.md. Current main route/mock behavior is covered by the consolidated HTTP regression test.
CORE-007,Core API,HTTP,Fetch series,docs/api-reference/openapi.json operationId=fetchSeries; core/src/BaseExchange.ts:842,"As a market-data user, I want to fetch recurring series when venues expose them so that I can navigate the Series to Event to Market hierarchy.",GET /api/{exchange}/fetchSeries returns venue series for supported venues and an empty array for venues without a series concept.,fixed_retest_pass,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/mockExchange.core.test.ts core/test/pipeline/http-route-regressions.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; npm test --workspace=pmxt-core -- --runInBand test/unit/baseExchange.core.test.ts; npm test --workspace=pmxt-core -- --runInBand test/pipeline/market-http-routes.test.ts; npm test --workspace=pmxt-core -- --runInBand,"Direct BaseExchange fallback test passed and HTTP retest passed after fix: GET /api/mock/fetchSeries now returns [] for a venue without a series concept instead of 501. Current main later regressed this route/mock behavior; core/test/unit/mockExchange.core.test.ts and core/test/pipeline/http-route-regressions.test.ts caught the drift, and c5253f2 restored mock filters, app-local exchange/router overrides, fetchTrades date normalization, single tags query normalization, and HTTP fetchSeries empty-array behavior. Latest verification passed TypeScript and full core Jest (715 passed, 3 skipped).",CORE-SERIES-001; CORE-HTTP-REGRESSION-001,de0d6a6; c5253f2,pass,Debugging note saved to docs/knowledge/debugging/2026-06-22-pmxt-fetchseries-http-empty-fallback.md. Current main route/mock behavior is covered by the consolidated HTTP regression test.
CORE-008,Core API,HTTP,Fetch single market,docs/api-reference/openapi.json operationId=fetchMarket; core/src/BaseExchange.ts:857,"As a developer, I want a single-market lookup so that I do not have to filter arrays myself.",GET /api/{exchange}/fetchMarket wraps fetchMarkets and returns exactly one UnifiedMarket or throws MarketNotFound when no match exists.,tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/unit/baseExchange.core.test.ts; npm test --workspace=pmxt-core -- --runInBand test/pipeline/market-http-routes.test.ts,BaseExchange direct tests passed for id and slug cache lookup plus MarketNotFound. HTTP route test passed: GET /api/mock/fetchMarket?marketId=mock-m1 returns the requested UnifiedMarket.,,,pass,
CORE-009,Core API,HTTP,Fetch single event,docs/api-reference/openapi.json operationId=fetchEvent; core/src/BaseExchange.ts:957,"As a developer, I want a single-event lookup so that I can load one grouped event by id, slug, or query.",GET /api/{exchange}/fetchEvent wraps fetchEvents and returns exactly one UnifiedEvent or throws EventNotFound when no match exists.,tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/unit/baseExchange.core.test.ts; npm test --workspace=pmxt-core -- --runInBand test/pipeline/market-http-routes.test.ts,BaseExchange direct tests passed for event id lookup plus EventNotFound. HTTP route test passed: GET /api/mock/fetchEvent?eventId=mock-event-0 returns the requested UnifiedEvent with grouped markets.,,,pass,
CORE-010,Core API,HTTP,Fetch OHLCV candles,docs/api-reference/openapi.json operationId=fetchOHLCV; core/src/BaseExchange.ts:977,"As a charting user, I want OHLCV candles for an outcome so that I can plot historical price movement.","GET /api/{exchange}/fetchOHLCV returns PriceCandle rows for an outcome using a required resolution plus optional start, end, and limit.",tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/pipeline/market-http-routes.test.ts test/pipeline/get-post-parity.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand,"HTTP route tests passed for PriceCandle rows with required resolution, ISO start/end query coercion, exact 1h timestamps, limit=3, and candle field sanity. GET/POST parity also passed for resolution=1h, limit=5, and date-time start/end coercion; full core suite passed.",,,pass,
CORE-011,Core API,HTTP,Fetch order book,docs/api-reference/openapi.json operationId=fetchOrderBook; core/src/BaseExchange.ts:1005,"As a trader, I want an order book for an outcome so that I can inspect bids, asks, and available depth.","GET /api/{exchange}/fetchOrderBook returns bids, asks, and timestamp for live books and supports historical snapshots or ranges where implemented.",tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/pipeline/market-http-routes.test.ts test/pipeline/get-post-parity.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand,"HTTP route tests passed for bids, asks, timestamps, limit=3 depth, and market-id outcome alias resolution matching direct outcome-token books. GET/POST parity also passed for deterministic prices and sizes; full core suite passed.",,,pass,
CORE-012,Core API,HTTP,Fetch order books batch,docs/api-reference/openapi.json operationId=fetchOrderBooks; core/src/BaseExchange.ts:1018,"As a trader, I want order books for multiple outcomes in one request so that I can compare related prices efficiently.",POST /api/{exchange}/fetchOrderBooks returns a map from outcome id to OrderBook for supported venues.,tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/unit/mockExchange.core.test.ts; npm test --workspace=pmxt-core -- --runInBand test/pipeline/market-http-routes.test.ts,MockExchange direct and HTTP route tests passed: fetchOrderBooks returns a map keyed by every requested outcome id and each returned book contains bids and asks.,,,pass,
CORE-013,Core API,HTTP,Fetch public trades,docs/api-reference/openapi.json operationId=fetchTrades; core/src/BaseExchange.ts:1031,"As a market-data user, I want raw trade history for an outcome so that I can analyze executed market activity.","GET /api/{exchange}/fetchTrades returns Trade rows and accepts optional start, end, and limit parameters.",fixed_retest_pass,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/mockExchange.core.test.ts core/test/pipeline/http-route-regressions.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; RED: npm test --workspace=pmxt-core -- --runInBand test/unit/mockExchange.core.test.ts test/pipeline/market-http-routes.test.ts; GREEN: npm test --workspace=pmxt-core -- --runInBand test/unit/mockExchange.core.test.ts test/pipeline/market-http-routes.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand,"Retest caught MockExchange ignoring start/end filters and HTTP GET dispatch passing fetchTrades start/end query values as strings. After fix, direct mock and HTTP routes apply start/end before limit and dispatch Date values to exchanges; full core suite passed. Current main later regressed this route/mock behavior; core/test/unit/mockExchange.core.test.ts and core/test/pipeline/http-route-regressions.test.ts caught the drift, and c5253f2 restored mock filters, app-local exchange/router overrides, fetchTrades date normalization, single tags query normalization, and HTTP fetchSeries empty-array behavior. Latest verification passed TypeScript and full core Jest (715 passed, 3 skipped).",CORE-TRADES-001; CORE-HTTP-REGRESSION-001,d31a42e; c5253f2,pass,Debugging note saved to docs/knowledge/debugging/2026-06-22-pmxt-fetchtrades-time-range-fix.md. Current main route/mock behavior is covered by the consolidated HTTP regression test.
CORE-014,Core API,HTTP,Create order,docs/api-reference/openapi.json operationId=createOrder; core/src/BaseExchange.ts:1045,"As a trader, I want to place an order through a unified method so that I can trade across venues with one interface.","POST /api/{exchange}/createOrder validates required order fields, supports buy or sell and market or limit types where supported, and returns a normalized Order.",tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/pipeline/get-post-parity.test.ts; npm test --workspace=pmxt-core -- --runInBand test/pipeline/order-http-routes.test.ts,"Validation path passed for missing required order fields. HTTP route test passed: POST /api/mock/createOrder places a filled market order and returns a normalized Order with matching market, outcome, fill, and remaining fields.",,,pass,
CORE-015,Core API,HTTP,Build order,docs/api-reference/openapi.json operationId=buildOrder; core/src/BaseExchange.ts:1061,"As a trader or middleware, I want to build an order without submitting it so that I can inspect, sign, or forward it later.",POST /api/{exchange}/buildOrder returns a BuiltOrder payload without placing the order.,tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/pipeline/order-lifecycle.test.ts; npm test --workspace=pmxt-core -- --runInBand test/pipeline/order-http-routes.test.ts,"MockExchange direct and HTTP route tests passed: buildOrder returns an inspectable BuiltOrder with exchange, params, and raw payload and does not place an order.",,,pass,
CORE-016,Core API,HTTP,Submit built order,docs/api-reference/openapi.json operationId=submitOrder; core/src/BaseExchange.ts:1071,"As a trader, I want to submit a previously built order so that signing and submission can be separated.",POST /api/{exchange}/submitOrder accepts a BuiltOrder from buildOrder and returns the resulting normalized Order.,tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/pipeline/order-lifecycle.test.ts; npm test --workspace=pmxt-core -- --runInBand test/pipeline/order-http-routes.test.ts,"MockExchange direct and HTTP route tests passed: submitOrder accepts the BuiltOrder returned by buildOrder, places the order, and returns a normalized filled Order.",,,pass,
CORE-017,Core API,HTTP,Cancel order,docs/api-reference/openapi.json operationId=cancelOrder; core/src/BaseExchange.ts:1081,"As a trader, I want to cancel an open order so that I can remove resting liquidity.",POST /api/{exchange}/cancelOrder cancels an existing order by id and returns the normalized Order result or a venue-specific not-supported error.,fixed_retest_pass,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/mockExchange.core.test.ts core/test/pipeline/http-route-regressions.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; RED: npm test --workspace=pmxt-core -- --runInBand test/pipeline/order-http-routes.test.ts; GREEN: npm test --workspace=pmxt-core -- --runInBand test/pipeline/order-http-routes.test.ts test/unit/mockExchange.core.test.ts test/pipeline/order-lifecycle.test.ts; npx tsc --project core/tsconfig.json --noEmit,"Route-level resting-order cancel initially could not be exercised because createApp ignored the supplied resting mock and used the immediate-fill singleton. After fix, POST cancelOrder returns a canceled order for an open resting order, GET fetchOpenOrders no longer lists it, and locked funds release. Current main later regressed this route/mock behavior; core/test/unit/mockExchange.core.test.ts and core/test/pipeline/http-route-regressions.test.ts caught the drift, and c5253f2 restored mock filters, app-local exchange/router overrides, fetchTrades date normalization, single tags query normalization, and HTTP fetchSeries empty-array behavior. Latest verification passed TypeScript and full core Jest (715 passed, 3 skipped).",CORE-OPEN-001; CORE-HTTP-REGRESSION-001,664a1ae; c5253f2,pass,Debugging note saved to docs/knowledge/debugging/2026-06-22-pmxt-http-open-orders-filter-fix.md. Current main route/mock behavior is covered by the consolidated HTTP regression test.
CORE-018,Core API,HTTP,Fetch order,docs/api-reference/openapi.json operationId=fetchOrder; core/src/BaseExchange.ts:1091,"As a trader, I want to fetch one order by id so that I can check its latest state.",GET /api/{exchange}/fetchOrder returns a normalized Order for supported venues or a not-supported error.,tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/pipeline/order-lifecycle.test.ts; npm test --workspace=pmxt-core -- --runInBand test/pipeline/order-http-routes.test.ts,MockExchange direct tests passed for exact order retrieval and unknown-order error. HTTP route test passed: fetchOrder returns the same normalized order created through POST /api/mock/createOrder.,,,pass,
CORE-019,Core API,HTTP,Fetch open orders,docs/api-reference/openapi.json operationId=fetchOpenOrders; core/src/BaseExchange.ts:1101,"As a trader, I want to list open orders so that I can monitor resting orders.","GET /api/{exchange}/fetchOpenOrders returns open Order rows, optionally filtered by market id.",fixed_retest_pass,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/mockExchange.core.test.ts core/test/pipeline/http-route-regressions.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; RED: npm test --workspace=pmxt-core -- --runInBand test/pipeline/order-http-routes.test.ts; GREEN: npm test --workspace=pmxt-core -- --runInBand test/pipeline/order-http-routes.test.ts test/unit/mockExchange.core.test.ts test/pipeline/order-lifecycle.test.ts; npx tsc --project core/tsconfig.json --noEmit,"Route-level GET fetchOpenOrders now lists resting open orders, filters by marketId, keeps unrelated open orders visible without a filter, and removes canceled orders. Retest caught and fixed both the immediate-fill HTTP singleton setup gap and MockExchange ignoring the marketId argument. Current main later regressed this route/mock behavior; core/test/unit/mockExchange.core.test.ts and core/test/pipeline/http-route-regressions.test.ts caught the drift, and c5253f2 restored mock filters, app-local exchange/router overrides, fetchTrades date normalization, single tags query normalization, and HTTP fetchSeries empty-array behavior. Latest verification passed TypeScript and full core Jest (715 passed, 3 skipped).",CORE-OPEN-001; CORE-OPEN-002; CORE-HTTP-REGRESSION-001,664a1ae; 5478bed; c5253f2,pass,Debugging note saved to docs/knowledge/debugging/2026-06-22-pmxt-http-open-orders-filter-fix.md. Current main route/mock behavior is covered by the consolidated HTTP regression test.
CORE-020,Core API,HTTP,Fetch my trades,docs/api-reference/openapi.json operationId=fetchMyTrades; core/src/BaseExchange.ts:1105,"As an authenticated trader, I want my fill history so that I can reconcile account activity.","GET /api/{exchange}/fetchMyTrades returns UserTrade rows with optional market, outcome, since, until, limit, or cursor filters where supported.",tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/pipeline/order-lifecycle.test.ts; npm test --workspace=pmxt-core -- --runInBand test/pipeline/order-http-routes.test.ts,"MockExchange direct tests passed for fill-created trade fields, outcome filtering, newest-first ordering, partial fills, and reset clearing. HTTP route test passed: fetchMyTrades with outcomeId returns the fill created through createOrder.",,,pass,
CORE-021,Core API,HTTP,Fetch closed orders,docs/api-reference/openapi.json operationId=fetchClosedOrders; core/src/BaseExchange.ts:1109,"As a trader, I want closed order history so that I can audit completed or cancelled orders.",GET /api/{exchange}/fetchClosedOrders returns closed Order rows where the venue supports historical orders.,tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/pipeline/order-lifecycle.test.ts; npm test --workspace=pmxt-core -- --runInBand test/pipeline/order-http-routes.test.ts,MockExchange direct tests passed for filled and canceled closed orders. HTTP route test passed: fetchClosedOrders includes a filled order created through createOrder.,,,pass,
CORE-022,Core API,HTTP,Fetch all orders,docs/api-reference/openapi.json operationId=fetchAllOrders; core/src/BaseExchange.ts:1113,"As a trader, I want all open and closed orders so that I can reconstruct order history.",GET /api/{exchange}/fetchAllOrders returns combined order history where supported.,tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/pipeline/order-lifecycle.test.ts test/unit/mockExchange.core.test.ts; npm test --workspace=pmxt-core -- --runInBand test/pipeline/order-http-routes.test.ts,MockExchange direct tests passed for all statuses and reset clearing history. HTTP route test passed: fetchAllOrders includes orders created through createOrder and submitOrder and remains empty after buildOrder alone.,,,pass,
CORE-023,Core API,HTTP,Fetch positions,docs/api-reference/openapi.json operationId=fetchPositions; core/src/BaseExchange.ts:1123,"As an account user, I want current positions so that I can see my exposure across markets.",GET /api/{exchange}/fetchPositions returns Position rows for the configured account or supplied address where supported.,tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/pipeline/order-lifecycle.test.ts test/unit/mockExchange.core.test.ts; npm test --workspace=pmxt-core -- --runInBand test/pipeline/order-http-routes.test.ts,"MockExchange direct tests passed for position creation, accumulation, weighted entry price, sell reduction/removal, and reset clearing. HTTP route test passed: fetchPositions returns the position created by a filled createOrder call.",,,pass,
CORE-024,Core API,HTTP,Fetch balance,docs/api-reference/openapi.json operationId=fetchBalance; core/src/BaseExchange.ts:1133,"As an account user, I want balances so that I know funds available for trading.",GET /api/{exchange}/fetchBalance returns Balance rows for the configured account or supplied address where supported.,tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/pipeline/get-post-parity.test.ts; npm test --workspace=pmxt-core -- --runInBand test/pipeline/order-http-routes.test.ts,Mock exchange GET and POST fetchBalance parity passed. HTTP route test passed: fetchBalance reflects available balance after a createOrder fill and preserves total = available + locked.,,,pass,
CORE-025,Core API,HTTP,Get execution price,docs/api-reference/openapi.json operationId=getExecutionPrice; core/src/BaseExchange.ts:1146,"As a trader, I want the average execution price for a target size so that I can estimate slippage.",POST /api/{exchange}/getExecutionPrice computes volume-weighted average price from an OrderBook and returns 0 when the requested size cannot fully fill.,tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/unit/baseExchange.core.test.ts; npm test --workspace=pmxt-core -- --runInBand test/pipeline/core-helper-routes.test.ts,BaseExchange helper tests passed weighted buy/sell fill and insufficient-liquidity behavior. HTTP route test passed: POST /api/mock/getExecutionPrice computes a weighted buy execution price from a supplied order book.,,,pass,
CORE-026,Core API,HTTP,Get detailed execution price,docs/api-reference/openapi.json operationId=getExecutionPriceDetailed; core/src/BaseExchange.ts:1158,"As a trader, I want fill details for an execution estimate so that I can understand partial fill behavior and levels consumed.","POST /api/{exchange}/getExecutionPriceDetailed returns detailed fill and partial-fill information from an OrderBook, side, and amount.",tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/unit/baseExchange.core.test.ts; npm test --workspace=pmxt-core -- --runInBand test/pipeline/core-helper-routes.test.ts,"BaseExchange helper tests passed full-fill, partial-fill, and invalid amount behavior. HTTP route test passed: POST /api/mock/getExecutionPriceDetailed reports partial filledAmount and fullyFilled=false for insufficient bid liquidity.",,,pass,
CORE-027,Core API,HTTP,Filter markets,docs/api-reference/openapi.json operationId=filterMarkets; core/src/BaseExchange.ts,"As a developer, I want to filter market arrays locally so that I can apply text and structured criteria after fetching.","POST /api/{exchange}/filterMarkets filters provided markets by string query, structured criteria, or a custom filter function where available.",tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/unit/baseExchange.core.test.ts; npm test --workspace=pmxt-core -- --runInBand test/pipeline/core-helper-routes.test.ts,"BaseExchange helper tests passed text, category, tags, binary price criteria, and predicate filters. HTTP route test passed: POST /api/mock/filterMarkets filters a supplied market array by category and tag criteria.",,,pass,
CORE-028,Core API,HTTP,Filter events,docs/api-reference/openapi.json operationId=filterEvents; core/src/BaseExchange.ts,"As a developer, I want to filter event arrays locally so that I can apply text and structured criteria after fetching.","POST /api/{exchange}/filterEvents filters provided events by string query, structured criteria, or a custom filter function where available.",tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/unit/baseExchange.core.test.ts; npm test --workspace=pmxt-core -- --runInBand test/pipeline/core-helper-routes.test.ts,"BaseExchange helper tests passed text, category, tags, market count, and predicate filters. HTTP route test passed: POST /api/mock/filterEvents filters a supplied event array by category and market-count criteria.",,,pass,
CORE-029,Core API,HTTP,Close exchange resources,docs/api-reference/openapi.json operationId=close; core/src/BaseExchange.ts,"As an application operator, I want to close exchange resources so that WebSocket and network handles are released cleanly.",POST /api/{exchange}/close closes WebSocket connections and other resources for the exchange instance.,tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/pipeline/close-route.test.ts; npm test --workspace=pmxt-core -- --runInBand,close-route pipeline test passed: POST /api/mock/close dispatches close with no args through the exchange factory and returns a success envelope. Full core suite passed.,,,pass,
CORE-030,Router,HTTP,Fetch market matches,docs/api-reference/openapi.json operationId=fetchMarketMatches; core/src/router/Router.ts:450,"As a cross-venue user, I want to find equivalent or related markets on other venues so that I can compare opportunities.","GET /api/router/fetchMarketMatches supports lookup mode and browse mode, returning MatchResult rows from the hosted match catalog or local mock handling.",fixed_retest_pass,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/mockExchange.core.test.ts core/test/pipeline/http-route-regressions.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; RED: npm test --workspace=pmxt-core -- --runInBand test/pipeline/router-http-routes.test.ts; GREEN: npm test --workspace=pmxt-core -- --runInBand test/pipeline/router-http-routes.test.ts test/pipeline/router-local-mock-matches.test.ts test/unit/router-aggregate-methods.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand,"Retest caught /api/router dispatch ignoring app-local Router overrides and calling the hosted API instead. After fix, HTTP route coverage passes for stubbed fetchMarketMatches lookup with relation/includePrices, local mock lookup still returns [], malformed hosted envelopes still fail clearly, and the full core suite passed. Current main later regressed this route/mock behavior; core/test/unit/mockExchange.core.test.ts and core/test/pipeline/http-route-regressions.test.ts caught the drift, and c5253f2 restored mock filters, app-local exchange/router overrides, fetchTrades date normalization, single tags query normalization, and HTTP fetchSeries empty-array behavior. Latest verification passed TypeScript and full core Jest (715 passed, 3 skipped).",CORE-ROUTER-001; CORE-HTTP-REGRESSION-001,7020a6b; c5253f2,pass,Debugging note saved to docs/knowledge/debugging/2026-06-22-pmxt-router-http-local-override-fix.md. Current main route/mock behavior is covered by the consolidated HTTP regression test.
CORE-031,Router,HTTP,Fetch event matches,docs/api-reference/openapi.json operationId=fetchEventMatches; core/src/router/Router.ts:512,"As a cross-venue user, I want to find equivalent or related events on other venues so that I can compare grouped markets.","GET /api/router/fetchEventMatches supports lookup mode and browse mode, returning EventMatchResult rows.",fixed_retest_pass,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/mockExchange.core.test.ts core/test/pipeline/http-route-regressions.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; RED: npm test --workspace=pmxt-core -- --runInBand test/pipeline/router-http-routes.test.ts; GREEN: npm test --workspace=pmxt-core -- --runInBand test/pipeline/router-http-routes.test.ts test/pipeline/router-local-mock-matches.test.ts test/unit/router-aggregate-methods.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand,"HTTP route coverage now passes for stubbed fetchEventMatches lookup using an app-local Router, while existing local mock event lookup and malformed hosted-envelope tests still pass; full core suite passed. Current main later regressed this route/mock behavior; core/test/unit/mockExchange.core.test.ts and core/test/pipeline/http-route-regressions.test.ts caught the drift, and c5253f2 restored mock filters, app-local exchange/router overrides, fetchTrades date normalization, single tags query normalization, and HTTP fetchSeries empty-array behavior. Latest verification passed TypeScript and full core Jest (715 passed, 3 skipped).",CORE-ROUTER-001; CORE-HTTP-REGRESSION-001,7020a6b; c5253f2,pass,Debugging note saved to docs/knowledge/debugging/2026-06-22-pmxt-router-http-local-override-fix.md. Current main route/mock behavior is covered by the consolidated HTTP regression test.
CORE-032,Router,HTTP,Compare market prices,docs/api-reference/openapi.json operationId=compareMarketPrices; core/src/router/Router.ts:551,"As a trader, I want live price comparisons for matched markets so that I can spot venue differences.",POST /api/router/compareMarketPrices returns side-by-side best bid and ask data for identity matches.,fixed_retest_pass,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/mockExchange.core.test.ts core/test/pipeline/http-route-regressions.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; RED: npm test --workspace=pmxt-core -- --runInBand test/pipeline/router-http-routes.test.ts; GREEN: npm test --workspace=pmxt-core -- --runInBand test/pipeline/router-http-routes.test.ts test/pipeline/router-local-mock-matches.test.ts test/unit/router-aggregate-methods.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand,"HTTP route coverage now passes for POST compareMarketPrices, forcing identity matches through the stubbed Router client and mapping best bid, best ask, relation, confidence, reasoning, and venue; full core suite passed. Current main later regressed this route/mock behavior; core/test/unit/mockExchange.core.test.ts and core/test/pipeline/http-route-regressions.test.ts caught the drift, and c5253f2 restored mock filters, app-local exchange/router overrides, fetchTrades date normalization, single tags query normalization, and HTTP fetchSeries empty-array behavior. Latest verification passed TypeScript and full core Jest (715 passed, 3 skipped).",CORE-ROUTER-001; CORE-HTTP-REGRESSION-001,7020a6b; c5253f2,pass,Debugging note saved to docs/knowledge/debugging/2026-06-22-pmxt-router-http-local-override-fix.md. Current main route/mock behavior is covered by the consolidated HTTP regression test.
CORE-033,Router,HTTP,Fetch related markets,docs/api-reference/openapi.json operationId=fetchRelatedMarkets; core/src/router/Router.ts:576,"As a researcher, I want subset or superset related markets so that I can reason about hedges and implications.",GET /api/router/fetchRelatedMarkets returns related PriceComparison rows across venues.,fixed_retest_pass,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/mockExchange.core.test.ts core/test/pipeline/http-route-regressions.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; RED: npm test --workspace=pmxt-core -- --runInBand test/pipeline/router-http-routes.test.ts; GREEN: npm test --workspace=pmxt-core -- --runInBand test/pipeline/router-http-routes.test.ts test/pipeline/router-local-mock-matches.test.ts test/unit/router-aggregate-methods.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand,"HTTP route coverage now passes for fetchRelatedMarkets, returning subset price comparisons with bid/ask fields and excluding overlap rows through the stubbed Router client; full core suite passed. Current main later regressed this route/mock behavior; core/test/unit/mockExchange.core.test.ts and core/test/pipeline/http-route-regressions.test.ts caught the drift, and c5253f2 restored mock filters, app-local exchange/router overrides, fetchTrades date normalization, single tags query normalization, and HTTP fetchSeries empty-array behavior. Latest verification passed TypeScript and full core Jest (715 passed, 3 skipped).",CORE-ROUTER-001; CORE-HTTP-REGRESSION-001,7020a6b; c5253f2,pass,Debugging note saved to docs/knowledge/debugging/2026-06-22-pmxt-router-http-local-override-fix.md. Current main route/mock behavior is covered by the consolidated HTTP regression test.
CORE-034,Router,HTTP,Fetch matched markets,docs/api-reference/openapi.json operationId=fetchMatchedMarkets; core/src/router/Router.ts:610,"As a cross-venue user, I want matched market pairs so that I can inspect catalog relationships.",GET /api/router/fetchMatchedMarkets returns MatchedMarketPair rows from the router catalog.,fixed_retest_pass,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/mockExchange.core.test.ts core/test/pipeline/http-route-regressions.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; RED: npm test --workspace=pmxt-core -- --runInBand test/pipeline/router-http-routes.test.ts; GREEN: npm test --workspace=pmxt-core -- --runInBand test/pipeline/router-http-routes.test.ts test/pipeline/router-local-mock-matches.test.ts test/unit/router-aggregate-methods.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand,"HTTP route coverage now passes for fetchMatchedMarkets, mapping stubbed arbitrage rows into legacy MatchedMarketPair shape with venues, prices, relation, confidence, and null reasoning; full core suite passed. Current main later regressed this route/mock behavior; core/test/unit/mockExchange.core.test.ts and core/test/pipeline/http-route-regressions.test.ts caught the drift, and c5253f2 restored mock filters, app-local exchange/router overrides, fetchTrades date normalization, single tags query normalization, and HTTP fetchSeries empty-array behavior. Latest verification passed TypeScript and full core Jest (715 passed, 3 skipped).",CORE-ROUTER-001; CORE-HTTP-REGRESSION-001,7020a6b; c5253f2,pass,Debugging note saved to docs/knowledge/debugging/2026-06-22-pmxt-router-http-local-override-fix.md. Current main route/mock behavior is covered by the consolidated HTTP regression test.
CORE-035,Router,HTTP,Fetch matched prices,docs/api-reference/openapi.json operationId=fetchMatchedPrices; core/src/router/Router.ts:638,"As a trader, I want matched market prices so that I can compare prices for catalog-paired markets.",GET /api/router/fetchMatchedPrices returns MatchedPricePair rows.,fixed_retest_pass,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/mockExchange.core.test.ts core/test/pipeline/http-route-regressions.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; RED: npm test --workspace=pmxt-core -- --runInBand test/pipeline/router-http-routes.test.ts; GREEN: npm test --workspace=pmxt-core -- --runInBand test/pipeline/router-http-routes.test.ts test/pipeline/router-local-mock-matches.test.ts test/unit/router-aggregate-methods.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand,"HTTP route coverage now passes for fetchMatchedPrices as the legacy alias returning the same MatchedMarketPair shape as fetchMatchedMarkets; full core suite passed. Current main later regressed this route/mock behavior; core/test/unit/mockExchange.core.test.ts and core/test/pipeline/http-route-regressions.test.ts caught the drift, and c5253f2 restored mock filters, app-local exchange/router overrides, fetchTrades date normalization, single tags query normalization, and HTTP fetchSeries empty-array behavior. Latest verification passed TypeScript and full core Jest (715 passed, 3 skipped).",CORE-ROUTER-001; CORE-HTTP-REGRESSION-001,7020a6b; c5253f2,pass,Debugging note saved to docs/knowledge/debugging/2026-06-22-pmxt-router-http-local-override-fix.md. Current main route/mock behavior is covered by the consolidated HTTP regression test.
CORE-036,Router,HTTP,Fetch hedges,docs/api-reference/openapi.json operationId=fetchHedges; core/src/router/Router.ts:599,"As a trader, I want hedging opportunities so that I can offset exposure across related markets.",GET /api/router/fetchHedges returns PriceComparison rows for hedge-like related markets.,fixed_retest_pass,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/mockExchange.core.test.ts core/test/pipeline/http-route-regressions.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; RED: npm test --workspace=pmxt-core -- --runInBand test/pipeline/router-http-routes.test.ts; GREEN: npm test --workspace=pmxt-core -- --runInBand test/pipeline/router-http-routes.test.ts test/pipeline/router-local-mock-matches.test.ts test/unit/router-aggregate-methods.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand,"HTTP route coverage now passes for fetchHedges as the deprecated alias delegating to related-market subset/superset comparisons and matching fetchRelatedMarkets output; full core suite passed. Current main later regressed this route/mock behavior; core/test/unit/mockExchange.core.test.ts and core/test/pipeline/http-route-regressions.test.ts caught the drift, and c5253f2 restored mock filters, app-local exchange/router overrides, fetchTrades date normalization, single tags query normalization, and HTTP fetchSeries empty-array behavior. Latest verification passed TypeScript and full core Jest (715 passed, 3 skipped).",CORE-ROUTER-001; CORE-HTTP-REGRESSION-001,7020a6b; c5253f2,pass,Debugging note saved to docs/knowledge/debugging/2026-06-22-pmxt-router-http-local-override-fix.md. Current main route/mock behavior is covered by the consolidated HTTP regression test.
CORE-037,Router,HTTP,Fetch arbitrage,docs/api-reference/openapi.json operationId=fetchArbitrage; core/src/router/Router.ts:644,"As a trader, I want arbitrage opportunities so that I can find crossed or mispriced matched markets.",GET /api/router/fetchArbitrage returns ArbitrageOpportunity rows.,fixed_retest_pass,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/mockExchange.core.test.ts core/test/pipeline/http-route-regressions.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; RED: npm test --workspace=pmxt-core -- --runInBand test/pipeline/router-http-routes.test.ts; GREEN: npm test --workspace=pmxt-core -- --runInBand test/pipeline/router-http-routes.test.ts test/pipeline/router-local-mock-matches.test.ts test/unit/router-aggregate-methods.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand,"HTTP route coverage now passes for fetchArbitrage with minSpread query params, validated opportunity rows, and existing malformed missing-price rejection coverage; full core suite passed. Current main later regressed this route/mock behavior; core/test/unit/mockExchange.core.test.ts and core/test/pipeline/http-route-regressions.test.ts caught the drift, and c5253f2 restored mock filters, app-local exchange/router overrides, fetchTrades date normalization, single tags query normalization, and HTTP fetchSeries empty-array behavior. Latest verification passed TypeScript and full core Jest (715 passed, 3 skipped).",CORE-ROUTER-001; CORE-HTTP-REGRESSION-001,7020a6b; c5253f2,pass,Debugging note saved to docs/knowledge/debugging/2026-06-22-pmxt-router-http-local-override-fix.md. Current main route/mock behavior is covered by the consolidated HTTP regression test.
CORE-038,Feeds,HTTP,List available feeds,docs/api-reference/openapi.json operationId=feedList; core/src/server/feed-factory.ts,"As a data-feed user, I want to list available feed providers so that I know what external market data can be queried.","GET /api/feeds returns the available feed names, currently binance and chainlink.",tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/pipeline/feed-routes.test.ts; npm test --workspace=pmxt-core -- --runInBand,Feed route test passed: GET /api/feeds returns binance and chainlink.,,,pass,
CORE-039,Feeds,HTTP,Load feed markets,docs/api-reference/openapi.json operationId=feedLoadMarkets; core/src/server/feed-routes.ts,"As a data-feed user, I want feed markets or symbols so that I can know which symbols the feed supports.",GET /api/feeds/{feed}/loadMarkets returns all trading pairs or feeds supported by the selected provider.,tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/pipeline/feed-routes.test.ts; npm test --workspace=pmxt-core -- --runInBand,Feed route tests passed: binance and chainlink loadMarkets return expected BTC pairs through /api/feeds/{feed}/loadMarkets.,,,pass,
CORE-040,Feeds,HTTP,Fetch feed ticker,docs/api-reference/openapi.json operationId=feedFetchTicker; core/src/server/feed-routes.ts,"As a data-feed user, I want one latest ticker so that I can read current external reference prices.",GET /api/feeds/{feed}/fetchTicker requires symbol and returns the latest ticker for that symbol.,tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/pipeline/feed-routes.test.ts; npm test --workspace=pmxt-core -- --runInBand test/pipeline/feed-success-routes.test.ts,"Feed route tests passed: missing Binance relay config returns a 503 with BINANCE_RELAY_WS_URL named, and the mocked success path returns a normalized ticker envelope for the requested symbol.",,,pass,
CORE-041,Feeds,HTTP,Fetch feed tickers,docs/api-reference/openapi.json operationId=feedFetchTickers; core/src/server/feed-routes.ts,"As a data-feed user, I want many latest tickers so that I can monitor several symbols efficiently.",GET /api/feeds/{feed}/fetchTickers returns all latest tickers or a subset from a comma-separated symbols query.,tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/pipeline/feed-routes.test.ts; npm test --workspace=pmxt-core -- --runInBand test/pipeline/feed-success-routes.test.ts,"Feed route tests passed: missing Binance relay config returns a 503 with BINANCE_RELAY_WS_URL named, and the mocked success path parses comma-separated symbols and returns keyed ticker data.",,,pass,
CORE-042,Feeds,HTTP,Fetch feed OHLCV,docs/api-reference/openapi.json operationId=feedFetchOHLCV; core/src/server/feed-routes.ts,"As a charting user, I want feed OHLCV candles so that I can plot external price history.","GET /api/feeds/{feed}/fetchOHLCV requires symbol, accepts timeframe, since, and limit, and returns candle rows where supported.",tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/pipeline/feed-routes.test.ts; npm test --workspace=pmxt-core -- --runInBand test/pipeline/feed-success-routes.test.ts,"Feed route tests passed: unsupported feeds return route-level 501, and a mocked supported feed receives symbol/timeframe/since/limit query parameters and returns OHLCV candle rows.",,,pass,
CORE-043,Feeds,HTTP,Fetch feed order book,docs/api-reference/openapi.json operationId=feedFetchOrderBook; core/src/server/feed-routes.ts,"As a data-feed user, I want an external order book so that I can inspect non-prediction-market liquidity.",GET /api/feeds/{feed}/fetchOrderBook requires symbol and returns an order book where the feed supports it or 501 otherwise.,tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/pipeline/feed-routes.test.ts; npm test --workspace=pmxt-core -- --runInBand test/pipeline/feed-success-routes.test.ts,"Feed route tests passed: unsupported feeds return route-level 501, and a mocked supported feed receives symbol/limit query parameters and returns a normalized order book envelope.",,,pass,
CORE-044,Feeds,HTTP,Fetch Chainlink oracle round,docs/api-reference/openapi.json operationId=feedFetchOracleRound; core/src/server/feed-routes.ts,"As an oracle-data user, I want the latest Chainlink round so that I can inspect on-chain reference data.",GET /api/feeds/{feed}/fetchOracleRound requires feed and returns the latest oracle round where supported.,tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/pipeline/feed-routes.test.ts; npm test --workspace=pmxt-core -- --runInBand test/pipeline/feed-success-routes.test.ts,"Feed route tests passed: missing Chainlink API config returns a 503 with CHAINLINK_API_URL named, and the mocked success path returns the latest oracle round for the requested feed.",,,pass,
CORE-045,Feeds,HTTP,Fetch Chainlink oracle history,docs/api-reference/openapi.json operationId=feedFetchOracleHistory; core/src/server/feed-routes.ts,"As an oracle-data user, I want historical Chainlink rounds so that I can audit price feed history.","GET /api/feeds/{feed}/fetchOracleHistory requires feed and optional limit, returning historical oracle rounds where supported.",tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/pipeline/feed-routes.test.ts; npm test --workspace=pmxt-core -- --runInBand test/pipeline/feed-success-routes.test.ts,"Feed route tests passed: missing Chainlink API config returns a 503 with CHAINLINK_API_URL named, and the mocked success path passes feed/limit to the provider and returns historical oracle rounds.",,,pass,
CORE-046,Feeds,HTTP,Fetch historical feed prices,docs/api-reference/openapi.json operationId=feedFetchHistoricalPrices; core/src/server/feed-routes.ts,"As a data-feed user, I want historical feed prices over a range so that I can backfill analysis.","GET /api/feeds/{feed}/fetchHistoricalPrices requires symbol and accepts fromTimestamp, untilTimestamp, maxSize, and order.",tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/pipeline/feed-routes.test.ts; npm test --workspace=pmxt-core -- --runInBand test/pipeline/feed-success-routes.test.ts,"Feed route tests passed: missing Chainlink API config returns a 503 with CHAINLINK_API_URL named, and the mocked success path passes range/order parameters to the provider and returns historical ticker rows.",,,pass,
CORE-047,Feeds,WebSocket,Watch feed ticker,docs/api-reference/openapi.json operationId=feedWatchTicker; core/src/server/ws-handler.ts,"As a streaming user, I want live feed ticker updates so that my app can react to price changes.",WebSocket subscribe with targetKind=feed and method=watchTicker sends subscribed and data events until unsubscribe or close.,tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/pipeline/create-app-websocket.test.ts,"createApp WebSocket test passed: documented feed watchTicker subscriptions over /ws return subscribed, bridge a fake Binance relay trade into a data event, and acknowledge feed unsubscribe.",,,pass,
STREAM-001,Exchange streaming,WebSocket,Watch order book,core/src/BaseExchange.ts:1431; core/src/server/ws-handler.ts,"As a streaming trader, I want live order book updates for one outcome so that my UI can stay current.","WebSocket subscribe with targetKind=exchange and method=watchOrderBook loops exchange.watchOrderBook and emits data events, or an error event on fatal failure.",tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/pipeline/exchange-websocket-streaming.test.ts,"Exchange WebSocket tests passed: /ws watchOrderBook returns subscribed, emits data with symbol and order book payload, forwards args to the exchange, acknowledges unwatchOrderBook unsubscribe, and sends an error event on fatal watchOrderBook failure.",,,pass,
STREAM-002,Exchange streaming,WebSocket,Watch order books,core/src/BaseExchange.ts:1446; core/src/server/ws-handler.ts,"As a streaming trader, I want batched live order book updates so that I can watch related outcomes together.",WebSocket subscribe with method=watchOrderBooks emits per-symbol data events from the returned record.,tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/pipeline/exchange-websocket-streaming.test.ts,"Exchange WebSocket tests passed: /ws watchOrderBooks returns subscribed, forwards outcome IDs and limit, splits returned records into per-symbol data events, acknowledges unsubscribe, and sends an error event on fatal batch-stream failure.",,,pass,
STREAM-003,Exchange streaming,WebSocket,Watch trades,core/src/BaseExchange.ts:1486; core/src/server/ws-handler.ts,"As a streaming trader, I want live trade updates so that I can monitor market prints.",WebSocket subscribe with method=watchTrades loops exchange.watchTrades and emits trade data events.,tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/pipeline/exchange-websocket-streaming.test.ts,"Exchange WebSocket tests passed: /ws watchTrades returns subscribed, forwards the outcome ID, emits trade-array data events, acknowledges unsubscribe, and sends an error event on fatal watchTrades failure.",,,pass,
STREAM-004,Exchange streaming,SDK,Watch all order books,sdks/typescript/pmxt/client.ts:1972; sdks/python/pmxt/client.py:2588,"As a hosted streaming user, I want a firehose of order-book updates so that I can consume multiple venues from one stream.",SDK watchAllOrderBooks subscribes to the hosted websocket and returns FirehoseEvent updates filtered by optional venues.,fixed_retest_pass,2026-06-23,"Production websocket smoke against wss://api.pmxt.dev/ws with watchAllOrderBooks, firehose, and watchAllOrderBooks([polymarket]); hosted main checks for 94cc6af; obdata relay cargo test","After fixes, hosted health reported priceWatcher.connected=true with cacheSize=452, final quick smoke received data in 0.68s, and combined 50.2s smoke stayed open past the old close window with no close while receiving all-watch=1257, all-firehose=1257, poly-watch=805 data frames.",HOSTED-WS-001,hosted-pmxt:bb61353; hosted-pmxt:528a593; hosted-pmxt:ccc2b38; hosted-pmxt:94cc6af; obdata:489a698,pass,"Root causes were Cloud Run 30s request timeout, stale hosted obdata route, and stale hosted obdata relay key. Protocol ping alone did not fix production; app heartbeat proved frames were visible but timeout still closed at ~32s. Cloud Run --timeout=900s fixed connection lifetime; OBDATA_WS_URL pin plus obdata WS_API_KEYS rotation restored upstream book data."
HOSTED-001,Hosted Router,HTTP,Fetch matched event clusters,docs/api-reference/openapi-hosted.json operationId=getV0Matched-event-clusters,"As a hosted API user, I want clustered matched events so that I can browse cross-venue event relationships without flattening to pairs.",GET /v0/matched-event-clusters returns connected clusters of semantically matched events across venues.,tested_pass,2026-06-22,npm test --workspace=pmxtjs -- --runInBand tests/ws-client.test.ts tests/hosted-dispatch.test.ts tests/router-clusters.test.ts; python3 -m pytest sdks/python/tests/test_streaming_ws_transport.py sdks/python/tests/test_ws_client.py sdks/python/tests/test_hosted_dispatch.py sdks/python/tests/test_router_clusters.py; npm test --workspace=pmxtjs; python3 -m pytest sdks/python/tests,"Focused TypeScript stream/hosted/router suites passed 24 tests and focused Python stream/hosted/router suites passed 45 tests; full TypeScript SDK suite passed 79 tests and full Python SDK suite passed 263 selected tests with 66 deselected. Router cluster contract tests verify authenticated GET /v0/matched-event-clusters with filters and parse connected event clusters, nested events, markets, relations, confidence, and raw match metadata. Read-only live hosted smoke with the local PMXT key returned 1 matched event cluster.",,,pass,SDK contract coverage plus live authenticated hosted read passed.
HOSTED-002,Hosted Router,HTTP,Fetch matched market clusters,docs/api-reference/openapi-hosted.json operationId=getV0Matched-market-clusters,"As a hosted API user, I want clustered matched markets so that I can browse cross-venue market relationships without flattening to pairs.",GET /v0/matched-market-clusters returns connected clusters of semantically matched markets across venues.,tested_pass,2026-06-22,npm test --workspace=pmxtjs -- --runInBand tests/ws-client.test.ts tests/hosted-dispatch.test.ts tests/router-clusters.test.ts; python3 -m pytest sdks/python/tests/test_streaming_ws_transport.py sdks/python/tests/test_ws_client.py sdks/python/tests/test_hosted_dispatch.py sdks/python/tests/test_router_clusters.py; npm test --workspace=pmxtjs; python3 -m pytest sdks/python/tests,"Focused TypeScript stream/hosted/router suites passed 24 tests and focused Python stream/hosted/router suites passed 45 tests; full TypeScript SDK suite passed 79 tests and full Python SDK suite passed 263 selected tests with 66 deselected. Router cluster contract tests verify authenticated GET /v0/matched-market-clusters with query, relation, venue, confidence, orderbook, raw-match, and pagination filters, then parse connected market clusters, nested markets/outcomes, relations, confidence, and raw match metadata. Read-only live hosted smoke with the local PMXT key returned 1 matched market cluster.",,,pass,SDK contract coverage plus live authenticated hosted read passed.
HOSTED-003,Enterprise,HTTP,Read-only SQL,docs/api-reference/openapi-hosted.json operationId=postV0Sql; core/src/server/sql-route.ts,"As an enterprise user, I want read-only SQL access so that I can query PMXT data safely.",POST /v0/sql executes read-only ClickHouse SQL and rejects unsafe or mutating statements.,tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/pipeline/sql-route.test.ts,"SQL route accepted hosted POST body and GET query shapes, rejected missing and write queries before config checks, enforced enterprise plan, and proxied read-only SQL to fake ClickHouse with readonly limits.",,,pass,
HOSTED-013,Enterprise,HTTP,Fetch Enterprise matched markets,sdks/cli/commands/enterprise/matched-markets.js; sdks/cli/scripts/verify-enterprise-cli.js; sdks/cli/cli/generated/metadata.js; core/src/router/client.ts,"As an enterprise CLI user, I want matched-market pairs so that I can inspect cross-venue relationships in the legacy pairwise Enterprise API.","GET /v0/matched-markets accepts authenticated read-only query params such as query, relations, minDifference, category, limit, minConfidence, and includePrices, and returns pairwise matched-market rows with pagination metadata.",tested_pass,2026-06-23,"npm test --workspace=@pmxt/cli; authenticated read-only smoke: /v0/matched-markets?limit=1","CLI verification passed across 84 files, including enterprise command routing and query serialization. Unauthenticated hosted smoke returned 401 missing api key, confirming the route is gated rather than absent. Authenticated read-only live smoke against api.pmxt.dev returned HTTP 200 with one matched-market row and data/meta keys.",,,pass,Read-only Enterprise endpoint; no trading side effects. Endpoint is intentionally represented through the Enterprise CLI surface rather than the public hosted OpenAPI navigation.
HOSTED-014,Enterprise,HTTP,Fetch Enterprise matched prices,sdks/cli/commands/enterprise/matched-prices.js; sdks/cli/scripts/verify-enterprise-cli.js; sdks/cli/cli/generated/metadata.js,"As an enterprise CLI user, I want matched-market prices so that I can query cross-venue pairwise price comparisons in the legacy Enterprise API.","GET /v0/matched-prices accepts authenticated read-only relation, minDifference, category, limit, minConfidence, and includePrices query params, and returns matched-price rows with pagination metadata.",tested_pass,2026-06-23,"npm test --workspace=@pmxt/cli; authenticated read-only smoke: /v0/matched-prices?limit=1","CLI verification passed across 84 files, including enterprise command routing and query serialization. Unauthenticated hosted smoke returned 401 missing api key, confirming the route is gated rather than absent. Authenticated read-only live smoke against api.pmxt.dev returned HTTP 200 with an empty successful data array and data/meta keys.",,,pass,Read-only Enterprise endpoint; no trading side effects. Endpoint is intentionally represented through the Enterprise CLI surface rather than the public hosted OpenAPI navigation.
HOSTED-004,Hosted trading,HTTP,Build hosted order,docs/api-reference/openapi-hosted-trading.json operationId=buildOrderHosted; sdks/typescript/pmxt/hosted-routing.ts,"As a hosted trader, I want to build an order before submitting so that a wallet can review and sign typed data.","POST /v0/trade/build-order returns typed_data, a built_order_id, quote details, resolved venue fields, and the originating build_request without placing the trade.",tested_pass,2026-06-23,npm test --workspace=pmxtjs -- --runInBand tests/hosted-dispatch.test.ts; python3 -m pytest sdks/python/tests/test_hosted_dispatch.py; live authenticated non-submitting Polymarket buildOrder smoke via node_modules/.bin/tsx using PMXT_API_KEY + wallet address only,"Mocked SDK dispatch coverage still passes. Live hosted buildOrder fetched 8 Polymarket markets, built a $10 market buy for will-congo-dr-win-the-2026-fifa-world-cup without signing/submitting, and returned built_order_id, typed_data, quote, resolved, pull_typed_data, side, and SDK-attached build_request.",,,pass,Live authenticated build-order coverage passed for a valid Polymarket market without using a private key or submitting. OpenAPI/schema contract uses quote/resolved rather than economics/order_preview. Edge observed during smoke: the first sampled market returned hosted 502 Failed to fetch orderbook from CLOB before a second market built successfully; local hosted-pmxt checkout did not contain the live /v0/trade/build-order implementation to patch.
HOSTED-005,Hosted trading,HTTP,Submit hosted order,docs/api-reference/openapi-hosted-trading.json operationId=submitOrderHosted; sdks/typescript/pmxt/hosted-routing.ts,"As a hosted trader, I want to submit a signed built order so that the trade is placed after explicit wallet approval.",POST /v0/trade/submit-order accepts built_order_id and signature before expiry and returns the resulting Order.,tested_partial,2026-06-23,"npm test --workspace=pmxtjs -- --runInBand tests/hosted-dispatch.test.ts; python3 -m pytest sdks/python/tests/test_hosted_dispatch.py; pmxt-trading uv run --extra dev pytest services/trading-api/tests/test_compute_quote_key.py services/trading-api/tests/test_v0_endpoints.py -q; live authenticated non-mutating POST /v0/trade/build-order then invalid-signature POST /v0/trade/submit-order smoke using PMXT_API_KEY and wallet address","SDK dispatch tests verify submitOrder routes to POST /v0/trade/submit-order with signer flow and raises locally when signer/signature requirements are missing. Live smoke built a valid order for will-congo-dr-win-the-2026-fifa-world-cup with built_order_id and typed_data. Before fix, invalid signature submit returned HTTP 500 with no structured body. After pmxt-trading fix and Hetzner deploy, the same invalid-signature path returned HTTP 422 with detail.code=invalid_signature and detail.message=Invalid signature; open order count stayed 1 before and after.",HOSTED-SUBMIT-001; HOSTED-LIVE-FUNDS-001,pmxt-trading:46f8023,pass,Valid live signed submit remains intentionally unattempted because it would place an order and spend funds; negative validation path and no-mutation behavior verified live.
HOSTED-006,Hosted trading,HTTP,Create hosted order,docs/api-reference/openapi-hosted-trading.json operationId=createOrderHosted; sdks/typescript/pmxt/client.ts:2574,"As a hosted trader, I want one-shot order creation so that the SDK can build, sign, and submit a trade for me.","POST /v0/trade/create-order places a buy or sell order on supported hosted venues and returns id, status, fill data, fees, and tx hash when available.",tested_partial,2026-06-23,"npm test --workspace=pmxtjs -- --runInBand tests/hosted-dispatch.test.ts; python3 -m pytest sdks/python/tests/test_hosted_dispatch.py; live authenticated TypeScript SDK createOrder smoke using fixed Polymarket outcome and throwaway mismatched signer","Hosted dispatch tests verify createOrder performs build-sign-submit sequencing, routes build and submit calls, preserves optional ID behavior, and raises locally without signer. Live TypeScript SDK createOrder smoke used a fixed will-congo-dr-win-the-2026-fifa-world-cup outcome and a throwaway mismatched signer; the SDK built and signed, production submit returned InvalidSignature with HTTP 422 invalid_signature, no order was created, and open order count stayed 1 before and after.",HOSTED-SUBMIT-001; HOSTED-LIVE-FUNDS-001,pmxt-trading:46f8023,pass,Live authenticated createOrder orchestration reached production build-sign-submit safely via mismatched signer. Valid live signed createOrder remains intentionally unattempted because it would place an order and spend funds.
HOSTED-007,Hosted trading,HTTP,Build hosted cancel,docs/api-reference/openapi-hosted-trading.json operationId=cancelOrderHosted,"As a hosted trader, I want to start a cancel flow so that a wallet can sign the cancel payload before it is submitted.","POST /v0/orders/cancel/build returns cancel typed data for an existing open order; the SDK cancelOrder chains build, sign, and submit.",tested_pass,2026-06-23,npm test --workspace=pmxtjs -- --runInBand tests/hosted-dispatch.test.ts; python3 -m pytest sdks/python/tests/test_hosted_dispatch.py; live authenticated non-submitting POST /v0/orders/cancel/build smoke using PMXT_API_KEY + wallet address,"Mocked SDK dispatch coverage verifies cancelOrder routes through POST /v0/orders/cancel/build and POST /v0/orders/cancel with signer-backed flow. Live hosted cancel-build smoke read 1 open order, then POST /v0/orders/cancel/build returned 200 with cancel_id, deadline, and typed_data without signing or submitting the cancel.",,,pass,Live authenticated cancel-build coverage passed without signing or submitting a cancellation. Signed live cancel submission remains intentionally unattempted because it would affect an open order.
HOSTED-008,Hosted account,HTTP,Fetch hosted balance,docs/api-reference/openapi-hosted-trading.json operationId=fetchBalanceHosted; sdks/typescript/pmxt/client.ts:1412,"As a hosted trader, I want escrow balance so that I know available PMXT trading funds.",GET /v0/user/{address}/balances returns the wallet balance inside PMXT escrow rather than wallet on-chain USDC.,fixed_retest_pass,2026-06-23,npm test --workspace=pmxtjs -- --runInBand tests/hosted-dispatch.test.ts; python3 -m pytest sdks/python/tests/test_hosted_dispatch.py; npx tsc --project sdks/typescript/tsconfig.json --noEmit; npm test --workspace=pmxtjs,"Retest caught the TypeScript SDK hosted fetchBalance path returning [] for the v0 { balances: [...] } envelope. After fix, hosted-dispatch passes for the balance envelope and full TypeScript SDK suite passes. Prior live authenticated hosted balance read coverage remains valid.",TS-SDK-001; TS-SDK-V0-WRAPPER-001,af68e88; 723fdd4,pass,Hosted balance v0 envelope parsing fixed and retested in TypeScript SDK; Python parity suite still passes.
HOSTED-009,Hosted account,HTTP,Fetch hosted positions,docs/api-reference/openapi-hosted-trading.json operationId=fetchPositionsHosted; sdks/typescript/pmxt/client.ts:1378,"As a hosted trader, I want open positions across hosted venues so that I can see my exposure.","GET /v0/user/{address}/positions returns positions with market, outcome, share count, and average entry price; mark-to-market fields may be null.",fixed_retest_pass,2026-06-23,npm test --workspace=pmxtjs -- --runInBand tests/hosted-dispatch.test.ts; python3 -m pytest sdks/python/tests/test_hosted_dispatch.py; npx tsc --project sdks/typescript/tsconfig.json --noEmit; npm test --workspace=pmxtjs,"Retest confirmed TypeScript SDK hosted fetchPositions now accepts the v0 { positions: [...] } envelope while preserving direct-array compatibility; focused hosted dispatch, Python parity, TypeScript typecheck, and full TypeScript SDK suite passed. Prior live authenticated positions read coverage remains valid.",TS-SDK-V0-WRAPPER-001,723fdd4,pass,Hosted positions v0 envelope parsing fixed and retested in TypeScript SDK.
HOSTED-010,Hosted account,HTTP,Fetch hosted open orders,docs/api-reference/openapi-hosted-trading.json operationId=fetchOpenOrdersHosted; sdks/typescript/pmxt/client.ts:1254,"As a hosted trader, I want open hosted orders so that I can monitor resting orders.",GET /v0/orders/open lists wallet orders that have not filled or cancelled and supports venue filtering.,tested_pass,2026-06-22,npm test --workspace=pmxtjs -- --runInBand tests/ws-client.test.ts tests/hosted-dispatch.test.ts tests/router-clusters.test.ts; python3 -m pytest sdks/python/tests/test_streaming_ws_transport.py sdks/python/tests/test_ws_client.py sdks/python/tests/test_hosted_dispatch.py sdks/python/tests/test_router_clusters.py; npx tsx sdks/typescript/tests/e2e/hosted-driver.ts; (cd sdks/python && python3 -m tests.e2e.hosted_driver); npm test --workspace=pmxtjs; python3 -m pytest sdks/python/tests,"Hosted read dispatch tests verify fetchOpenOrders routes to GET /v0/orders/open with wallet address query, supports market filtering in Python, and raises MissingWalletAddress before network when no wallet is configured. Focused TypeScript stream/hosted/router suites passed 24 tests; focused Python stream/hosted/router suites passed 45 tests; TS hosted e2e driver passed 12/12 with 5 captured trade.pmxt.dev/v0 URLs; Python hosted e2e driver passed 15/15 with 5 captured trade.pmxt.dev/v0 URLs; full SDK suites passed 79 TypeScript tests and 263 selected Python tests. Read-only live authenticated hosted smoke returned 1 open order for the configured wallet.",,,pass,"Mocked transport, bogus-key URL-routing, and live authenticated hosted read coverage passed."
HOSTED-011,Hosted account,HTTP,Fetch hosted trades,docs/api-reference/openapi-hosted-trading.json operationId=fetchMyTradesHosted; sdks/typescript/pmxt/client.ts:1292,"As a hosted trader, I want fill history so that I can reconcile hosted order executions.","GET /v0/user/{address}/trades returns historical fills with executed price, size, and settlement tx hash where available.",tested_pass,2026-06-22,npm test --workspace=pmxtjs -- --runInBand tests/ws-client.test.ts tests/hosted-dispatch.test.ts tests/router-clusters.test.ts; python3 -m pytest sdks/python/tests/test_streaming_ws_transport.py sdks/python/tests/test_ws_client.py sdks/python/tests/test_hosted_dispatch.py sdks/python/tests/test_router_clusters.py; npx tsx sdks/typescript/tests/e2e/hosted-driver.ts; (cd sdks/python && python3 -m tests.e2e.hosted_driver); npm test --workspace=pmxtjs; python3 -m pytest sdks/python/tests,Hosted read dispatch tests verify fetchMyTrades routes to GET /v0/user/{address}/trades and raises MissingWalletAddress before network when no wallet is configured. Focused TypeScript stream/hosted/router suites passed 24 tests; focused Python stream/hosted/router suites passed 45 tests; TS hosted e2e driver passed 12/12 with 5 captured trade.pmxt.dev/v0 URLs; Python hosted e2e driver passed 15/15 with 5 captured trade.pmxt.dev/v0 URLs; full SDK suites passed 79 TypeScript tests and 263 selected Python tests. Read-only live authenticated hosted smoke returned 100 trades for the configured wallet.,,,pass,"Mocked transport, bogus-key URL-routing, and live authenticated hosted read coverage passed."
HOSTED-012,Hosted account,HTTP,Fetch hosted order,docs/api-reference/openapi-hosted-trading.json operationId=fetchOrderHosted; sdks/typescript/pmxt/client.ts:1222,"As a hosted trader, I want to look up one hosted order so that I can check current status and fill progress.","GET /v0/orders/{order_id} returns order status, filled and remaining size, average price, and tx hash when settled.",fixed_retest_pass,2026-06-23,npm test --workspace=pmxtjs -- --runInBand tests/hosted-dispatch.test.ts; python3 -m pytest sdks/python/tests/test_hosted_dispatch.py; npx tsc --project sdks/typescript/tsconfig.json --noEmit; npm test --workspace=pmxtjs,"Retest confirmed TypeScript SDK hosted fetchOrder now unwraps the v0 { order: {...} } envelope before mapping to Order; focused hosted dispatch, Python parity, TypeScript typecheck, and full TypeScript SDK suite passed. Prior live authenticated fetchOrder coverage remains valid.",TS-SDK-V0-WRAPPER-001,723fdd4,pass,Hosted fetchOrder v0 envelope parsing fixed and retested in TypeScript SDK.
SDK-001,SDK,TypeScript,TypeScript exchange client,sdks/typescript/pmxt/client.ts; sdks/typescript/package.json,"As a TypeScript developer, I want a typed PMXT client so that I can call local or hosted PMXT methods from Node applications.","The pmxtjs package exposes exchange classes with camelCase methods, converts response models, chooses hosted or local base URL, and dispatches hosted trading when PMXT API key and wallet configuration require it.",fixed_retest_pass,2026-06-23,"npm test --workspace=pmxtjs -- --runInBand tests/hosted-dispatch.test.ts; python3 -m pytest sdks/python/tests/test_hosted_dispatch.py; npx tsc --project sdks/typescript/tsconfig.json --noEmit; npm test --workspace=pmxtjs; RED/GREEN: npm test --workspace=pmxtjs -- --runInBand sdks/typescript/tests/sidecar-order-param-forwarding.test.ts; npm test --workspace=pmxtjs -- --runInBand","Retest caught three TypeScript SDK regressions: hosted v0 read methods did not consistently unwrap {balances|positions|order} envelopes, explicit local baseUrl clients still followed a sidecar lock on a different port, and PMXT_BASE_URL=LOCAL_URL clients also followed that lock. After fixes, focused hosted dispatch passed 18 tests, Python parity passed 26 tests, TypeScript typecheck passed, and the full TypeScript SDK suite passed 53 tests.",TS-SDK-001; TS-SDK-002; TS-SDK-003; TS-SDK-V0-WRAPPER-001; TS-SDK-BASEURL-001; TS-SDK-BASEURL-002,af68e88; d17bc0c; f738d74; 723fdd4; cf9758d; cc8ded0,pass,"TypeScript SDK logistical failures fixed and fully retested, including hosted v0 wrapper parsing, explicit local baseUrl precedence, and PMXT_BASE_URL env override precedence over sidecar lock discovery."
SDK-002,SDK,Python,Python exchange client,sdks/python/pmxt/client.py; sdks/python/pyproject.toml,"As a Python developer, I want a Pythonic PMXT client so that I can call the same PMXT features with snake_case methods.","The pmxt package exposes exchange classes with snake_case methods, converts dataclasses, chooses hosted or local base URL, and dispatches hosted trading where supported.",fixed_retest_pass,2026-06-23,"python3 -m pytest sdks/python/tests; python3 -c 'import sys; sys.path.insert(0, ""sdks/python""); import pmxt; h=pmxt.Hunch(); print(type(h).__name__, getattr(h, ""exchange_name"", None))'","Python SDK test suite previously passed 263 selected tests. Current smoke initially reproduced PMXT server startup timeout through the default local constructor path; after ac31338, pmxt.Hunch() constructed successfully against the real local sidecar and printed Hunch hunch.",SDK-LAUNCHER-001,ac31338,pass,Default Python exchange construction now survives an unhealthy existing launcher lock after the shared launcher refreshes it.
SDK-003,SDK,TypeScript Python and CLI,Local server manager,sdks/typescript/pmxt/server-manager.ts; sdks/python/pmxt/server_manager.py; sdks/cli/cli/server-manager.js; core/bin/pmxt-ensure-server; core/bin/pmxt-ensure-server.js,"As an SDK or CLI user, I want to start, stop, restart, and check a local PMXT service so that self-hosted calls work without manual server management.","Server manager helpers and launchers locate or launch the bundled local service, refresh unhealthy stale locks, expose status, start, stop, restart, health, and logs behavior, and avoid attaching to unrelated sidecars.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxtjs -- --runInBand sdks/typescript/tests/server-manager.test.ts; node sdks/cli/scripts/verify-server-manager.js; python3 -m pytest sdks/python/tests/test_server_manager.py; npm test --workspace=pmxt-core -- --runInBand core/test/server/pmxt-ensure-server.test.ts; core/bin/pmxt-ensure-server; python3 -c Hunch constructor smoke; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand","Retest caught lockless server-manager drift across TypeScript SDK, CLI, and Python SDK, then a current launcher drift where pmxt-ensure-server preserved an unhealthy existing lock and timed out instead of waiting for the replacement sidecar lock. After fixes, focused launcher red/green passed, real launcher exited 0 outside sandbox, Python constructor smoke passed, core typecheck passed, and full core suite passed 731 tests with 3 skipped.",SDK-SERVER-001; SDK-SERVER-002; SDK-LAUNCHER-001,72aaf62; 5b68eca; ac31338,pass,"Server managers now require the current HOME lock port before health/status probes, Python wait-for-health waits for the new launcher's lock, and pmxt-ensure-server removes the matching unhealthy lock before spawning a replacement sidecar."
SDK-004,SDK,TypeScript and Python,Hosted typed-data validation and signing,sdks/typescript/pmxt/hosted-typed-data.ts; sdks/python/pmxt/_hosted_typeddata.py,"As a hosted trader, I want typed data verified before and after signing so that malformed or tampered orders are rejected client side.","Hosted signing validates schema, economics, 65-byte signature shape, low-s canonical signatures, v value, and recovered signer.",tested_pass,2026-06-22,npm test --workspace=pmxtjs -- --runInBand tests/hosted-typed-data.test.ts; npm test --workspace=pmxtjs; python3 -m pytest sdks/python/tests/test_hosted_typeddata.py,"TypeScript direct guardrail tests passed for valid Polymarket buy schema/economics, wrong chain, foreign contract, reordered fields, extra or missing message keys, expired deadline, wallet mismatch, tampered max cost, invalid market worst price, valid signature verification, wrong length, high-s, and wrong recovered signer. Python hosted typed-data suite passed 34 tests for prod fixtures, schema guardrails, economics, signature recovery, high-s rejection, wrong length, wrong recovered address, v normalization, and 6-dec precision.",,,pass,
SDK-005,SDK,TypeScript and Python,Escrow helper,sdks/typescript/pmxt/escrow.ts; sdks/typescript/pmxt/client.ts; sdks/python/pmxt/escrow.py,"As a hosted trader, I want escrow helpers so that I can deposit, withdraw, and inspect escrow lifecycle from the SDK.","Escrow helper wraps hosted custody operations, validates inputs locally, includes configured wallet context, omits inapplicable optional fields, and uses configured wallet and signer data without hardcoded secrets.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxtjs -- --runInBand sdks/typescript/tests/escrow.test.ts; npx tsc --project sdks/typescript/tsconfig.json --noEmit; npm test --workspace=pmxtjs -- --runInBand","TypeScript escrow drift recurred: approval omitted user_address, kept uppercase token, sent amount_wei:null, deposit/withdraw omitted user_address and token fields, withdraw sent amount:null for claim/cancel, and invalid token/amount/action/include values reached network dispatch. The fix restored Python-parity validation and payload shape, and exposed walletAddress/signer on PolymarketOptions. Focused escrow tests passed, TypeScript typecheck passed, and full TypeScript SDK passed 57 tests.",SDK-ESCROW-001; SDK-ESCROW-002,8d8f06b; 8f23935,pass,"Logistical SDK parity/validation error in TypeScript escrow helper fixed again with restored regression coverage; Polymarket hosted wallet/signer options are now typed."
CLI-001,CLI,Command line,Root help and aliases,sdks/cli/bin/pmxt.js; sdks/cli/cli/argv-aliases.js; sdks/cli/cli/help.js,"As a CLI user, I want clear root help and aliases so that I can discover PMXT commands quickly.",pmxt with no command or help flags renders root help; alias normalization maps curated short names to generated operation commands.,tested_pass,2026-06-22,npm test --workspace=@pmxt/cli,"CLI validation, argv alias normalizer, root help, color, runtime error, feed, enterprise, and production copy verifiers all passed after fixing feed verifier isolation.",,,pass,
CLI-002,CLI,Command line,Auth management,sdks/cli/commands/auth/*.js; sdks/cli/cli/auth-store.js,"As a CLI user, I want to save and inspect PMXT and venue credentials so that repeated commands can authenticate without flags.","auth login, logout, status, set-exchange, status-exchange, and remove-exchange manage local credential storage and avoid printing secrets.",tested_pass,2026-06-22,npm test --workspace=@pmxt/cli,"Full CLI suite passed. verify-auth-cli covered login, status, logout, set-exchange, status-exchange, remove-exchange, secret redaction, and auth store mode 0600 in an isolated temp store.",,,pass,
CLI-003,CLI,Command line,Exchange data commands,sdks/cli/commands/markets.js; sdks/cli/commands/events.js; sdks/cli/commands/market.js; sdks/cli/commands/event.js,"As a CLI user, I want exchange-first data commands so that I can fetch markets, events, order books, trades, balances, and positions from a terminal.","CLI data commands resolve exchange, hosted or local mode, parameters, output format, and call the matching PMXT operation.",tested_pass,2026-06-22,node sdks/cli/scripts/verify-venue-order-cli.js; npm test --workspace=@pmxt/cli,"verify-venue-order-cli covered markets, market, events, event, paginated market/event fetches, orderbook(s), trades, balance, positions, OHLCV, execution-price commands, credentials serialization, and HTTP method/args. Full CLI suite also covered exchange-first argv normalization and runtime local/hosted/custom mode selection.",,,pass,
CLI-004,CLI,Command line,Order commands,sdks/cli/commands/order/*.js; sdks/cli/commands/orders/*.js,"As a CLI trader, I want order commands so that I can build, create, submit, cancel, and inspect orders from a terminal.","order and orders commands call buildOrder, createOrder, submitOrder, cancelOrder, fetchOrder, fetchOpenOrders, fetchClosedOrders, fetchAllOrders, and fetchMyTrades as appropriate.",tested_pass,2026-06-22,node sdks/cli/scripts/verify-venue-order-cli.js; npm test --workspace=@pmxt/cli,"verify-venue-order-cli covered createOrder, buildOrder, submitOrder, cancelOrder, fetchOrder, fetchOpenOrders, fetchClosedOrders, fetchAllOrders, fetchMyTrades, and local validation for missing limit-order price before network I/O. Full CLI suite passed.",,,pass,
CLI-005,CLI,Command line,Local server commands,sdks/cli/commands/server/*.js; sdks/cli/cli/server-manager.js,"As a CLI user, I want to manage the local PMXT server so that local mode is operational from the terminal.","server start, stop, restart, status, health, and logs manage or inspect a local PMXT service.",fixed_retest_pass,2026-06-22,RED: node sdks/cli/scripts/verify-server-cli.js; GREEN: npm test --workspace=@pmxt/cli; isolated CLI lifecycle commands with HOME=/private/tmp/pmxt-cli-server-lifecycle-codex,"Manual isolated CLI lifecycle passed server start, status, health, logs, restart, and stop outside the sandbox. Regression test covers command dispatch and verifies status/health do not probe the default port when the current HOME has no lock. Post-fix stopped status reports stopped instead of attaching to an unrelated sidecar.",SDK-SERVER-001,72aaf62,pass,Initial sandboxed server start failed with EPERM on loopback bind; approved outside-sandbox isolated temp-HOME retest passed.
CLI-006,CLI,Command line,Watch commands,sdks/cli/commands/watch/*.js; sdks/cli/cli/streaming.js,"As a CLI user, I want streaming commands so that I can watch order books and trades as JSONL.","watch commands subscribe over WebSocket, print data events, and handle errors and interrupts cleanly.",tested_pass,2026-06-22,node sdks/cli/scripts/verify-watch-cli.js; npm test --workspace=@pmxt/cli,"verify-watch-cli covered watchOrderBook, watchOrderBooks, watchAllOrderBooks, and watchTrades subscribe payloads against a local WebSocket server, JSONL data output with --max-messages shutdown, stream error rejection, and SIGINT listener cleanup. Full CLI suite passed.",,,pass,
CLI-007,CLI,Command line,Feed commands,sdks/cli/commands/feed/*.js; sdks/cli/scripts/verify-feed-cli.js,"As a CLI user, I want feed commands so that I can fetch Binance and Chainlink feed data from the terminal.","feed commands map to feed operations for loadMarkets, ticker, tickers, OHLCV, order book, oracle round, oracle history, historical prices, and watch ticker.",fixed_retest_pass,2026-06-22,RED: npm test --workspace=@pmxt/cli; GREEN: node scripts/verify-feed-cli.js and npm test --workspace=@pmxt/cli,"Initial CLI suite failed because verify-feed-cli expected --hosted without auth to reject, but the verifier used the real ~/.pmxt auth store. Fixed the verifier to isolate HOME and PMXT_AUTH_STORE_PATH in a temp empty store; full CLI suite now passes.",CLI-FEED-001,765ca03,pass,"Logistical test isolation error, not runtime behavior."
CLI-008,CLI,Command line,Enterprise commands,sdks/cli/commands/enterprise/*.js; sdks/cli/scripts/verify-enterprise-cli.js,"As an enterprise CLI user, I want matched-market and SQL commands so that I can query hosted PMXT data from the terminal.","enterprise commands expose matched markets, matched prices, and read-only SQL with hosted authentication.",tested_pass,2026-06-22,npm test --workspace=@pmxt/cli,"Enterprise CLI verifier passed hosted flag, custom base URL, env auth, auth-store, query mapping, and deprecated command absence checks.",,,pass,
TOOL-001,Migration tool,CLI,Dome to PMXT codemod,tools/dome-to-pmxt/index.js; tools/dome-to-pmxt/index.test.js; docs/MIGRATE_FROM_DOMEAPI.md,"As a Dome API user, I want an automated migration helper so that common imports, constructors, methods, parameters, and statuses convert to PMXT equivalents.","dome-to-pmxt walks TS, JS, and Python files, applies ordered regex transforms, supports --dry-run, skips build and dependency directories, binds rewritten Polymarket calls to a declared poly client, and reports TODOs for manual follow-up.",fixed_retest_pass,2026-06-23,node --test tools/dome-to-pmxt/index.test.js,"Regression tests caught the constructor alias drift again: JS/JSX and Python DomeClient declarations were rewritten to dome = pmxt.Polymarket() while Polymarket method calls were rewritten to poly.*. After fix, node --test covers JS/JSX aliasing, Python aliasing, skipped node_modules, dry-run no-write behavior, status/pagination parameter rewrites, and property-access preservation.",TOOL-CODEMOD-001; TOOL-CODEMOD-002,cccdff5; 9215cae,pass,"Codemod constructor alias mismatch fixed again with restored tests; README example now declares poly before poly.fetchMarkets."
VENUE-001,Venue adapter,Exchange,Polymarket,core/src/server/exchange-factory.ts; core/src/exchanges/polymarket/index.ts; core/src/BaseExchange.ts; core/COMPLIANCE.md,"As a PMXT user, I want Polymarket support so that I can read and trade Polymarket through the unified API.",createExchange('polymarket') returns PolymarketExchange with credentials from args or environment and supports the compliance-grid features for Polymarket.,tested_partial,2026-06-23,"npm test --workspace=pmxt-core -- --runInBand test/server/exchange-factory.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; credential-free live Polymarket smoke via node_modules/.bin/tsx; read-only authenticated account smoke via core exchange factory fetchBalance/fetchPositions/fetchOpenOrders; RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/baseExchange.core.test.ts","Factory test verified createExchange('polymarket') constructs PolymarketExchange, maps local env credentials, and full core suite plus TypeScript passed. Earlier ad-hoc live smoke showed fetchMarkets({ limit: 1 }) failed with a Gamma 422 when the base class stripped simple limits before venue fetches. Current main regressed this: RED baseExchange.core.test.ts showed fetchMarkets/fetchEvents implementations received no simple limit. After f1e623d, BaseExchange forwards pure market/event limits to venue implementations again; TypeScript passed and full core Jest passed 721 tests with 3 skipped. Prior credential-free Polymarket live smoke returned one market and one event in 552ms with 2 total requests.",VENUE-POLYMARKET-001; VENUE-PUBLIC-BOUNDS-002; VENUE-LIVE-TRADING-001,092f099; f1e623d,pass,"Local env credential propagation covered. Public Polymarket market/event reads are live-smoked without credentials, and simple limit forwarding is covered by baseExchange.core.test.ts. Read-only authenticated account smoke passed: balance returned 1 row, positions returned 0 rows, and open orders returned 0 rows; authenticated trading and compliance behavior remain pending."
VENUE-002,Venue adapter,Exchange,Kalshi,core/src/server/exchange-factory.ts; core/src/exchanges/kalshi/index.ts; core/src/exchanges/kalshi/fetcher.ts; core/src/BaseExchange.ts; core/COMPLIANCE.md,"As a PMXT user, I want Kalshi support so that I can read and trade Kalshi through the unified API.",createExchange('kalshi') returns KalshiExchange with API key and RSA private key credentials and supports the compliance-grid features for Kalshi.,tested_partial,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/pipeline/kalshi-pagination.test.ts; npm test --workspace=pmxt-core -- --runInBand core/test/unit/baseExchange.core.test.ts; npm test --workspace=pmxt-core -- --runInBand test/server/exchange-factory.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; credential-free live Kalshi smoke via node_modules/.bin/tsx; read-only authenticated account smoke via core exchange factory fetchBalance/fetchPositions/fetchOpenOrders","Factory test verified createExchange('kalshi') constructs KalshiExchange, maps local env credentials, and full core suite plus TypeScript passed. Cross-venue live smoke then showed fetchMarkets({ limit: 1 }) passed but fetchEvents({ limit: 1 }) timed out at 30s because the default active event path crawled all open cursor pages. Current main regressed this: RED kalshi-pagination.test.ts returned two events and multiple GetEvents calls for fetchRawEvents({ limit: 1 }). After f1e623d, default active limited event reads use fetchRawEventPage again, simple limits are forwarded by BaseExchange, TypeScript passed, and full core Jest passed 721 tests with 3 skipped. Prior credential-free Kalshi live smoke returned one market and one event in 8949ms.",VENUE-KALSHI-001; VENUE-PUBLIC-BOUNDS-002; VENUE-LIVE-TRADING-001,ccd742b; f1e623d,pass,"Local env credential propagation covered. Public Kalshi market/event reads are bounded by regression tests and previously live-smoked without credentials. Read-only authenticated account smoke passed: balance returned 1 row, positions returned 0 rows, and open orders returned 0 rows; authenticated trading and compliance behavior remain pending."
VENUE-003,Venue adapter,Exchange,Kalshi demo,core/src/server/exchange-factory.ts; core/src/exchanges/kalshi-demo/index.ts; core/src/exchanges/kalshi/fetcher.ts,"As a PMXT user, I want Kalshi demo support so that I can test Kalshi flows against demo infrastructure.",createExchange('kalshi-demo') returns KalshiDemoExchange using Kalshi credential fields and demo-specific configuration.,tested_partial,2026-06-23,RED: npm test --workspace=pmxt-core -- --runInBand core/test/unit/exchange-factory.test.ts; GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/exchange-factory.test.ts; RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/pipeline/kalshi-pagination.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; credential-free live Kalshi demo smoke via node_modules/.bin/tsx; read-only authenticated account smoke via core exchange factory fetchBalance/fetchPositions/fetchOpenOrders,"Factory test verified createExchange('kalshi-demo') constructs KalshiDemoExchange, then caught that demo-specific env credentials were ignored in favor of production KALSHI_* values. After 0551cf9, kalshi-demo prefers KALSHI_DEMO_API_KEY and KALSHI_DEMO_PRIVATE_KEY with legacy KALSHI_* fallback. Current main later regressed this precedence; RED core/test/unit/exchange-factory.test.ts observed production credentials winning, and 1c27877 restored KALSHI_DEMO_* before legacy KALSHI_* fallback. Cross-venue live smoke then showed demo fetchMarkets({ limit: 1 }) passed but fetchEvents({ limit: 1 }) timed out at 30s through the shared Kalshi event fetcher. Current main regressed the shared bounded event path again; f1e623d restored fetchRawEventPage for default active limited reads. Latest verification passed TypeScript and full core Jest (721 passed, 3 skipped). Credential-free Kalshi demo live smoke previously returned one market and one event in 11396ms.",VENUE-KALSHI-DEMO-001; VENUE-KALSHI-DEMO-002; VENUE-KALSHI-DEMO-003; VENUE-PUBLIC-BOUNDS-002; VENUE-DEMO-CREDENTIALS-001; VENUE-LIVE-TRADING-001,0551cf9; ccd742b; 1c27877; f1e623d,pass,Local demo credential propagation fixed again on current main. Public Kalshi demo market/event reads are bounded by shared Kalshi fetcher tests and previously live-smoked without credentials. Read-only demo account smoke using fallback Kalshi credentials returned 401 authentication_error; demo-specific authenticated/trading behavior remains pending.
VENUE-004,Venue adapter,Exchange,Limitless,core/src/server/exchange-factory.ts; core/src/exchanges/limitless/index.ts; core/COMPLIANCE.md,"As a PMXT user, I want Limitless support so that I can read and trade Limitless markets through the unified API.",createExchange('limitless') returns LimitlessExchange with private key and API credential support and compliance-grid features for Limitless.,tested_partial,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/exchange-factory.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; RED: npm test --workspace=pmxt-core -- --runInBand test/server/exchange-factory.test.ts; GREEN: npm test --workspace=pmxt-core -- --runInBand test/server/exchange-factory.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; credential-free live Limitless smoke via node_modules/.bin/tsx; read-only authenticated account smoke via core exchange factory fetchBalance/fetchPositions/fetchOpenOrders,"Factory test verified createExchange('limitless') constructs LimitlessExchange, then caught that LIMITLESS_BASE_URL was ignored for unauthenticated read-path fetches. After the fix, Limitless resolves auth host, explicit baseUrl, LIMITLESS_BASE_URL, then the default before constructing the fetcher. Additional factory coverage verifies local env private key, API key, API secret, and passphrase mapping; full core suite passed. Credential-free live public smoke returned one market (btc-up-or-down-5-min-1782159911473) and one event (world-cup-france-vs-iraq-jun-22-2026-1775500701455) in 770ms. Current main later regressed this env/config fallback; core/test/unit/exchange-factory.test.ts caught the regression again, and a5ad884 restored the documented fallback. Latest verification passed TypeScript and full core Jest (708 passed, 3 skipped).",VENUE-LIMITLESS-001; VENUE-ENV-REGRESSION-001; VENUE-ACTIVE-CONTEXT-001; VENUE-LIVE-TRADING-001,9baa865; a5ad884,pass,Local read-path base URL and credential env propagation covered. Public Limitless market/event reads are live-smoked without credentials. Read-only authenticated account smoke returned 1 balance row; positions returned User not found and open orders require marketId/slug context. Live authenticated trading/compliance behavior remains pending. Current main env/config fallback is covered by the consolidated exchange-factory regression test.
VENUE-005,Venue adapter,Exchange,Probable,core/src/server/exchange-factory.ts; core/src/exchanges/probable/index.ts; core/COMPLIANCE.md,"As a PMXT user, I want Probable support so that I can access Probable markets through the unified API.","createExchange('probable') returns ProbableExchange with API key, secret, passphrase, and private key credential support.",tested_partial,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/exchange-factory.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; RED: npm test --workspace=pmxt-core -- --runInBand test/server/exchange-factory.test.ts; GREEN: npm test --workspace=pmxt-core -- --runInBand test/server/exchange-factory.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; credential-free live Probable smoke via node_modules/.bin/tsx,"Factory test verified createExchange('probable') constructs ProbableExchange, then caught that PROBABLE_BASE_URL was ignored for adapter fetches. After the fix, Probable resolves explicit baseUrl, PROBABLE_BASE_URL, then the default before registering API descriptors and constructing the fetcher. Additional factory coverage verifies local env API key, secret, passphrase, and private key mapping; full core suite passed. Credential-free live public smoke returned one market (1645) and one event (180) in 2715ms. Current main later regressed this env/config fallback; core/test/unit/exchange-factory.test.ts caught the regression again, and a5ad884 restored the documented fallback. Latest verification passed TypeScript and full core Jest (708 passed, 3 skipped).",VENUE-PROBABLE-001; VENUE-ENV-REGRESSION-001; VENUE-LIVE-TRADING-001,cebae29; a5ad884,pass,Local base URL and credential env propagation covered. Public Probable market/event reads are live-smoked without credentials; live authenticated trading/compliance behavior remains pending. Current main env/config fallback is covered by the consolidated exchange-factory regression test.
VENUE-006,Venue adapter,Exchange,Baozi,core/src/server/exchange-factory.ts; core/src/exchanges/baozi/index.ts; core/src/exchanges/baozi/fetcher.ts; core/src/exchanges/baozi/normalizer.ts; core/test/normalizers/exchange-normalizers-3.test.ts; core/test/pipeline/baozi-websocket-resolvers.test.ts; core/COMPLIANCE.md,"As a PMXT user, I want Baozi support so that I can access Baozi markets through the unified API.","createExchange('baozi') returns BaoziExchange with private key support, keyless public market/event reads, normalized boolean and race markets, emulated OHLCV/trades/open orders where documented, and documented unsupported cancel or trade-stream behavior.",tested_partial,2026-06-23,"npm test --workspace=pmxt-core -- --runInBand core/test/normalizers/exchange-normalizers-3.test.ts core/test/pipeline/baozi-websocket-resolvers.test.ts; npm test --workspace=pmxt-core -- --runInBand core/test/unit/exchange-factory.test.ts; node_modules/.bin/tsx credential-free Baozi market/event smoke","Baozi-focused local tests passed 137 assertions covering normalizer fixtures and websocket resolver queues; exchange factory test passed 9 assertions. Credential-free live public smoke on current main returned one market and one event for 9RX4qTzJUtg4cd1DacPKnAwosexpyTzpFoWUiZCxtVkY in 233ms.",VENUE-LIVE-TRADING-001; VENUE-WALLET-COMPLIANCE-001,,pass,"Local env credential propagation covered. Public Baozi market/event reads are live-smoked without credentials on current main; live trading, Solana wallet, and compliance behavior remain pending."
VENUE-007,Venue adapter,Exchange,Myriad,core/src/server/exchange-factory.ts; core/src/exchanges/myriad/index.ts; core/COMPLIANCE.md,"As a PMXT user, I want Myriad support so that I can access Myriad markets through the unified API.",createExchange('myriad') returns MyriadExchange with API key and wallet-address credential support.,tested_partial,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/exchange-factory.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; RED: npm test --workspace=pmxt-core -- --runInBand test/server/exchange-factory.test.ts; GREEN: npm test --workspace=pmxt-core -- --runInBand test/server/exchange-factory.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; credential-free live Myriad smoke via node_modules/.bin/tsx; read-only authenticated account smoke via core exchange factory fetchBalance/fetchPositions/fetchOpenOrders,"Factory test verified createExchange('myriad') constructs MyriadExchange, then caught that MYRIAD_BASE_URL was ignored for adapter fetches. After the fix, Myriad resolves explicit baseUrl, MYRIAD_BASE_URL, then the default before registering API descriptors and constructing the fetcher. Additional factory coverage verifies local env API key and wallet-address mapping; full core suite passed. Credential-free live public smoke returned one market (2741:490) and one event (213) in 670ms. Current main later regressed this env/config fallback; core/test/unit/exchange-factory.test.ts caught the regression again, and a5ad884 restored the documented fallback. Latest verification passed TypeScript and full core Jest (708 passed, 3 skipped).",VENUE-MYRIAD-001; VENUE-ENV-REGRESSION-001; VENUE-WALLET-CONTEXT-001; VENUE-LIVE-TRADING-001,2fab858; a5ad884,pass,Local base URL and credential env propagation covered. Public Myriad market/event reads are live-smoked without credentials. Read-only authenticated smoke returned 0 open orders; balance and positions require a wallet address env not present in this session. Live authenticated venue behavior remains pending. Current main env/config fallback is covered by the consolidated exchange-factory regression test.
VENUE-008,Venue adapter,Exchange,Opinion,core/src/server/exchange-factory.ts; core/src/exchanges/opinion/index.ts; core/COMPLIANCE.md,"As a PMXT user, I want Opinion support so that I can access Opinion markets and hosted trading routes through PMXT.","createExchange('opinion') returns OpinionExchange with API key, private key, and funder address credential support.",tested_partial,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/exchange-factory.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; RED: npm test --workspace=pmxt-core -- --runInBand test/server/exchange-factory.test.ts; GREEN: npm test --workspace=pmxt-core -- --runInBand test/server/exchange-factory.test.ts; RED: RUN_OPINION_READONLY_E2E=1 npm test --workspace=pmxt-core -- --runInBand test/e2e/opinion-readonly-live.e2e.test.ts; GREEN: same live command without OPINION_API_KEY skips cleanly; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; read-only authenticated account smoke via core exchange factory fetchBalance/fetchPositions/fetchOpenOrders,"Factory test verified createExchange('opinion') constructs OpinionExchange, then caught that documented OPINION_BASE_URL was ignored for adapter fetches. After the first fix, Opinion resolves explicit baseUrl, OPINION_BASE_URL, then the existing default/legacy OPINION_API_URL path. Follow-up factory coverage caught that OPINION_FUNDER_ADDRESS was ignored even though trading requires funderAddress; after the second fix, Opinion maps explicit funderAddress, OPINION_FUNDER_ADDRESS, then OPINION_PROXY_ADDRESS. Live read-only E2E reached Opinion and failed with HTTP 401 when run keylessly; after the guard fix, it skips unless OPINION_API_KEY is present. Full core suite passed. Current main later regressed this env/config fallback; core/test/unit/exchange-factory.test.ts caught the regression again, and a5ad884 restored the documented fallback. Latest verification passed TypeScript and full core Jest (708 passed, 3 skipped).",VENUE-OPINION-001; VENUE-OPINION-002; VENUE-OPINION-003; VENUE-ENV-REGRESSION-001; VENUE-WALLET-CONTEXT-001; VENUE-LIVE-TRADING-001,fa1deec; 1752e45; 9047f2b; a5ad884,pass,Local base URL and funder credential env propagation fixed. Read-only authenticated smoke returned 0 open orders; fetchBalance is not implemented and positions require a wallet/funder address env not present in this session. Live authenticated venue behavior remains pending. Current main env/config fallback is covered by the consolidated exchange-factory regression test.
VENUE-009,Venue adapter,Exchange,Metaculus,core/src/server/exchange-factory.ts; core/src/exchanges/metaculus/index.ts; core/COMPLIANCE.md,"As a PMXT user, I want Metaculus support so that forecasts can be represented through the unified API.","createExchange('metaculus') returns MetaculusExchange with apiToken support, fetchMarkets and fetchEvents, and forecast create or withdraw behavior mapped to createOrder and cancelOrder.",tested_partial,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/exchange-factory.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; RED: npm test --workspace=pmxt-core -- --runInBand test/server/exchange-factory.test.ts; GREEN: npm test --workspace=pmxt-core -- --runInBand test/server/exchange-factory.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; keyless live Metaculus smoke via node_modules/.bin/tsx,"Factory test verified createExchange('metaculus') constructs MetaculusExchange, then caught that METACULUS_BASE_URL was ignored for adapter API configuration. After the fix, Metaculus resolves explicit baseUrl, METACULUS_BASE_URL, then the default before registering API descriptors. Additional factory coverage verifies local env API token mapping; full core suite passed. Keyless live smoke failed fast with AuthenticationError: Metaculus API token required, so authenticated live behavior remains unverified. Current main later regressed this env/config fallback; core/test/unit/exchange-factory.test.ts caught the regression again, and a5ad884 restored the documented fallback. Latest verification passed TypeScript and full core Jest (708 passed, 3 skipped).",VENUE-METACULUS-001; VENUE-ENV-REGRESSION-001; VENUE-CREDENTIALS-001,c9d3f88; a5ad884,pass,Local base URL and credential env propagation covered. Keyless live behavior correctly requires an API token; authenticated Metaculus venue behavior remains pending. Current main env/config fallback is covered by the consolidated exchange-factory regression test.
VENUE-010,Venue adapter,Exchange,Smarkets,core/src/server/exchange-factory.ts; core/src/exchanges/smarkets/index.ts; core/src/exchanges/smarkets/fetcher.ts; core/src/BaseExchange.ts,"As a PMXT user, I want Smarkets support so that I can access Smarkets markets through the unified API.",createExchange('smarkets') returns SmarketsExchange with email and password credential mapping and Smarkets read and trading methods where implemented.,tested_partial,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/exchange-factory.test.ts; RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/exchanges/smarkets-fetcher.test.ts; npm test --workspace=pmxt-core -- --runInBand core/test/unit/baseExchange.core.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; credential-free live Smarkets smoke via node_modules/.bin/tsx,"Factory test verified createExchange('smarkets') constructs SmarketsExchange, then caught that SMARKETS_BASE_URL was ignored for adapter API configuration. After 8912ff4, Smarkets config resolves explicit baseUrl, SMARKETS_BASE_URL, then the default. New fetcher tests caught unauthenticated public reads calling auth-only volume enrichment and Smarkets event fetches ignoring simple limits. After 092f099, unauthenticated volume calls are skipped, direct market lookup uses the guarded volume helper, BaseExchange forwards pure market/event limits to venue implementations, and Smarkets event pagination honors the requested limit. Current main later regressed both env/config fallback and public-read bounds; a5ad884 restored the env/config fallback, and f1e623d restored unauthenticated volume skipping, direct market lookup guarded volumes, event limit pagination, and BaseExchange simple-limit forwarding. Latest verification passed TypeScript and full core Jest (721 passed, 3 skipped). Prior credential-free live smoke returned one market and one event in 525ms with 6 total requests.",VENUE-SMARKETS-001; VENUE-SMARKETS-002; VENUE-ENV-REGRESSION-001; VENUE-PUBLIC-BOUNDS-002; VENUE-CREDENTIALS-001; VENUE-LIVE-TRADING-001,8912ff4; 092f099; a5ad884; f1e623d,pass,"Local base URL and credential env propagation covered. Public Smarkets market/event reads are bounded by restored fetcher/base regression tests and were previously live-smoked without credentials; authenticated trading, account, and compliance behavior remain pending."
VENUE-011,Venue adapter,Exchange,Polymarket US,core/src/server/exchange-factory.ts; core/src/exchanges/polymarket_us/index.ts,"As a PMXT user, I want Polymarket US support so that US venue markets can be read through the unified API.",createExchange('polymarket_us') returns PolymarketUSExchange with key id and secret key credential mapping.,tested_partial,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/exchange-factory.test.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand; RED: npm test --workspace=pmxt-core -- --runInBand test/server/exchange-factory.test.ts; GREEN: npm test --workspace=pmxt-core -- --runInBand test/server/exchange-factory.test.ts; npx tsx core/scripts/smoke-polymarket-us.ts; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand,"Factory test verified createExchange('polymarket_us') constructs PolymarketUSExchange, then caught that POLYMARKET_US_BASE_URL and POLYMARKET_US_GATEWAY_URL were captured at module load and ignored when changed before factory construction. After the fix, Polymarket US resolves explicit baseUrl and runtime env values before existing defaults. Additional factory coverage verifies local env key id and secret key mapping. Live public smoke passed 15 checks for fetchMarkets, fetchEvents, fetchOrderBook, suffix handling, and unauthenticated auth gates; full core suite passed. Current main later regressed this env/config fallback; core/test/unit/exchange-factory.test.ts caught the regression again, and a5ad884 restored the documented fallback. Latest verification passed TypeScript and full core Jest (708 passed, 3 skipped).",VENUE-POLYMARKET-US-001; VENUE-ENV-REGRESSION-001; VENUE-CREDENTIALS-001,d19ef19; a5ad884,pass,Local config/credential coverage and live public read smoke passed; live authenticated venue behavior pending. Current main env/config fallback is covered by the consolidated exchange-factory regression test.
VENUE-012,Venue adapter,Exchange,Hyperliquid,core/src/server/exchange-factory.ts; core/src/exchanges/hyperliquid/index.ts; core/src/exchanges/hyperliquid/fetcher.ts; core/src/exchanges/hyperliquid/normalizer.ts; core/test/normalizers/exchange-normalizers-3.test.ts,"As a PMXT user, I want Hyperliquid prediction market support so that I can read and trade supported Hyperliquid markets through the unified API.","createExchange('hyperliquid') returns HyperliquidExchange with wallet-address read credentials and private-key trading credentials, supports keyless public market/event reads, normalizes outcome markets and events, and exposes read-only balance, position, and open-order account methods when a wallet address is configured.",tested_partial,2026-06-23,"npm test --workspace=pmxt-core -- --runInBand core/test/normalizers/exchange-normalizers-3.test.ts core/test/pipeline/baozi-websocket-resolvers.test.ts; npm test --workspace=pmxt-core -- --runInBand core/test/unit/exchange-factory.test.ts; node_modules/.bin/tsx credential-free Hyperliquid market/event smoke; source .env and node_modules/.bin/tsx read-only Hyperliquid account smoke","Current main local normalizer/websocket test run passed 137 assertions and exchange factory test passed 9 assertions. Credential-free live public smoke returned one market (hl-outcome-171) and one event (32) in 3542ms. Read-only account smoke with local env loaded returned 1 balance row, 0 positions, and 0 open orders in 1287ms.",VENUE-LIVE-TRADING-001,,pass,"Local env credential propagation covered. Public Hyperliquid market/event reads and read-only account methods were live-smoked on current main; live authenticated trading behavior remains pending because valid create/cancel order flows can move funds or affect orders."
VENUE-013,Venue adapter,Exchange,Gemini Titan,core/src/server/exchange-factory.ts; core/src/exchanges/gemini-titan/index.ts; core/src/exchanges/gemini-titan/fetcher.ts; core/src/exchanges/gemini-titan/normalizer.ts; core/src/exchanges/gemini-titan/websocket.ts; core/test/exchanges/gemini-titan-fetcher.test.ts; core/test/normalizers/gemini-titan-normalizer.test.ts; core/test/exchanges/gemini-titan-websocket.test.ts,"As a PMXT user, I want Gemini Titan support so that Gemini prediction markets can be read through PMXT.","createExchange('gemini-titan') returns GeminiTitanExchange with Gemini API key and secret credential mapping, supports keyless public market/event reads, normalizes Gemini events/contracts, supports websocket depth parsing, and gates authenticated order, position, and account methods behind Gemini API credentials.",tested_partial,2026-06-23,"npm test --workspace=pmxt-core -- --runInBand core/test/exchanges/gemini-titan-fetcher.test.ts core/test/normalizers/gemini-titan-normalizer.test.ts core/test/exchanges/gemini-titan-websocket.test.ts core/test/unit/exchange-factory.test.ts; node_modules/.bin/tsx credential-free Gemini Titan market/event smoke; source .env and node_modules/.bin/tsx read-only Gemini Titan account smoke","Focused Gemini Titan fetcher, normalizer, websocket, and factory tests passed 17 assertions. Credential-free live public smoke on current main returned one market (gemi-GEMI-WC2026-FRANCE) and one event (WC2026) in 1134ms. Read-only authenticated account smoke is blocked in this environment by missing Gemini apiKey/apiSecret and fails fast with AuthenticationError before network.",VENUE-CREDENTIALS-001; VENUE-LIVE-TRADING-001,,pass,"Local env credential propagation covered. Public Gemini Titan market/event reads were live-smoked without credentials on current main; authenticated account/trading behavior remains pending until Gemini API credentials are available."
VENUE-014,Venue adapter,Exchange,SuiBets,core/src/server/exchange-factory.ts; core/src/exchanges/suibets/index.ts; core/src/exchanges/suibets/fetcher.ts; core/src/exchanges/suibets/normalizer.ts; core/test/normalizers/suibets-normalizer.test.ts,"As a PMXT user, I want SuiBets support so that Sui prediction markets can be read through the unified API.","createExchange('suibets') returns SuiBetsExchange with wallet address and baseUrl credential mapping, supports keyless public market/event reads, normalizes P2P Sui sports offers, emulates order books from offer odds, and gates position reads behind a Sui wallet address.",tested_partial,2026-06-23,"npm test --workspace=pmxt-core -- --runInBand core/test/normalizers/suibets-normalizer.test.ts core/test/unit/exchange-factory.test.ts; node_modules/.bin/tsx credential-free SuiBets market/event smoke; source .env and node_modules/.bin/tsx read-only SuiBets positions smoke","Focused SuiBets normalizer and exchange-factory tests passed 67 assertions. Credential-free live public smoke on current main reached the venue and returned zero markets and zero events in 368ms without throwing. Read-only positions smoke is blocked in this environment by missing SUIBETS_WALLET_ADDRESS and fails fast with AuthenticationError before network.",VENUE-ACTIVE-OFFERS-001; VENUE-WALLET-CONTEXT-001,,pass,"Local env credential propagation covered. Public SuiBets endpoint is reachable on current main but has no current markets/events; active-offer behavior and wallet-connected positions remain pending."
VENUE-015,Venue adapter,Exchange,Rain,core/src/server/exchange-factory.ts; core/src/exchanges/rain/index.ts; core/src/exchanges/rain/fetcher.ts; core/src/exchanges/rain/normalizer.ts,"As a PMXT user, I want Rain support so that Rain markets can be read and traded through the unified API.","createExchange('rain') returns RainExchange with private key, wallet, subgraph, RPC, and environment configuration, supports keyless public market/event reads, normalizes Rain markets/events/order books, and gates wallet/account/trading methods behind wallet or private-key credentials.",tested_partial,2026-06-23,"npm test --workspace=pmxt-core -- --runInBand core/test/unit/exchange-factory.test.ts; node_modules/.bin/tsx credential-free Rain market/event smoke; source .env and node_modules/.bin/tsx read-only Rain balance/positions smoke","Exchange factory test passed 9 assertions. Credential-free live public smoke on current main returned one market and one event for rain:691e2ab9875e01ffa0161f3b in 3791ms. Read-only balance/positions smoke is blocked in this environment by missing Rain wallet/private key and fails fast with AuthenticationError before network.",VENUE-WALLET-CONTEXT-001; VENUE-LIVE-TRADING-001,,pass,"Local env credential propagation covered. Public Rain market/event reads were live-smoked without credentials on current main; wallet/account reads and live trading behavior remain pending until wallet/private-key credentials are available."
VENUE-016,Venue adapter,Exchange,Hunch,core/src/server/exchange-factory.ts; core/src/exchanges/hunch/index.ts; core/src/exchanges/hunch/fetcher.ts; core/src/exchanges/hunch/utils.ts; core/test/exchanges/hunch-fetcher.test.ts; core/test/normalizers/hunch-normalizer.test.ts; sdks/typescript/pmxt/client.ts; sdks/python/pmxt/_exchanges.py; core/COMPLIANCE.md,"As a PMXT user, I want Hunch support so that parimutuel Hunch markets can be represented through the unified API.","createExchange('hunch') returns HunchExchange, supports keyless reads, drains the full catalog via nextCursor when no explicit limit is supplied, honors explicit limits as one-page reads, surfaces list odds, 24h volume, category/tags, exports Hunch in TypeScript and Python SDKs, supports x402 market-order createOrder, and documents unsupported cancel or order-fetch behavior.",tested_partial,2026-06-23,"npm test --workspace=pmxt-core -- --runInBand core/test/exchanges/hunch-fetcher.test.ts core/test/normalizers/hunch-normalizer.test.ts; npx tsc --noEmit in sdks/typescript; python3 -c Hunch constructor smoke; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand","Focused Hunch fetcher/normalizer tests passed 56 assertions covering nextCursor draining, explicit-limit one-page reads, list odds, volume24h, and category/tags. TypeScript SDK compile passed, Python Hunch constructor smoke passed after SDK launcher fix, core typecheck passed, and full core suite passed 731 tests with 3 skipped. Prior credential-free live public smoke returned one market and one event.",SDK-LAUNCHER-001; VENUE-X402-LIVE-001; VENUE-LIVE-TRADING-001,dd1332c; ac31338,pass,"Local env credential propagation covered. Public Hunch market/event reads are locally covered and previously live-smoked without credentials. Upstream Hunch surfacing commit dd1332c is reflected in the story; x402 trading and live order behavior remain pending because valid createOrder would move funds."
VENUE-017,Venue adapter,Exchange,Mock,core/src/server/exchange-factory.ts; core/src/exchanges/mock/index.ts,"As a PMXT developer, I want a mock exchange so that local tests can exercise PMXT behavior without external venue dependencies.",createExchange('mock') returns MockExchange with deterministic fixtures for local and test use.,tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/server/exchange-factory.test.ts test/unit/mockExchange.core.test.ts; npm test --workspace=pmxt-core -- --runInBand,Factory test verified createExchange('mock') constructs MockExchange; existing MockExchange unit tests and full core suite passed.,,,pass,
FEED-001,Feed provider,Data feed,Binance feed,core/src/server/feed-factory.ts; core/src/feeds/binance/binance-feed.ts,"As a data-feed user, I want Binance feed support so that crypto reference prices are available through PMXT feed methods.",getFeed('binance') returns a singleton BinanceFeed using OBDATA_API_KEY when present and supports feed methods implemented by BinanceFeed.,tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/unit/dataFeeds.success.test.ts; npm test --workspace=pmxt-core -- --runInBand,"Binance provider success test used a local WebSocket relay, verified subscribe_all, consumed a BTCUSDT trade event through fetchTicker, and normalized it to BTC/USDT with price and timestamp. Existing feed tests cover factory-backed loadMarkets/provider listing, missing relay errors, and unsupported OHLCV/order book capability errors.",,,pass,Local in-process relay coverage; external obdata relay not required for code-level pass.
FEED-002,Feed provider,Data feed,Chainlink feed,core/src/server/feed-factory.ts; core/src/feeds/chainlink/chainlink-feed.ts,"As an oracle-data user, I want Chainlink feed support so that oracle rounds and historical oracle prices are available through PMXT feed methods.","getFeed('chainlink') returns a singleton ChainlinkFeed using OBDATA_API_KEY when present and supports oracle round, oracle history, and historical price methods.",tested_pass,2026-06-22,npm test --workspace=pmxt-core -- --runInBand test/unit/dataFeeds.success.test.ts; npm test --workspace=pmxt-core -- --runInBand,"Chainlink provider success tests used local REST and WebSocket servers, verified latest prices, filtered tickers, oracle round/history/historical price request mapping and normalization, subscribe_all, and live ticker normalization. Existing feed tests cover factory-backed loadMarkets, missing REST URL errors, and unsupported order book capability errors.",,,pass,Local in-process REST/WebSocket coverage; external Chainlink API not required for code-level pass.
DOC-001,Documentation,Markdown,Feature support compliance matrix,core/scripts/generate-compliance.js; core/COMPLIANCE.md; readme.md,"As a PMXT user, I want the feature support and compliance matrix to list every production venue so that I can understand venue capabilities and required auth variables.","npm run generate:compliance --workspace=pmxt-core generates core/COMPLIANCE.md with every production exchange directory except kalshi-demo and mock, stable display names, method support rows, and credential-variable guidance for authenticated venue tests.",fixed_retest_pass,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/generate-compliance.test.js; npm test --workspace=pmxt-core -- --runInBand,"RED test caught that generated COMPLIANCE.md omitted PolymarketUS, Smarkets, Hyperliquid, GeminiTitan, SuiBets, and Rain and did not document credential variables for newly listed venues. After 222a0f2, the generator discovers production exchange directories, excludes only kalshi-demo and mock, regenerates the matrix with 15 venue headers, writes authenticated-test env guidance, focused generator tests passed, and full core Jest passed 733 tests with 3 skipped.",DOC-COMPLIANCE-MATRIX-001; DOC-COMPLIANCE-CREDENTIALS-001,222a0f2,pass,Logistical documentation generation error fixed; compliance matrix now covers current production venue surface without requiring live venue credentials or order placement.
DOC-002,Documentation,Markdown,README supported exchange strip,readme.md; core/test/unit/readme-supported-exchanges.test.js; core/src/server/exchange-factory.ts,"As a new PMXT user, I want the README supported exchanges to match production adapters so that I can discover all available venues before reading detailed docs.","README supported exchange strip includes image alt entries for every production venue: Polymarket, Polymarket US, Kalshi, Limitless, Probable, Baozi, Myriad, Opinion, Metaculus, Smarkets, Hyperliquid, Gemini Titan, SuiBets, Rain, and Hunch.",fixed_retest_pass,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/readme-supported-exchanges.test.js; npm test --workspace=pmxt-core -- --runInBand,"RED test caught missing alt=""Baozi"" and the audit also showed SuiBets absent from README while both are production adapters. After b84e4c1, README includes Baozi and SuiBets entries and removes the stale Baozi warning comment; focused README test passed, and full core Jest passed 734 tests with 3 skipped.",DOC-README-VENUE-LIST-001,b84e4c1,pass,Logistical README discoverability error fixed; no live venue access required.
DOC-003,Documentation,Mintlify,Supported venues documentation page,scripts/generate-mintlify-docs.js; docs/concepts/venues.mdx; core/test/unit/mintlify-venues.test.js,"As a PMXT docs reader, I want the Supported Venues page to show user-facing venue names and exclude internal targets so that I can choose real venue keys without being misled by mock or router internals.","npm run generate:mintlify regenerates docs/concepts/venues.mdx with display labels for current venue keys, excludes internal mock and router targets from the venue table, preserves hosted autogen blocks, and keeps pass-through URL examples for real venue targets.",fixed_retest_pass,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/mintlify-venues.test.js; npm test --workspace=pmxt-core -- --runInBand,"RED test caught raw labels for gemini-titan, hyperliquid, suibets, rain, and hunch and showed mock/router listed as venues. After 0cf05eb, generate-mintlify-docs maps the newer venue labels, filters internal mock/router targets, updates the venues page copy, preserves the hosted catalog block, focused test passed, and full core Jest passed 735 tests with 3 skipped.",DOC-MINTLIFY-VENUES-001,0cf05eb,pass,Logistical docs-generation error fixed; no live venue access or trading required.
DOC-004,Documentation,OpenAPI,SDK code sample class names,core/scripts/generate-openapi.js; docs/api-reference/openapi.json; core/test/unit/openapi-code-samples.test.js; sdks/typescript/index.ts; sdks/python/pmxt/__init__.py,"As a PMXT docs reader, I want generated OpenAPI SDK examples to use exported SDK class names so that copied Python and TypeScript examples run.","Generated x-codeSamples and x-sdk-constructors use class names exported by the TypeScript and Python SDKs, including canonical PolymarketUS and SuiBets labels.",fixed_retest_pass,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/openapi-code-samples.test.js; npm test --workspace=pmxt-core -- --runInBand,"RED test caught generated samples missing PolymarketUS and using PolymarketUs/Suibets casing. After 49c7489, generator constructor overrides emit PolymarketUS and SuiBets, checked-in OpenAPI examples use the exported names, focused regression passed, and full core Jest passed 736 tests with 3 skipped.",DOC-OPENAPI-SAMPLES-001,49c7489,pass,Logistical docs code-sample error fixed; no live venue access or trading required.
DOC-005,Documentation,LLMS,LLMS Supported Venues artifact,scripts/generate-llms.js; docs/llms-full.txt; docs/concepts/venues.mdx; core/test/unit/llms-docs.test.js,"As an LLM or docs consumer, I want the generated llms-full Supported Venues section to match the public Supported Venues page so that venue names and real targets are not misleading.","npm run docs:llms regenerates docs/llms-full.txt from current docs sources with user-facing venue labels, the current Supported Venues wording, and no internal mock or router targets.",fixed_retest_pass,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/llms-docs.test.js; npm test --workspace=pmxt-core -- --runInBand,"RED test caught checked-in docs/llms-full.txt drifting from generator output: raw gemini-titan/hyperliquid/suibets/rain/hunch labels, stale Hosted wording, and internal mock/router rows. After a5b6684, npm run docs:llms refreshed docs/llms-full.txt from the fixed venues page, focused LLMS regression passed, and full core Jest passed 737 tests with 3 skipped.",DOC-LLMS-VENUES-001,a5b6684,pass,Logistical generated-docs error fixed; no live venue access or trading required.
DOC-006,Documentation,LLMS,LLMS hosted trading API reference,scripts/generate-llms.js; docs/docs.json; docs/llms.txt; docs/llms-full.txt; docs/api-reference/openapi-hosted-trading.json; core/test/unit/llms-docs.test.js,"As an LLM or docs consumer, I want hosted trading and account API reference pages included in generated LLMS docs so that the static docs cover the same API pages as the Mintlify navigation.","npm run docs:llms resolves the exact OpenAPI spec named by each docs navigation group, including openapi-hosted-trading.json, and emits /v0/trade, /v0/orders, and /v0/user hosted trading/account endpoints in docs/llms.txt and docs/llms-full.txt.",fixed_retest_pass,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/llms-docs.test.js; npm test --workspace=pmxt-core -- --runInBand,"RED test caught docs/llms.txt missing createOrderHosted/fetchBalanceHosted links and docs/llms-full.txt missing hosted trading/account endpoint sections because hosted-trading pages were resolved against openapi-hosted.json. After 4228219, generate-llms resolves the exact OpenAPI spec filename, npm run docs:llms added nine hosted trading/account entries to docs/llms.txt and 445 generated lines to docs/llms-full.txt, focused LLMS regression passed, and full core Jest passed 737 tests with 3 skipped.",DOC-LLMS-HOSTED-TRADING-001,4228219,pass,Logistical generated-docs error fixed; no live venue access or trading required.
DOC-007,Documentation,OpenAPI,Hosted balance SDK samples,docs/api-reference/openapi-hosted-trading.json; docs/llms-full.txt; core/test/unit/hosted-openapi-code-samples.test.js; sdks/typescript/pmxt/client.ts; sdks/python/pmxt/client.py,"As a hosted SDK docs reader, I want balance examples to match the SDK return shape so that copied Python and TypeScript snippets do not treat a balance list as a single object.","Hosted OpenAPI and LLMS examples for fetchBalanceHosted show Python fetch_balance() and TypeScript fetchBalance() returning a list/array, then read balances[0].available and currency.",fixed_retest_pass,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/hosted-openapi-code-samples.test.js; npm test --workspace=pmxt-core -- --runInBand core/test/unit/hosted-openapi-code-samples.test.js core/test/unit/llms-docs.test.js core/test/unit/openapi-code-samples.test.js; npm test --workspace=pmxt-core -- --runInBand,"RED test caught hosted fetchBalance samples using balance = client.fetch_balance()/const balance = await client.fetchBalance() and balance.amount despite SDK methods returning List[Balance]/Balance[]. After 71947c9, hosted OpenAPI samples use balances = client.fetch_balance(), const balances = await client.fetchBalance(), balances[0].available, npm run docs:llms refreshed docs/llms-full.txt, focused docs tests passed, and full core Jest passed 738 tests with 3 skipped.",DOC-HOSTED-BALANCE-SAMPLES-001,71947c9,pass,Logistical docs code-sample error fixed; no live venue access or trading required.
DOC-008,Documentation,Markdown,TypeScript README self-hosted imports,sdks/typescript/README.md; core/test/unit/typescript-readme-samples.test.js; sdks/typescript/index.ts,"As a TypeScript SDK reader, I want README self-hosted examples to import the classes they instantiate so that copied snippets compile without an unbound pmxt namespace.","Self-hosted TypeScript README snippets instantiate Polymarket, Kalshi, and Limitless using named imports from pmxtjs instead of referencing an unimported pmxt namespace.",fixed_retest_pass,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/typescript-readme-samples.test.js; npm test --workspace=pmxtjs; npm test --workspace=pmxt-core -- --runInBand,"RED test caught sdks/typescript/README.md self-hosted snippets using new pmxt.Polymarket, new pmxt.Kalshi, and new pmxt.Limitless without importing a pmxt namespace. After d4f145b, those snippets import the named classes and instantiate Polymarket/Kalshi/Limitless directly, the focused README regression passed, TypeScript SDK Jest passed 57 tests, and full core Jest passed 739 tests with 3 skipped.",DOC-TS-README-IMPORTS-001,d4f145b,pass,Logistical README copy/paste error fixed; no live venue access or trading required.
DOC-009,Documentation,Markdown,Standalone SDK docs imports,docs/MIGRATE_FROM_DOMEAPI.md; docs/authentication.mdx; docs/llms-full.txt; core/test/unit/docs-copy-paste-samples.test.js,"As a PMXT docs reader, I want standalone SDK setup and authentication snippets to import the SDK namespace they use so that copied Python and TypeScript examples run without hidden context.","Standalone TypeScript snippets using new pmxt.* include import pmxt from 'pmxtjs' in the same fenced block, and standalone Python snippets using pmxt.* include import pmxt in the same fenced block.",fixed_retest_pass,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js core/test/unit/llms-docs.test.js; npm test --workspace=pmxt-core -- --runInBand,"RED test caught standalone DomeAPI migration and authentication snippets using pmxt.Polymarket/pmxt.Limitless without in-snippet imports. After f8c7542, the migration guide TypeScript and Python setup examples import pmxt, the multi-exchange TypeScript example imports pmxt, the direct auth Python/TypeScript snippets import pmxt, npm run docs:llms refreshed docs/llms-full.txt, focused docs tests passed, and full core Jest passed 741 tests with 3 skipped.",DOC-STANDALONE-DOCS-IMPORTS-001,f8c7542,pass,Logistical docs copy/paste error fixed; no live venue access or trading required.
DOC-010,Documentation,Markdown,Standalone setup docs imports,core/test/unit/docs-copy-paste-samples.test.js; docs/introduction.mdx; docs/api-reference/configuration.mdx; docs/guides/self-hosted.mdx; docs/guides/signing.mdx; readme.md; sdks/python/README.md; docs/llms-full.txt,"As a PMXT docs reader, I want standalone setup and server-management examples to import the SDK package and support modules they use so that copied snippets run without relying on previous page context.",Standalone Python snippets that instantiate pmxt clients or call pmxt.server import pmxt in the same fenced block; README self-hosted snippets that call os.getenv also import os; standalone TypeScript direct-class snippets import Polymarket from pmxtjs.,fixed_retest_pass,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js core/test/unit/llms-docs.test.js; npm test --workspace=pmxt-core -- --runInBand,"RED tests caught standalone introduction, configuration, self-hosted, signing, README, and Python SDK README snippets using pmxt or os.getenv without same-snippet imports, plus a TypeScript signing snippet using new Polymarket without importing Polymarket. After 5168aa8, those snippets import pmxt/os/Polymarket as needed, npm run docs:llms refreshed docs/llms-full.txt, focused docs tests passed, and full core Jest passed 744 tests with 3 skipped.",DOC-STANDALONE-SETUP-IMPORTS-001,5168aa8,pass,Logistical docs copy/paste error fixed; no live venue access or trading required.
DOC-011,Documentation,Markdown,README TypeScript import guidance,readme.md; core/test/unit/docs-copy-paste-samples.test.js; sdks/typescript/index.ts,"As a TypeScript SDK reader, I want README import guidance to match the SDK's exported classes so that I do not avoid valid named imports or copy contradictory examples.",Root README TypeScript guidance states that named imports such as import { Polymarket } from pmxtjs and the default pmxt namespace import are both supported.,fixed_retest_pass,2026-06-23,RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; npx tsc --project sdks/typescript/tsconfig.esm.json --noEmit; npm test --workspace=pmxt-core -- --runInBand,"RED test caught the root README saying named imports do not work in ESM while the same section used import { Polymarket } from pmxtjs and sdks/typescript/index.ts exports Polymarket as a named ESM export. After d0e5c00, the README says named class imports and default namespace imports are both supported, TypeScript ESM compile passed, focused docs test passed, isolated launcher test passed after an unrelated timing flake, and full core Jest passed 745 tests with 3 skipped.",DOC-README-TS-IMPORT-GUIDANCE-001,d0e5c00,pass,Logistical README guidance error fixed; no live venue access or trading required.
TEST-001,Testing,Jest,Launcher stale-lock regression stability,core/test/server/pmxt-ensure-server.test.ts; core/bin/pmxt-ensure-server,"As a PMXT maintainer, I want the stale-lock launcher regression test to be stable inside the full core suite so that unrelated fixes are not blocked by timing-sensitive false failures.",The pmxt-ensure-server stale-lock test keeps a short stale-lock health wait but gives the replacement fake sidecar enough full-suite budget to write its lock and pass health checks deterministically.,fixed_retest_pass,2026-06-23,RED/GREEN: repeated npm test --workspace=pmxt-core -- --runInBand full-suite failures in test/server/pmxt-ensure-server.test.ts; npm test --workspace=pmxt-core -- --runInBand core/test/server/pmxt-ensure-server.test.ts; npm test --workspace=pmxt-core -- --runInBand,"Repeated full-suite verification caught the stale-lock launcher test returning status 1 while the same test passed in isolation, indicating a timing-sensitive harness rather than a launcher regression. After 174de73, the test uses named timing constants, keeps the stale existing-server health wait at 100ms, widens the replacement lock/health budget to 2500ms, increases the spawned launcher timeout, and both the isolated launcher test and full core Jest passed with 745 tests and 3 skipped.",TEST-LAUNCHER-STALE-LOCK-FLAKE-001,174de73,pass,Logistical test flake fixed; no production behavior or live venue access required.
TS-SDK-002,SDK,TypeScript,Hosted order parameter typing,sdks/typescript/pmxt/models.ts; core/src/types.ts; sdks/typescript/README.md; readme.md; sdks/typescript/API_REFERENCE.md; sdks/typescript/tests/hosted-order-params-types.test.ts; core/test/unit/docs-copy-paste-samples.test.js,"As a TypeScript hosted-trading user, I want the SDK order parameter type to include hosted fields such as denom and slippage_pct so that README examples compile without unsafe casts.","CreateOrderParams accepts hosted denom and slippage_pct fields, TypeScript README/root README hosted market-order snippets do not require `as any`, and the TypeScript API reference documents those hosted fields.",fixed_retest_pass,2026-06-23,RED/GREEN: npm test --workspace=pmxtjs -- --runInBand sdks/typescript/tests/hosted-order-params-types.test.ts; npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; npx tsc --project sdks/typescript/tsconfig.json --noEmit; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxtjs; npm test --workspace=pmxt-core -- --runInBand,"RED compiler test caught CreateOrderParams rejecting denom on hosted market-order params, and docs regression caught root/TypeScript README snippets requiring `} as any);`. After c549264, core and TypeScript SDK CreateOrderParams include denom and slippage_pct, README snippets no longer use unsafe casts, the TypeScript API reference documents the hosted fields, focused tests passed, TypeScript SDK Jest passed 58 tests, TypeScript/core compiles passed, and full core Jest passed 746 tests with 3 skipped.",TS-SDK-HOSTED-ORDER-PARAM-TYPES-001,c549264,pass,Logistical SDK typing and docs UX error fixed; no live venue access or trading required.
DOC-012,Documentation,Markdown,Hosted limit order documentation,docs/trading-quickstart.mdx; docs/guides/hosted-errors.mdx; docs/llms-full.txt; core/test/unit/docs-copy-paste-samples.test.js,"As a hosted trading docs reader, I want limit-order guidance to reflect current SDK denom behavior so that I do not avoid supported limit BUY orders or fall back to self-hosted unnecessarily.","Trading quickstart and hosted error docs state that hosted limit BUY and SELL are supported, both use denom=""shares"" in hosted SDK requests, and generated LLMS docs do not include the stale SDK denom mismatch caveat.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; npm run docs:llms; npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js core/test/unit/llms-docs.test.js; npm test --workspace=pmxt-core -- --runInBand","RED test caught docs/trading-quickstart.mdx and docs/guides/hosted-errors.mdx still saying limit BUY was being patched for an SDK denom mismatch and telling NoLiquidity users to post limits via self-hosted. After 827c611, both docs state hosted limit BUY and SELL are supported with denom shares, LLMS full docs were regenerated, focused docs/LLMS tests passed, and full core Jest passed with 747 tests and 3 skipped.",DOC-HOSTED-LIMIT-ORDER-DOCS-001,827c611,pass,Logistical docs UX error fixed; no live order placement required.
DOC-013,Documentation,Markdown,Hosted error TypeScript examples,docs/guides/hosted-errors.mdx; docs/api-reference/errors.mdx; docs/llms-full.txt; core/test/unit/docs-copy-paste-samples.test.js; sdks/typescript/pmxt/hosted-errors.ts,"As a TypeScript hosted-trading user, I want hosted error examples to use the SDK's typed status/detail fields so that copied recovery code does not rely on unsafe any casts.","Hosted error docs use e.detail and e.status after instanceof narrowing, generated LLMS docs mirror that, and source docs do not contain (e as any) casts.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; npm run docs:llms; npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js core/test/unit/llms-docs.test.js; npm test --workspace=pmxt-core -- --runInBand; npx tsc --project sdks/typescript/tsconfig.json --noEmit","RED test caught docs/guides/hosted-errors.mdx and docs/api-reference/errors.mdx using (e as any) to read hosted error detail/status despite the TypeScript SDK classes declaring those fields. After aefd493, docs use e.detail and e.status directly after instanceof narrowing, LLMS full docs were regenerated, focused docs/LLMS tests passed, full core Jest passed with 748 tests and 3 skipped, and TypeScript SDK compile passed.",DOC-HOSTED-ERROR-TYPED-FIELDS-001,aefd493,pass,Logistical docs copy-paste UX error fixed; no live venue access or trading required.
DOC-014,Documentation,OpenAPI,Order book SDK code samples,core/scripts/generate-openapi.js; docs/api-reference/openapi.json; docs/llms-full.txt; core/test/unit/openapi-code-samples.test.js; sdks/typescript/pmxt/client.ts; sdks/python/pmxt/client.py,"As an SDK docs reader, I want generated order-book samples to match the Python and TypeScript SDK method signatures so that copied examples compile and pass the expected positional arguments.","Generated OpenAPI and LLMS samples call TypeScript fetchOrderBook(outcomeId, limit, params), TypeScript fetchOrderBooks([outcomeId]), Python fetch_order_book(outcome_id, limit=..., params=...), and Python fetch_order_books([outcome_id]) instead of object-shaped or zero-argument calls.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/openapi-code-samples.test.js; npm run generate:openapi --workspace=pmxt-core; npm run docs:llms; npm test --workspace=pmxt-core -- --runInBand core/test/unit/openapi-code-samples.test.js core/test/unit/llms-docs.test.js; npm test --workspace=pmxt-core -- --runInBand","RED test caught generated TypeScript fetchOrderBook samples calling exchange.fetchOrderBook({ ... }) despite the SDK signature taking positional outcomeId/limit/params, and also covers fetchOrderBooks requiring an outcome-id array. After 638e2d2, generator overrides emit positional order-book SDK calls, checked-in OpenAPI and LLMS docs reflect those calls, focused OpenAPI/LLMS tests passed, and full core Jest passed with 749 tests and 3 skipped.",DOC-OPENAPI-ORDER-BOOK-SAMPLES-001,638e2d2,pass,Logistical generated-docs code-sample error fixed; no live venue access required.
TS-SDK-003,SDK,TypeScript,Outcome shorthand order parameter typing,sdks/typescript/pmxt/models.ts; sdks/typescript/pmxt/client.ts; sdks/typescript/tests/hosted-order-params-types.test.ts; sdks/typescript/API_REFERENCE.md; sdks/typescript/README.md; docs/guides/hosted-errors.mdx; docs/llms-full.txt; core/test/unit/docs-copy-paste-samples.test.js,"As a TypeScript trading user, I want createOrder/buildOrder to accept an outcome object without redundant marketId/outcomeId fields so that the documented outcome shorthand compiles in strict TypeScript.","TypeScript createOrder/buildOrder public argument types accept either explicit marketId/outcomeId fields or an outcome object returned by fetchMarkets; hosted error docs and the TypeScript API reference use CreateOrderInput for retry/order helpers; README examples narrow market.yes before passing it.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxtjs -- --runInBand sdks/typescript/tests/hosted-order-params-types.test.ts; npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; npm run docs:llms; npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js core/test/unit/llms-docs.test.js; npx tsc --project sdks/typescript/tsconfig.json --noEmit; npm test --workspace=pmxtjs; npm test --workspace=pmxt-core -- --runInBand","RED TypeScript SDK test caught Parameters<Polymarket['buildOrder'|'createOrder']>[0] rejecting the documented outcome shorthand because CreateOrderParams still required marketId and outcomeId. RED docs test caught hosted/API docs naming CreateOrderParams instead of the public shorthand-capable input type. After 29f441a, CreateOrderInput models the explicit-id or outcome-object variants, createOrder/buildOrder signatures use it, focused docs/LLMS checks passed, TypeScript compile passed, pmxtjs Jest passed 59 tests, and full core Jest passed with 750 tests and 3 skipped.",TS-SDK-OUTCOME-ORDER-SHORTHAND-TYPES-001,29f441a,pass,Logistical TypeScript SDK typing and docs UX error fixed; no live order placement required.
DOC-015,Documentation,OpenAPI,Submit order SDK code samples,core/scripts/generate-openapi.js; docs/api-reference/openapi.json; docs/api-reference/openapi-hosted-trading.json; docs/llms-full.txt; core/test/unit/openapi-code-samples.test.js; core/test/unit/hosted-openapi-code-samples.test.js,"As an SDK docs reader, I want submitOrder examples to build valid orders with concrete outcome inputs so that copied build-then-submit flows do not fail validation or strict TypeScript checks.","Self-hosted OpenAPI submitOrder samples call buildOrder/build_order with both marketId/market_id and outcomeId/outcome_id before submitOrder; hosted build-submit samples resolve a concrete YES outcome before passing it to buildOrder/build_order instead of using market.yes directly.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/hosted-openapi-code-samples.test.js; npm test --workspace=pmxt-core -- --runInBand core/test/unit/openapi-code-samples.test.js; npm run docs:llms; npm test --workspace=pmxt-core -- --runInBand core/test/unit/hosted-openapi-code-samples.test.js core/test/unit/openapi-code-samples.test.js core/test/unit/llms-docs.test.js; npm test --workspace=pmxt-core -- --runInBand","RED hosted OpenAPI test caught submitOrderHosted Python/TypeScript build-submit samples passing market.yes directly. RED generated OpenAPI test caught self-hosted submitOrder samples building orders without outcomeId/outcome_id. After 87d0ee2, generator and checked-in specs include the concrete outcome inputs, LLMS full docs were regenerated, focused OpenAPI/LLMS tests passed, structured spec checks passed, and full core Jest passed with 752 tests and 3 skipped.",DOC-SUBMIT-ORDER-SAMPLES-001,87d0ee2,pass,Logistical generated-docs code-sample error fixed; no live order placement required.
DOC-016,Documentation,SDK API Reference,SDK API reference order examples,scripts/generate-api-docs.js; scripts/templates/api-reference.typescript.md.hbs; sdks/typescript/API_REFERENCE.md; sdks/python/API_REFERENCE.md; core/workflow-examples.json; core/test/unit/docs-copy-paste-samples.test.js,"As an SDK docs reader, I want generated Python and TypeScript API reference order examples to include valid order parameters so that copied create/build/submit/order-book snippets match SDK signatures.","Generated TypeScript API reference examples call fetchOrderBooks with an outcome-id array, createOrder/buildOrder with marketId/outcomeId/side/type/amount/price, submitOrder with a BuiltOrder returned from buildOrder, and keep CreateOrderInput documented after regeneration; generated Python examples call fetch_order_books with a list, create_order/build_order with required keyword args, submit_order with a built order, and render List[str]/Dict[str, ...] types.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; npm run extract:jsdoc --workspace=pmxt-core; node scripts/generate-api-docs.js; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED docs test caught SDK API reference examples with await exchange.fetchOrderBooks(""12345""), empty createOrder/buildOrder calls, submitOrder(""..."") placeholders, Python scalar fetch_order_books, empty create_order/build_order, submit_order(built=""..."") placeholder, and malformed Python List[string]/Dictstr type rendering. After 9a797f2, the generator emits method-specific order examples, TypeScript CreateOrderInput is generator-owned, workflow source preserves the guarded outcome shorthand, Python type rendering uses List[str]/Dict[str, T], focused docs test passed, and full core Jest passed with 753 tests and 3 skipped.",DOC-SDK-API-REFERENCE-SAMPLES-001,9a797f2,pass,Logistical generated SDK API reference sample/type UX error fixed; no live venue access or order placement required.
DOC-017,Documentation,SDK API Reference,SDK API reference positional samples,scripts/generate-api-docs.js; sdks/typescript/API_REFERENCE.md; sdks/python/API_REFERENCE.md; core/test/unit/docs-copy-paste-samples.test.js,"As an SDK docs reader, I want generated API reference examples for positional methods to pass arguments in the same positions as the SDK signatures so that copied optional-argument examples compile and call the intended parameters.","Generated TypeScript API reference examples pass positional arguments for fetchOrderBook, watchOrderBook, watchOrderBooks, fetchOpenOrders, fetchPositions, and fetchBalance; generated Python order-book/watch examples pass params dictionaries instead of string placeholders.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; node scripts/generate-api-docs.js; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED docs test caught TypeScript examples passing object-shaped optional args to positional SDK methods (fetchOrderBook, fetchOpenOrders, fetchPositions, fetchBalance, watchOrderBook, watchOrderBooks) and Python order-book/watch examples passing params=""..."". After 75fd3a0, generator overrides emit positional TypeScript calls and Python params={}, focused docs test passed, and full core Jest passed with 754 tests and 3 skipped.",DOC-SDK-API-REFERENCE-POSITIONAL-SAMPLES-001,75fd3a0,pass,Logistical generated SDK API reference positional sample UX error fixed; no live venue access or order placement required.
DOC-018,Documentation,SDK API Reference,SDK API reference object/list placeholder samples,scripts/generate-api-docs.js; sdks/typescript/API_REFERENCE.md; sdks/python/API_REFERENCE.md; core/test/unit/docs-copy-paste-samples.test.js,"As an SDK docs reader, I want generated API reference examples for object and list parameters to use real objects/lists instead of string placeholders so that copied snippets satisfy the SDK method signatures.","Generated Python and TypeScript API reference examples for fetchOHLCV, fetchTrades, getExecutionPrice, getExecutionPriceDetailed, filterMarkets, filterEvents, watchTrades, and watchAddress use valid parameter objects, fetched lists, order books, numeric timestamps, and subscription arrays instead of string placeholders.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; node scripts/generate-api-docs.js; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED docs test caught TypeScript fetchOHLCV/fetchTrades/getExecutionPrice/filter/watch examples and Python fetch_ohlcv/fetch_trades/get_execution_price/filter/watch examples using string placeholders where object, list, order-book, numeric timestamp, or subscription-array inputs are required. After 25ddcca, generator overrides emit concrete object/list examples, focused docs test passed, and full core Jest passed with 755 tests and 3 skipped.",DOC-SDK-API-REFERENCE-PLACEHOLDER-SAMPLES-001,25ddcca,pass,Logistical generated SDK API reference placeholder sample UX error fixed; no live venue access or order placement required.
DOC-019,Documentation,SDK API Reference,SDK API reference callback samples,scripts/generate-api-docs.js; sdks/typescript/API_REFERENCE.md; sdks/python/API_REFERENCE.md; core/test/unit/docs-copy-paste-samples.test.js,"As an SDK docs reader, I want generated callback examples to pass callable functions and language-native callback signatures so that copied watch helper snippets compile instead of passing strings as callbacks.","Generated TypeScript API reference examples for Limitless watchPrices, watchUserPositions, and watchUserTransactions pass inline callbacks and render callback: (data: any) => void signatures; generated Python examples define callback functions before passing them and render Callable[[Any], None] plus None returns instead of TypeScript callback/void syntax.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; node scripts/generate-api-docs.js; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED docs test caught generated TypeScript callback examples passing strings to watchPrices, watchUserPositions, and watchUserTransactions; generated Python examples passing callback=""...""; invalid TypeScript callback type text in TypeScript signatures; and Python signatures using callback: (data: any) / -> void. After e1c021e, generator emits callable examples, TypeScript callback signatures render => void, Python callback signatures render Callable[[Any], None] and void returns render None, focused docs test passed, and full core Jest passed with 756 tests and 3 skipped.",DOC-SDK-API-REFERENCE-CALLBACK-SAMPLES-001,e1c021e,pass,Logistical generated SDK API reference callback sample/signature UX error fixed; no live venue access required.
DOC-020,Documentation,SDK API Reference,Python API reference type rendering,scripts/generate-api-docs.js; sdks/python/API_REFERENCE.md; core/test/unit/docs-copy-paste-samples.test.js,"As a Python SDK docs reader, I want generated API reference signatures to use Python-native type syntax so that copied signatures and method names are understandable and do not contain TypeScript object, union, or null syntax.","Generated Python API reference signatures render inline object params as dict, TypeScript unions as Union, literal sides as Literal, nullable returns as Optional, and ById/BySlug method names as get_event_by_id/get_event_by_slug.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; node scripts/generate-api-docs.js; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED docs test caught Python API reference signatures containing Optional[{ limit?: number; cursor?: string; filter?: ... }], string | union syntax, UnifiedEvent | null returns, side: 'buy' | 'sell', and get_event_byid/get_event_byslug method names. After 0635ce0, the generator renders dict, Union, Literal, Optional, and by_id/by_slug forms, focused docs test passed with 15 tests, and full core Jest passed with 757 tests and 3 skipped.",DOC-PYTHON-API-REFERENCE-TYPE-SYNTAX-001,0635ce0,pass,Logistical generated Python API reference signature UX error fixed; no live venue access required.
PY-SDK-004,SDK,Python,Documented exchange-only helper methods,sdks/python/API_REFERENCE.md; sdks/python/pmxt/client.py; sdks/python/tests/test_public_exports.py,"As a Python SDK user reading the API reference, I want documented exchange-only helper methods to exist on the Python client so that copied preWarmMarket and Probable event lookup snippets do not fail with AttributeError.","Python Exchange exposes pre_warm_market, get_event_by_id, and get_event_by_slug; pre_warm_market dispatches preWarmMarket, Probable event lookup helpers dispatch getEventById/getEventBySlug and convert non-null responses to UnifiedEvent.",fixed_retest_pass,2026-06-23,"RED/GREEN: uv run pytest sdks/python/tests/test_public_exports.py; uv run pytest sdks/python/tests; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED Python test caught Exchange lacking pre_warm_market and Probable event lookup helpers documented in the Python API reference. After 65e9163, Exchange.pre_warm_market dispatches preWarmMarket, get_event_by_id/get_event_by_slug dispatch and convert returned event payloads, focused Python test passed with 8 tests, full Python suite passed with 249 selected tests and 66 deselected, and full core Jest passed with 757 tests and 3 skipped.",PY-SDK-DOCUMENTED-EXCHANGE-HELPERS-001,65e9163,pass,Logistical Python SDK/API-reference mismatch fixed; no live venue access required.
DOC-021,Documentation,SDK API Reference,SDK API reference getter documentation,scripts/generate-api-docs.js; scripts/templates/api-reference.typescript.md.hbs; scripts/templates/api-reference.python.md.hbs; sdks/typescript/API_REFERENCE.md; sdks/python/API_REFERENCE.md; core/test/unit/docs-copy-paste-samples.test.js,"As an SDK docs reader, I want property getters documented as properties so that copied has/implicitApi snippets do not call non-callable getters.","Generated TypeScript and Python API references render has as property access with get has(): ExchangeHas / has: ExchangeHas examples, and no longer publish implicitApi/implicit_api as callable method sections.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; node scripts/generate-api-docs.js; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED docs test caught generated TypeScript API reference showing async has(): Promise<ExchangeHas>, await exchange.has(), and implicitApi as a method; it also caught Python API reference showing def has(), exchange.has(), and implicit_api as a method. After f973898, generator/template overrides render has as property access, override the bad extracted has summary, and exclude implicitApi from method docs; focused docs test passed with 16 tests and full core Jest passed with 758 tests and 3 skipped.",DOC-SDK-API-REFERENCE-GETTER-DOCS-001,f973898,pass,Logistical generated SDK API reference getter UX error fixed; no live venue access required.
DOC-022,Documentation,SDK API Reference,SDK API reference account history and firehose coverage,scripts/extract-jsdoc.js; scripts/generate-api-docs.js; core/src/BaseExchange.ts; sdks/typescript/pmxt/client.ts; sdks/typescript/API_REFERENCE.md; sdks/python/API_REFERENCE.md; core/test/unit/docs-copy-paste-samples.test.js,"As an SDK docs reader, I want every public account-history and watch-all/firehose SDK method listed in the generated Python and TypeScript API references so that I can discover and copy the methods that the SDKs expose.","Generated Python and TypeScript SDK API references include fetchMyTrades/fetch_my_trades, fetchClosedOrders/fetch_closed_orders, fetchAllOrders/fetch_all_orders, watchAllOrderBooks/watch_all_order_books, and firehose with valid signatures and examples.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; npm run extract:jsdoc --workspace=pmxt-core; node scripts/generate-api-docs.js; npx tsc --project core/tsconfig.json --noEmit; npx tsc --project sdks/typescript/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand; npm test --workspace=pmxtjs","RED docs test caught generated SDK API references omitting account-history methods and hosted watch-all/firehose methods even though the SDKs, OpenAPI, CLI aliases, hosted docs, and capability maps expose them. After 9b4c47c, JSDoc extraction includes the missing account-history and SDK-only watch-all/firehose methods, generated examples are copy-pasteable, focused docs test passed with 17 tests, full core Jest passed with 759 tests and 3 skipped, and TypeScript SDK Jest passed with 59 tests.",DOC-SDK-API-REFERENCE-MISSING-METHODS-001,9b4c47c,pass,Logistical generated SDK API reference coverage UX error fixed; no live venue access or order placement required.
DOC-023,Documentation,OpenAPI SDK Samples,OpenAPI SDK date-time sample values,core/scripts/generate-openapi.js; docs/api-reference/openapi.json; docs/llms-full.txt; core/test/unit/openapi-code-samples.test.js,"As an OpenAPI docs reader, I want generated SDK samples for date filters to use valid ISO date-time strings so that copied snippets are meaningful and accepted by the documented schema.","Generated Python and TypeScript OpenAPI SDK samples for date-time params use ISO strings such as 2026-01-01T00:00:00Z and 2026-01-31T00:00:00Z instead of placeholder value strings.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/openapi-code-samples.test.js; npm run generate:openapi --workspace=pmxt-core; npm run docs:llms; rg -n 'since[=:] ""value""|until[=:] ""value""|start[=:] ""value""|end[=:] ""value""|since=""value""|until=""value""|start=""value""|end=""value""' docs/api-reference/openapi.json docs/llms-full.txt; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED OpenAPI sample test caught generated fetchMyTrades samples using since: ""value"" / until: ""value"". After 4d18f98, exampleValue emits ISO strings for date-time schemas, generated OpenAPI/LLMS samples have no start/end/since/until ""value"" placeholders, focused OpenAPI/LLMS tests passed with 5 tests, TypeScript compile passed, and full core Jest passed with 760 tests and 3 skipped.",DOC-OPENAPI-DATETIME-SAMPLE-VALUES-001,4d18f98,pass,Logistical generated OpenAPI SDK sample UX error fixed; no live venue access or order placement required.
DOC-024,Documentation,OpenAPI SDK Samples,OpenAPI data-feed code samples,core/scripts/generate-openapi.js; docs/api-reference/openapi.json; docs/llms-full.txt; core/test/unit/openapi-code-samples.test.js,"As a data-feed API docs reader, I want generated feed examples to use the feed client or the documented HTTP/WebSocket transport so that copied snippets do not call nonexistent prediction-market exchange methods.","Generated OpenAPI and LLMS samples for data-feed endpoints use raw HTTP for feed list and feed order book, FeedClient for SDK-backed feed methods, WebSocket subscription code for watchTicker, and no generic exchange.feed* calls or value placeholders for symbols, timeframes, or oracle feeds.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/openapi-code-samples.test.js; npm run generate:openapi --workspace=pmxt-core; npm run docs:llms; rg -n 'symbols=""value""|symbols: ""value""|timeframe=""value""|timeframe: ""value""|feed=""value""|feed: ""value""|exchange\\.feed|exchange\\.feed_' docs/api-reference/openapi.json docs/llms-full.txt; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED OpenAPI sample test caught feed endpoints receiving 18 generic venue samples per language instead of curated feed samples. After 9324bf3, feed operations prefer buildFeedCodeSamples, feedFetchOHLCV and feedFetchOrderBook have explicit curated samples, generated OpenAPI/LLMS docs no longer contain exchange.feed* snippets or feed value placeholders, focused OpenAPI/LLMS tests passed with 6 tests, TypeScript compile passed, and full core Jest passed with 761 tests and 3 skipped.",DOC-FEED-OPENAPI-SAMPLES-001,9324bf3,pass,"Logistical generated data-feed docs sample UX error fixed; no live feed access, venue access, or order placement required."
DOC-025,Documentation,OpenAPI SDK Samples,OpenAPI paginated list filter sample values,core/scripts/generate-openapi.js; docs/api-reference/openapi.json; docs/llms-full.txt; core/test/unit/openapi-code-samples.test.js,"As an OpenAPI docs reader, I want paginated market and event examples to avoid fake filter placeholders so that copied snippets do not pass an invalid string where the SDK expects structured filter criteria.","Generated Python and TypeScript OpenAPI and LLMS samples for fetchMarketsPaginated and fetchEventsPaginated include limit and cursor examples without inventing filter=""value"" / filter: ""value"" placeholders.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/openapi-code-samples.test.js; npm run generate:openapi --workspace=pmxt-core; npm run docs:llms; rg -n 'filter=""value""|filter: ""value""' docs/api-reference/openapi.json docs/llms-full.txt core/src/server/openapi.yaml; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED OpenAPI sample test caught fetchMarketsPaginated TypeScript samples passing filter: ""value"". After 998ba22, generator parameter overrides for fetchMarketsPaginated and fetchEventsPaginated emit only limit/cursor sample args, generated OpenAPI/LLMS docs have no filter value placeholders, focused OpenAPI/LLMS tests passed with 7 tests, TypeScript compile passed, and full core Jest passed with 762 tests and 3 skipped.",DOC-OPENAPI-PAGINATED-FILTER-PLACEHOLDER-001,998ba22,pass,Logistical generated paginated OpenAPI sample UX error fixed; no live venue access or order placement required.
DOC-026,Documentation,TypeScript Generated SDK Docs,TypeScript generated model reference examples,sdks/typescript/scripts/fix-generated.js; sdks/typescript/generated/docs/*.md; core/test/unit/typescript-generated-docs.test.js,"As a TypeScript generated SDK docs reader, I want model reference pages to avoid template placeholder examples so that I can rely on property tables instead of copying invalid null-filled samples.","npm run generate:sdk:typescript --workspace=pmxt-core runs the TypeScript generated SDK post-processor, removes OpenAPI Generator model example blocks with TODO/null placeholders from generated model docs, and leaves API endpoint examples untouched.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/typescript-generated-docs.test.js; npm run generate:sdk:typescript --workspace=pmxt-core; node sdks/typescript/scripts/fix-generated.js; rg -n 'TODO: Update the object below with actual values' sdks/typescript/generated/docs; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED generated-doc test caught OpenAPI Generator model docs publishing TODO/null placeholder examples. After 0496ee7, fix-generated.js strips model ## Example blocks from non-Api generated docs, exports cleanup helpers for isolated regression tests, normal SDK generation succeeds, placeholder scan returned no hits, TypeScript compile passed, and full core Jest passed with 764 tests and 3 skipped.",DOC-TS-GENERATED-MODEL-TODO-001,0496ee7,pass,Logistical generated SDK docs UX error fixed; generated directory is ignored so the durable fix is the post-processor and regression test; no live venue access or order placement required.
DOC-027,Documentation,TypeScript Generated SDK Docs,TypeScript generated endpoint examples,sdks/typescript/scripts/fix-generated.js; sdks/typescript/generated/docs/*Api.md; core/test/unit/typescript-generated-docs.test.js,"As a TypeScript generated SDK docs reader, I want endpoint reference pages to avoid unbound placeholder variables so that generated docs do not present non-copyable examples like feed_example or exchange_example.","npm run generate:sdk:typescript --workspace=pmxt-core runs the TypeScript generated SDK post-processor, removes generated API endpoint ### Example blocks with unbound placeholder variables from *Api.md docs, and preserves method summaries, signatures, parameter tables, return types, auth, and response details.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/typescript-generated-docs.test.js; npm run generate:sdk:typescript --workspace=pmxt-core; rg -n '\\b[A-Za-z0-9_]+_example\\b' sdks/typescript/generated/docs/DataFeedsApi.md sdks/typescript/generated/docs/DefaultApi.md; rg -n 'TODO: Update the object below with actual values' sdks/typescript/generated/docs; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED generated-doc test caught the missing API-doc cleanup helpers while generated *Api.md docs still contained unbound feed_example/exchange_example placeholders. After d116c1e, fix-generated.js strips generated API endpoint ### Example blocks from *Api.md files, normal SDK generation removes placeholder examples from 2 generated API docs, placeholder scans returned no hits, TypeScript compile passed, and full core Jest passed with 766 tests and 3 skipped.",DOC-TS-GENERATED-ENDPOINT-PLACEHOLDER-001,d116c1e,pass,Logistical generated SDK endpoint docs UX error fixed; generated directory is ignored so the durable fix is the post-processor and regression test; no live venue access or order placement required.
DOC-028,Documentation,TypeScript Generated SDK Docs,TypeScript generated README usage example,sdks/typescript/scripts/fix-generated.js; sdks/typescript/generated/README.md; core/test/unit/typescript-generated-docs.test.js,"As a TypeScript generated SDK reader, I want the generated README to avoid unbound placeholder quickstart code so that the ignored generated package docs do not publish invalid feed_example/symbol_example snippets.","npm run generate:sdk:typescript --workspace=pmxt-core runs the TypeScript generated SDK post-processor, removes the generated README's placeholder Usage example block, and preserves install instructions plus generated API endpoint/model documentation tables.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/typescript-generated-docs.test.js; npm run generate:sdk:typescript --workspace=pmxt-core; rg -n '\\b[A-Za-z0-9_]+_example\\b|TODO: Update the object below with actual values|Next, try it out' sdks/typescript/generated/README.md sdks/typescript/generated/docs; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED generated-doc test caught missing README usage cleanup helpers while generated README still published feed_example/symbol_example placeholders. After 42fefca, fix-generated.js strips the generated README usage block between Next, try it out and ## Documentation, normal SDK generation removes the placeholder block, placeholder scans returned no hits across generated README/docs, TypeScript compile passed, and full core Jest passed with 768 tests and 3 skipped.",DOC-TS-GENERATED-README-PLACEHOLDER-001,42fefca,pass,Logistical generated SDK README UX error fixed; generated directory is ignored so the durable fix is the post-processor and regression test; no live venue access or order placement required.
DOC-029,Documentation,OpenAPI SDK Samples,OpenAPI public SDK sample targets,core/scripts/generate-openapi.js; core/src/server/openapi.yaml; docs/api-reference/openapi.json; docs/llms-full.txt; docs/concepts/venues.mdx; core/test/unit/openapi-code-samples.test.js,"As an OpenAPI docs reader, I want generated public SDK samples to show only user-facing constructor targets with realistic market/event list filters so that copied snippets do not instantiate internal mocks, use Router for unsupported generic methods, or pass placeholder filter strings.","Generated sidecar and hosted OpenAPI docs scope SDK samples to capability-supported public venues; hosted docs strip internal mock constructor metadata; Router samples appear only for router-backed operations; fetchMarkets/fetchEvents examples use query, limit, and status instead of sourceExchange/series/filter/category ""value"" placeholders; generated venue/LLMS docs are synced to pmxt-core 2.17.1.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/openapi-code-samples.test.js; npm run build --workspace=pmxt-core; npm run generate:openapi --workspace=pmxt-core; npm run generate:mintlify --workspace=pmxt-core; npm run docs:llms; rg -n 'pmxt\.Mock|import \{ Mock \}|new Mock|""className"": ""Mock""' docs/api-reference/openapi.json docs/llms-full.txt; rg -n 'source_exchange=""value""|sourceExchange: ""value""|series=""value""|series: ""value""|filter=""value""|filter: ""value""|category=""value""|category: ""value""' docs/api-reference/openapi.json docs/llms-full.txt core/src/server/openapi.yaml; npm test --workspace=pmxt-core -- --runInBand core/test/unit/openapi-code-samples.test.js core/test/unit/llms-docs.test.js core/test/unit/mintlify-venues.test.js; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED OpenAPI sample tests caught public hosted constructor metadata containing mock, generic loadMarkets samples containing Router, fetchMarkets/fetchEvents placeholder filters, and a stale capability map missing Hyperliquid/GeminiTitan/Hunch. After bd34ca7, generated docs contain no Mock SDK samples or generic filter value placeholders, Router remains in documented router-backed operations, current public venues remain in market/event samples, focused docs tests passed with 12 tests, TypeScript compile passed, and full core Jest passed with 772 tests and 3 skipped.",DOC-OPENAPI-PUBLIC-SDK-SAMPLES-001,bd34ca7,pass,"Logistical generated OpenAPI/LLMS docs UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-030,Documentation,OpenAPI SDK Samples,Router order-book SDK samples,core/scripts/generate-openapi.js; docs/api-reference/openapi.json; core/test/unit/openapi-code-samples.test.js; core/src/router/Router.ts,"As an OpenAPI docs reader, I want fetchOrderBook examples to instantiate only venue clients that can call the method with the shown constructor arguments so that copied Router examples do not fail immediately at runtime.","Generated hosted OpenAPI samples do not include Router for fetchOrderBook because Router.fetchOrderBook requires configured exchange instances; Router samples remain available for catalog-backed and router-only operations such as fetchMarkets, fetchEvents, fetchSeries, and fetchMarketMatches.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/openapi-code-samples.test.js; npm run generate:openapi --workspace=pmxt-core; npm run docs:llms; node -e OpenAPI label check for fetchOrderBook/fetchMarkets/fetchEvents/fetchSeries/fetchMarketMatches; npm test --workspace=pmxt-core -- --runInBand core/test/unit/openapi-code-samples.test.js core/test/unit/llms-docs.test.js; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED OpenAPI sample test caught fetchOrderBook still publishing Python and TypeScript Router samples even though Router.fetchOrderBook throws without RouterOptions.exchanges. After 6f0ed22, generated public OpenAPI has zero Router labels for fetchOrderBook while retaining Router labels for fetchMarkets, fetchEvents, fetchSeries, and fetchMarketMatches; focused OpenAPI/LLMS tests passed with 11 tests, TypeScript compile passed, and full core Jest passed with 772 tests and 3 skipped.",DOC-OPENAPI-ROUTER-ORDERBOOK-SAMPLE-001,6f0ed22,pass,"Logistical generated OpenAPI docs UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-031,Documentation,OpenAPI SDK Samples,OpenAPI SDK positional and typed sample calls,core/scripts/generate-openapi.js; docs/api-reference/openapi.json; docs/llms-full.txt; core/test/unit/openapi-code-samples.test.js; sdks/typescript/pmxt/client.ts; sdks/python/pmxt/client.py,"As an OpenAPI SDK docs reader, I want generated examples to match the Python and TypeScript SDK method signatures and value types so that copied snippets call positional methods correctly and do not pass placeholder objects where concrete SDK objects are required.","Generated TypeScript OpenAPI samples call fetchOrder, cancelOrder, fetchOpenOrders, fetchPositions, fetchBalance, fetchOHLCV, and fetchTrades with positional arguments; TypeScript date filters use Date objects where the SDK types require Date; Python OHLCV samples use datetime objects; execution-price samples in both languages use a concrete OrderBook instead of an orderBook string placeholder; account samples use a syntactically valid example address instead of 0xabc....",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/openapi-code-samples.test.js; npm run generate:openapi --workspace=pmxt-core; npm run docs:llms; node -e OpenAPI object-call/orderBook/address scan; npm test --workspace=pmxt-core -- --runInBand core/test/unit/openapi-code-samples.test.js core/test/unit/llms-docs.test.js; npm run build --workspace=pmxt-core; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED OpenAPI sample tests caught generated TypeScript samples calling fetchOrder({ orderId: ... }) and execution-price samples passing orderBook=""orderBook"". The audit also found fetchOHLCV/fetchTrades/fetchOpenOrders/fetchPositions/fetchBalance/cancelOrder using object-shaped TypeScript calls despite positional SDK signatures, ISO string dates where TypeScript/Python SDK methods require Date/datetime values, and 0xabc... address placeholders. After 48055b6, generated OpenAPI and LLMS samples use positional SDK calls, SDK-native date values, concrete OrderBook examples, and a valid example address; focused OpenAPI/LLMS tests passed with 13 tests, core build passed, diff check passed, and full core Jest passed with 774 tests and 3 skipped.",DOC-OPENAPI-SDK-POSITIONAL-SAMPLES-001,48055b6,pass,"Logistical generated OpenAPI/LLMS code-sample UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-032,Documentation,TypeScript SDK API Reference,TypeScript API reference sync member rendering,scripts/generate-api-docs.js; scripts/templates/api-reference.typescript.md.hbs; sdks/typescript/API_REFERENCE.md; core/test/unit/docs-copy-paste-samples.test.js; sdks/typescript/pmxt/client.ts; core/src/BaseExchange.ts,"As a TypeScript SDK API reference reader, I want synchronous properties and helpers to be documented without await or Promise wrappers so that copied examples and return expectations match the runtime SDK behavior.","Generated TypeScript API reference renders has as a property returning ExchangeHas, getExecutionPrice as getExecutionPrice(orderBook: OrderBook, side: 'buy' | 'sell', amount: number): number, the getExecutionPrice return line as number, and the getExecutionPrice example without await while keeping async methods such as getExecutionPriceDetailed documented as Promise-returning calls.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; node scripts/generate-api-docs.js; rg -n 'await exchange\.getExecutionPrice\(orderBook|Promise<ExchangeHas>|async getExecutionPrice\(orderBook|Promise<number> - Average execution price' sdks/typescript/API_REFERENCE.md; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED docs-copy-paste test caught sdks/typescript/API_REFERENCE.md still showing await exchange.getExecutionPrice(orderBook, ""buy"", 50) and **Returns:** Promise<ExchangeHas> for the has property. After 664baa0, the generator marks TypeScript sync members, the template renders sync signatures and return lines without Promise wrappers, generated TypeScript API reference has no stale sync-member strings, focused docs test passed with 17 tests, TypeScript compile passed, diff check passed, and full core Jest passed with 774 tests and 3 skipped.",DOC-TS-API-REFERENCE-SYNC-PROMISE-001,664baa0,pass,"Logistical generated TypeScript API reference UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-033,Documentation,TypeScript Examples,Execution price await usage in docs and examples,core/API_REFERENCE.md; sdks/typescript/examples/market-data/execution_price.ts; core/src/BaseExchange.ts; sdks/typescript/pmxt/client.ts; core/test/unit/docs-copy-paste-samples.test.js,"As a TypeScript docs and examples reader, I want execution-price snippets to await only methods that actually return Promises so that copied examples communicate which helpers are synchronous and which SDK calls are asynchronous.","Core API reference examples call getExecutionPrice and core getExecutionPriceDetailed synchronously; the TypeScript SDK market-data execution_price example calls synchronous api.getExecutionPrice without await while keeping api.getExecutionPriceDetailed awaited because the pmxtjs client method is async.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; rg -n 'await [^\n]*getExecutionPrice\(' core/API_REFERENCE.md sdks/typescript/examples/market-data/execution_price.ts; npx tsc --project core/tsconfig.json --noEmit; npx tsc --project sdks/typescript/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand; npm test --workspace=pmxtjs","RED docs-copy-paste test caught core/API_REFERENCE.md still using await for polymarket.getExecutionPrice and polymarket.getExecutionPriceDetailed. After 8b6440f, core API reference uses synchronous helper calls, the TypeScript SDK execution_price example no longer awaits api.getExecutionPrice, the stale await scan returned no sync-helper hits, focused docs test passed with 18 tests, TypeScript compiles passed for core and pmxtjs, full core Jest passed with 775 tests and 3 skipped, and pmxtjs Jest passed with 59 tests.",DOC-EXECUTION-PRICE-AWAIT-DOCS-001,8b6440f,pass,"Logistical static docs/example UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-034,Documentation,Core API Reference,Core API reference TypeScript import guidance,core/API_REFERENCE.md; readme.md; sdks/typescript/README.md; sdks/typescript/tsconfig.esm.json; core/test/unit/docs-copy-paste-samples.test.js,"As a TypeScript docs reader, I want the core API reference import guidance to match the package's current named and namespaced exports so that I do not avoid supported ESM named imports or copy outdated dynamic-import advice.","Core API reference import guidance shows named class imports such as import { Polymarket, Kalshi } from 'pmxtjs' plus the default pmxt namespace form, and it does not claim pmxtjs is CommonJS-only or that named exports fail in ESM projects.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; rg -n 'CommonJS-only|Named exports like .*will \\*\\*not work\\*\\*|Named imports do not work' core/API_REFERENCE.md readme.md sdks/typescript/README.md; npx tsc --project sdks/typescript/tsconfig.esm.json --noEmit; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand; npm test --workspace=pmxtjs","RED docs-copy-paste test caught core/API_REFERENCE.md still lacking the current named import example and still claiming pmxtjs is CommonJS-only / named exports fail in ESM. After 9fc107c, the stale import-warning scan returned no hits, the ESM TypeScript config compiled, core TypeScript compile passed, focused docs test passed with 18 tests, full core Jest passed with 775 tests and 3 skipped, and pmxtjs Jest passed with 59 tests.",DOC-CORE-API-REFERENCE-IMPORT-GUIDANCE-001,9fc107c,pass,"Logistical static core API reference UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-035,Documentation,Core API Reference,Core API reference legacy market lookup names,core/API_REFERENCE.md; core/src/BaseExchange.ts; core/test/unit/docs-copy-paste-samples.test.js,"As a core API reference reader, I want market lookup examples to use current public methods so that copied snippets do not call removed legacy helpers such as getMarketsBySlug.","Core API reference describes query and slug filters without legacy alias wording, slug lookup examples use fetchMarkets, and the error-handling example uses fetchMarket({ slug }) so missing single-market lookups throw MarketNotFound through a current public method.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; rg -n 'getMarketsBySlug|replaces searchMarkets' core/API_REFERENCE.md readme.md docs sdks/typescript/README.md sdks/python/README.md -g '!docs/llms-full.txt' -g '!docs/api-reference/openapi.json' -g '!docs/api-reference/openapi-hosted-trading.json'; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED docs-copy-paste test caught core/API_REFERENCE.md still mentioning getMarketsBySlug and using kalshi.getMarketsBySlug('INVALID-TICKER') in the error-handling example. After 96ddbbf, the docs use current fetchMarkets/fetchMarket lookup methods, the legacy lookup scan returned no hits in current static docs, core TypeScript compile passed, focused docs test passed with 19 tests, diff check passed, and full core Jest passed with 776 tests and 3 skipped.",DOC-CORE-API-REFERENCE-LEGACY-MARKET-LOOKUP-001,96ddbbf,pass,"Logistical static core API reference UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-036,Documentation,Core API Reference,Core API reference venue scope wording,core/API_REFERENCE.md; docs/concepts/venues.mdx; core/test/unit/docs-copy-paste-samples.test.js,"As a core API reference reader, I want the overview and authentication sections to describe PMXT's current multi-venue scope so that I do not think the SDK only covers Polymarket and Kalshi.","Core API reference describes PMXT as a unified interface for multiple prediction market exchanges and venues, and its authenticated-trading section says trading is available on venues that expose trading APIs with venue-specific credentials while keeping Polymarket and Kalshi as examples.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; rg -n 'multiple prediction market exchanges \\(Kalshi, Polymarket\\) identically|Both Polymarket and Kalshi support authenticated trading operations' core/API_REFERENCE.md readme.md docs sdks/typescript/README.md -g '!docs/llms-full.txt' -g '!docs/api-reference/openapi.json'; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED docs-copy-paste test caught core/API_REFERENCE.md still describing the product as Kalshi/Polymarket-only and saying only those two support authenticated trading operations. After 8361455, the stale two-venue scope scan returned no hits in current static docs, core TypeScript compile passed, focused docs test passed with 20 tests, diff check passed, and full core Jest passed with 777 tests and 3 skipped.",DOC-CORE-API-REFERENCE-VENUE-SCOPE-001,8361455,pass,"Logistical static core API reference UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-037,Documentation,Core API Reference,Core API reference import example variable names,core/API_REFERENCE.md; core/test/unit/docs-copy-paste-samples.test.js,"As a core API reference reader, I want setup snippets to define the same variables used by later examples so that copied snippets can be combined without renaming poly to polymarket.","Core API reference import examples define polymarket and kalshi in both named-import and pmxt namespace forms, matching later snippets that call polymarket.fetchMarkets, polymarket.fetchOrderBook, and polymarket trading methods.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; rg -n 'const poly =|\\bpoly\\.' core/API_REFERENCE.md; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED docs-copy-paste test caught core/API_REFERENCE.md import examples defining const poly while later examples use polymarket. After 1d41fa7, the import examples define const polymarket in both import styles, the poly alias scan returned no hits in core/API_REFERENCE.md, core TypeScript compile passed, focused docs test passed with 20 tests, diff check passed, and full core Jest passed with 777 tests and 3 skipped.",DOC-CORE-API-REFERENCE-EXAMPLE-VARIABLES-001,1d41fa7,pass,"Logistical static core API reference UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-038,Documentation,Streaming API Reference,Streaming API reference venue scope,docs/api-reference/watch-order-book.mdx; docs/api-reference/watch-order-books.mdx; docs/api-reference/watch-trades.mdx; docs/llms-full.txt; core/test/pipeline/watch-order-book-api.test.ts,"As a streaming API reference reader, I want each WebSocket page to list the venues implemented for that streaming method so that I can choose a supported venue without assuming the hosted firehose list is the full sidecar streaming scope.","watchOrderBook and watchOrderBooks docs list all implemented order-book streaming venues: polymarket, kalshi, limitless, opinion, polymarket_us, probable, baozi, myriad, gemini-titan, rain, and hunch. watchTrades docs list implemented trade-stream venues: polymarket, kalshi, limitless, opinion, polymarket_us, myriad, gemini-titan, rain, and hunch. watchAllOrderBooks keeps the hosted OBDATA venue list: polymarket, kalshi, limitless, opinion.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/pipeline/watch-order-book-api.test.ts; npm run docs:llms; npm test --workspace=pmxt-core -- --runInBand core/test/unit/llms-docs.test.js core/test/pipeline/watch-order-book-api.test.ts; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED pipeline test caught stale four-venue Supported venues lines in watchOrderBook, watchOrderBooks, watchTrades, and stale LLMS output. After 246c00f, the MDX pages and docs/llms-full.txt list the implemented streaming venue scope, the stale four-venue scan returned no hits on affected single/batch stream pages, focused pipeline and LLMS tests passed with 4 tests, core TypeScript compile passed, diff check passed, and full core Jest passed with 778 tests and 3 skipped.",DOC-STREAMING-VENUE-SCOPE-001,246c00f,pass,"Logistical API reference UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-039,Documentation,Venue and LLMS Docs,Top-level venue count copy,docs/introduction.mdx; docs/router/overview.mdx; scripts/generate-llms.js; docs/llms.txt; docs/llms-full.txt; docs/concepts/venues.mdx; core/test/unit/llms-docs.test.js,"As a docs reader or LLM consumer, I want top-level PMXT venue-count copy to match the generated Supported Venues table so that I do not underestimate the current venue surface.","Introduction, Router overview, LLMS compact index, and LLMS full docs describe Polymarket, Kalshi, Limitless, Smarkets, and 12 more venues, matching the 16 pass-through venue targets in docs/concepts/venues.mdx.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/llms-docs.test.js; npm run docs:llms; rg -n '8 more venues|12 more venues' docs scripts/generate-llms.js core/test/unit/llms-docs.test.js --glob '!node_modules'; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED LLMS docs test computed 16 pass-through venue rows from docs/concepts/venues.mdx and caught stale 8-more-venues copy in docs/introduction.mdx, docs/router/overview.mdx, and generated LLMS outputs. After 3cf7340, source docs, generator header, docs/llms.txt, and docs/llms-full.txt use 12 more venues, the only remaining 8-more-venues hit is the negative regression assertion, focused LLMS test passed, core TypeScript compile passed, diff check passed, and full core Jest passed with 778 tests and 3 skipped.",DOC-VENUE-COUNT-COPY-001,3cf7340,pass,"Logistical docs/LLMS UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-040,Documentation,Router Docs,Router stale API-count wording,docs/router/overview.mdx; docs/llms-full.txt; core/test/unit/llms-docs.test.js,"As a Router documentation reader, I want cross-venue search copy to avoid stale hardcoded API counts so that the performance explanation stays correct as PMXT adds or removes venues.","Router overview and LLMS full docs describe shared-catalog search as avoiding one call per venue and fanning out to venue APIs, with no hardcoded 11 sequential API calls or 11 different APIs wording.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/llms-docs.test.js; npm run docs:llms; rg -n '11 sequential API calls|11 different APIs|not one call per venue|not fanning\\s+out to venue APIs' docs core/test/unit/llms-docs.test.js --glob '!node_modules'; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED LLMS docs test caught docs/router/overview.mdx still saying results avoid 11 sequential API calls; audit also found 11 different APIs in the same page. After f33b1bf, Router overview and docs/llms-full.txt use count-free shared-catalog wording, stale 11-count scans returned no source/artifact hits, focused LLMS test passed, core TypeScript compile passed, diff check passed, and full core Jest passed with 778 tests and 3 skipped.",DOC-ROUTER-STALE-API-COUNT-001,f33b1bf,pass,"Logistical Router docs/LLMS UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-041,Documentation,Hosted and Self-hosted Docs,Self-hosted write support scope,docs/guides/self-hosted.mdx; docs/trading-quickstart.mdx; docs/concepts/hosted-trading.mdx; docs/authentication.mdx; docs/llms-full.txt; core/test/unit/llms-docs.test.js,"As a hosted/self-hosted docs reader, I want write support guidance to say venue-native self-hosted trading is available where the venue exposes writes so that I do not assume every PMXT venue supports order placement or cancellation.","Self-hosted and hosted-trading docs avoid blanket claims that self-hosted writes work on every supported venue, describe venue-native writes as venue-specific, and point readers to Feature Support & Compliance for per-venue support.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/llms-docs.test.js; npm run docs:llms; rg -n 'Self-hosted writes work on every venue PMXT supports|\| \*\*Trading venues\*\* \| Polymarket, Opinion, Limitless \| Every venue PMXT supports \||use \[self-hosted\]\([^)]*\) to trade them|Use \[self-hosted\]\([^)]*\) for writes' docs core/test/unit/llms-docs.test.js --glob '!node_modules'; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED LLMS docs test caught the self-hosted guide claiming writes work on every PMXT venue and, during review, the hosted-trading comparison table claiming self-hosted trading venues were every PMXT venue. After 9872fef, the source docs and docs/llms-full.txt say venue-native self-hosted writes are available where the venue exposes writes and link to Feature Support & Compliance, stale blanket-claim scans returned no source/artifact hits, focused LLMS test passed, core TypeScript compile passed, diff check passed, and full core Jest passed with 778 tests and 3 skipped.",DOC-SELF-HOSTED-WRITE-SUPPORT-SCOPE-001,9872fef,pass,"Logistical hosted/self-hosted docs UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-042,Documentation,OHLCV API Reference,OHLCV support and API-key scope,docs/api-reference/fetch-ohlcv.mdx; docs/llms-full.txt; core/COMPLIANCE.md; core/test/unit/llms-docs.test.js,"As an OHLCV API reference reader, I want candle-history docs to describe hosted and self-hosted routing plus venue-specific support so that I do not think Kalshi and Limitless OHLCV are still future work or that every venue has identical candle depth.","The Fetch OHLCV page and LLMS full docs no longer say Kalshi, Limitless, and more are coming soon or that unauthenticated OHLCV is limited to Polymarket. They explain that hosted calls require a PMXT API key, self-hosted calls use local pmxt-core and venue-native APIs, and fetchOHLCV returns normalized PriceCandle rows for venues whose implementation supports it, with Feature Support & Compliance as the current matrix.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/llms-docs.test.js; npm run docs:llms; rg -n 'Kalshi, Limitless, and more are coming soon|Without an API key, OHLCV is limited to Polymarket|Pass pmxt_api_key for volume data and deeper history|Pass pmxtApiKey for volume data and deeper history|venues whose implementation supports `fetchOHLCV`|Feature Support & Compliance' docs/api-reference/fetch-ohlcv.mdx docs/llms-full.txt core/test/unit/llms-docs.test.js; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED LLMS docs test caught docs/api-reference/fetch-ohlcv.mdx and docs/llms-full.txt still saying Kalshi, Limitless, and more are coming soon and claiming no-key OHLCV was limited to Polymarket. After 7f4516f, the source page and LLMS full docs use hosted/self-hosted routing language, link to Feature Support & Compliance, align Python and TypeScript examples with hosted API-key guidance, stale scans returned no source/artifact hits for the old claims, focused LLMS test passed, core TypeScript compile passed, diff check passed, and full core Jest passed with 778 tests and 3 skipped.",DOC-OHLCV-SUPPORT-SCOPE-001,7f4516f,pass,"Logistical OHLCV docs/LLMS UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-043,Documentation,Introduction and LLMS Docs,Introduction hardcoded API count,docs/introduction.mdx; docs/llms-full.txt; core/test/unit/llms-docs.test.js,"As an Introduction reader, I want the cross-venue search problem statement to avoid stale hardcoded API counts so that the page stays correct as PMXT adds or removes venues.","The Introduction page and LLMS full docs describe the search-layer problem as querying venue APIs sequentially rather than querying 11 APIs sequentially.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/llms-docs.test.js; npm run docs:llms; rg -n 'querying 11 APIs sequentially is slow|querying venue APIs sequentially is slow|11 sequential API calls|11 different APIs' docs/introduction.mdx docs/llms-full.txt docs/router/overview.mdx core/test/unit/llms-docs.test.js; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED LLMS docs test caught docs/introduction.mdx and docs/llms-full.txt still saying querying 11 APIs sequentially is slow. After 57d988a, the Introduction page and LLMS full docs use count-free venue API wording, stale count scans returned no source/artifact hits for the old Introduction claim, focused LLMS test passed, core TypeScript compile passed, diff check passed, and full core Jest passed with 778 tests and 3 skipped.",DOC-INTRO-STALE-API-COUNT-001,57d988a,pass,"Logistical Introduction docs/LLMS UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-044,Documentation,Router Docs,Router hosted catalog ingestion scope,docs/router/overview.mdx; docs/concepts/venues.mdx; docs/llms-full.txt; core/test/unit/llms-docs.test.js,"As a Router docs reader, I want the catalog ingestion explanation to distinguish hosted catalog venues from all PMXT pass-through targets so that I do not assume Router search indexes every venue client PMXT can instantiate.","Router overview and LLMS full docs say the continuously updated catalog ingests markets, events, and outcomes from hosted catalog venues rather than every venue PMXT supports.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/llms-docs.test.js; npm run docs:llms; rg -n 'ingests markets, events, and outcomes from every venue PMXT supports|ingests markets, events, and outcomes from the hosted catalog venues|hosted catalog currently ingests' docs/router/overview.mdx docs/concepts/venues.mdx docs/llms-full.txt core/test/unit/llms-docs.test.js; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED LLMS docs test caught docs/router/overview.mdx and docs/llms-full.txt claiming the hosted Router catalog ingests from every venue PMXT supports, contradicting the Supported Venues hosted catalog list. After 3fedf6c, Router overview and LLMS full docs scope ingestion to hosted catalog venues, stale overclaim scans returned no source/artifact hits, focused LLMS test passed, core TypeScript compile passed, diff check passed, and full core Jest passed with 778 tests and 3 skipped.",DOC-ROUTER-CATALOG-SCOPE-001,3fedf6c,pass,"Logistical Router docs/LLMS UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-045,Documentation,Router and Quickstart Docs,Router search hosted catalog scope,docs/introduction.mdx; docs/quickstart.mdx; docs/router/overview.mdx; docs/router/search.mdx; docs/llms.txt; docs/llms-full.txt; core/test/unit/llms-docs.test.js,"As a Router search docs reader, I want search examples and page summaries to say Router searches the hosted catalog rather than every PMXT pass-through venue so that I understand why Router results may differ from the full venue API surface.","Introduction, Quickstart, Router overview, Router search, LLMS compact index, and LLMS full docs describe Router search as hosted-catalog or catalog-venue search rather than every-venue search, while full venue API wording remains reserved for pass-through methods.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/llms-docs.test.js; npm run docs:llms; rg -n 'Search every venue at once|unified view of every prediction market|One query fans out across every venue|Search events and markets across every venue in a single query|Search markets and events across every venue in a single query|across every venue PMXT ingests|Search catalog venues at once|across the hosted catalog|Hosted catalog search' docs/introduction.mdx docs/quickstart.mdx docs/router/overview.mdx docs/router/search.mdx docs/llms.txt docs/llms-full.txt core/test/unit/llms-docs.test.js; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED LLMS docs test caught Router, Quickstart, and Introduction copy still saying Router searches every venue or every prediction market despite Router search being backed by the hosted catalog. After a47eb6c, source docs and LLMS outputs say Router searches catalog venues or the hosted catalog, stale over-scope scans returned no source/artifact hits for the old phrases, focused LLMS test passed, core TypeScript compile passed, diff check passed, and full core Jest passed with 778 tests and 3 skipped.",DOC-ROUTER-SEARCH-HOSTED-CATALOG-SCOPE-001,a47eb6c,pass,"Logistical Router and Quickstart docs UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-046,Documentation,Router Price Docs,Router price comparison hosted catalog scope,docs/router/overview.mdx; docs/router/prices.mdx; docs/llms-full.txt; core/test/unit/llms-docs.test.js,"As a Router price-comparison docs reader, I want compareMarketPrices copy to say it compares identity matches in the hosted catalog rather than the same market on every venue so that I do not assume the helper covers all PMXT pass-through venues.","Router overview, Router prices, and LLMS full docs describe compareMarketPrices as side-by-side bid/ask for identity matches in the hosted catalog. They no longer claim that Router price comparison returns the same market on every venue.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/llms-docs.test.js; npm run docs:llms; rg -n 'Side-by-side bid/ask for the same market on every venue|Side-by-side bid/ask for identity matches in the hosted catalog|same market on every venue' docs/router/overview.mdx docs/router/prices.mdx docs/llms-full.txt core/test/unit/llms-docs.test.js; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED LLMS docs test caught docs/router/overview.mdx, docs/router/prices.mdx, and docs/llms-full.txt still saying Router price comparison shows the same market on every venue despite compareMarketPrices being a Router catalog helper over identity matches. After cbba273, source docs and LLMS full docs say identity matches in the hosted catalog, the stale phrase scan only found the old text in the negative regression assertion, focused LLMS test passed, core TypeScript compile passed, diff check passed, and full core Jest passed with 778 tests and 3 skipped.",DOC-ROUTER-PRICE-HOSTED-CATALOG-SCOPE-001,cbba273,pass,"Logistical Router price docs UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-047,Documentation,Top-Level Docs and OpenAPI,Top-level PMXT tagline support scope,docs/introduction.mdx; scripts/generate-llms.js; docs/llms.txt; docs/llms-full.txt; core/scripts/generate-openapi.js; docs/api-reference/openapi.json; core/test/unit/llms-docs.test.js; core/test/unit/openapi-code-samples.test.js,"As a docs or OpenAPI reader, I want PMXT's top-level tagline to describe supported prediction markets and support-scoped hosted trading so that I do not assume PMXT covers every prediction market globally or that every venue supports writes.","Introduction frontmatter, LLMS compact/full headers, and hosted OpenAPI metadata say PMXT supports supported prediction markets, hosted catalog search, and venue-native trading where venues expose writes. Generated artifacts no longer claim one API for every prediction market or the complete venue surface from reads to trades.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/llms-docs.test.js core/test/unit/openapi-code-samples.test.js; npm run generate:openapi --workspace=pmxt-core; npm run docs:llms; rg -n 'One API for every prediction market|complete venue surface|One API for supported prediction markets|venue-native trading where venues expose writes|Trading where venues expose writes' docs core/scripts/generate-openapi.js scripts/generate-llms.js core/test/unit/llms-docs.test.js core/test/unit/openapi-code-samples.test.js; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED LLMS/OpenAPI tests caught Introduction, LLMS headers, and hosted OpenAPI metadata still saying one API for every prediction market and describing a complete venue surface from reads to trades. After 57d541f, source generators and generated artifacts use supported-prediction-market, hosted-catalog-search, and venue-native-trading-where-supported wording; stale scans found old claims only in negative assertions; focused LLMS/OpenAPI tests passed with 14 tests; core TypeScript compile passed; diff check passed; and full core Jest passed with 779 tests and 3 skipped.",DOC-TOP-LEVEL-TAGLINE-SUPPORT-SCOPE-001,57d541f,pass,"Logistical top-level docs/OpenAPI UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-048,Documentation,Introduction and LLMS Docs,Introduction venue method support scope,docs/introduction.mdx; docs/llms-full.txt; core/test/unit/llms-docs.test.js,"As an Introduction reader, I want the unified venue interface section to explain that method names and response shapes are unified while method support varies by venue so that I do not assume create_order or fetch_positions work on every PMXT venue.","Introduction and LLMS full docs say method names and response shapes are unified with support varying by venue, and that fetch_markets, create_order, and fetch_positions use the unified schema where the venue implements them. The data-pipeline comparison now says supported venues rather than every venue.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/llms-docs.test.js; npm run docs:llms; rg -n 'Same methods, same response shape, every venue|create_order`, `fetch_positions` work identically whether|open, resolve, and re-price across every venue|support varying by venue|where the venue implements them|across supported venues' docs/introduction.mdx docs/llms-full.txt core/test/unit/llms-docs.test.js; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED LLMS docs test caught the Introduction and LLMS full docs claiming every venue has the same methods and that create_order/fetch_positions work identically across Polymarket or Kalshi, plus every-venue data-pipeline wording. After 4b1452e, source and LLMS docs scope method support to venues that implement each method and say supported venues for data-pipeline freshness; stale scans found old claims only in negative assertions; focused LLMS test passed; core TypeScript compile passed; diff check passed; and full core Jest passed with 779 tests and 3 skipped.",DOC-INTRO-VENUE-METHOD-SUPPORT-SCOPE-001,4b1452e,pass,"Logistical Introduction docs/LLMS UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-049,Documentation,Quickstart and LLMS Docs,Quickstart hosted catalog and pass-through method support scope,docs/quickstart.mdx; docs/llms-full.txt; core/test/unit/llms-docs.test.js,"As a Quickstart reader, I want Router search and Full venue API cards to distinguish hosted catalog venues from the broader pass-through surface and explain that pass-through methods are available where each venue implements them so that I do not assume Router searches everything or every venue supports order books, OHLCV, account methods, and trading.","Quickstart and LLMS full docs say Router rows come from hosted catalog venues, omit the venue filter to search the hosted catalog, and describe the Full venue API methods as supported where each venue implements them via POST /api/:exchange/:method.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/llms-docs.test.js; npm run docs:llms; rg -n 'Polymarket, Kalshi, Limitless, or anywhere else|search everything|Order books, trades, OHLCV, positions, balances, and trading — all via `POST /api/:exchange/:method`|another hosted catalog venue|search the hosted catalog|supported where each venue implements them' docs/quickstart.mdx docs/llms-full.txt core/test/unit/llms-docs.test.js; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED LLMS docs test caught Quickstart and LLMS full docs saying Router rows may come from anywhere else, instructing users to search everything, and implying order books, trades, OHLCV, positions, balances, and trading are all available via the pass-through route. After 2f62c42, source and LLMS full docs scope Router results to hosted catalog venues, say to omit the venue filter to search the hosted catalog, and describe pass-through methods as supported where each venue implements them; stale scans found old claims only in negative assertions; focused LLMS test passed; core TypeScript compile passed; diff check passed; and full core Jest passed with 779 tests and 3 skipped.",DOC-QUICKSTART-CATALOG-METHOD-SUPPORT-SCOPE-001,2f62c42,pass,"Logistical Quickstart docs/LLMS UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-050,Documentation,Quickstart and LLMS Docs,Quickstart venue method support wording,docs/quickstart.mdx; docs/llms-full.txt; core/test/unit/llms-docs.test.js,"As a Quickstart reader, I want the Query a venue section to say PMXT shares method names and response shapes where each venue supports the method so that I do not assume every venue class has identical capabilities.","Quickstart and LLMS full docs say the SDK has unified method names and response shapes where the venue supports them, and that per-venue capabilities are documented on Supported venues. They no longer say methods and response shapes are identical regardless of venue.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/llms-docs.test.js; npm run docs:llms; rg -n 'interface — same methods, same response shape, regardless of which venue|The methods and response shapes are identical|same method names and response shapes where the venue|per-venue capabilities|PMXT keeps the schema consistent' docs/quickstart.mdx docs/llms-full.txt core/test/unit/llms-docs.test.js; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED LLMS docs test caught Quickstart still saying the SDK has the same methods and response shape regardless of venue and that methods/response shapes are identical after switching venue classes. After ee3267c, source and LLMS full docs say the schema is consistent where venues support the method and link readers to per-venue capabilities; stale scans found old claims only in negative assertions; focused LLMS test passed; core TypeScript compile passed; diff check passed; and full core Jest passed with 779 tests and 3 skipped.",DOC-QUICKSTART-VENUE-METHOD-SUPPORT-SCOPE-001,ee3267c,pass,"Logistical Quickstart docs/LLMS UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-051,Documentation,Introduction and LLMS Docs,Introduction top-level venue support wording,docs/introduction.mdx; docs/llms-full.txt; core/test/unit/llms-docs.test.js,"As an Introduction reader, I want the lead and venue-swap copy to say PMXT shares SDK method names and response shapes where each venue supports or implements the capability so that I do not assume every supported venue has identical methods.","Introduction and LLMS full docs describe PMXT as supporting supported prediction-market venues, say shared SDK method names and unified response shapes apply where each venue supports the capability, and say swapped venue classes use the same method names and response shapes where that venue implements the capability.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/llms-docs.test.js; npm run docs:llms; rg -n 'Same\s+SDK methods, same response shape, regardless of which venue|methods and response shapes stay the same|shared SDK method names and unified response shapes|where that venue implements the\s+capability|supported prediction-market venues' docs/introduction.mdx docs/llms-full.txt core/test/unit/llms-docs.test.js; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED LLMS docs test caught Introduction and LLMS full docs saying PMXT has the same SDK methods and response shape regardless of venue and that swapping venue classes keeps methods and response shapes the same. After f0448a1, source and LLMS docs scope PMXT to supported prediction-market venues and say shared method names and response shapes apply where each venue supports or implements the capability; stale scans found old claims only in negative assertions; focused LLMS test passed; core TypeScript compile passed; diff check passed; token scan found no API key or secret hits in touched files; and full core Jest passed with 779 tests and 3 skipped.",DOC-INTRO-TOP-LEVEL-VENUE-SUPPORT-SCOPE-001,f0448a1,pass,"Logistical Introduction docs/LLMS UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-052,Documentation,Prediction Markets 101 and LLMS Docs,Group A hosted venue support wording,docs/concepts/prediction-markets-101.mdx; docs/llms-full.txt; core/test/unit/llms-docs.test.js,"As a Prediction Markets 101 reader, I want Group A methods to be described as a shared method surface where venues implement the capability so that I do not assume create_order, balances, positions, and trade history work identically across every hosted venue.","Prediction Markets 101 and LLMS full docs say Group A is the shared trading and account method surface for venues that implement those capabilities, method names and response schemas are unified where supported, and hosted write support is venue-specific with links to hosted trading, supported venues, and API reference support details.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/llms-docs.test.js; npm run docs:llms; rg -n 'venue-agnostic trading and read methods that work identically across every hosted venue|The unified surface that makes PMXT a single SDK across venues|shared trading and account method surface for venues that implement those capabilities|hosted write support is venue-specific' docs/concepts/prediction-markets-101.mdx docs/llms-full.txt core/test/unit/llms-docs.test.js; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED LLMS docs test caught Prediction Markets 101 and LLMS full docs saying Group A methods work identically across every hosted venue and form a single SDK surface across venues. After 11de9b7, source and LLMS docs scope Group A to venues that implement the trading/account capabilities, state that hosted write support is venue-specific, and link to current support details; stale scans found old claims only in negative assertions; focused LLMS test passed; core TypeScript compile passed; diff check passed; token scan found no API key or secret hits in touched files; and full core Jest passed with 779 tests and 3 skipped.",DOC-GROUP-A-HOSTED-VENUE-SUPPORT-SCOPE-001,11de9b7,pass,"Logistical Prediction Markets 101 docs/LLMS UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-053,Documentation,Root README,README hosted trading support scope,readme.md; core/test/unit/docs-copy-paste-samples.test.js,"As a README reader, I want hosted trading copy to list the venues with hosted writes today and point Kalshi-style venue-native writes to self-hosted mode so that I do not assume one PMXT API key can place orders on every listed trading venue.","The root README headline and Why pmxt trading bullet say hosted writes cover Polymarket, Opinion, and Limitless today, and say to self-host for venue-native writes such as Kalshi where supported. The README no longer says one API key can trade Polymarket, Kalshi, Opinion, and more or that orders can be placed across Polymarket, Kalshi, and Limitless with one interface.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; rg -n 'trade Polymarket, Kalshi, Opinion, and more from one API key|Place orders across Polymarket, Kalshi, and Limitless with a single interface|Polymarket, Opinion, and Limitless writes today|self-host for venue-native writes such as Kalshi where supported' readme.md core/test/unit/docs-copy-paste-samples.test.js; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED docs-copy-paste regression caught the root README claiming one PMXT API key can trade Polymarket, Kalshi, Opinion, and more and that users can place orders across Polymarket, Kalshi, and Limitless with one interface. After 8b0b93b, the README scopes hosted writes to Polymarket, Opinion, and Limitless today and points Kalshi-style venue-native writes to self-hosting where supported; stale scans found old claims only in negative assertions; focused docs-copy-paste test passed with 21 tests; core TypeScript compile passed; diff check passed; token scan found no API key or secret hits in touched files; and full core Jest passed with 780 tests and 3 skipped.",DOC-README-HOSTED-TRADING-SUPPORT-SCOPE-001,8b0b93b,pass,"Logistical README docs UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-054,Documentation,Root README,README Trading section support scope,readme.md; core/test/unit/docs-copy-paste-samples.test.js,"As a README reader, I want the Trading section to say unified trading is available where venues expose writes and to explain when self-hosting is needed so that I do not assume hosted mode is the default path for every exchange write API.","The root README Trading section says pmxt supports unified trading where venues expose writes, hosted trading is default for supported hosted venues, and self-hosting is for raw venue credentials or another venue's write API. It no longer says pmxt supports unified trading across exchanges with hosted API as the default.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; rg -n 'pmxt supports unified trading across exchanges. The hosted API is the default|pmxt supports unified trading where venues expose writes|self-host when you need raw venue credentials' readme.md core/test/unit/docs-copy-paste-samples.test.js; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED docs-copy-paste regression caught the root README Trading section still saying pmxt supports unified trading across exchanges and that the hosted API is the default. After 89fa721, the Trading section scopes unified trading to venues that expose writes, says hosted trading is default only for supported hosted venues, and tells readers to self-host when they need raw venue credentials or another venue's write API; stale scans found old claims only in negative assertions; focused docs-copy-paste test passed with 21 tests; core TypeScript compile passed; diff check passed; token scan found no API key or secret hits in touched files; and full core Jest passed with 780 tests and 3 skipped.",DOC-README-TRADING-SECTION-SUPPORT-SCOPE-001,89fa721,pass,"Logistical README Trading section UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-055,Documentation,Rate Limits and LLMS Docs,Rate limits pass-through support scope,docs/rate-limits.mdx; docs/llms-full.txt; core/test/unit/llms-docs.test.js,"As a Rate Limits reader, I want the API-key surface summary to say venue pass-through is supported rather than complete so that I do not assume every plan or venue exposes every pass-through method.","Rate Limits and LLMS full docs say every API key includes cross-venue search, unified schema, and the supported venue pass-through. They no longer describe the venue pass-through surface as complete.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/llms-docs.test.js; npm run docs:llms; rg -n 'complete venue pass-through|supported venue pass-through' docs/rate-limits.mdx docs/llms-full.txt core/test/unit/llms-docs.test.js; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED LLMS docs test caught Rate Limits and LLMS full docs saying every API key includes the complete venue pass-through. After d4a5170, source and LLMS docs say supported venue pass-through; stale scans found the old phrase only in the negative assertion; focused LLMS test passed; core TypeScript compile passed; diff check passed; token scan found no API key or secret hits in touched files; and full core Jest passed with 780 tests and 3 skipped.",DOC-RATE-LIMITS-PASS-THROUGH-SUPPORT-SCOPE-001,d4a5170,pass,"Logistical Rate Limits docs/LLMS UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-056,Documentation,Hosted trading and LLMS Docs,Hosted trading identifier guidance scope,docs/concepts/hosted-trading.mdx; docs/guides/migrate-to-hosted-trading.mdx; docs/llms-full.txt; core/test/unit/llms-docs.test.js,"As a hosted trading docs reader, I want catalog UUID and venue-native identifier guidance to match SDK wire behavior so that I know when to pass UUIDs versus venue_outcome_id.","Hosted trading, migration, and LLMS full docs say catalog UUIDs are portable identifiers, the SDK accepts outcomes from venue clients or Router, and raw REST must use catalog UUIDs or an explicit venue + venue_outcome_id pair rather than bare conditionId/tokenId strings.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/llms-docs.test.js; npm run docs:llms; rg -n 'Every hosted endpoint speaks|none of those work directly against `trade\.pmxt\.dev`|requires \*\*catalog UUIDs\*\*|Catalog UUIDs replace conditionId|Catalog UUIDs are the shared address space|Raw REST can use catalog UUIDs or an explicit `venue` \+ `venue_outcome_id` pair' docs/concepts docs/guides docs/llms-full.txt core/test/unit/llms-docs.test.js; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED LLMS docs test caught Hosted Trading and migration docs saying hosted endpoints speak only catalog UUIDs and that trade.pmxt.dev requires catalog UUIDs rather than Polymarket conditionId/tokenId. After b166568, the source and LLMS docs describe catalog UUIDs as portable identifiers, explain the venue + venue_outcome_id wire shape for venue-native outcomes, and warn that bare Polymarket conditionId/tokenId strings lack enough context; stale scans found old claims only in negative assertions; focused LLMS test passed; core TypeScript compile passed; diff check passed; token scan found no API key or secret hits in touched files; and full core Jest passed with 780 tests and 3 skipped.",DOC-HOSTED-IDENTIFIER-GUIDANCE-SCOPE-001,b166568,pass,"Logistical hosted trading identifier docs/LLMS UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-057,Documentation,Security and Error Docs,Hosted identifier security/error scope,docs/security.mdx; docs/api-reference/errors.mdx; docs/llms-full.txt; core/test/unit/llms-docs.test.js,"As a hosted trading reader, I want security and error-reference docs to describe the outcome target generically so that I do not assume hosted build-order only sends catalog UUIDs or that OutcomeNotFound only means a venue-native ID was used where a UUID was required.","Security, Error Reference, and LLMS full docs say PMXT receives an outcome target, wallet address, and signature; build-order targets are either catalog UUIDs or venue + venue_outcome_id pairs; and OutcomeNotFound means the backend could not resolve either supported identifier path.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/llms-docs.test.js; npm run docs:llms; rg -n 'Catalog UUIDs, signatures, public wallet address|with catalog UUIDs and parameters|server receives on the wire: catalog UUIDs|venue-native ID\*\* to a hosted endpoint that expects a \*\*catalog UUID|Outcome target, signatures, public wallet address|the backend could not resolve either a catalog UUID or a `venue` \+ `venue_outcome_id` pair' docs/security.mdx docs/api-reference/errors.mdx docs/llms-full.txt core/test/unit/llms-docs.test.js; npx tsc --project core/tsconfig.json --noEmit; git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED LLMS docs test caught Security and Error Reference docs saying PMXT receives catalog UUIDs, hosted build-order sends catalog UUIDs and parameters, and OutcomeNotFound usually means a venue-native ID was sent to an endpoint expecting a catalog UUID. After b765180, source and LLMS docs describe the generic outcome target, catalog UUID or venue + venue_outcome_id request shapes, and resolver failure across either identifier path; stale scans found old claims only in negative assertions; focused LLMS test passed; core TypeScript compile passed; diff check passed; token scan found no API key or secret hits in touched files; and full core Jest passed with 780 tests and 3 skipped.",DOC-HOSTED-IDENTIFIER-SECURITY-ERROR-SCOPE-001,b765180,pass,"Logistical hosted security/error docs and LLMS UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-058,Documentation,Router and LLMS Docs,Router compose identifier scope,docs/introduction.mdx; docs/router/overview.mdx; docs/router/prices.mdx; docs/llms-full.txt; core/test/unit/llms-docs.test.js,"As a Router docs reader, I want compose-with-venues examples to distinguish catalog IDs from venue-native IDs so that I do not pass Router catalog IDs directly into direct self-hosted venue calls.","Introduction, Router overview, Router prices, and LLMS full docs say Router/catalog IDs work for Router and hosted flows, while direct self-hosted venue calls need venue-native IDs returned by that venue client. The compose example no longer passes a Router cluster outcome directly into a local Polymarket order-book call or says marketId works everywhere.",fixed_retest_pass,2026-06-23,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/llms-docs.test.js; npm run docs:llms; rg -n 'same `marketId`\.|same schema — `marketId` works everywhere|so `marketId`, `outcomes`, and all other fields work interchangeably|pass a `marketId` from the Router straight into|catalog IDs for Router and hosted flows|venue-native IDs for direct self-hosted writes|identifiers keep their address space' docs/introduction.mdx docs/router/overview.mdx docs/router/prices.mdx docs/llms-full.txt core/test/unit/llms-docs.test.js; npx tsc --project core/tsconfig.json --noEmit; /Library/Developer/CommandLineTools/usr/bin/git diff --check; npm test --workspace=pmxt-core -- --runInBand","RED LLMS docs test caught Router compose copy saying the same marketId works everywhere and that Router marketId/outcomes are interchangeable with venue exchanges. After c04d581, Introduction, Router overview, Router prices, and LLMS docs scope IDs to their address spaces, and the compose example re-fetches or reverse-resolves the matched venue market before using a venue-native outcome ID for direct self-hosted order-book calls; stale scans found old claims only in negative assertions; focused LLMS test passed; core TypeScript compile passed; diff check passed via Command Line Tools git because /usr/bin/git was blocked by an Xcode license prompt; token scan found no API key or secret hits in touched files; and full core Jest passed with 780 tests and 3 skipped.",DOC-ROUTER-COMPOSE-IDENTIFIER-SCOPE-001,c04d581,pass,"Logistical Router compose docs/LLMS UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-059,Documentation,Introduction and LLMS Docs,Local and hosted SDK mode scope,docs/introduction.mdx; docs/llms-full.txt; core/test/unit/llms-docs.test.js,"As an Introduction reader, I want local and hosted SDK examples to say the call shape is shared while runtime target, credentials, and write support vary so that I do not assume hosted and self-hosted mode behave identically.","Introduction and LLMS full docs say the SDK call shape is shared but the runtime target changes, hosted mode uses a PMXT API key and hosted services, self-hosted mode talks to local pmxt-core with venue-native credentials where needed, and the Same SDK card says credentials and supported writes vary by mode.",fixed_retest_pass,2026-06-24,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/llms-docs.test.js; npm run docs:llms; rg -n 'The SDK call shape is shared, but the runtime target changes|Credentials and supported writes vary by mode|The code is identical either way|SDKs work identically' docs/introduction.mdx docs/llms-full.txt core/test/unit/llms-docs.test.js; npx tsc --project core/tsconfig.json --noEmit; /Library/Developer/CommandLineTools/usr/bin/git diff --check; rg -n 'pmxt_live_[A-Za-z0-9_-]+|sk-[A-Za-z0-9]{20,}|api[_-]?key\s*[:=]\s*[""'][A-Za-z0-9_-]{20,}' docs/introduction.mdx docs/llms-full.txt core/test/unit/llms-docs.test.js; npm test --workspace=pmxt-core -- --runInBand","RED LLMS docs test caught Introduction and LLMS full docs saying the code is identical either way and the SDKs work identically against localhost or the hosted API. After 80e5676, source and LLMS docs say the SDK call shape is shared but the runtime target changes, and the Same SDK card says credentials and supported writes vary by mode; stale scans found old claims only in negative assertions; focused LLMS test passed; core TypeScript compile passed; diff check passed; token scan found no API key or secret hits in touched files; and full core Jest passed outside the sandbox with 782 tests and 3 skipped.",DOC-LOCAL-HOSTED-SDK-SCOPE-001,80e5676,pass,"Logistical Introduction docs/LLMS UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required. The sandboxed full core suite run hit loopback socket restrictions in the existing pmxt-ensure-server test, then the same suite passed outside the sandbox."
DOC-060,Documentation,Hosted Trading and LLMS Docs,Hosted/self-hosted SDK surface scope,docs/concepts/hosted-trading.mdx; docs/llms-full.txt; core/test/unit/llms-docs.test.js,"As a Hosted Trading reader, I want the self-hosted comparison to say SDK class and method naming is shared only where capabilities are supported so that I do not assume hosted and self-hosted expose the exact same write surface.","Hosted Trading and LLMS full docs say both modes use the same SDK classes and method names where the capability is supported, and that differences include execution location, key custody, and which write venues each mode supports. They no longer say both modes expose the same SDK surface with only execution/key-holder differences.",fixed_retest_pass,2026-06-24,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/llms-docs.test.js; npm run docs:llms; rg -n 'Both modes expose the same SDK surface|Both modes use the same SDK classes and method names where the capability|which write venues each mode supports' docs/concepts/hosted-trading.mdx docs/llms-full.txt core/test/unit/llms-docs.test.js; npx tsc --project core/tsconfig.json --noEmit; /Library/Developer/CommandLineTools/usr/bin/git diff --check; rg -n 'pmxt_live_[A-Za-z0-9_-]+|sk-[A-Za-z0-9]{20,}|api[_-]?key\s*[:=]\s*[""'][A-Za-z0-9_-]{20,}' docs/concepts/hosted-trading.mdx docs/llms-full.txt core/test/unit/llms-docs.test.js; npm test --workspace=pmxt-core -- --runInBand","RED LLMS docs test caught Hosted Trading and LLMS full docs saying both modes expose the same SDK surface and differ only by execution location and who holds keys. After 9650a0c, source and LLMS docs scope the shared SDK surface to supported capabilities and call out write-venue support differences; stale scans found the old claim only in the negative assertion; focused LLMS test passed; core TypeScript compile passed; diff check passed; token scan found no API key or secret hits in touched files; and full core Jest passed outside the sandbox with 782 tests and 3 skipped.",DOC-HOSTED-SDK-SURFACE-SCOPE-001,9650a0c,pass,"Logistical Hosted Trading docs/LLMS UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-061,Documentation,Hosted Trading and Escrow Lifecycle Docs,Hosted funding current-venue scope,docs/concepts/hosted-trading.mdx; docs/guides/escrow-lifecycle.mdx; docs/llms-full.txt; core/test/unit/llms-docs.test.js,"As a hosted funding docs reader, I want Polygon funding and key-reuse copy to name the currently hosted venues so that I do not assume future or every hosted venue will automatically use the same escrow, chain, or key model.","Hosted Trading, Escrow Lifecycle, and LLMS full docs say Polygon PreFundedEscrow funding applies to the currently hosted trading venues Polymarket, Opinion, and Limitless; the same EVM wallet/key can trade those currently hosted venues; and the Polygon escrow serves the payment legs for Polymarket, Opinion, and Limitless. They no longer promise future venues, every hosted venue, every supported venue, or every venue payment leg.",fixed_retest_pass,2026-06-24,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/llms-docs.test.js; npm run docs:llms; rg -n -e 'future venues' -e 'more coming' -e 'same key handles every venue' -e 'single funding location for \*every\* hosted venue' -e 'single Polygon-based `PreFundedEscrow` contract for every supported venue' -e 'serves every venue' -e 'same EVM wallet/key' -e 'currently hosted trading venues' -e 'serves the payment legs for Polymarket, Opinion, and Limitless' docs/concepts/hosted-trading.mdx docs/guides/escrow-lifecycle.mdx docs/llms-full.txt core/test/unit/llms-docs.test.js; npx tsc --project core/tsconfig.json --noEmit; /Library/Developer/CommandLineTools/usr/bin/git diff --check; rg -n 'pmxt_live_[A-Za-z0-9_-]+|sk-[A-Za-z0-9]{20,}|api[_-]?key\s*[:=]\s*[""'][A-Za-z0-9_-]{20,}' docs/concepts/hosted-trading.mdx docs/guides/escrow-lifecycle.mdx docs/llms-full.txt core/test/unit/llms-docs.test.js; npm test --workspace=pmxt-core -- --runInBand","RED LLMS docs test caught Hosted Trading and Escrow Lifecycle docs saying hosted trading uses one Polygon PreFundedEscrow for every supported venue, same wallet/key trades future venues, Polygon escrow is the single funding location for every hosted venue with more coming, the same key handles every venue, and the Polygon escrow serves every venue's payment leg. After 28a8092, source and LLMS docs scope funding, key reuse, and payment-leg copy to Polymarket, Opinion, and Limitless as the currently hosted trading venues; stale scans found old claims only in negative assertions; focused LLMS test passed; core TypeScript compile passed; diff check passed; token scan found no API key or secret hits in touched files; and full core Jest passed outside the sandbox with 782 tests and 3 skipped.",DOC-HOSTED-FUNDING-CURRENT-VENUE-SCOPE-001,28a8092,pass,"Logistical hosted funding docs/LLMS UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-062,Documentation,Hosted OpenAPI and LLMS Docs,Hosted OpenAPI funding current-venue scope,docs/api-reference/openapi-hosted-trading.json; docs/llms-full.txt; core/test/unit/hosted-openapi-code-samples.test.js,"As a hosted OpenAPI docs reader, I want hosted funding callouts, examples, and balance schema descriptions to name the currently hosted venues so that I do not assume future or every hosted venue will automatically use the same Polygon escrow model.","Hosted OpenAPI and LLMS full docs say current hosted venues are funded once on Polygon, the PreFundedEscrow funding copy applies to Polymarket, Opinion, and Limitless, and the hosted balance amount backs trading on Polymarket, Opinion, and Limitless. They no longer say all hosted venues are funded once on Polygon, the escrow is the single funding location for every hosted venue, or balance backs trading across every hosted venue.",fixed_retest_pass,2026-06-24,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/hosted-openapi-code-samples.test.js; npm run docs:llms; npm test --workspace=pmxt-core -- --runInBand core/test/unit/hosted-openapi-code-samples.test.js core/test/unit/llms-docs.test.js; rg -n 'All hosted venues are funded once on Polygon|single funding location for every hosted venue|Backs trading across every hosted venue|Current hosted venues are funded once on Polygon|Backs trading on Polymarket, Opinion, and Limitless' docs/api-reference/openapi-hosted-trading.json docs/llms-full.txt core/test/unit/hosted-openapi-code-samples.test.js; npx tsc --project core/tsconfig.json --noEmit; /Library/Developer/CommandLineTools/usr/bin/git diff --check; rg -n 'pmxt_live_[A-Za-z0-9_-]+|sk-[A-Za-z0-9]{20,}|api[_-]?key\s*[:=]\s*[""'][A-Za-z0-9_-]{20,}' docs/api-reference/openapi-hosted-trading.json docs/llms-full.txt core/test/unit/hosted-openapi-code-samples.test.js; npm test --workspace=pmxt-core -- --runInBand","RED hosted OpenAPI test failed before the spec patch because current hosted trading OpenAPI examples said all hosted venues are funded once on Polygon, Mintlify callouts said the Polygon PreFundedEscrow was the single funding location for every hosted venue, and BalanceV0.amount said it backed trading across every hosted venue. After ef2f9a1, hosted OpenAPI, LLMS full output, and the regression scope funding copy to current hosted venues and to Polymarket, Opinion, and Limitless; stale scans found old claims only in negative assertions; focused hosted OpenAPI and LLMS tests passed; core TypeScript compile passed; diff check passed; token scan found no API key or secret hits in touched files; full core Jest first hit the known pmxt-ensure-server full-suite timing flake, the launcher test passed in isolation, and the full core suite then passed with 783 tests and 3 skipped.",DOC-HOSTED-OPENAPI-FUNDING-CURRENT-VENUE-SCOPE-001,ef2f9a1,pass,"Logistical hosted OpenAPI docs/LLMS UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-063,Documentation,Hosted OpenAPI Docs,Hosted OpenAPI Limitless venue enums,docs/api-reference/openapi-hosted-trading.json; core/test/unit/hosted-openapi-code-samples.test.js,"As a hosted OpenAPI docs reader, I want every hosted venue enum to include Limitless so raw REST and SDK docs do not contradict hosted availability callouts.","Hosted OpenAPI spec includes `limitless` in every venue enum that lists `polymarket` and `opinion`: open orders filter, build-order venue, resolved order venue, user trade venue, position venue, and balance venue. Venue-native identifier descriptions mention Limitless token addresses.",fixed_retest_pass,2026-06-24,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/hosted-openapi-code-samples.test.js; npm run docs:llms; npm test --workspace=pmxt-core -- --runInBand core/test/unit/hosted-openapi-code-samples.test.js core/test/unit/llms-docs.test.js; node -e structural hosted venue enum scan; rg -n 'Polymarket `tokenId`, Opinion outcome hash|Polymarket ERC-1155 `tokenId`, or Opinion outcome hash|Opinion-native integer market id\. `null` for Polymarket orders\.|Limitless token address|""limitless""' docs/api-reference/openapi-hosted-trading.json docs/llms-full.txt core/test/unit/hosted-openapi-code-samples.test.js; npx tsc --project core/tsconfig.json --noEmit; /Library/Developer/CommandLineTools/usr/bin/git diff --check; rg -n 'pmxt_live_[A-Za-z0-9_-]+|sk-[A-Za-z0-9]{20,}|api[_-]?key\s*[:=]\s*[""'][A-Za-z0-9_-]{20,}' docs/api-reference/openapi-hosted-trading.json docs/llms-full.txt core/test/unit/hosted-openapi-code-samples.test.js; npm test --workspace=pmxt-core -- --runInBand","RED hosted OpenAPI test failed before the spec patch because hosted venue enums that already listed polymarket and opinion omitted limitless, despite hosted routing and OpenAPI callouts saying Limitless is a hosted trading venue. After 776a374, all six hosted venue enums include limitless and related venue-native descriptions mention Limitless token addresses; focused hosted OpenAPI and LLMS tests passed; structural enum scan reported 6 hosted venue enums and no missing Limitless; core TypeScript compile passed; diff check passed; token scan found no API key or secret hits in touched files; and full core Jest passed with 784 tests and 3 skipped.",DOC-HOSTED-OPENAPI-LIMITLESS-ENUMS-001,776a374,pass,"Logistical hosted OpenAPI docs UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required. `npm run docs:llms` produced no final LLMS diff for this enum-only spec change."
SDK-006,SDK,TypeScript and Python,Hosted Limitless cancel routing and typed-data schemas,sdks/python/pmxt/client.py; sdks/python/pmxt/_hosted_typeddata.py; sdks/typescript/pmxt/client.ts; sdks/typescript/pmxt/hosted-typed-data.ts; sdks/python/tests/test_hosted_dispatch.py; sdks/python/tests/test_hosted_typeddata.py; sdks/typescript/tests/hosted-typed-data.test.ts,"As a hosted Limitless trader, I want cancelOrder/cancel_order to build, validate, sign, and submit cancel requests like other hosted venues so that I can cancel hosted Limitless orders from either SDK.","Python and TypeScript hosted cancel route helpers resolve Limitless to cancel_limitless_polygon plus cancel_limitless_base_pull; both SDK typed-data validators accept those routes with Polygon PreFundedEscrow primary cancel data and Base VenueEscrow pull-cancel data; Python Limitless.cancel_order dispatches cancel build then cancel with primary and pull signatures when pull_typed_data is returned.",fixed_retest_pass,2026-06-24,"RED/GREEN: python3 -m pytest tests/test_hosted_dispatch.py::TestHostedWriteDispatch::test_limitless_cancel_order_routes_build_then_cancel_with_pull_signature tests/test_hosted_typeddata.py::test_validate_typed_data_accepts_cancel_route_fixtures -q from sdks/python; npm test --workspace=pmxtjs -- --runInBand sdks/typescript/tests/hosted-typed-data.test.ts; python3 -m pytest tests/test_hosted_dispatch.py tests/test_hosted_typeddata.py tests/test_hosted_signers.py tests/test_hosted_routing.py -q from sdks/python; python3 -m pytest tests -q from sdks/python; npm test --workspace=pmxtjs; npx tsc --project sdks/typescript/tsconfig.json --noEmit; npx tsc --project sdks/typescript/tsconfig.esm.json --noEmit; npx tsc --project core/tsconfig.json --noEmit; /Library/Developer/CommandLineTools/usr/bin/git diff --check; rg secret scan; npm test --workspace=pmxt-core -- --runInBand","RED Python tests failed because Limitless.cancel_order raised NotSupported after cancel/build and Python typed-data validation reported unknown cancel_limitless_polygon/cancel_limitless_base_pull routes. RED TypeScript test failed with unknown hosted typed_data route for both Limitless cancel routes. After 8f0112d, both SDK schema maps include the Limitless cancel routes, Python cancel route selection includes Limitless, TypeScript route helpers are typed as HostedRoute, focused RED/GREEN tests passed, full Python unit suite passed with 255 passed and 66 deselected, full TypeScript SDK Jest passed with 67 tests, both TypeScript compile targets passed, core TypeScript compile passed, diff check passed, token scan found no secret hits, and full core Jest passed with 784 tests and 3 skipped.",SDK-HOSTED-LIMITLESS-CANCEL-001,8f0112d,pass,"Logistical hosted SDK UX/parity error fixed; no live venue access, feed access, funds-moving behavior, order placement, or live cancel submission was run. uv runner still has the existing pyproject requires-python/urllib3 resolver conflict, so Python verification used python3 -m pytest."
DOC-064,Documentation,"Hosted OpenAPI, LLMS, and SDK READMEs",Hosted account/current venue scope,docs/api-reference/openapi-hosted-trading.json; docs/llms.txt; docs/llms-full.txt; sdks/typescript/README.md; sdks/python/README.md; core/test/unit/hosted-openapi-code-samples.test.js; core/test/unit/docs-copy-paste-samples.test.js; core/test/unit/llms-docs.test.js,"As a hosted OpenAPI and SDK docs reader, I want account, order creation, open-order filtering, and custody copy to name the current hosted venues so that I do not assume Limitless is unavailable or that hosted account docs are Polymarket/Opinion-only.","Hosted OpenAPI, LLMS, TypeScript README, and Python README say create order, account data, open-order venue filters, trade history, hosted custody, and hosted exchange examples apply to Polymarket, Opinion, and Limitless. Stale Polymarket-and-Opinion-only phrasing remains only in negative regression assertions.",fixed_retest_pass,2026-06-24,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/hosted-openapi-code-samples.test.js core/test/unit/docs-copy-paste-samples.test.js core/test/unit/llms-docs.test.js; npm run docs:llms; npx tsc --project core/tsconfig.json --noEmit; stale hosted venue-scope scan; /Library/Developer/CommandLineTools/usr/bin/git diff --check; changed-file secret scan; npm test --workspace=pmxt-core -- --runInBand","RED focused docs tests failed before the patch because createOrderHosted, hosted positions, hosted trades, open-order venue filter copy, error exchange examples, and SDK README hosted custody copy still described Polymarket and Opinion without Limitless. After 7113bc5, hosted OpenAPI, LLMS, and SDK README copy names Polymarket, Opinion, and Limitless; focused docs tests passed with 28 tests; docs:llms regenerated LLMS outputs; core TypeScript compile passed; stale scans found old wording only in negative assertions; diff check and changed-file secret scan passed; full core Jest first exposed the unrelated Hyperliquid stale test and then passed after 667fd63 with 786 tests and 3 skipped.",DOC-HOSTED-ACCOUNT-CURRENT-VENUE-SCOPE-001,7113bc5,pass,"Logistical hosted docs UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
TEST-002,Testing,Hyperliquid normalizer tests,Hyperliquid unknown-expiry resolutionDate test,core/test/normalizers/exchange-normalizers-3.test.ts; core/src/exchanges/hyperliquid/normalizer.ts; changelog.md,"As a PMXT maintainer, I want Hyperliquid normalizer tests to reflect unknown-expiry behavior so that the full suite verifies the no-mass-close contract introduced for markets without parseable expiry.","Hyperliquid outcome markets with no parseable expiry leave resolutionDate undefined; tests assert undefined rather than epoch fallback; isolated normalizer and full core suites pass.",fixed_retest_pass,2026-06-24,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/normalizers/exchange-normalizers-3.test.ts after 3070e8a failed while expecting epoch; npm test --workspace=pmxt-core -- --runInBand core/test/normalizers/exchange-normalizers-3.test.ts passed after 667fd63; npx tsc --project core/tsconfig.json --noEmit; npm test --workspace=pmxt-core -- --runInBand","Full core and isolated Hyperliquid normalizer suites failed after 3070e8a because the test still expected resolutionDate.getTime() to equal 0 even though the source now intentionally leaves unknown expiry undefined to avoid mass-closing live Hyperliquid markets. After 667fd63, the test name and assertion match the undefined contract; the isolated normalizer suite passed with 136 tests; core TypeScript compile passed; and full core Jest passed with 786 tests and 3 skipped.",TEST-HYPERLIQUID-UNKNOWN-EXPIRY-001,667fd63,pass,"Test maintenance fix only; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-065,Documentation,Generated SDK Artifacts,Generated SDK sidecar API description venue scope,core/scripts/generate-openapi.js; core/src/server/openapi.yaml; core/test/unit/typescript-generated-docs.test.js; sdks/typescript/generated; sdks/python/generated,"As an SDK docs and generated-code reader, I want generated SDK package headers and sidecar OpenAPI descriptions to describe supported prediction markets without stale venue lists so that I do not assume PMXT only supports Polymarket/Kalshi/Limitless or still supports Predict.fun.","Sidecar OpenAPI generator/source and regenerated TypeScript/Python SDK artifacts use the support-scoped description. Stale `Polymarket, Kalshi, Limitless` and `Predict.fun` sidecar description fragments do not appear in the generator, checked-in sidecar spec, or regenerated SDK artifacts.",fixed_retest_pass,2026-06-24,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/typescript-generated-docs.test.js failed before the fix with 746 stale offenders and sourceHasCurrentDescription false; npm run generate:sdk:python --workspace=pmxt-core after cleaning ignored generated output; npm run generate:sdk:typescript --workspace=pmxt-core after cleaning ignored generated output; rg -n 'A unified local sidecar API for prediction markets|Predict\.fun' core/scripts/generate-openapi.js core/src/server/openapi.yaml sdks/typescript/generated sdks/python/generated; npm test --workspace=pmxt-core -- --runInBand core/test/unit/typescript-generated-docs.test.js; npm test --workspace=pmxt-core -- --runInBand core/test/unit/openapi-code-samples.test.js core/test/unit/typescript-generated-docs.test.js; npx tsc --project core/tsconfig.json --noEmit; npx tsc --project sdks/typescript/tsconfig.json --noEmit; npx tsc --project sdks/typescript/generated/tsconfig.json --noEmit; /Library/Developer/CommandLineTools/usr/bin/git diff --check; changed-file token scan; npm test --workspace=pmxt-core -- --runInBand","RED regression found stale sidecar API descriptions in the checked-in sidecar OpenAPI source and existing generated TypeScript/Python SDK artifacts. After c1519c1, generator and sidecar YAML use support-scoped copy; ignored SDK output directories were cleaned and regenerated; stale-description scan returned no hits; focused generated-doc tests passed with 7 tests; focused OpenAPI/generated-doc tests passed with 20 tests; core, SDK, and generated TypeScript compiles passed; diff check and token scan passed; and full core Jest passed with 787 tests and 3 skipped.",DOC-GENERATED-SDK-API-DESCRIPTION-SCOPE-001,c1519c1,pass,"Logistical generated SDK/docs UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-066,Documentation,SDK API Reference,SDK API reference venue scope,scripts/templates/api-reference.typescript.md.hbs; scripts/templates/api-reference.python.md.hbs; sdks/typescript/API_REFERENCE.md; sdks/python/API_REFERENCE.md; core/test/unit/docs-copy-paste-samples.test.js,"As an SDK API reference reader, I want the TypeScript and Python API reference headers to describe supported prediction markets instead of a stale three-venue list so that I do not assume the SDKs only cover Polymarket, Kalshi, and Limitless.","Generated TypeScript and Python API reference templates and checked-in outputs use support-scoped SDK copy with local sidecar and hosted-service scope. The stale `interacting with multiple prediction market exchanges (Polymarket, Kalshi, Limitless)` header remains only in negative regression assertions.",fixed_retest_pass,2026-06-24,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js failed before the fix with staleOffenders and missingCurrentDescriptions for pythonApiReference, pythonApiReferenceTemplate, typescriptApiReference, and typescriptApiReferenceTemplate; node scripts/generate-api-docs.js; npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; rg -n 'interacting with multiple prediction market exchanges \(Polymarket, Kalshi, Limitless\)|A unified TypeScript SDK for supported prediction markets|A unified Python SDK for supported prediction markets' scripts/templates/api-reference.typescript.md.hbs scripts/templates/api-reference.python.md.hbs sdks/typescript/API_REFERENCE.md sdks/python/API_REFERENCE.md core/test/unit/docs-copy-paste-samples.test.js; npx tsc --project core/tsconfig.json --noEmit; /Library/Developer/CommandLineTools/usr/bin/git diff --check; changed-file token scan; npm test --workspace=pmxt-core -- --runInBand","RED regression failed because both checked-in SDK API references and both templates still had the Polymarket/Kalshi/Limitless-only header. After ef018b6, templates and regenerated SDK API references use support-scoped SDK copy; stale scan found the old header only in the negative assertion; focused docs suite passed with 23 tests; core TypeScript compile passed; diff check and token scan passed; full core Jest passed with 788 tests and 3 skipped.",DOC-SDK-API-REFERENCE-VENUE-SCOPE-001,ef018b6,pass,"Logistical generated SDK API reference docs UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-067,Documentation,Core error handling guide,Error handling guide venue scope,core/docs/ERRORS.md; core/test/unit/docs-copy-paste-samples.test.js,"As an error handling guide reader, I want the guide to describe unified errors across supported exchanges and venues so that I do not assume PMXT error semantics only apply to Polymarket, Kalshi, and Limitless.","Core error handling guide uses support-scoped venue copy and no longer says unified error handling applies only across all exchanges `(Polymarket, Kalshi, Limitless)`. The stale phrase remains only in the negative regression assertion.",fixed_retest_pass,2026-06-24,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js failed before the fix with hasStaleThreeVenueScope true and hasSupportedVenueScope false; npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; rg -n 'unified error handling across all exchanges \(Polymarket, Kalshi, Limitless\)|unified error handling across supported exchanges and venues' core/docs/ERRORS.md core/test/unit/docs-copy-paste-samples.test.js; npx tsc --project core/tsconfig.json --noEmit; /Library/Developer/CommandLineTools/usr/bin/git diff --check; changed-file token scan; npm test --workspace=pmxt-core -- --runInBand","RED regression failed because core/docs/ERRORS.md opened with a Polymarket/Kalshi/Limitless-only error handling scope. After d418138, the guide says unified error handling applies across supported exchanges and venues; stale scan found the old phrase only in the negative assertion; focused docs suite passed with 24 tests; core TypeScript compile passed; diff check and token scan passed; full core Jest passed with 789 tests and 3 skipped.",DOC-ERROR-GUIDE-VENUE-SCOPE-001,d418138,pass,"Logistical core docs UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-068,Documentation,DomeAPI migration guide,DomeAPI migration guide current support scope,docs/MIGRATE_FROM_DOMEAPI.md; core/test/unit/docs-copy-paste-samples.test.js,"As a DomeAPI migration guide reader, I want the guide to reflect current PMXT support, replacement surfaces, and capability-scoped method parity so that I do not assume PMXT only covers an old venue subset or lacks feeds and historical order-book support.","DomeAPI migration guide uses past-tense shutdown wording, describes PMXT as a supported venue catalog, maps Binance/Chainlink price feeds to FeedClient/feed endpoints, maps historical order-book snapshots to PMXT Archive where supported plus live watch streaming, and says PMXT uses the same method names where venues implement each capability.",fixed_retest_pass,2026-06-24,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js failed before the fix with staleClaims for shutdown tense, old exchange list, feature-gap intro, feeds unavailable, historical orderbooks live-only, and same-methods-on-all-exchanges copy; npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; rg LLMS inclusion check showed the migration guide is not emitted into docs/llms.txt or docs/llms-full.txt; npx tsc --project core/tsconfig.json --noEmit; /Library/Developer/CommandLineTools/usr/bin/git diff --check; changed-file token scan; npm test --workspace=pmxt-core -- --runInBand","RED regression failed because docs/MIGRATE_FROM_DOMEAPI.md still said DomeAPI is shutting down, listed only Polymarket/Kalshi/Limitless/Probable/Baozi/Myriad, said Binance/Chainlink feeds were unavailable, pointed historical orderbook users only to live watch_order_book, and claimed same methods on all exchanges. After 1a4b5b2, the migration guide uses current shutdown tense, support-catalog venue copy, FeedClient/feed endpoint replacements, PMXT Archive guidance, and capability-scoped method-name wording; focused docs suite passed with 25 tests; core TypeScript compile passed; diff check and token scan passed; full core Jest passed with 790 tests and 3 skipped.",DOC-DOMEAPI-MIGRATION-SUPPORT-SCOPE-001,1a4b5b2,pass,"Logistical migration guide docs UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-069,Documentation,SDK entrypoints,SDK entrypoint docs venue scope and Python example,sdks/typescript/index.ts; sdks/python/pmxt/__init__.py; core/test/unit/docs-copy-paste-samples.test.js,"As an SDK package reader, I want the TypeScript and Python package entrypoints to describe supported prediction markets and show runnable first examples so that I do not assume PMXT is only Kalshi/Polymarket or copy invalid Python await usage.","TypeScript and Python entrypoint comments/docstrings use support-scoped SDK copy with local sidecar and hosted-service scope; the Python docstring fetch_markets example uses the synchronous SDK call without await; stale Kalshi/Polymarket-only wording remains only in negative regression assertions.",fixed_retest_pass,2026-06-24,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js failed before the fix with staleOffenders and missingCurrentClaims for pythonEntrypoint and typescriptEntrypoint; npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; npx tsc --project core/tsconfig.json --noEmit; npx tsc --project sdks/typescript/tsconfig.json --noEmit; python3 -m pytest tests/test_public_exports.py -q from sdks/python; /Library/Developer/CommandLineTools/usr/bin/git diff --check; stale entrypoint scan; changed-file token scan; npm test --workspace=pmxt-core -- --runInBand","RED regression failed because both SDK entrypoints still used Kalshi/Polymarket-only identical-interface copy, and the Python docstring used await on the synchronous fetch_markets SDK method. After bef8af8, both entrypoints use support-scoped local-sidecar/hosted-services copy, the Python example is synchronous, the focused docs suite passed with 26 tests, core and TypeScript SDK compiles passed, Python public export tests passed with 8 tests, diff check and token scan passed, and full core Jest passed with 791 tests and 3 skipped.",DOC-SDK-ENTRYPOINT-SCOPE-001,bef8af8,pass,"Logistical SDK entrypoint docs UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-070,Documentation,Root README,README DomeAPI migration note support scope,readme.md; core/test/unit/docs-copy-paste-samples.test.js,"As a README reader migrating from DomeAPI, I want the migration note to preserve the DomeAPI Polymarket/Kalshi workflow promise while also making PMXT's broader current venue catalog explicit so that I do not assume PMXT is only a two-venue interface.","Root README DomeAPI migration copy says pmxt is a drop-in replacement for DomeAPI's Polymarket/Kalshi workflows and also exposes PMXT's broader supported venue catalog where current capabilities exist. The stale two-venue-only README sentence remains only in the negative regression assertion.",fixed_retest_pass,2026-06-24,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js failed before the README patch with a stale readme claim and missing current readme claims; npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; npx tsc --project core/tsconfig.json --noEmit; /Library/Developer/CommandLineTools/usr/bin/git diff --check; stale README migration note scan; changed-file token scan; npm test --workspace=pmxt-core -- --runInBand","RED regression failed because the root README still said pmxt is a drop-in replacement with a unified interface for Polymarket and Kalshi, despite the DomeAPI migration guide using current support-catalog wording. After f50b58f, the README scopes the DomeAPI replacement claim to Polymarket/Kalshi workflows and names PMXT's broader supported venue catalog; focused docs suite passed with 26 tests; core TypeScript compile passed; diff check and token scan passed; stale scan found the old sentence only in the negative assertion; and full core Jest passed with 791 tests and 3 skipped.",DOC-README-DOMEAPI-SUPPORT-SCOPE-001,f50b58f,pass,"Logistical README migration docs UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-071,Documentation,DomeAPI migration guide,DomeAPI order-book migration historical archive scope,docs/MIGRATE_FROM_DOMEAPI.md; core/test/unit/docs-copy-paste-samples.test.js,"As a DomeAPI migration guide reader using orderbook-history, I want the replacement docs to explain both PMXT live order books and PMXT Archive-backed historical snapshots so that I do not lose historical-order-book functionality during migration.","DomeAPI migration guide order-book section maps historical orderbook snapshots to PMXT Archive-backed fetchOrderBook/fetch_order_book with since/until params where supported, keeps live current-book usage as the no-archive-params path, and the quick reference maps DomeAPI orderbook-history to historical fetchOrderBook/fetch_order_book calls.",fixed_retest_pass,2026-06-24,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js failed before the docs patch with stale and missing-current claims for the order-book migration note and quick reference row; npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; npx tsc --project core/tsconfig.json --noEmit; /Library/Developer/CommandLineTools/usr/bin/git diff --check; stale order-book migration scan; changed-file token scan; npm test --workspace=pmxt-core -- --runInBand","RED regression failed because the migration guide still said DomeAPI historical orderbook snapshots map only to the current live PMXT order book, and the quick reference mapped orderbook-history to live fetchOrderBook/fetch_order_book calls without archive params. After e3bed37, the guide describes PMXT Archive-backed historical params where supported, keeps the live-order-book call path, includes TypeScript and Python historical examples, narrows the TypeScript union result before reading length, and updates the quick reference; focused docs suite passed with 26 tests; core TypeScript compile passed; diff check and token scan passed; stale scan found old claims only in negative assertions; and full core Jest passed with 791 tests and 3 skipped.",DOC-DOMEAPI-ORDERBOOK-HISTORY-SCOPE-001,e3bed37,pass,"Logistical migration guide docs UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-072,Documentation,Unified schema docs,Unified schema source-aware identifier semantics,docs/concepts/unified-schema.mdx; docs/llms-full.txt; core/test/unit/docs-copy-paste-samples.test.js,"As a PMXT docs reader using Router, hosted catalog, and venue-client responses, I want Unified Schema identifier fields to explain source-aware ID semantics so that I do not assume every marketId/outcomeId is a catalog UUID or every outcomeId is venue-native.","Unified Schema docs and LLMS output say marketId/outcomeId semantics are source-aware: Router and hosted catalog rows use stable PMXT UUIDs, while venue clients and local pass-throughs may use venue-native identifiers. The stale table rows claiming marketId is always a stable PMXT UUID and outcomeId is always venue-native remain only in negative regression assertions.",fixed_retest_pass,2026-06-24,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js failed before the docs patch with stale Unified Schema identifier rows and missing source-aware claims; npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; npm run docs:llms; npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js core/test/unit/llms-docs.test.js; npx tsc --project core/tsconfig.json --noEmit; /Library/Developer/CommandLineTools/usr/bin/git diff --check; unified-schema stale/current scan; changed-file token scan; npm test --workspace=pmxt-core -- --runInBand","RED regression failed because docs/concepts/unified-schema.mdx said marketId was a stable PMXT UUID and outcomeId was a venue-native outcome id without source scope, while hosted trading and catalog docs distinguish Router/hosted catalog UUIDs from venue-client native IDs. After 92e24a2, Unified Schema and regenerated LLMS output describe source-aware identifier semantics, focused docs and LLMS tests passed with 28 tests, core TypeScript compile passed, diff check and token scan passed, stale scan found old rows only in negative assertions, and full core Jest passed with 792 tests and 3 skipped.",DOC-UNIFIED-SCHEMA-SOURCE-AWARE-IDS-001,92e24a2,pass,"Logistical docs UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-073,Documentation,SDK READMEs,SDK README support scope headers,sdks/python/README.md; sdks/typescript/README.md; core/test/unit/docs-copy-paste-samples.test.js,"As an SDK README reader, I want the Python and TypeScript README headers to describe supported prediction markets and the hosted/local-sidecar runtime model so that I do not assume the SDKs are tied to a stale venue list or old ccxt-style framing.","Python and TypeScript SDK READMEs open with support-scoped SDK copy and explicitly say hosted services are the default, with local sidecar access for self-hosted venue integrations. The stale Python fixed venue-list header and TypeScript ccxt-style header remain only in negative regression assertions.",fixed_retest_pass,2026-06-24,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js failed before the README patch with staleOffenders and missingCurrentClaims for pythonReadme and typescriptReadme; npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; npx tsc --project core/tsconfig.json --noEmit; /Library/Developer/CommandLineTools/usr/bin/git diff --check; SDK README stale/current scan; changed-file token scan; npm test --workspace=pmxt-core -- --runInBand","RED regression failed because the Python SDK README opened with a fixed Polymarket/Kalshi/Limitless/Opinion venue list and the TypeScript SDK README opened with old ccxt-style prediction-market positioning instead of current hosted/local-sidecar support scope. After 10af815, both SDK README headers use supported-prediction-market wording and state hosted services are the default with local sidecar access for self-hosted integrations; focused docs suite passed with 28 tests; core TypeScript compile passed; diff check and token scan passed; stale scan found old headers only in negative assertions; and full core Jest passed with 793 tests and 3 skipped.",DOC-SDK-README-SUPPORT-SCOPE-001,10af815,pass,"Logistical SDK README docs UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-074,Documentation,Package metadata,Package metadata support scope descriptions,core/package.json; sdks/typescript/package.json; sdks/python/pyproject.toml; core/test/unit/docs-copy-paste-samples.test.js,"As a package-registry reader, I want npm and PyPI metadata descriptions to use current support-scoped wording so that package listings do not advertise stale ccxt-style positioning.","pmxt-core package metadata describes the local sidecar API for supported prediction markets; TypeScript and Python SDK metadata describe SDKs for supported prediction markets with hosted services and local sidecar access. The old `The ccxt for prediction markets` phrase remains only in negative regression assertions.",fixed_retest_pass,2026-06-24,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js failed before the metadata patch with staleOffenders for corePackage, typescriptPackage, and pythonProject plus missing current descriptions; npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js; npx tsc --project core/tsconfig.json --noEmit; node package JSON parse check; python3 pyproject TOML parse check; /Library/Developer/CommandLineTools/usr/bin/git diff --check; package metadata stale/current scan; npm test --workspace=pmxt-core -- --runInBand","RED regression failed because core, TypeScript SDK, and Python SDK package metadata still used old `The ccxt for prediction markets` descriptions. After 66229a7, package metadata uses support-scoped sidecar/SDK descriptions; focused docs suite passed with 29 tests; core TypeScript compile passed; package JSON and pyproject TOML parsing passed; diff check passed; stale scan found the ccxt phrase only in negative assertions; and full core Jest passed with 794 tests and 3 skipped.",DOC-PACKAGE-METADATA-SUPPORT-SCOPE-001,66229a7,pass,"Logistical package metadata UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."
DOC-075,Documentation,Catalog identifier docs,Catalog UUID vs venue ID no-conversion wording,docs/concepts/catalog-uuid-vs-venue-id.mdx; docs/llms-full.txt; core/test/unit/docs-copy-paste-samples.test.js,"As a hosted trading docs reader, I want catalog-UUID and venue-ID examples to say both forms work without conversion rather than identically so that I understand the SDK chooses different wire fields for different identifier sources.","Catalog UUID vs Venue ID docs and LLMS output say venue-client and Router outcomes both work against trade.pmxt.dev without a conversion step. They no longer say the two paths work identically, while surrounding copy still explains that the SDK chooses the correct wire field.",fixed_retest_pass,2026-06-24,"RED/GREEN: npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js failed before the docs patch with hasStaleIdenticalClaim true and hasScopedNoConversionClaim false; npm run docs:llms; npm test --workspace=pmxt-core -- --runInBand core/test/unit/docs-copy-paste-samples.test.js core/test/unit/llms-docs.test.js; npx tsc --project core/tsconfig.json --noEmit; /Library/Developer/CommandLineTools/usr/bin/git diff --check; catalog identifier stale/current scan; changed-file token scan; npm test --workspace=pmxt-core -- --runInBand","RED regression failed because the Catalog UUID vs Venue ID example said venue-client and Router outcomes work identically against trade.pmxt.dev even though the page explains they use different wire fields. After e5fb276, source and LLMS docs use no-conversion wording; focused docs and LLMS tests passed with 31 tests; core TypeScript compile passed; diff check and token scan passed; stale scan found the old phrase only in negative assertions; and full core Jest passed with 795 tests and 3 skipped.",DOC-CATALOG-IDENTIFIER-NO-CONVERSION-WORDING-001,e5fb276,pass,"Logistical catalog identifier docs UX error fixed; no live venue access, feed access, funds-moving behavior, or order placement required."