Fix Zephyr Workspace & BLE

My Zephyr setup inside VS Code suddenly stopped recognizing its West Workspace and, at the same time, the BLE fields in the NUS sample keep snapping back to Zephyr’s hard-coded defaults. I already tried the normal “Initialize West Workspace” button in the nRF Connect extension, but it still shows “Not initialized”.

Here is what I need during a live screen-share session (VS Code GUI only—no terminal, PowerShell, or Linux commands):

• Walk me through restoring a healthy West Workspace so the nRF Connect extension sees all boards, SDK paths, and build configurations again.
• Point out exactly which files or overlay/kconfig entries control the BLE advertising data—device name, company name, model name, version, etc.—and show how to change them so the new values survive every build of the NUS sample.
• Confirm the app builds successfully inside VS Code and the resulting firmware advertises the updated fields when scanned.

If you’ve wrestled with Zephyr or Nordic’s nRF Connect extension before, this should be straightforward. I just want clear, click-by-click guidance and a quick recap of the steps so I can repeat them later.