[stefan-jansen]

Closes #95

Outcome

Select the stored adapter before provider history-limit checks and actual incremental fetching, not only when rewriting metadata. Explicit arguments still win; legacy empty/auto metadata still uses routing. This prevents acquisition from failing or choosing a different source while metadata claims the stored provider was reused.

Executed verification

• Regression-only a0b589e, production identical to main55b86e2: two real public DataManager/SyntheticProvider/storage workflows fail to route SPY despite a recorded synthetic provider. Four explicit-override/atomic-failure controls pass. Both Flat and Hive are exercised; no mocked acquisition ignores provider selection.
• Fix8ff2fa0: 18 passed /52 deselected across tests/test_update_provider_reuse.py and provider/metadata cases in tests/test_data_manager_storage.py, with POLARS_MAX_THREADS=1 and ResourceWarning as error.
• Ruff lint/format, ty, diff check and commit hooks pass. Full supported/resource/coverage/package/ecosystem and documentation workflows must pass at the exact head before ordinary merge. No local full suite during Backtest's timing reservation.

Scope and assistance

One acquisition selection defect, two production lines, one regression file. Calendar repairs remain in their existing PR92/94. AI-assisted reproduction and repair under maintainer direction, reviewed by owner for explicit precedence, legacy auto semantics, metadata identity and atomic failure. No release/deploy or changes to published0.2.1.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.