changed verifier bot to marksbot

deploy/migrations/20260714003126_rename_verifier_bot_to_marks_bot.down.sql

@@ -0,0 +1,11 @@
+UPDATE public.peer_usernames
+SET username_lower = 'verifierbot',
+    username = 'verifierbot',
+    updated_at = now()
+WHERE peer_type = 'user' AND peer_id = 1250000013 AND username_lower = 'marksbot';
+
+UPDATE public.users
+SET first_name = 'Verifier Bot',
+    username = 'verifierbot',
+    updated_at = now()
+WHERE id = 1250000013;

deploy/migrations/20260714003126_rename_verifier_bot_to_marks_bot.up.sql

@@ -0,0 +1,27 @@
+-- Renames the built-in third-party-verification bot from @verifierbot
+-- ("Verifier Bot") to @marksbot ("Marks Bot").
+--
+-- The old name was too easy to confuse at a glance with @verifybot ("Verify
+-- Bot"), the unrelated official-checkmark front door (0153/0112) -- one grants
+-- the platform badge, the other grants a third-party icon+description mark,
+-- and the two must never read each other's state (see internal/domain/system.go
+-- and 0156/20260714003115). This migration only touches the identity (name,
+-- handle); the account id, access_hash and its bot_verifier_settings grant (if
+-- any operator already made one) are untouched.
+--
+-- 20260714003115 already applied on any existing deployment created the
+-- account under the old name via INSERT ... ON CONFLICT DO UPDATE -- editing
+-- that historical file in place would not reach a database where it already
+-- ran, hence a separate migration here instead.
+
+UPDATE public.users
+SET first_name = 'Marks Bot',
+    username = 'marksbot',
+    updated_at = now()
+WHERE id = 1250000013;
+
+UPDATE public.peer_usernames
+SET username_lower = 'marksbot',
+    username = 'marksbot',
+    updated_at = now()
+WHERE peer_type = 'user' AND peer_id = 1250000013 AND username_lower = 'verifierbot';

deploy/migrations/20260714003127_marks_bot_verified.down.sql

@@ -0,0 +1,4 @@
+UPDATE public.users
+SET verified = false,
+    updated_at = now()
+WHERE id = 1250000013;

deploy/migrations/20260714003127_marks_bot_verified.up.sql

@@ -0,0 +1,12 @@
+-- @marksbot (formerly @verifierbot) now carries the platform checkmark itself
+-- (domain.VerifierBotUser().Verified = true). This is a deliberate operator
+-- choice on top of the original upstream design (which kept it unverified to
+-- avoid implying the third-party mark it grants is somehow platform-endorsed):
+-- the checkmark here only asserts "this account is a legitimate first-party
+-- service bot", not "this bot's grants are official" -- the two mechanisms
+-- remain fully independent regardless of this flag.
+
+UPDATE public.users
+SET verified = true,
+    updated_at = now()
+WHERE id = 1250000013;