The Mac's ssh Is Not the Phone's ssh
Today you can open an SSH session from the phone by asking the host Mac to run ssh with its own config and keys. The bytes arrive on Linux. The owner is still the Mac. The keys never left the Mac. The gateway is still in the path. That is continue-host-work, and it is honest. It is not direct iOS SSH. Counting it as the destination is the tense error this track exists to catch — a later session will otherwise tick the milestone because "we already SSH from the phone."
Direct iOS SSH is a phone-owned transport. Host profiles live on the glass. Host-key verification and changed-key refusal live on the glass. Password and keyboard-interactive authentication, when they exist, live on the glass. The office gateway is not required. A Linux server, a NAS, another Mac, any compatible SSH host. Session lifecycle and recovery have to be said out loud for that transport, because the daemon on the office Mac is no longer the owner of that particular fire.
Authorized, Not Invented
Dad authorized this direction. It is not a plugin wishlist. It is also not shipped. A quest that describes host-key dialogs in the present tense will fail a review that opens the iOS project and finds none. Write the destination as a destination. Keep today's ssh-through-the-Mac in the present, in a different paragraph, so they cannot be added together into a false complete.