Release v0.13.0 — Futu OpenD connector and data substrate hardening · byteseek/Mira

Highlights

Adds an optional read-only Futu OpenD connector for tools/mira_data.
- New fetch families: futu_market_price, futu_historical_bars, futu_option_chain, and futu_future_info.
- New mira_data futu probe command for local OpenD connectivity checks.
- MIRA_MARKET_DATA_DEFAULT_SOURCE=futu_opend can route generic market_price and technical OHLCV workflows to the local connector.
Registers futu_opend_local as a private authorized local quote gateway in the source registry and evidence policy.
Documents the Futu private-data boundary in docs/futu-private-data.md: quote-only, no trade context, no order placement, and raw provider/account artifacts stay under private/.
Hardens the Mira data substrate from the post-v0.12.0 fixes:
- bounded retry handling for transient HTTP/body decode failures,
- SEC companyfacts ticker-map resilience,
- source-registry hardening,
- regression tests wired into the local quality gate.
Fixes issue-triage root causes from #102:
- skill frontmatter validation,
- compact analysis-routing entrypoint with full reference split-out,
- clearer question-lens and evidence-surface boundaries.

python scripts/run_quality_gate.py
- py_compile: pass
- mira_data_futu_tests: pass
- mira_data_net_tests: pass
- repo_validation_contract_tests: pass
- repo_validation: pass
- release_gate: pass
python scripts/validate_repo.py reports 0 errors; existing stale-after warnings are historical research-case freshness warnings.

Futu OpenD support is optional and requires the user's own local OpenD session plus the optional futu-api Python package.
The connector is market-data/read-only research infrastructure. It is not autonomous trading infrastructure and does not create a trading context.
Broker/provider raw artifacts, entitlement notes, and account-specific data remain private machine state, not tracked product state.