PyneCore v6.6.0 released — PyneCore becomes a platform: data sources, live streaming,…

Plugin system

• One pyne.plugin entry-point group with a layered hierarchy — ProviderPlugin -> LiveProviderPlugin -> BrokerPlugin, and CLIPlugin as a parallel axis; capabilities compose via multiple inheritance. Install a package and PyneCore finds it at startup — no registration, no config edits.
• pyne plugin list / pyne plugin info <name> enumerate installed plugins and their capabilities (--json for tooling); self-healing per-plugin workdir/config/plugins/<name>.toml generated from a typed Config.
• Pluggable CLI: plugins mount pyne <name> … subcommands and inject --flags into run and data download.

Data & tooling

• Interactive data-download TUI: run pyne data download with just a provider name for a full-screen browse/search/inspect/download UI, with provider and broker pickers.
• Provider strings provider:[broker:]symbol[@timeframe] unified across pyne data download, pyne run and request.security(); --chunk-size, --extra-data, resumable -f continue, and data-gap reporting.
• Structured visual output pyne run --viz writes NDJSON of full plot/drawing state; completes the Pine plot family (plotcandle, plotbar, barcolor, three-form fill, …).

Live & broker trading

• Live mode pyne run --live streams beyond history with tick-accurate strategies, a feed-liveness watchdog and graceful shutdown.
• Broker trading pyne run --broker: venue-agnostic execution engine with exactly-once client-order ids, idempotent restart/reconnect recovery and a shared SQLite journal; ships capitalcom, bybit and ctrader plugins.

Pine engine

• New barmerge.lookahead_last_closed mode and the @pyne edge script variant.

Status — the plugin system, the data TUI and structured visual output are stable; the live and broker layers are new and should be treated as a release candidate, so run brokers against demo/paper accounts for now.

Full release notes: https://github.com/PyneSys/pynecore/releases/tag/v6.6.0