Skip to content

[Audit] 2026-05-21 multi-reviewer SDK sweep — 34-issue umbrella #224

Closed

Description

@TexasCoding

Audit: 2026-05-21 multi-reviewer SDK sweep

This umbrella tracks the 34 issues opened from a parallel-reviewer audit of v2.3.0 spanning security, HTTP transport + concurrency, WebSocket subsystem, models + types + Decimal, resource API surface, performance hot paths, test coverage + contract drift, and docs + DX.

Goal: harden the SDK against the workloads it markets to — real-time orderbook streaming, automated trading, integration into production trading systems.

Reviewer outputs are captured in this orchestrator's agent:// artifacts (one per reviewer). All evidence is cross-referenced inline in each child issue with file:line + verbatim code excerpts.


Tier 1 — Critical / High (release-blocking class)

Correctness or money-impact defects on the hot paths. These should land before the next minor release.

Tier 2 — Medium (next minor)

Important correctness, consistency, and DX gaps.

Tier 3 — Polish bundles (opportunistic)

Each is a small atomic refactor; bundled to keep the issue tracker focused.


Suggested release plan

  1. Patch (v2.3.1) — WS: orderbook permanently desyncs after a sequence gap (no resnapshot) #189 (orderbook resync) + Page.to_dataframe / Page.to_polars silently corrupt Decimal columns (str instead of Decimal) #190 (DataFrame Decimal) + DollarDecimal serialization can emit scientific notation (Kalshi may reject) #191 (scientific notation). These three are user-money-impact and have small, non-breaking fixes.
  2. Minor (v2.4.0) — bulk of Tier 1 (Retry: include Cloudflare 5xx (520–524) and 408 in RETRYABLE_STATUS_CODES #192, Retry: cap total wall-clock budget; no per-request deadline today (~180s worst case) #193, WS: generic subscribe() silently drops unknown params keys #195–Docs: migration guide missing v2.1→v2.3 sections + self-contradicting list_all() cap #200) + non-breaking Tier 2 (most of M*/D*).
  3. Major (v3.0.0) — Orders: V1 batch_create / batch_cancel must return typed per-leg responses (partial-success defect) #194 (V1 batch endpoints, breaking) + any opportunistic Tier 2 with breaking shape.
  4. Polish bundles — fold into v2.4 / v3.0 wherever a bundle item naturally co-occurs with a tracked issue.

Source

Identified during the 2026-05-21 parallel-reviewer audit (8 subagents: security/auth, HTTP transport + concurrency, WebSocket, models + types, resources, performance hot paths, tests + contract drift, docs + DX).

Activity

  1. TexasCoding commented on May 21, 2026

    @TexasCoding
    OwnerAuthor

    Release-cut decision: fold #194 into v2.4.0

    Per audit-orchestrator discussion with maintainer (2026-05-21): the V1 batch_create / batch_cancel typed-response fix lands in v2.4.0 minor rather than waiting for v3.0.0. Rationale: the current V1 implementation is unsafe as-shipped (crashes on partial-success, discards reduced_by_fp), the V2 family already exists as the safe path, and breaking the V1 return type is the right correctness call.

    Revised release plan:

    This is the de-facto active milestone now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    infraInfrastructure/tooling

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions