Fix: ALPHA-INSIDER received every alert and never placed an order

[mpont91]

The fund polls aware_alerts, finds them, and trades nothing. Four gates in sequence, none of which logs above debug except the first.

1. No token to trade. The detector writes market_slug and direction but never a token_id, and InsiderFollowStrategy cannot place an order without knowing which outcome token to buy:

WARN InsiderFollowStrategy : Alert 1dda9d4c... missing token_id in metadata     (x130)

The alerts now carry one, resolved in a single batch query per run from the (market_slug, outcome) pairs they name. Markets whose outcomes are not labelled Yes/No — a sports market names the teams — fall back to the outcome index, where 0 is YES/UP and 1 is NO/DOWN. An outcome with no trades on record resolves to nothing and the alert goes out without a token, which the strategy skips rather than guessing.

2. NEW_ACCOUNT_WHALE named a side, not an outcome. It set direction from argMax(side, total_bet), so 872 alerts carried BUY or SELL. InsiderAlert.direction is documented as "YES" or "NO" and everything downstream reads it as the outcome. It groups on outcome now.

3. determineAction read the direction as a side. Wrong in both directions: "NO" mapped to SELL, when following someone entering the No outcome means buying the No token; and anything outside six hardcoded words returned null, so every alert on a team-named market was discarded as "could not determine action". The action comes from the alert type now, which is what actually separates an entry from an exit — the outcome is already pinned by token_id.

4. No strength, so everything was filtered. ActiveFundExecutor.validateSignal drops a signal whose strength is below config.minStrength, which forInsiderStrategy sets to 0.60. The detector never emitted the field, so every signal took the consumer's 0.5 default and failed the check — at debug level, so the fund looked like it was accepting alerts and simply choosing not to act.

Derived from severity, whose levels already state how actionable each is: LOW is "interesting but not actionable" and MEDIUM "worth monitoring", so both stay under the bar; HIGH is "consider following" and CRITICAL "act quickly", so both clear it.

After

INFO ActiveFundExecutor : Order submitted: sim-955c9b72-...
INFO ActiveFundExecutor : Order submitted: sim-46460d10-...

Seven executions in the first ten minutes.