URGENT — Review & Certify MT5 Trade Engine Module (5 Days)

We have a professionally built MT5 Expert Advisor with pre-written code ready. We need an experienced MQL5 developer to REVIEW, FIX, and CERTIFY the ENGINE MODULE.

YOU ARE NOT BUILDING FROM SCRATCH.

You are reviewing 8 existing .mqh files. WHAT YOU WILL DO:

1. Review 8 pre-written .mqh engine files

2. Fix known shutdown bug: "invalid pointer access in AlmudoEngine.mqh (60,10)"

3. Achieve ZERO warnings in MT5 Build 4500+

4. Verify custom mutex (m_trade_lock) is bulletproof

5. Confirm all 8 callback interface points fire correctly

6. Write 1 unit test script

FILES YOU WILL RECEIVE:

- AlmudoEngine_Types.mqh (READ ONLY - do not change)

- IAlmudoEngineCallback.mqh (READ ONLY - do not change)

- AlmudoEngine_TradeLock.mqh (Review and fix)

- AlmudoEngine_Execution.mqh (Review and fix)

- AlmudoEngine_PositionMgmt.mqh (Review and fix)

- AlmudoEngine_Filters.mqh (Review and fix)

- AlmudoEngine_Signals.mqh (Review and fix)

- AlmudoEngine.mqh (Review and fix)

STRICT NON-NEGOTIABLE RULES:

- No DLL imports anywhere

- No Sleep() calls — only GetTickCount()

- Magic Number constant: ALMUDO_EA_MAGIC = 26052026

- Zero compilation warnings

- All class names keep CAlmudo_ prefix

- All member variables keep m_ prefix

- NDA must be signed before code is shared

KNOWN BUG (Priority Fix):

"invalid pointer access in AlmudoEngine.mqh (60,10)" This crashes on EA shutdown. Fix the destructor pointer cleanup sequence.

DELIVERABLES:

- All 8 certified .mqh files (5 days)

- 1 unit test .mq5 script

- Changelog documenting every fix

MILESTONE PAYMENT STRUCTURE:

Day 2: TradeLock + Callback interface ($30) -

Day 4: Execution + Filters + Signals ($30) -

Day 5: Full engine + bug fix + test script ($40)

SCREENING QUESTION (must answer to be considered):

What causes "invalid pointer access" in MQL5 and how do you fix it? Give a code example.