chore: migrate domain asepharyana.tech to asepharyana.my.id

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

docs/superpowers/specs/2026-05-17-telegram-uploader-backend-design.md

@@ -35,7 +35,7 @@ Production-ready backend untuk Telegram file uploader dengan dual upload methods
 4. Bot extracts `telegram_file_id`, `telegram_file_unique_id`, `storage_message_id`
 5. Bot generates `public_id` using nanoid
 6. Bot saves metadata to PostgreSQL
-7. Bot replies with download link: `https://tele.asepharyana.tech/f/{public_id}`
+7. Bot replies with download link: `https://tele.asepharyana.my.id/f/{public_id}`
 
 #### Upload via HTTP API
 1. Client POSTs to `/api/upload` with file (multipart or base64)
@@ -115,7 +115,7 @@ fileName: optional_filename.ext
   "size_bytes": 1024000,
   "file_type": "document",
   "created_at": "2026-05-17T23:42:19Z",
-  "download_url": "https://tele.asepharyana.tech/f/abc123xyz"
+  "download_url": "https://tele.asepharyana.my.id/f/abc123xyz"
 }
 ```
 
@@ -212,7 +212,7 @@ schema.sql
 ```
 BOT_TOKEN=<telegram_bot_token>
 STORAGE_CHANNEL_ID=<private_channel_id>
-BASE_URL=https://tele.asepharyana.tech
+BASE_URL=https://tele.asepharyana.my.id
 DATABASE_URL=postgresql://user:password@localhost:5432/telegram_uploader
 PORT=3000
 NODE_ENV=production