Polymarket -> Kuest compatibility

Migrating Polymarket bots to Kuest requires endpoint, authentication, network, and V2 signed-order changes.

What's here

MIGRATION.md — step-by-step migration guide for humans.
mapping.json — machine-readable mapping for automation or LLM-assisted refactors.
AGENTS.md — compact instructions for coding agents and migration tooling.

Replace POLYMARKET_ with KUEST_ in env vars and auth headers.
Replace *.polymarket.com with *.kuest.com (same subdomain).
Kuest order signing uses the EIP-712 domain CTF Exchange, version 2.
V2 orders remove taker, expiration, nonce, and feeRateBps from the signed payload and add timestamp, metadata, and builder.
Use Deposit Wallet as maker and signer, with signature type 3.
Send owner as the CLOB API key, not KUEST_ADDRESS.
In Kuest CLOB order responses, deserialize owner as a ULID/string user identifier.
Use builderCode/builder_code for attribution; Kuest encodes a builder wallet as bytes32(uint256(uint160(wallet))).
Deploy the Deposit Wallet before posting orders. Relayer calls require Builder credentials and use WALLET / WALLET-CREATE.

Kuest runs on Polygon Mainnet (chainId 137) and uses Circle USDC.
Polymarket V2 uses Polygon (chainId 137) and pUSD collateral; Kuest V2 uses USDC Circle directly.

For the full migration guide, see MIGRATION.md.