- **A-window (600-bar window vs full history)**: f6_eqpos (54.9%), f14/f15 dist (31%/30%), f17_range (54.9%) — LARGE in strong-trend regimes: range_atr 56.99 vs 10.44; eqpos -21 vs -0.86. **The README claim "practically does not change results" is REFUTED by measurement.**
- **B-formula**: f10_eqh (98.5%), f11_eql (100%) — EQ semantics (Python same-type pairs + pivot-bar ATR vs EA/v4.4 consecutive-list pairs + current ATR) -> **FLAG=BLOCKING DESIGN DECISION**. f0-f2 HTF bias (36-51%) — EA output not reproduced by a faithful replica on the same data -> EA D1 cache content in the tester differs; root cause **NOT FULLY TRACED** -> **FLAG=BLOCKING**. f18_conf (52%) = derived from f0-f2/EQ.
- Lesson: my initial "mom off-by-one" finding was **WRONG** (misread of the tc/tcv convention); the harness caught the mistaken fix and the revert restored perfect parity.
- Test A (AUC metric): **PASS** · Test B (purge): **PASS** · Test C (parity harness): report + clean-rate features + design flags · Test D: `build_features --selftest` B1-B5 **PASS**, `train_hybrid --selftest` B1-B5 **PASS**, EA compile **0/0**.
1. f0-f2 HTF bias (36-51%): root cause not yet fully traced (needs an EA BTTFBias input debug dump in the tester). **BLOCKING.**
2. f10/f11 EQ: design decision (training vs live v4.4/EA) — do not silently align. **BLOCKING.**
3. f6/f14/f15/f17 window (54.9%): runtime 600-bar != full-history training in strong-trend regimes — potential explanation for the runtime AUC drop 0.627->0.5305. Design decision: stateful runtime (stream from the start) vs retrain with the window. **LARGEST ECONOMIC IMPACT.**
4. v4.4 live shares EQ semantics with the EA; v4.4 HTF bias not yet verified (only the EA was tested).
Do NOT build LSTM/Informer/MS-GARCH/meta-gate. P2 = resolve the 3 design decisions (EQ, HTF bias, window) via: (a) EA debug dump to trace f0-f2; (b) user decision for the EQ & window source of truth; (c) align runtime<->training according to the decision; (d) re-measure parity and re-run the CSV mode-0 backtest on the parity-corrected basis. Only then evaluate H0/H1 (regime-aware ML).