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 ✅

.github/copilot-instructions.md

@@ -69,6 +69,74 @@ User is building from $901 → $100,000+ with this system. Every bug costs money
 
 ---
 
+## 📋 MANDATORY: ROADMAP MAINTENANCE - NO EXCEPTIONS
+
+**THIS IS A CRITICAL REQUIREMENT - NOT OPTIONAL**
+
+### Why Roadmap Updates Are MANDATORY
+
+User discovered critical documentation bug (Nov 27, 2025):
+- Roadmap said: "Phase 3: Smart Entry Timing - NOT STARTED"
+- Reality: Fully deployed as Phase 7.1 (718-line smart-entry-timer.ts operational)
+- User confusion: "i thought that was already implemented?" → User was RIGHT
+- **Result:** Documentation misleading, wasted time investigating "next feature" already deployed
+
+### IRON-CLAD RULES for Roadmap Updates
+
+**1. UPDATE ROADMAP IMMEDIATELY AFTER DEPLOYMENT**
+- ✅ Phase completed → Mark as COMPLETE with deployment date
+- ✅ Phase started → Update status to IN PROGRESS
+- ✅ Expected impact realized → Document actual data vs expected
+- ✅ Commit roadmap changes SAME SESSION as feature deployment
+
+**2. VERIFY ROADMAP ACCURACY BEFORE RECOMMENDING FEATURES**
+- ❌ NEVER suggest implementing features based ONLY on roadmap status
+- ✅ ALWAYS grep codebase for existing implementation before recommending
+- ✅ Check: Does file exist? Is it integrated? Is ENV variable set?
+- ✅ Example: Phase 3 "not started" but smart-entry-timer.ts exists = roadmap WRONG
+
+**3. MAINTAIN PHASE NUMBERING CONSISTENCY**
+- If code says "Phase 7.1" but roadmap says "Phase 3", consolidate naming
+- Update ALL references (roadmap files, code comments, documentation)
+- Prevent confusion from multiple names for same feature
+
+**4. ROADMAP FILES TO UPDATE**
+- `1MIN_DATA_ENHANCEMENTS_ROADMAP.md` (main detailed roadmap)
+- `docs/1MIN_DATA_ENHANCEMENTS_ROADMAP.md` (documentation copy)
+- `OPTIMIZATION_MASTER_ROADMAP.md` (high-level consolidated view)
+- Website roadmap API endpoint (if applicable)
+- This file's "When Making Changes" section (if new pattern learned)
+
+**5. ROADMAP UPDATE CHECKLIST**
+When completing ANY feature or phase:
+- [ ] Mark phase status: NOT STARTED → IN PROGRESS → COMPLETE
+- [ ] Add deployment date: ✅ COMPLETE (Nov 27, 2025)
+- [ ] Document actual impact vs expected (after 50-100 trades data)
+- [ ] Update phase numbering if inconsistencies exist
+- [ ] Commit with message: "docs: Update roadmap - Phase X complete"
+- [ ] Verify website roadmap updated (if applicable)
+
+**6. BEFORE RECOMMENDING "NEXT FEATURE"**
+```bash
+# 1. Read roadmap to identify highest-impact "NOT STARTED" feature
+cat 1MIN_DATA_ENHANCEMENTS_ROADMAP.md | grep "NOT STARTED"
+
+# 2. VERIFY it's actually not implemented (grep for files/classes)
+grep -r "SmartEntryTimer" lib/
+grep -r "SMART_ENTRY_ENABLED" .env
+
+# 3. If files exist → ROADMAP WRONG, update it first
+# 4. Only then recommend truly unimplemented features
+```
+
+**WHY THIS MATTERS:**
+
+User relies on roadmap for strategic planning. Wrong roadmap = wrong decisions = wasted development time = delayed profit optimization. In a real money system, time wasted = money not earned.
+
+**Outdated roadmap = wasted user time = lost profits**
+
+---
+
 ## Mission & Financial Goals
 
 **Primary Objective:** Build wealth systematically from $106 → $100,000+ through algorithmic trading