fix: log removeDevice failures during removeConnection with structured error fields

[Copilot]

Description

removeConnection swallowed removeDevice errors in a bare catch {}, hiding failures silently. This PR adds a log.warn with structured error fields, and reformats an overly long chained call for readability.

Related Issues

Changes Made

• removeConnection catch block: replaced catch {} with structured error logging — extracts err.name / err.message instead of passing the raw err object (which serializes to {} in JSON-based loggers), consistent with error handling in teardown() and connect():

} catch (e) {
  const err = e as Error;
  log.warn("removeDevice failed during removeConnection", {
    id,
    meshDeviceId: conn.meshDeviceId,
    name: err?.name,
    message: err?.message,
  });
}

• connect: reformatted long useDeviceStore.getState().savedConnections.find(...) chain across multiple lines

Testing Done

Verified no TypeScript or CodeQL errors introduced. Pattern matches existing error logging callsites in the same file.

Screenshots (if applicable)

Checklist

• Code follows project style guidelines
• Documentation has been updated or added
• Tests have been added or updated
• All i18n translation labels have been added (read
  CONTRIBUTING_I18N_DEVELOPER_GUIDE.md for more details)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
web-test	Ready	Preview, Comment	Jul 14, 2026 2:03am