Catch eligibility: catcher needs level >= the level the buyer is LEAVING, not the level being bought

Matches _payUpline (level > levelIndex, levelIndex = buyer.level-1). The old
depth+1 rule told #21 (Culmen) it could not catch #49's Apex buy; #21 is #49's
4th matrix upline and does catch it. Fixed in the owner alert, coaching scan,
dashboard pipeline, AI prompt, leader digest, chatbot and how-pay-works copy.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

public/suite-leader.js

@@ -48,7 +48,7 @@
           '<td>' + (r.upgradeCost ? n(r.upgradeCost) : '—') + '</td></tr>';
       }).join('');
       out.push('<div class="l-sec"><h2>Money forming they can\'t catch</h2>' +
-        '<div class="why">A position only catches an upgrade payment if it is qualified <em>and</em> already at or above the level being bought. These people have activity underneath them that is passing them by — the fastest, kindest conversation you can have this week.</div>' +
+        '<div class="why">A position only catches an upgrade payment if it is qualified <em>and</em> already at or above the level the buyer is leaving. These people have activity underneath them that is passing them by — the fastest, kindest conversation you can have this week.</div>' +
         '<div class="table-wrap"><table class="l-tbl"><thead><tr><th>Position</th><th>Level</th><th>What they need</th><th>POL passing them</th><th>Earned</th><th>Upgrade cost</th></tr></thead><tbody>' +
         rows + '</tbody></table></div></div>');
     }