crypto_exc_all 0.1.1

# Task Plan: Exchange SDK Aggregation

## Goal

在已完成 OKX/Binance 聚合与发布经验的基础上，继续把 Bitget 接入为独立 SDK crate，并在根 crate `crypto_exc_all` 中提供统一聚合入口。

## Phases

- [x] Phase 1: Plan and setup
- [x] Phase 2: Research project architecture and unfinished work
- [x] Phase 3: Research Binance official API/SDK guidance
- [x] Phase 4: Write architecture and implementation plan
- [x] Phase 5: Implement one prioritized unfinished Binance feature with tests
- [x] Phase 6: Verify and deliver
- [x] Phase 7: Add Bitget independent SDK crate and root aggregation
- [x] Phase 8: Verify Bitget aggregation and update integration playbook
- [x] Phase 9: Add root unified positions and basic trade facade for OKX/Binance/Bitget
- [x] Phase 10: Add root unified order query facade for OKX/Binance/Bitget
- [x] Phase 11: Add root unified fills facade for OKX/Binance/Bitget
- [x] Phase 12: Add root unified orderbook and candles facade for OKX/Binance/Bitget
- [x] Phase 13: Add root unified derivatives market metrics for OKX/Binance/Bitget
- [x] Phase 14: Add root unified market sentiment stats for OKX/Binance/Bitget
- [x] Phase 15: Add root unified set-leverage account setting for OKX/Binance/Bitget
- [x] Phase 16: Add root unified set-position-mode account setting for OKX/Binance/Bitget
- [x] Phase 17: Add Bitget V2 WebSocket base client, events, and reconnect manager
- [x] Phase 18: Add Bitget WebSocket typed DTOs for ticker/orders/account/positions
- [x] Phase 19: Add Bitget WebSocket typed DTOs for books/trade/candles
- [x] Phase 20: Add Bitget WebSocket typed DTO for private fill channel
- [x] Phase 21: Add Bitget WebSocket place/cancel trade request helpers and ack parser
- [x] Phase 22: Add Bitget WebSocket inbound stall reconnect guard
- [x] Phase 23: Add Bitget WebSocket private login replay and ack gate before subscription replay
- [x] Phase 24: Add Bitget WebSocket runtime subscribe/unsubscribe command path
- [x] Phase 25: Count connected-session failures against Bitget WebSocket max reconnect attempts
- [x] Phase 26: Lock native SDK parameter pass-through boundary with Bitget regression tests
- [x] Phase 27: Refactor Bitget WebSocket architecture to follow OKX proven manager/client layering
- [x] Phase 28: Add Bitget WebSocket URL fallback pool, exponential backoff config, and message timeout
- [x] Phase 29: Add Bitget WebSocket root unified event stream facade only after bitget_rs is stable
- [ ] Phase 30: Prepare bitget_rs as independently publishable crate and switch root dependency to released version

## Iteration Update Protocol

每次后续迭代必须更新本文件，至少包含：

1. 本次完成内容：在 `Phases` 勾选完成项，必要时新增下一阶段。
2. 剩余工作：更新 `Remaining Work Backlog` 的状态，不允许只在对话中说明。
3. 架构偏差：如果实现偏离 OKX/Binance 已验证模式，必须在 `Architecture Guardrails` 记录原因和回滚/纠偏路径。
4. 验证证据：在 `Status` 写明实际跑过的命令和结果；真实下单、WebSocket 实盘验证必须单独注明是否执行。
5. 发布状态：涉及独立 crate 时，记录是否已发布 crates.io、根 crate 是否仍使用 path 依赖。

## Architecture Guardrails

- `bitget_rs` 是最终独立 SDK crate；`crypto_exc_all` 只应通过 facade/adapter 引入并统一输出，不应把 Bitget 原生协议逻辑散落到根 crate。
- `bitget_rs`、`bnb_rs`/Binance、未来 `bybit_rs` 都必须是单独可用的原生 SDK 包。它们只暴露交易所原生字段和值，不负责统一 `cross/crossed/CROSSED`、`post_only/GTX`、`one_way_mode/Hedge` 这类跨交易所兼容参数。
- 兼容参数、统一枚举、用户友好别名和跨交易所映射只能放在 `crypto_exc_all` 这一层：例如 `MarginMode::Cross` 到 Binance `CROSSED`、OKX `cross`、Bitget `crossed` 的转换必须在 root adapter 完成。
- 原生 SDK 如果提供 helper builder，也只能是交易所原生命名的便捷构造，不能把其它交易所或 root facade 的兼容语义带进去。
- 根 crate 当前为了 workspace 开发使用 `bitget_rs = { version = "0.1.0", path = "bitget_rs" }`。发布后应切换为仅依赖已发布版本，保留 workspace path 只作为本仓库开发便利。
- Bitget WebSocket 后续不再继续堆叠临时 manager 行为；需要参考 OKX 已验证的 `AutoReconnectWebsocketClient + OkxWebsocketManager` 分层：
  - 底层 client 负责 URL fallback、连接、登录、心跳、消息超时、自动重连和 ws_sender。
  - 上层 manager 负责 public/private/business 或 Bitget public/private 连接编排、订阅 registry、运行中 subscribe/unsubscribe、状态查询和消息转发。
  - 订阅状态使用 key 化 registry，记录 active/pending，重连后统一重放。
  - 私有连接必须先 login ack 成功，再订阅 private channel。
  - 连接成功但会话失败也必须计入重连失败，避免无限循环。
- 当前 Bitget WebSocket 实现是可运行的轻量实现，但已经暴露出多次稳定性补丁；后续优先做架构纠偏，而不是继续局部补洞。

## Remaining Work Backlog

### P0 - Bitget WebSocket 架构纠偏

- [x] 对齐 OKX `AutoReconnectWebsocketClient` 的底层 client：抽出 Bitget 独立 auto reconnect client，避免所有状态堆在 `BitgetWebsocketManager` 一个 loop 中。
- [x] 对齐 OKX `OkxWebsocketManager` 的 manager 分层：public/private 连接分离，统一 message forwarder，订阅 registry 独立于 socket loop。
- [x] 增加 URL fallback pool：默认主 URL + 环境变量 `BITGET_WS_FALLBACKS` + `with_fallback_urls`，失败时轮换候选 URL。
- [x] 增加指数退避配置：`reconnect_interval`、`backoff_factor`、`max_backoff`，避免失败时固定频率重连。
- [x] 增加 message timeout 语义：用 `message_timeout` 表达“多久没有入站消息视为 stale”，不再硬编码为 `ping_interval * 3`。
- [x] 增加连接状态细分：连接中、登录中、已认证、已订阅、重连中、已停止，便于外部诊断。
- [x] 增加 WebSocket 实盘 smoke example：连接 public ticker/orderbook 并等待一条消息；private smoke 只登录并订阅 account/orders，不下单。

### P1 - Bitget 原生 SDK 完整度

- [x] 补 Bitget private WebSocket 频道：ADL、trigger order、plan/strategy order、history position（以官方当前文档为准）。
- [x] 补 Bitget REST 计划单/条件单/止盈止损相关接口。
- [x] 补 Bitget REST 历史持仓、账户资产模式更细字段、手续费等级/费率映射 DTO。
- [x] 为 bitget_rs 增加 crate-level 文档和公开 examples，保证作为独立 SDK 使用时不依赖 `crypto_exc_all`。

### P1 - 独立 crate 发布与根 crate 依赖

- [x] 发布或确认 `bitget_rs` crates.io 名称可用；如不可用，确定替代 crate 名称。
- [x] 为 `bitget_rs` 补齐 crates.io 元数据：`readme`、`documentation`、`repository`、`homepage`、`keywords`。
- [x] `bitget_rs` 发布前 dry-run、package list、tarball 内容和敏感路径审计通过。
- [ ] 执行真实 `cargo publish -p bitget_rs` 并等待 crates.io index 可见。
- [ ] `bitget_rs` 发布后，根 `crypto_exc_all` 的 `Cargo.toml` 依赖切换为版本依赖，workspace 开发再决定是否保留 path override。
- [x] 为根 `crypto_exc_all` 0.1.1 补齐发布元数据；当前 root publish dry-run 明确阻塞在 crates.io 还找不到 `bitget_rs`。
- [x] 根 crate 只保留统一接口、adapter 和 `raw::bitget` re-export；不在根 crate 新增 Bitget 协议细节。
- [x] 为未来 `bybit_rs` 建立同样边界：Bybit 原生包只接收 Bybit 参数，`crypto_exc_all` adapter 才做统一枚举和兼容别名转换。

### P2 - 根 crate 统一事件流

- [x] 等 `bitget_rs` WebSocket 架构稳定后，再设计 `crypto_exc_all` 的统一 event stream facade。
- [x] 统一 event stream 先覆盖 ticker/orderbook/trades/orders/account/positions/fills，不强行统一交易所特有字段，保留 `raw`。
- [x] 设计统一错误、重连、订阅生命周期事件，避免策略层直接依赖各交易所 socket manager。

### P2 - 后续交易所

- [ ] Bybit：按 `bitget_rs` 独立 crate 经验新增独立 SDK crate，再接入根 facade。
- [ ] Hyperliquid：复用已调研的官方 hypersdk 方向，先 market-data，再 private/trade。

## Key Questions

1. 项目当前的模块边界、配置加载、交易所抽象和执行入口是什么？
2. README 或代码中标记的未完成功能有哪些，哪个最适合作为第一项交付？
3. Binance USDⓈ-M Futures 官方当前推荐的 SDK 或 REST/WebSocket 接入方式是什么？
4. 如何在不泄露 `.env` 密钥的前提下复用现有配置完成可验证实现？
5. Bitget WebSocket 后续如何最大化复用 OKX 已验证的自动重连架构，而不是继续局部自造？
6. `bitget_rs` 独立发布后，根 crate 如何从 path dependency 平滑切到版本 dependency？

## Decisions Made

- 使用持久化计划文件跟踪该多阶段任务。
- Binance 第一阶段采用与 OKX 对齐的本地轻量 SDK 结构，而不是直接暴露官方自动生成 `binance-sdk` 类型。
- 优先交付 Binance USDⓈ-M Futures 只读签名接口 `GET /fapi/v2/balance`，同时实现公共 `GET /fapi/v1/time`。
- 第二阶段继续按 OKX 主要能力补 Binance REST wrapper：市场数据、账户/持仓、订单/成交记录。
- 用户明确要求执行真实下单测试后，新增受控实盘 post-only example：按实时交易规则构造 `LIMIT + GTX` 最小挂单，接受后立即撤单。
- 第三阶段继续补 OKX 对齐缺口，优先补 Binance Futures 核心 REST：批量订单、改单、全部撤单、账户配置、交易限制、杠杆档位、持仓模式、mark price/open interest/多空比/taker volume。
- 第四阶段继续补 OKX 对齐缺口中的资产域：采用 Binance Wallet/SAPI REST，新增独立 `BINANCE_SAPI_API_URL`，但复用现有签名、错误解析和 builder 风格。
- 第五阶段补公告和 WebSocket 必要 API 接口：公告采用 Binance 网站 BAPI best-effort wrapper，WebSocket 补 listenKey REST、2026-04-23 前需迁移的新分流 URL 构造器、JSON 消息循环、订阅/取消订阅、基础自动重连订阅重放和 SOCKS5/SOCKS5h 代理连接。
- 第六阶段补 WebSocket 稳定性增强：按 Binance 官方 `/public`、`/market`、`/private` 分流多连接，增加连接状态/健康度指标，为核心私有事件 `ORDER_TRADE_UPDATE`、`ACCOUNT_UPDATE` 提供 typed parser，并区分 combined stream URL 与 JSON `SUBSCRIBE` 模式，避免重复订阅。
- 第七阶段继续补 WebSocket typed parser 完整性：覆盖 `listenKeyExpired`、`MARGIN_CALL`、`TRADE_LITE`、`ACCOUNT_CONFIG_UPDATE`、`STRATEGY_UPDATE`、`GRID_UPDATE`、`CONDITIONAL_ORDER_TRIGGER_REJECT`、`ALGO_UPDATE`，并支持 combined stream `{stream,data}` 私有事件解包。
- Bitget 接入采用和 Binance 一样的双层结构：`bitget_rs` 只负责 Bitget V2 原生 API/签名，根 crate adapter 负责统一 `ExchangeId`、`Instrument`、`Ticker`、`Balance` 和错误映射。
- Bitget 第一阶段以 USDT 永续只读能力为聚合面：`GET /api/v2/mix/market/ticker` 和签名账户列表 `GET /api/v2/mix/account/accounts`，默认 `productType=USDT-FUTURES`，后续再扩展交易、WebSocket 和更多 product type。
- Bitget 第二阶段补齐 OKX/Binance 已有 REST 域的主要等价能力：market/account/trade/asset/announcements/common trade-rate。根 facade 继续只稳定暴露跨交易所 `ticker` 和 `balances`，交易所特有细节通过 `crypto_exc_all::raw::bitget` 使用。
- 根 crate 第三阶段在已有 `ticker` / `balances` 基础上补统一 `positions`、`place_order`、`cancel_order`。统一 DTO 只覆盖三家可稳定对齐的字段；订单高级参数、批量单、改单、资产划转等仍先走 `raw` 入口。
- 根 crate 第四阶段补统一订单查询 facade：`OrderFacade::get/open/history` 对齐 Binance `order/openOrders/allOrders`、OKX `order/orders-pending/orders-history`、Bitget `detail/orders-pending/orders-history`，统一输出 `Order` DTO，保留 `raw` 字段承载交易所差异。
- 根 crate 第五阶段补统一成交明细 facade：`FillFacade::list` 对齐 Binance `userTrades`、OKX `fills`、Bitget `fills`，统一输出 `Fill` DTO，覆盖成交 ID、订单 ID、方向、价格、数量、手续费、手续费币种、maker/taker、时间戳和 raw。
- 根 crate 第六阶段扩展 `MarketFacade`：`orderbook` 对齐 Binance `depth`、OKX `books`、Bitget `orderbook`；`candles` 对齐 Binance `klines`、OKX `candles`、Bitget `candles`，统一输出 `OrderBook` 和 `Candle` DTO。
- 根 crate 第七阶段扩展 `MarketFacade` 衍生品市场指标：`funding_rate`、`funding_rate_history`、`mark_price`、`open_interest` 对齐 Binance、OKX、Bitget 的公共 REST，统一输出 `FundingRate`、`MarkPrice`、`OpenInterest` DTO，并为 OKX SDK 补齐 `public/mark-price` 与 `public/open-interest` wrapper。
- 根 crate 第八阶段扩展 `MarketFacade` 市场情绪统计：`long_short_ratio` 和 `taker_buy_sell_volume` 对齐 Binance futures data、OKX rubik big-data、Bitget mix market 统计接口，统一输出 `LongShortRatio` 和 `TakerBuySellVolume` DTO。
- 根 crate 第九阶段扩展 `AccountFacade` 交易设置：`set_leverage` 对齐 Binance `POST /fapi/v1/leverage`、OKX `/api/v5/account/set-leverage`、Bitget `/api/v2/mix/account/set-leverage`，统一输出 `LeverageSetting` DTO。OKX 合约类 instrument 只发送 `instId/lever/mgnMode/posSide`，避免把 Bitget 所需的 `marginCoin` 误映射为 OKX `ccy`。
- 根 crate 第十阶段扩展 `AccountFacade` 持仓模式设置：`set_position_mode` 对齐 Binance `POST /fapi/v1/positionSide/dual`、OKX `/api/v5/account/set-position-mode`、Bitget `/api/v2/mix/account/set-position-mode`，统一 `PositionMode::OneWay/Hedge`，并为 OKX SDK 补齐原生 `set_position_mode` wrapper。
- 根 crate 第十一阶段扩展账户能力发现和 symbol 保证金模式设置：`AccountFacade::capabilities()` 暴露 `set_symbol_margin_mode` 与 `order_level_margin_mode`；`set_symbol_margin_mode` 对齐 Binance `POST /fapi/v1/marginType` 和 Bitget `/api/v2/mix/account/set-margin-mode`，OKX 明确返回 `Unsupported`，避免把 OKX 下单 `tdMode`/杠杆 `mgnMode` 伪装成持久 symbol 配置。
- 根 crate 第十二阶段扩展策略层保证金模式入口：`ensure_order_margin_mode` 对 Binance/Bitget 复用 symbol 保证金模式真实切换，对 OKX 返回 order-level 应用结果，不发送不存在的配置请求；统一输出 `MarginModeApplyMethod::SymbolConfiguration/OrderLevel`。
- 根 crate 第十三阶段扩展策略层下单前预配置入口：`prepare_order_settings` 聚合 position mode、margin mode、leverage 三类可选配置，按持仓模式、保证金模式、杠杆顺序执行，并复用已有三家 adapter 能力，避免策略层散落交易所分支。
- Bitget WebSocket 纠偏决定：当前轻量 manager 已经多次暴露稳定性问题，后续不继续在单 loop 上叠补丁；改为参考 OKX 已验证的 `AutoReconnectWebsocketClient + Manager` 分层，实现 Bitget 自己包内的稳定 socket 架构。
- Bitget 独立包边界决定：`bitget_rs` 自己承担 REST/WebSocket 原生能力、examples、文档和发布；`crypto_exc_all` 只引入 `bitget_rs` 并提供统一 facade/adapter，不复制 Bitget socket 业务逻辑。
- 参数兼容边界决定：`bitget_rs`/`bnb_rs`/未来 `bybit_rs` 不能承担跨交易所兼容输入；root adapter 才负责把统一请求转换为各交易所原生字段和值。本轮新增 `native_bitget_sdk_preserves_exchange_parameter_values` 回归测试，锁定 `bitget_rs` 对原生 `marginMode` 等值做透传。

## Errors Encountered

- Live Binance read-only request failed before reaching Binance because local `all_proxy` uses `socks5://127.0.0.1:7897` and `reqwest` did not enable the `socks` feature. Resolution: enable `reqwest/socks` in `binance_rs/Cargo.toml`.
- After enabling SOCKS support, signed live request and public Binance time endpoints still timed out through the default current network/proxy path. Resolution: explicitly normalize `socks5://` proxy URLs to `socks5h://` and wire proxy configuration into `reqwest::Client`.
- Real `POST /fapi/v1/order` was attempted against Binance USDⓈ-M Futures mainnet through the current proxy. Binance rejected it before order creation with code `-2015` (`Invalid API-key, IP, or permissions for action`), so no `orderId` was created and no cancel request could be issued.
- After the IP whitelist update, Binance accepted a real DOGEUSDT `LIMIT + GTX` post-only order and the example immediately canceled it. Earlier BTCUSDT attempts surfaced Hedge Mode `positionSide` and insufficient-margin constraints.
- Bitget live read-only account example initially failed locally before request dispatch because `.env` used `bitget_PASSPHRASE` while the SDK accepted only `BITGET_PASSPHRASE` / lowercase variants. Resolution: add this existing mixed-case key name to both `bitget_rs::Credentials` and root `BitgetExchangeConfig` env lookup, with tests.
- After the env-name fix, Bitget live read-only V2 account request reached the exchange but Bitget returned code `40012` (`apikey/password is incorrect`). A separate `curl + openssl` reproduction returned the same `40012` for multiple V2 signed endpoints, while the same key/passphrase authenticated against UTA V3 and returned `40084` (`You are in Classic Account mode, and the Unified Account API is not supported at this time`). This points to a Bitget key/account-mode compatibility issue for V2 signed APIs, not a local signing/query/body implementation failure.
- After replacing the Bitget API key/passphrase and adding the current egress IP to the whitelist, Bitget V2 signed account reads succeeded. A real `post_only` BTCUSDT futures order attempt reached the trade endpoint but was rejected with `40762` (`The order amount exceeds the balance`) because USDT-Futures available balance and spot USDT available balance are both `0`.
- This iteration initially used an invalid `cargo test` invocation with two test filters. Resolution: rerun with the shared `websocket_manager_` filter.
- The first fallback/message-timeout TDD run exposed two test-shape issues after the implementation compiled: local mock WebSocket servers closed immediately after sending one message, racing connection-state assertions, and the old stall test implicitly depended on the former `ping_interval * 3` timeout. Resolution: keep mock sockets open until manager stop and make the stall timeout explicit with `with_message_timeout`.
- Full `cargo test --workspace` in this iteration reached unrelated OKX crate live/env-dependent tests and failed because `OKX_API_KEY` is not set (`okx_rs/src/api/*` tests creating APIs from env). Resolution for this iteration: keep Bitget/root verification scoped with `cargo test --workspace --exclude okx`, which passed; do not change unrelated OKX live tests in this Bitget WebSocket architecture slice.
- Plan-order REST clippy verification initially warned that `PlanOrderRequest::limit/market` had too many arguments. Resolution: refactor to `PlanOrderRequest::new(...).with_limit_price(...).with_trigger(...)` builder style and rerun clippy cleanly.
- `cargo publish --dry-run --allow-dirty -p bitget_rs` hit transient crates.io SSL timeout warnings while updating the index, then retried, packaged, verified, and reached the dry-run upload abort successfully. No real publish was performed.
- Phase 29 root unified event stream verification passed with `cargo clippy -p crypto_exc_all --all-targets`, `cargo test -p crypto_exc_all external_consumer_can_stream_bitget_public_events -- --nocapture`, `cargo test -p crypto_exc_all`, and `cargo test --workspace --exclude okx`. Clippy still reports unrelated existing warnings in `bnb_rs`/`okx`; no new crypto_exc_all error was reported.
- Phase 29 feature-gating check found the first event stream implementation broke README-advertised single-exchange builds when Bitget was disabled: `cargo check -p crypto_exc_all --no-default-features --features binance` and `--features okx` failed because `EventStreamInner` had no variant outside the Bitget feature. Resolution: add a non-Bitget internal placeholder branch and gate Bitget-only helpers/imports. `cargo check -p crypto_exc_all --no-default-features --features binance`, `--features okx`, and `--features bitget` now all exit 0. Running with no exchange feature at all remains outside the advertised usage and still fails on the pre-existing empty `ExchangeClient` shape.
- Phase 30 publish-prep checks completed without external upload: `bitget_rs` now includes repository/homepage/keywords metadata, `cargo publish --dry-run --allow-dirty -p bitget_rs` packaged and verified 22 files, `cargo package -p bitget_rs --allow-dirty --list` showed both WebSocket smoke examples included, `cargo package -p bitget_rs --allow-dirty --no-verify` produced `target/package/bitget_rs-0.1.0.crate`, and tarball path/key scan found no `.env`, `.idea`, `target`, `.git`, `secret`, `credential`, or `passphrase` entries. `cargo clippy -p bitget_rs --all-targets` and `cargo test -p bitget_rs` exited 0. `cargo publish --dry-run --allow-dirty -p crypto_exc_all` currently fails as expected with `no matching package named bitget_rs found`; real root publish is blocked until `bitget_rs` is actually published and visible in the crates.io index.

## Status

**Currently complete for Bitget REST aggregation parity plus root market/account-setting/trade/position/order-query/fills/derivatives-metrics/sentiment-stats/event-stream facade and Bitget WebSocket base client/manager split** - Binance market/account/trade REST wrappers, the live post-only order harness, Wallet/SAPI asset wrappers, announcement wrapper, and WebSocket listenKey/URL/session/reconnect/split-route/health helpers are implemented and verified locally. Private user-data typed parsers now cover the current USDⓈ-M Futures event set documented by Binance. A real Binance Futures order was created on DOGEUSDT and immediately canceled with zero executed quantity. Bitget now has an independent `bitget_rs` crate plus root facade adapter for market ticker, orderbook, candles, funding rate, funding rate history, mark price, open interest, long-short ratio, taker buy-sell volume, account balances, set leverage, set position mode, set symbol margin mode with capability discovery, ensure order margin mode, prepare order settings, positions, basic order placement, cancellation, order detail, open orders, order history, fills, and unified event stream. `bitget_rs` now covers the major OKX/Binance REST domains: market data, account/position, order/trade, plan/conditional/TPSL orders, wallet/asset, announcements, and common trade-rate, and includes Bitget V2 WebSocket public/private URL config, login signing, ping/pong, subscribe/unsubscribe, place/cancel trade request helpers, trade ack parsing, typed base event parsing, ticker/orders/account/positions/books/trade/candles/fill typed DTOs, SOCKS5/SOCKS5h connection support, reconnect metrics, runtime subscribe/unsubscribe command path, timed ping, private login replay with login ack gate before subscription replay, inbound stall timeout reconnect, connected-session failure attempt limiting, subscription replay, public/private manager connection split, unified manager message forwarding, pending/active subscription registry, and granular connection states (`Connecting` / `LoggingIn` / `Authenticated` / `Subscribed` / `Reconnecting` / `Stopped`).

Current correction focus: Bitget WebSocket core architecture has been corrected to follow OKX's validated auto-reconnect client and manager split, and the root unified event stream now delegates to that native manager instead of duplicating protocol behavior. Native SDK packages must remain independently usable and parameter-native; compatibility mapping belongs in `crypto_exc_all`. The remaining work is tracked in `Remaining Work Backlog`; every future iteration must update this file before final delivery.

Latest iteration: Phase 30 publish preparation advanced up to the external-upload boundary. `bitget_rs` and root `crypto_exc_all` now both carry crates.io-facing repository/homepage metadata; `bitget_rs` also has keywords. Fresh `bitget_rs` verification passed with `cargo publish --dry-run --allow-dirty -p bitget_rs`, `cargo package -p bitget_rs --allow-dirty --list`, `cargo package -p bitget_rs --allow-dirty --no-verify`, tarball sensitive-path scan, `cargo clippy -p bitget_rs --all-targets`, and `cargo test -p bitget_rs`. The generated package includes 22 files, including `websocket_public_smoke.rs` and `websocket_private_smoke.rs`; no sensitive path/key-name entries were found in the tarball listing. Root `crypto_exc_all` 0.1.1 dry-run publish now reaches the expected blocker: crates.io cannot resolve `bitget_rs` until the real child crate publish is performed and the index updates. No real `cargo publish` upload was executed in this iteration.