Rebrand public site to RM Circle Team Build (remove Crypto Team Build Network)

Public promo is now RM-Circle-only; the Crypto Team Build Network is learned
after joining, not surfaced to prospects.
- nav brand "Crypto Team Build" -> "RM Circle" (subtitle "Premium Team Build")
- all <title>, og:site_name, twitter meta, footers, disclaimers, 404, chatbot
  system prompt + canned answers, config siteName/supportLabel swept
- removed "a project of the Crypto Team Build Network" framing from prose
- banners regenerated: eyebrow now "The RM Circle · Polygon" (was Crypto Team Build)
- og-card.jpg regenerated (was "CRYPTO TEAM BUILD NETWORK PRESENTS")
- roadmap.webp already RM-Circle branded (no change needed)
- social posts/swipes: #CryptoTeamBuild -> #RMCircle, "crypto team build" -> "RM Circle team build"

Videos still reference old branding (VO + embedded site screenshot) — rebuilt next.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

server.js

@@ -32,7 +32,7 @@ function chatRateLimited(ip) {
 function chatSystemPrompt() {
   const c = getConfig(), sponsors = getSponsors(), a = activeSponsor(sponsors);
   const waiting = sponsors.filter(s=>s.status==='waiting').length;
-  return `You are "Team Help", the assistant on ${c.siteName || 'Crypto Team Build'} (https://rmcircle.team), the team site for the RM Circle Premium team build — a project of the Crypto Team Build Network.
+  return `You are "Team Help", the assistant on ${c.siteName || 'RM Circle Team Build'} (https://rmcircle.team), the team site for the RM Circle Premium team build.
 
 FACTS:
 - Strategy: enter RM Circle dApp at Premium tier (${c.premiumEntryPol || 362} POL on Polygon Mainnet, chain ID 137, POL is the gas token). Each member gets 2 directs to become "qualified"; the team then recommends retiring that link and helping those 2 get their 2 with their OWN links (moving-link strategy) — a position only qualifies through its own directs. If an extra signup lands on a qualified link anyway, present it as a BONUS, not a rule violation: it still pays that member the full entry reward and spills downward into the first open slot in their leg (depth). Spillover never qualifies the people below.
@@ -523,7 +523,7 @@ function serveMemberPage(req,res,file,kind,id){
   const img=`${base}/og-card.jpg`;
   const og=[
     `<meta property="og:type" content="website">`,
-    `<meta property="og:site_name" content="Crypto Team Build Network">`,
+    `<meta property="og:site_name" content="RM Circle Team Build">`,
     `<meta property="og:title" content="${title}">`,
     `<meta property="og:description" content="${desc}">`,
     `<meta property="og:url" content="${url}">`,
@@ -559,7 +559,7 @@ const server=http.createServer(async(req,res)=>{
     if(file&&staticFile(req,res,file))return;return staticFile(req,res,path.join(PUBLIC_DIR,'404.html'),404);
   }catch(e){console.error(e);json(res,500,{error:'Internal server error'});}
 });
-server.listen(PORT,()=>{console.log(`Crypto Team Build sponsor router running on http://localhost:${PORT}`);if(ADMIN_PASSWORD==='changeme')console.warn('WARNING: Set ADMIN_PASSWORD before production deployment.');});
+server.listen(PORT,()=>{console.log(`RM Circle Team Build sponsor router running on http://localhost:${PORT}`);if(ADMIN_PASSWORD==='changeme')console.warn('WARNING: Set ADMIN_PASSWORD before production deployment.');});
 // Team-activity alerts: any NEW on-chain event at/below config.teamRootId goes
 // to the Telegram group topic, with the sponsor's contact email when we have it.
 // Owner upgrade watcher: emails/Telegrams when an owned position (config.ownerIds)