Update documentation to reflect new polling architecture

Update replit.md to document the change from HTTP-based sync to bot polling for new posts, including the polling interval and architectural improvements.

Replit-Commit-Author: Agent
Replit-Commit-Session-Id: 9203795e-937a-4306-b81d-b4d5c78c240e
Replit-Commit-Checkpoint-Type: intermediate_checkpoint
Replit-Commit-Event-Id: 66425bcd-ee56-43a1-bb31-0b7f812183fd
Replit-Commit-Screenshot-Url: https://storage.googleapis.com/screenshot-production-us-central1/7c94b7a0-29c7-4f2e-94ef-44b2153872b7/9203795e-937a-4306-b81d-b4d5c78c240e/duiWnI1
Replit-Helium-Checkpoint-Created: true

.replit

@@ -52,6 +52,10 @@ externalPort = 80
 localPort = 8044
 externalPort = 3003
 
+[[ports]]
+localPort = 35709
+externalPort = 3002
+
 [[ports]]
 localPort = 38557
 externalPort = 3000

replit.md

@@ -145,12 +145,12 @@ https://supabase.aethex.tech/auth/v1/callback
 ## Recent Changes (December 3, 2025)
 - ✅ **Bidirectional Discord-Feed Bridge**: Full two-way sync between Discord and AeThex feed
   - **Discord → AeThex**: Messages from Discord FEED channel sync to community feed
-  - **AeThex → Discord**: Posts created in AeThex appear in Discord with rich embeds
+  - **AeThex → Discord**: Bot polls Supabase every 5 seconds for new posts (works from production!)
   - Bot listens to configured channel (DISCORD_MAIN_CHAT_CHANNELS env var)
   - Posts display with purple Discord badge and channel name
   - Supports images/videos from both platforms
   - Loop prevention: Discord-sourced posts don't re-post back to Discord
-  - API endpoint: Discord bot exposes `/send-to-discord` for main server to call
+  - **Architecture**: Bot polls `community_posts` table directly - no HTTP dependency on server
 - ✅ **Moved /feed to /community/feed**: Feed is now a tab within the Community page
   - Old /feed URL redirects to /community/feed
   - Added redirect in vercel.json for production