SKANDER servertelegram v3.7.1 — Direction Parser Validation
Date: 2026-08-29

ROOT CAUSE: CONFIRMED
The old parser scanned the full Telegram post and matched the standalone token UP inside the referral URL path `sign-up`, so a real Arabic PUT signal could become CALL before the parser evaluated `هبوط 🔴`.

REPRODUCTION BEFORE FIX:
Input direction: الاتجاه : هبوط 🔴
Referral: https://broker-qx.pro/sign-up/?lid=1757108
Old parsed direction: CALL  <-- WRONG

FIX:
PASS explicit direction label has first priority
PASS Arabic هبوط / red emoji => PUT
PASS Arabic صعود / green emoji => CALL
PASS URL text removed before generic fallback direction scan
PASS UP/DOWN only used as final fallback
PASS real-time Telegram edit/update protocol preserved
PASS package/server version bumped to 3.7.1

TESTS EXECUTED:
npm run check: PASS
npm test: PASS
v3.7.1 URL-safe direction regression: PASS
PUT with sign-up URL => PUT
CALL with sign-up URL => CALL

DEPLOYMENT:
Preserve existing .env and data/state.json on hosting.
Replace server source files, then Restart Node.js app in cPanel.