order_version_mismatch recurrence on order submissions — polymarket-cli v0.1.5 (~25 days after #69 fix)

[16bitapex]

Filing as recurrence of #69 (closed 2026-04-29 "seems to be solved now" — no CLI release between filing and fix). Same symptom returned on 2026-05-23.

Error

POST /order → 400 Bad Request
{"error": "order_version_mismatch"}

Surfaced by polymarket clob create-order CLI exit 1.

Environment

• CLI: polymarket-cli v0.1.5 (latest GitHub release, published 2026-03-10)
• Binary path: /usr/local/bin/polymarket (single binary, no node deps)
• Signature types tested: BOTH proxy AND eoa — both fail with identical error (confirmed via SIGNATURE_TYPE=proxy then redeploy with SIGNATURE_TYPE=eoa)
• Order types tested: GTC limit order via clob create-order
• Chain: Polygon (137)
• Read endpoints: all OK (clob ok, clob book, clob price, clob market, wallet show)
• Order endpoints: ALL fail with order_version_mismatch

Reproducer

polymarket clob create-order \n  --token <real-mlb-totals-token-id> \n  --side buy --price 0.50 --size 1 \n  --signature-type proxy --output json

Returns:

{"error":"Status: error(400 Bad Request) making POST call to /order with {\"error\":\"order_version_mismatch\"}"}

Identical when --signature-type eoa substituted.

Hypothesis (per closed #69)

Issue #69 was resolved server-side at the CLOB API without a CLI release. Today's recurrence suggests the schema/version drift has returned. Either:

1. CLOB API expects a new order schema version that v0.1.5 doesn't construct
2. EIP-712 typed-data domain version bumped on the protocol side
3. Required field added to order struct that v0.1.5 doesn't populate

Differential vs #69

• 25 days elapsed since order_version_mismatch on all order submissions since April 28 — polymarket-cli v0.1.4 / v0.1.5 #69 was fixed
• Same CLI version (v0.1.5 — no release in between)
• Same symptom across all signature types (matches order_version_mismatch on all order submissions since April 28 — polymarket-cli v0.1.4 / v0.1.5 #69)
• Read endpoints all healthy (matches order_version_mismatch on all order submissions since April 28 — polymarket-cli v0.1.4 / v0.1.5 #69)

Request

1. Confirm whether CLOB API is currently in a schema-drift state similar to April 28-29
2. If yes — same server-side rollback path as last time, or new CLI release needed?
3. Any flag / env var to control the order version manually for forward-compat?

Linking #69 for prior occurrence.