Binary Trading AI Engine v6.0.7

Release Date: September 4, 2026 Tags: DASHBOARD, CORRECTNESS

Requires Core v6.7.6.

Overview

A correctness cleanup with no change an operator will see, and one comment that was wrong. The admin dashboard's high-severity action feed filtered on a list of action types that included two the column cannot hold: RISK_ALERT and WHALE_ORDER_DETECTED are not among the twenty values of binaryAiEngineAction.actionType.

The feed was already correct — a term an enum column can never hold matches nothing — so no row appears or disappears in this release.

What is worth recording is the reason the file gave for keeping one of them. It said WHALE_ORDER_DETECTED was retained "so an older install that wrote the other spelling still surfaces". An enum column cannot hold a value outside its own list at any age of install: no row has ever carried it, on any install, and none could. The comment described a compatibility concern that was never possible, which is the kind of reasoning that keeps dead code alive indefinitely.

Both terms were already known to be dead — the file said so in its own comment. What changed is that a scanner added to the build in this cycle now fails the gate on any enum literal a column cannot hold, so the terms, and the reasoning that had kept them, had to go.

Update Instructions

# 1. Update the addon in Admin → System → Extensions
# 2. Restart the backend
pnpm updator

No schema change, no seeder, no .env change, and no row moves.

Fixed

• Fixed — the high-severity action feed listed RISK_ALERT and WHALE_ORDER_DETECTED among the action types it matches; neither is a value of that column. Both terms are removed, along with the comment that justified one of them with a backwards-compatibility case an enum column makes impossible.