docs: CRITICAL - Fix roadmap Phase 7.1/7.2 status + add MANDATORY update requirements

PROBLEM DISCOVERED (Nov 27, 2025):
User: "whats next on our roadmap with the biggest impact?"
Agent: "Phase 3 Smart Entry Timing - NOT STARTED"
User: "i thought that was already implemented?" ← USER WAS RIGHT!
Reality: Phase 3 = Phase 7.1 (smart-entry-timer.ts, 718 lines, DEPLOYED)

ROOT CAUSE:
- Roadmap said "Phase 3: NOT STARTED"
- Code reality: Phase 7.1 Smart Entry Timer fully operational
- Phase 7.2 Signal Quality Validation also deployed Nov 27
- Documentation completely out of sync with deployed code

IMPACT:
- User confusion justified (roadmap misleading)
- Wasted time investigating "next feature" already deployed
- Agent suggested implementing feature that exists
- Phase numbering confusion (Phase 2/3/7.1/7.2 mixed)

FIXES APPLIED:

1. 1MIN_DATA_ENHANCEMENTS_ROADMAP.md:
   - Phase 7.1: Smart Entry Timer → ✅ COMPLETE (DEPLOYED)
   - Added complete documentation of deployed system
   - Explained timeout protection (NO MISSED TRADES)
   - Showed ENV config (SMART_ENTRY_ENABLED=true)
   - Phase 7.2: Already marked complete (Nov 27)

2. .github/copilot-instructions.md:
   - NEW SECTION: "📋 MANDATORY: ROADMAP MAINTENANCE"
   - 6 iron-clad rules for roadmap updates
   - Update immediately after deployment (same session)
   - Verify roadmap accuracy BEFORE recommending features
   - Never suggest features based only on roadmap status
   - ALWAYS grep codebase to verify implementation
   - Checklist for roadmap updates
   - Before recommending "next feature" verification steps

MANDATORY WORKFLOW (ALL FUTURE AGENTS):
. Complete feature/phase
. Update roadmap status → COMPLETE with date
. Document actual impact (after data collection)
. Consolidate phase numbering if inconsistencies
. Commit roadmap changes SAME SESSION
. VERIFY feature exists before recommending

LESSON LEARNED:
Roadmap documentation is CRITICAL in real money system.
Wrong roadmap = wrong priorities = wasted time = lost profits.
User time is valuable - outdated docs waste it.

FILES CHANGED:
- 1MIN_DATA_ENHANCEMENTS_ROADMAP.md (Phase 7.1 marked COMPLETE)
- .github/copilot-instructions.md (MANDATORY section added)

STATUS: Documentation now reflects deployed reality ✅

1MIN_DATA_ENHANCEMENTS_ROADMAP.md

@@ -95,51 +95,46 @@ Watch logs for validation results on next Smart Entry signal (quality ≥90):
 
 ---
 
-## Phase 3: Smart Entry Timing 🎯 NEXT PRIORITY
+## Phase 7.1: Smart Entry Timer ✅ COMPLETE (DEPLOYED)
 
-**Goal:** Improve average entry price by 0.2-0.5% per trade by waiting for optimal 1-minute confirmation
+**Goal:** Improve average entry price by 0.2-0.5% per trade by waiting for optimal pullback
 
-**Status:** NOT STARTED
+**Status:** DEPLOYED and OPERATIONAL (aliased as "Phase 3" in original roadmap)
 
+**Implementation:**
+- **File:** `lib/trading/smart-entry-timer.ts` (718 lines)
+- **Configuration:** SMART_ENTRY_ENABLED=true in .env
+- **Timeout Protection:** NO MISSED TRADES - executes at market after 2 minutes
+
+**How It Works:**
 1. **Signal Arrives** (5-minute candle close)
    - Bot receives: LONG SOL-PERP, quality 95, ADX 28
    - Current price: $142.50
+   - Signal queued for smart entry
+
+2. **Monitor for Optimal Pullback** (every 15 seconds, up to 2 minutes)
+   - **LONG:** Wait for price to dip 0.15-0.50% below signal price
+   - **SHORT:** Wait for price to bounce 0.15-0.50% above signal price
+   - Track best price observed during wait period
+   - Validate ADX hasn't dropped >2 points (trend intact)
 
-2. **Wait for 1-Minute Confirmation** (up to 2 minutes)
-   - Monitor next 2 × 1-minute bars
-   - Look for:
-     * Price pullback 0.2-0.3% (LONG: price dips, SHORT: price rises)
-     * Volume spike on next bar (confirmation)
-     * ADX holds or increases (trend intact)
-   
 3. **Execute When Conditions Met**
-   - Best case: Enter at $142.15 (0.25% better than signal)
-   - Timeout: If no pullback within 2 minutes, execute at market
-   - Validation: ADX must still be >= signal ADX - 2 points
+   - **Pullback confirmed:** Enter immediately at better price (e.g., $142.15 vs $142.50)
+   - **Timeout at 2 minutes:** Execute at current market price (no missed trades)
+   - **Pullback too large (>0.50%):** Keep waiting (might be reversal, not pullback)
 
-**Implementation:**
+**Timeout Protection (lines 186-192):**
 ```typescript
-// New service: lib/trading/smart-entry-timer.ts
-class SmartEntryTimer {
-  // Queue signal for delayed execution
-  queueSignal(signal, maxWaitMs = 120000) // 2 minutes
-  
-  // Monitor 1-minute bars for optimal entry
-  monitorForEntry(signal) {
-    // Check every 1-minute bar:
-    // - Price pullback?
-    // - Volume confirmation?
-    // - ADX still strong?
-  }
-  
-  // Execute when conditions met or timeout
-  executeEntry(signal, actualPrice)
+if (now >= signal.expiresAt) {
+  console.log(`⏰ Smart Entry: Timeout for ${symbol} (waited 120s)`)
+  const currentPrice = latestPrice?.price || signal.signalPrice
+  await this.executeSignal(signal, currentPrice, 'timeout')
 }
 ```
 
 **Configuration:**
 ```bash
-# .env additions
+# .env (CURRENTLY ACTIVE)
 SMART_ENTRY_ENABLED=true
 SMART_ENTRY_MAX_WAIT_MS=120000  # 2 minutes
 SMART_ENTRY_PULLBACK_MIN=0.15   # 0.15% minimum
@@ -147,6 +142,9 @@ SMART_ENTRY_PULLBACK_MAX=0.50   # 0.50% maximum
 SMART_ENTRY_ADX_TOLERANCE=2     # ADX can't drop >2 points
 ```
 
+**Integration with Phase 7.2:**
+Smart Entry Timer runs first (wait for pullback), then Phase 7.2 validation runs (check if conditions still good), then execution. Both phases work together seamlessly.
+
 **Expected Impact:**
 - Average entry improvement: 0.2-0.5% per trade
 - On $8,000 position: $16-40 better entry