temporarily remove migrate-to from docs and DMs help text

not quite ready to launch that after all 😆

dms.py

@@ -122,10 +122,10 @@ def help_text(from_user, to_proto):
 <li><em>[handle]</em>: ask me to DM a user on {to_proto.PHRASE} to request that they bridge their account into {from_user.PHRASE}
 <li><em>block [handle]</em>: block a user on {to_proto.PHRASE} who's not bridged here
 <li><em>unblock [handle]</em>: unblock a user on {to_proto.PHRASE} who's not bridged here
-<li><em>migrate-to [handle]</em>: migrate your bridged account on {to_proto.PHRASE} out of Bridgy Fed to a native account
 {extra}
 <li><em>help</em>: print this message
 </ul>"""
+# <li><em>migrate-to [handle]</em>: migrate your bridged account on {to_proto.PHRASE} out of Bridgy Fed to a native account
 
     if from_user.LABEL == 'atproto':
         text = source.html_to_text(text, ignore_emphasis=True)

templates/docs.html

@@ -265,8 +265,9 @@
 
 <li id="migration" class="question">Is account migration supported?</li>
 <li class="answer">
-<p>Somewhat. Currently, if you have a Bluesky account or web site that's bridged into the fediverse, you can <a href="https://docs.joinmastodon.org/user/moving/#migration">migrate</a> that bridged fediverse account out to a native fediverse account with the <a href="#dm-commands"><code>migrate-to</code> DM command</a>.
-<p>Otherwise, not yet. If you bridge your fediverse account and then <a href="https://docs.joinmastodon.org/user/moving/#migration">migrate to a new instance</a>, or bridge your Bluesky account and then <a href="https://bsky.social/about/blog/4-28-2023-domain-handle-tutorial">change your handle</a>, or bridge your web site and then move it to a new domain, Bridgy Fed doesn't officially support that right now. Some parts of bridging may continue to work, but probably not all.
+<!-- <p>Somewhat. Currently, if you have a Bluesky account or web site that's bridged into the fediverse, you can <a href="https://docs.joinmastodon.org/user/moving/#migration">migrate</a> that bridged fediverse account out to a native fediverse account with the <a href="#dm-commands"><code>migrate-to</code> DM command</a>. -->
+<!-- <p>Otherwise,  -->
+<p>Not yet. If you bridge your fediverse account and then <a href="https://docs.joinmastodon.org/user/moving/#migration">migrate to a new instance</a>, or bridge your Bluesky account and then <a href="https://bsky.social/about/blog/4-28-2023-domain-handle-tutorial">change your handle</a>, or bridge your web site and then move it to a new domain, Bridgy Fed doesn't officially support that right now. Some parts of bridging may continue to work, but probably not all.
 <p>Details in <a href="https://github.com/snarfed/bridgy-fed/issues/330">these</a> <a href="https://github.com/snarfed/bridgy-fed/issues/1074">issues</a>. Hopefully this will be more fully supported in the future.
 <p><a href="https://github.com/snarfed/bridgy-fed/issues/1137">Bridgy Fed also doesn't support migrating an existing account into it to become a bridged account, or migrating a bridged account out to be a normal account.</a> Those are unlikely to be supported, even in the future.
 </li>
@@ -389,7 +390,7 @@
 <li><em>did</em>: get your bridged Bluesky account's <a href="https://atproto.com/guides/identity#identifiers">DID</a> (only supported with the Bluesky bot)
 <li><em>block [handle]</em>: <a href="#block">block a user on another network who's not bridged into your network</a>
 <li><em>unblock [handle]</em>: <a href="#block">unblock a user on another network who's not bridged into your network</a>
-<li><em>migrate-to [handle]</em>: <a href="#migrate-to">migrate your bridged account out of Bridgy Fed to a native account</a>
+<!-- <li><em>migrate-to [handle]</em>: <a href="#migrate-to">migrate your bridged account out of Bridgy Fed to a native account</a> -->
 </ul>
 </li>