trading_bot_v4

root/trading_bot_v4

Fork 0

Commit Graph

Author	SHA1	Message	Date
mindesbunister	ba1fe4433e	feat: Indicator score bypass - v11.2 sends SCORE:100 to bypass bot quality scoring Changes: - moneyline_v11_2_indicator.pinescript: Alert format now includes SCORE:100 - parse_signal_enhanced.json: Added indicatorScore parsing (SCORE:X regex) - execute/route.ts: Added hasIndicatorScore bypass (score >= 90 bypasses quality check) - Money_Machine.json: Both Execute Trade nodes now pass indicatorScore to API Rationale: v11.2 indicator filters already optimized (2.544 PF, +51.80% return). Bot-side quality scoring was blocking proven profitable signals (e.g., quality 75). Now indicator passes SCORE:100, bot respects it and executes immediately. This completes the signal chain: Indicator (SCORE:100) → n8n parser (indicatorScore) → workflow → bot endpoint (bypass)	2025-12-26 11:40:12 +01:00
mindesbunister	c5b27ad802	fix: Use getUserAccount().orders instead of non-existent getOpenOrders()	2025-12-13 17:39:43 +01:00
mindesbunister	5d5868d802	critical: Fix Smart Validation Queue blockReason mismatch (Bug #84 ) Root Cause: check-risk endpoint passes blockReason='SMART_VALIDATION_QUEUED' but addSignal() only accepted 'QUALITY_SCORE_TOO_LOW' → signals blocked but never queued Impact: Quality 85 LONG signal at 08:40:03 saved to database but never monitored User missed validation opportunity when price moved favorably Fix: Accept both blockReason variants in addSignal() validation check Evidence: - Database record cmj41pdqu0101pf07mith5s4c has blockReason='SMART_VALIDATION_QUEUED' - No logs showing addSignal() execution (would log '⏰ Smart validation queued') - check-risk code line 451 passes 'SMART_VALIDATION_QUEUED' - addSignal() line 76 rejected signals != 'QUALITY_SCORE_TOO_LOW' Result: Quality 50-89 signals will now be properly queued for validation	2025-12-13 17:24:38 +01:00

Author

SHA1

Message

Date

mindesbunister

ba1fe4433e

feat: Indicator score bypass - v11.2 sends SCORE:100 to bypass bot quality scoring

Changes:
- moneyline_v11_2_indicator.pinescript: Alert format now includes SCORE:100
- parse_signal_enhanced.json: Added indicatorScore parsing (SCORE:X regex)
- execute/route.ts: Added hasIndicatorScore bypass (score >= 90 bypasses quality check)
- Money_Machine.json: Both Execute Trade nodes now pass indicatorScore to API

Rationale: v11.2 indicator filters already optimized (2.544 PF, +51.80% return).
Bot-side quality scoring was blocking proven profitable signals (e.g., quality 75).
Now indicator passes SCORE:100, bot respects it and executes immediately.

This completes the signal chain:
Indicator (SCORE:100) → n8n parser (indicatorScore) → workflow → bot endpoint (bypass)

2025-12-26 11:40:12 +01:00

mindesbunister

c5b27ad802

fix: Use getUserAccount().orders instead of non-existent getOpenOrders()

2025-12-13 17:39:43 +01:00

mindesbunister

5d5868d802

critical: Fix Smart Validation Queue blockReason mismatch (Bug #84 )

Root Cause: check-risk endpoint passes blockReason='SMART_VALIDATION_QUEUED'
but addSignal() only accepted 'QUALITY_SCORE_TOO_LOW' → signals blocked but never queued

Impact: Quality 85 LONG signal at 08:40:03 saved to database but never monitored
User missed validation opportunity when price moved favorably

Fix: Accept both blockReason variants in addSignal() validation check

Evidence:
- Database record cmj41pdqu0101pf07mith5s4c has blockReason='SMART_VALIDATION_QUEUED'
- No logs showing addSignal() execution (would log '⏰ Smart validation queued')
- check-risk code line 451 passes 'SMART_VALIDATION_QUEUED'
- addSignal() line 76 rejected signals != 'QUALITY_SCORE_TOO_LOW'

Result: Quality 50-89 signals will now be properly queued for validation

2025-12-13 17:24:38 +01:00

3 Commits