0.6.2: no approving a command you could not read whole

• Clipped commands can only be blocked from a device. An approval prompt used to cut the command to 87
  characters, and a spoken "yes" or an approve button still allowed it, so a user could approve a command they only
  partly saw or heard. The prompt now carries the whole command up to 300 characters. A longer one is clipped and
  offers deny only: a spoken yes or an approve button resolves nothing, and the prompt says to use /approve after
  reading the full command. Short commands shown whole are still approved by voice as before.
• Answers go through Hermes's card resolver. On Hermes 0.23 and later, button and voice answers resolve through
  resolve_gateway_approval_card, so Hermes's own Deny-only rule for clipped commands applies too.
• Speech, G2 and Pebble. When Hermes's text-to-speech drops part of a command from a spoken prompt (it skips
  paths and web addresses), a spoken yes can only block it; buttons and typed /approve still work. The G2 app
  offers only Deny when the lens cannot show the whole command (or it spans lines), and a tap answers only the card
  already on the lens. Pebble shows approval prompts verbatim. A yes is
  also checked when Hermes asked for approval as text, so a bare yes never reaches Hermes's own oldest-request rule.
• Omi: only your own voice answers an approval. A yes or no counts only from transcript segments marked
  is_user (the wearer); speech from anyone nearby is not acted on and not passed to Hermes as a bare yes.