mt5cli 1.4.2__tar.gz → 1.6.0__tar.gz

{mt5cli-1.4.2 → mt5cli-1.6.0}/.agents/skills/local-qa/scripts/qa.sh

@@ -32,9 +32,9 @@ case "${OSTYPE}" in
       | xargs -0 -t shellcheck
 
     # GitHub Actions
-    zizmor --fix=safe .github/workflows
+    uvx zizmor --fix=safe .github/workflows
     git ls-files -z -- '.github/workflows/*.yml' | xargs -0 -t actionlint
-    checkov --framework=all --output=github_failed_only --directory=.
+    uvx checkov --framework=all --output=github_failed_only --directory=.
     ;;
   *)
     echo 'GitHub Actions and shell script linting is only supported on Linux and macOS.'

{mt5cli-1.4.2 → mt5cli-1.6.0}/.github/workflows/claude.yml

@@ -27,8 +27,7 @@ jobs:
     if: >
       github.event_name == 'pull_request'
       && (! github.event.pull_request.draft)
-      && (! startsWith(github.head_ref, 'dependabot/'))
-      && (! startsWith(github.head_ref, 'renovate/'))
+      && github.event.pull_request.user.type != 'Bot'
     permissions:
       contents: read
       pull-requests: write
@@ -46,7 +45,7 @@ jobs:
       || (github.event_name == 'pull_request_review' && contains(github.event.review.body, '@claude'))
       || (github.event_name == 'issues' && (contains(github.event.issue.body, '@claude') || contains(github.event.issue.title, '@claude')))
     permissions:
-      contents: read
+      contents: write
       pull-requests: write
       issues: write
       id-token: write

{mt5cli-1.4.2 → mt5cli-1.6.0}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.4
+Metadata-Version: 2.5
 Name: mt5cli
-Version: 1.4.2
+Version: 1.6.0
 Summary: Generic MT5 data and execution infrastructure for Python applications
 Project-URL: Repository, https://github.com/dceoy/mt5cli.git
 Author-email: dceoy <dceoy@users.noreply.github.com>

{mt5cli-1.4.2 → mt5cli-1.6.0}/docs/api/public-contract.md

@@ -39,6 +39,7 @@ operational capability still has exactly one owning module:
 | Module                 | Owns                                                                                                                                        |
 | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
 | `mt5cli.client`        | Connection lifecycle (`build_config`, `mt5_session`, `MT5Client`); the sole session factory                                                 |
+| `mt5cli.lifecycle`     | Account selection within an already-active persistent MT5 session (`switch_account`)                                                        |
 | `mt5cli.marketdata`    | Stateless one-off market-data reads and multi-account rate collection (`AccountSpec`, `collect_latest_rates_for_accounts`, etc.)            |
 | `mt5cli.history`       | Legacy history collection, incremental updates, and SQLite storage (`collect_history`, `update_history`, `write_*_dataset`)                 |
 | `mt5cli.rates`         | Canonical rate persistence/loading and stable update wrappers (`load_rate_series_from_sqlite`, `update_history`, `ThrottledHistoryUpdater`) |
@@ -66,6 +67,7 @@ These names are exported from `mt5cli` and enumerated in
 | `build_config`                                  | Build the underlying MT5 connection config from connection fields; `login` accepts `int \| str \| None` — numeric strings are coerced to `int`, blank strings are treated as unset, and `${ENV_VAR}` / `$ENV_NAME` placeholders in string parameters are expanded when `allow_whole_dollar_env=True` |
 | `substitute_mapping_values`                     | Generic selected-key environment substitution for downstream configuration adapters                                                                                                                                                                                                                  |
 | `mt5_session`                                   | Canonical context manager: initialize/login once, yield `MT5Client`, shut down once; a supplied `client=` remains caller-owned.                                                                                                                                                                      |
+| `switch_account`                                | Change the account selected by an already-active persistent `MT5Client` with MT5 `login()` only; verifies the requested login/server and does not reinitialize or shut down the terminal                                                                                                             |
 | `Mt5Config`                                     | Canonical pdmt5 connection configuration type returned by `build_config` and accepted by managed-session wrappers                                                                                                                                                                                    |
 | `AccountSpec`                                   | Generic account group: symbols plus optional credentials                                                                                                                                                                                                                                             |
 | `resolve_account_spec`, `resolve_account_specs` | Merge overrides and expand `${ENV_VAR}` placeholders; opt-in `allow_whole_dollar_env` for bare `$NAME`                                                                                                                                                                                               |
@@ -87,17 +89,34 @@ timestamp normalization in downstream apps.
 
 ### SQLite history collection and rate loading
 
-| Symbol                                                            | Role                                                                                                             |
-| ----------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
-| `collect_history`                                                 | One-shot date-range export into SQLite                                                                           |
-| `report_rate_gaps`                                                | SQLite-only one-row-per-gap report for the canonical rates table or an explicit custom table                     |
-| `update_history`, `update_history_with_config`                    | Incremental append from `MAX(time)` cursors; explicit naive trade-server `date_to` required                      |
-| `ThrottledHistoryUpdater`                                         | Minimum interval between successful incremental updates; explicit `date_to`; optional `update_backend` injection |
-| `RateTarget`, `build_rate_targets`                                | Neutral `(symbol, timeframe)` series descriptors                                                                 |
-| `load_rate_series_from_sqlite`, `load_rate_series_by_granularity` | Load normalized `rates` series or explicit custom tables; reject invalid targets clearly                         |
+| Symbol                                                            | Role                                                                                                                       |
+| ----------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
+| `collect_history`                                                 | One-shot date-range export into SQLite                                                                                     |
+| `report_rate_gaps`                                                | SQLite-only one-row-per-gap report for the canonical rates table or an explicit custom table                               |
+| `update_history`, `update_history_with_config`                    | Incremental append from `MAX(time)` cursors; explicit naive trade-server `date_to` required                                |
+| `ThrottledHistoryUpdater`                                         | Minimum interval between successful incremental updates; explicit `date_to`; optional `update_backend` injection           |
+| `capture_history_datasets`                                        | MT5-bound half of `update_history`: resolves cursors and fetches MT5 data, returns a `HistoryCapture`, writes nothing      |
+| `persist_history_datasets`                                        | MT5-free half of `update_history`: writes a `HistoryCapture` to SQLite (append/dedup/index/views); owns its own connection |
+| `HistoryCapture`                                                  | Frozen, MT5-independent bundle returned by `capture_history_datasets` and consumed by `persist_history_datasets`           |
+| `RateTarget`, `build_rate_targets`                                | Neutral `(symbol, timeframe)` series descriptors                                                                           |
+| `load_rate_series_from_sqlite`, `load_rate_series_by_granularity` | Load normalized `rates` series or explicit custom tables; reject invalid targets clearly                                   |
 
 See [History Collection (SQLite)](history.md) for the canonical schema, loading contract, and ER diagrams.
 
+`update_history(client=...)` is exactly `capture_history_datasets(client=...)`
+followed by `persist_history_datasets(...)` on the returned capture (skipped
+when it is `None`, i.e. no datasets selected). Downstream applications that
+must keep SQLite writes off an MT5-bound thread — for example a live trading
+loop that cannot block on database I/O — call `capture_history_datasets` on
+the thread holding the connected client, hand the returned `HistoryCapture` to
+a separate persistence worker, and call `persist_history_datasets` there;
+`persist_history_datasets` never accesses MT5 or any connection-scoped MT5
+state. Capturing again for the same `output` before a prior capture has been
+persisted re-reads the same not-yet-advanced incremental cursor and may
+re-fetch an overlapping range (safe under `deduplicate=True`, but wasteful);
+callers that queue persistence work should avoid capturing a new batch for a
+target while one is still pending.
+
 Shared package-root helpers used by downstream adapters include `Dataset`,
 `parse_timeframe`, and `resolve_history_timeframes`. These are stable exports;
 downstream applications should not import them from `mt5cli.utils` or
@@ -184,16 +203,28 @@ idempotent (`CREATE TABLE IF NOT EXISTS`, `DROP VIEW IF EXISTS` + `CREATE
 VIEW`, `CREATE INDEX IF NOT EXISTS`). Missing source tables are skipped with a
 warning rather than raising an error.
 
-| Symbol                             | Role                                                                                        |
-| ---------------------------------- | ------------------------------------------------------------------------------------------- |
-| `update_observability`             | Append one timestamped snapshot row per data type from a connected client implementation    |
-| `update_observability_with_config` | Standalone wrapper: opens/closes MT5 connection automatically around `update_observability` |
-
-Both functions write to the SQLite path given by `output=`. The optional
-`symbols` parameter filters `positions_get` / `orders_get` by symbol.
-`with_grafana_schema=False` (default) skips Grafana view/index setup; run
-`grafana-schema` once to set up the schema, then call `snapshot` repeatedly
-without this flag.
+| Symbol                             | Role                                                                                                                                      |
+| ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
+| `update_observability`             | Append one timestamped snapshot row per data type from a connected client implementation                                                  |
+| `update_observability_with_config` | Standalone wrapper: opens/closes MT5 connection automatically around `update_observability`                                               |
+| `capture_observability_snapshot`   | MT5-bound half of `update_observability`: reads account/position/order/terminal state, returns an `ObservabilitySnapshot`, writes nothing |
+| `persist_observability_snapshot`   | MT5-free half of `update_observability`: writes an `ObservabilitySnapshot` to SQLite; owns its own connection                             |
+| `ObservabilitySnapshot`            | Frozen, MT5-independent bundle returned by `capture_observability_snapshot` and consumed by `persist_observability_snapshot`              |
+
+`update_observability` and `persist_observability_snapshot` write to the
+SQLite path given by `output=`. The optional `symbols` parameter filters
+`positions_get` / `orders_get` by symbol. `with_grafana_schema=False`
+(default) skips Grafana view/index setup; run `grafana-schema` once to set up
+the schema, then call `snapshot` repeatedly without this flag.
+
+`update_observability(client=...)` is exactly
+`capture_observability_snapshot(client=...)` followed by
+`persist_observability_snapshot(...)`. As with history, a downstream
+application that must keep SQLite writes off an MT5-bound thread calls
+`capture_observability_snapshot` on the thread holding the connected client
+and hands the returned `ObservabilitySnapshot` to a separate persistence
+worker; `persist_observability_snapshot` never accesses MT5 or any
+connection-scoped MT5 state.
 
 Pass the `MT5Client` yielded by `mt5_session()` directly to both
 `update_history(client=...)` and `update_observability(client=...)`. These