[Chore] Use fictional placeholder data in test fixtures and dev examples

.agents/skills/mock-slack-testing/SKILL.md

@@ -42,9 +42,9 @@ INSERT INTO slack_installations (organization_id, team_id, team_name, app_id, bo
 VALUES ('<org_id>', 'TROOMOTE', 'roomote-mock', 'AMOCK', 'BROOMOTE', 'xoxb-mock-token', '<user_id>', true)
 ON CONFLICT (team_id) DO NOTHING;
 
--- Seed user mapping for mock user UDAN
+-- Seed user mapping for mock user UGRACE
 INSERT INTO slack_user_mappings (slack_user_id, slack_team_id, user_id, organization_id)
-VALUES ('UDAN', 'TROOMOTE', '<user_id>', '<org_id>')
+VALUES ('UGRACE', 'TROOMOTE', '<user_id>', '<org_id>')
 ON CONFLICT ON CONSTRAINT slack_user_mappings_unique DO NOTHING;
 ```
 
@@ -103,7 +103,7 @@ curl -s -X POST http://127.0.0.1:3012/mock/events \
     "event": {
       "type": "app_mention",
       "channel": "C123ABC456",
-      "user": "UDAN",
+      "user": "UGRACE",
       "text": "<@BROOMOTE> !fast what file handles Slack mentions?",
       "ts": "1710000000.000200",
       "channel_type": "channel"

.agents/skills/mock-telegram-testing/SKILL.md

@@ -22,7 +22,7 @@ Telegram has no threads: conversation continuity is inferred from **chat id (+ f
 | Example scenario              | `packages/communication/scripts/mock-telegram.example.json` |
 | Webhook secret source         | `Env.R_TELEGRAM_WEBHOOK_SECRET` from dotenvx                |
 | Mock bot identity             | `roomote_mock_bot` (id `7000000001`)                        |
-| Mock linked user              | Telegram user id `111000111` (`dan_mock`)                   |
+| Mock linked user              | Telegram user id `111000111` (`grace_mock`)                   |
 
 ## Step 1: Seed the database
 
@@ -41,7 +41,7 @@ Then seed (adjust user_id from the query above):
 ```sql
 -- Link mock Telegram user 111000111 to a local Roomote user
 INSERT INTO telegram_user_mappings (telegram_user_id, telegram_chat_id, telegram_username, user_id)
-VALUES ('111000111', '111000111', 'dan_mock', '<user_id>')
+VALUES ('111000111', '111000111', 'grace_mock', '<user_id>')
 ON CONFLICT ON CONSTRAINT telegram_user_mappings_unique DO NOTHING;
 ```
 
@@ -92,8 +92,8 @@ curl -s -X POST http://127.0.0.1:3013/mock/events \
   -d '{
     "kind": "message",
     "message": {
-      "chat": { "id": 111000111, "type": "private", "first_name": "Dan" },
-      "from": { "id": 111000111, "first_name": "Dan", "username": "dan_mock" },
+      "chat": { "id": 111000111, "type": "private", "first_name": "Grace" },
+      "from": { "id": 111000111, "first_name": "Grace", "username": "grace_mock" },
       "text": "!fast what file handles Telegram webhooks?"
     }
   }'
@@ -104,8 +104,8 @@ curl -s -X POST http://127.0.0.1:3013/mock/events \
   -d '{
     "kind": "message",
     "message": {
-      "chat": { "id": 111000111, "type": "private", "first_name": "Dan" },
-      "from": { "id": 111000111, "first_name": "Dan", "username": "dan_mock" },
+      "chat": { "id": 111000111, "type": "private", "first_name": "Grace" },
+      "from": { "id": 111000111, "first_name": "Grace", "username": "grace_mock" },
       "text": "also check the retry logic please"
     }
   }'
@@ -117,7 +117,7 @@ curl -s -X POST http://127.0.0.1:3013/mock/events \
     "kind": "callback_query",
     "callbackQuery": {
       "id": "cbq-manual-1",
-      "from": { "id": 111000111, "first_name": "Dan", "username": "dan_mock" },
+      "from": { "id": 111000111, "first_name": "Grace", "username": "grace_mock" },
       "data": "cancel_task:<cloudJobId>",
       "message": { "message_id": 42, "chat": { "id": 111000111, "type": "private" } }
     }

apps/api/src/handlers/ado/getAdoAutomationTargets.ts

@@ -50,7 +50,7 @@ export function isRoomoteAdoIdentity(identityName: string): boolean {
   // Match Roomote's own bot by its identity name/handle only. A bare
   // `@roomote` substring check also matched every human whose Azure DevOps
   // uniqueName is an email in a `roomote.*` tenant (e.g.
-  // `dan@roomote.onmicrosoft.com`), which silently dropped their `@roomote`
+  // `grace@roomote.onmicrosoft.com`), which silently dropped their `@roomote`
   // PR comment mentions. The comment path additionally guards against
   // Roomote's own posts with `isDeploymentTokenAuthor`, which resolves the
   // exact deployment identity rather than guessing from the name.

apps/dev/src/services/env.ts

@@ -129,7 +129,7 @@ export class EnvService {
           'domain, Cloudflare Tunnel, Tailscale Funnel, or your own domain). For\n' +
           'an ngrok domain, pnpm dev starts and reuses the tunnel for you:\n' +
           '\n' +
-          'R_PUBLIC_URL=https://roomote-matt.ngrok.app\n',
+          'R_PUBLIC_URL=https://your-ngrok-domain.ngrok.app\n',
       );
     }