Delete the rotation queue; sponsors.json stays as the member directory

Marty (2026-09-19): delete it if it no longer serves a purpose. The public link has run on the
chain walk since the mode flip and the queue's active head never received a join. Gone:
active/waiting/qualified statuses, normalizeStatuses, activeSponsor, publicSponsorPayload, the
increment/activate/qualify/reset actions, the click counter, the auto-count/auto-advance/
level-sync block, the legacy queue branches in current-sponsor and the submit-id classifier,
the chatbot's "placements waiting" facts, and the queue columns and buttons in admin. What stays
is a member directory (name, parent, level, notes, contact email) because the payout alerts and
the feed's name map read it. The chain walk is the only company rotation now.

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

public/chat.js

@@ -106,7 +106,7 @@
     {k:['after join','next','what happens','confirmed','joined','i bought','i am in'],
      a:()=>`Once your position is confirmed: tell the team your new RM Circle ID and your sponsor ID (in the Telegram group: ${tgLink('here')}) so your placement gets mapped. Then your job is simple — get your 2 directs, and when you're qualified, help your 2 get their 2.`},
     {k:['waiting','queue','line','how long','when my turn'],
-     a:()=>{const w=sponsorInfo&&typeof sponsorInfo.waitingCount==='number'?sponsorInfo.waitingCount:null;return `${w!==null?`Right now there ${w===1?'is':'are'} <strong>${w}</strong> team placement${w===1?'':'s'} waiting behind the current sponsor. `:''}The queue moves every time a position qualifies with its 2 directs — the more the team helps each other, the faster it rotates.`}},
+     a:()=>`The company rotation always offers the next open position in the team tree, read live from the blockchain. It moves the moment that position gets its 2 directs. A member's own invite link is different: it places people inside that member's own team.`},
   ];
 
   function answer(q){