v2.7.1

Fixed

• The plane guard now sees a Mist or Security Director client kept in an
  apply-groups group. It reads system services outbound-ssh with
  | display inheritance, so a managed device with its client in a group is no
  longer treated as writable. A release that cannot parse the pipe falls back to
  the plain command, which cannot see groups; any other probe failure still
  refuses the write.
• A reload_devices or SIGHUP that pointed a device name at a different
  address could still be acted on with the old device's session: a change set
  already holding the candidate lock was judged by the new device's settings
  (plane authority, rollback guards), and a session in use during the reload
  went back into the pool and was reused for the new device. Sessions now
  remember the address they connected to; a write caught by a retarget is
  refused, with any candidate released, and a stale pooled session is discarded.