AXIS v2.25.2

[2.25.2] — 2026-10-20

Added

• The dataset flush reaches the engine. AXIS caches the venue's OHLCV twice: in the local dataset store and in the engine's series store (the shared venue cache behind GET /data/series). Flushing only the local side left the engine serving the old — stale, holed — window, and the live path mirrors the engine's copy. Settings → Data → "Flush dataset manager" now also drops the engine's series for every key AXIS knows about (per key — the engine's store is shared), and the MCP exposes it as engine.flush.

Fixed

• A dataset write that was queued before a reset no longer repopulates the store. The suite resets the shared singletons between files, and a write that was still queued when the reset ran landed in the next file's mirror — a dataset the next file never created, which then failed its "the mirror is empty" assertion (order-dependent, CI-only). A queued write now carries the store's generation and is dropped when the store was reset underneath it.
• A live apply keeps the script's input descriptors. The socket payload carries the values, not the run's metadata, so a live apply replaced the run's input list with an empty one (the Results panel and the Script Settings modal read it from there). The descriptors of the script's last full run are carried over.
• A live script subscription now covers the chart's whole window. The socket subscribed the script with the series depth — the short live snapshot (500 bars), which is right for the chart's own OHLCV (the chart is painted from REST) but wrong for a script: the engine's script state was 500 bars deep, so every live apply repainted the indicator over the last 500 bars only, blanked the rest of the window and collapsed the script's band fill with it. The script subscription now asks for the chart's own depth (capped by the Rolling window).
• A script's input values now reach the engine. The live socket subscribed the script without its inputs, so the engine evaluated it with the Pine defaults: changing an input (a Keltner channel length, an EMA period) repainted the chart with the new values and the next live tick overwrote them with the old ones — the change looked like it did nothing. The values now travel with the subscribe frame, and a changed value re-subscribes (the engine keys its session on the inputs).

---

Desktop installers (Tauri 2). CLI tarball, worker bundle, and checksums attach from the Release workflow.