gamma Market deserializer: unknown fields `feeSchedule` and `feeType` cause WARN on every fetch

[ItsCodejac]

Summary

polymarket_client_sdk_v2::gamma::types::response::Market (0.5.1 and current main) does not include feeSchedule or feeType fields. Both are present on every market response from https://gamma-api.polymarket.com/markets. The SDK's serde_helpers logs a WARN per missing field per market fetched.

Repro

Any call into the gamma client:

let c = polymarket_client_sdk_v2::gamma::client::Client::new("https://gamma-api.polymarket.com")?;
let req = polymarket_client_sdk_v2::gamma::types::request::MarketBySlugRequest::builder()
    .slug("btc-updown-5m-1778794800".into())
    .build();
let m = c.market_by_slug(&req).await?;

Produces:

WARN polymarket_client_sdk_v2::serde_helpers: unknown field in API response
  field=?.feeSchedule value={"exponent":1,"rate":0.07,"rebateRate":0.2,"takerOnly":true}
WARN polymarket_client_sdk_v2::serde_helpers: unknown field in API response
  field=?.feeType value="crypto_fees_v2"

Suggested fix

Add to Market:

#[serde(rename = "feeSchedule")]
pub fee_schedule: Option<FeeSchedule>,
#[serde(rename = "feeType")]
pub fee_type: Option<String>,

With FeeSchedule { exponent: i32, rate: Decimal, rebate_rate: Decimal, taker_only: bool }.

Why this matters

For downstream apps that follow a strict "no log suppression" policy, every gamma fetch produces these two WARN lines. They drown real schema-drift signals.

Env

• SDK 0.5.1
• gamma-api.polymarket.com, BTC 5m markets (slug pattern btc-updown-5m-<unix_ts>)