I can understand your frustrations as I too expressed my frustrations to our developers for the contradictions. I'm sorry for not including that in my original reply. Everything that has been discussed internally is that Travel Mode is meant as a preventative for Vaults and not an end all method to protect your information from people who have access to your device through 1Password.com. Travel Mode was introduced long before "magic unlock" and its delegated session management. My team and I have let our developers know how magic unlock makes Travel Mode almost pointless when someone who has access to your device can turn off Travel Mode by simply navigating to 1Password.com. I'm contacting our docs team to see if they can update the article you provided to mitigate any future confusion or frustration.
If this had been your first answer then I would be a lot less cranky right now. Having said that, it's mind-boggling to me that 1Password would choose to “fix” this by updating the documentation vs. _fixing the feature_ by requiring the user to reauthenticate before performing sensitive operations such as turning Travel Mode off.
I got back a second response from #1Password that was much better than the first. Here's their second response and what I sent back.
