feat: add driver restart option to debug capture wizard

[Copilot]

Several issues require driver startup logs for diagnosis. The debug wizard now includes an optional checkbox to restart the driver with debug logging enabled, capturing the complete startup sequence.

Changes

Backend (api/lib/DebugManager.ts)

• Added restartDriver parameter to startSession() that triggers zwaveClient.restart() after debug transports are attached

API (api/app.ts, src/apis/ConfigApis.js)

• /api/debug/start endpoint accepts restartDriver from request body
• Frontend API forwards the parameter to backend

UI (src/App.vue)

• Start Capture dialog includes unchecked checkbox: "Restart driver to capture startup logs"
• Uses existing app.confirm() pattern with input fields

Screenshot

The driver restarts only when explicitly enabled, ensuring debug transports capture all startup logs including driver initialization, controller interview, and node discovery.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• 224.0.0.251

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Make it easy to capture a log of the driver startup with the new debugging wizard</issue_title>
<issue_description>For several issues it is required to see startup driver logs to diagnose them. With the new debugging wizard, it would be great to have a one-click way to capture that restart in the debugging package. Maybe a checkbox (default unchecked) in the "Start Capture" dialog to restart the driver with the custom transport attached?</issue_description>

Comments on the Issue (you are @copilot in this section)

@robertsLando > Maybe a checkbox (default unchecked) in the "Start Capture" dialog to restart the driver with the custom transport attached?

Yeah, makes sense</comment_new>

• Fixes Make it easy to capture a log of the driver startup with the new debugging wizard #4480

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[zwave-js-assistant]

💡 The pull request title does not match our guidelines 💡

We follow conventional commits, check out the description and examples. This means that the PR title must...

• start with the type of change, e.g. feat:, or fix:
• optionally specify a scope, for example we use config for changes to config files: feat(config):
• contain a description that explains what is being changed, e.g. add a parameter, correct a typo, ...
• and ideally explains what the change affects, e.g. the device (manufacturer, device label, firmware, ...)

The description should use uppercase and lowercase normally, except for the first character which must be lowercase.