docs: update onboarding flow with v2 pyDirect app

Author: jetpax

docs-src/assets/pydirect-setup.png

@@ -2,17 +2,28 @@
 
 Get started with ScriptO Studio and pyDirect.
 
-## Choose Your Path
+![pyDirect Setup](../assets/pydirect-setup.png)
 
-### 🆕 New Device (Blank ESP32)
+## pyDirect Setup Tool
+
+The **pyDirect Setup** tool at [pydirect.com](https://pydirect.com) provides a unified workflow for all device scenarios. Connect your ESP32 via USB and choose from four options:
+
+| Scenario | Description |
+|----------|-------------|
+| **New Device** | Flash fresh firmware onto a blank ESP32 |
+| **Forgot Credentials** | View saved hostname and password |
+| **Change WiFi** | Update network settings on existing device |
+| **Re-provision** | Fresh start with new certificates |
+
+## New Device Setup
 
 If you have a brand new ESP32 chip without firmware:
 
 1. **Go to [pydirect.com](https://pydirect.com)**
 2. Connect your ESP32 via USB
-3. Click **Connect & Install pyDirect**
-4. Select your chip type when detected
-5. Flash the firmware
+3. Click **Connect Device**
+4. Select **New Device** when the chip is detected
+5. Flash the firmware (automatically selected for your chip)
 6. Configure WiFi when prompted
 7. Device reboots and redirects you to the device's web interface
 8. **Accept the browser security warning** (self-signed certificate) - click Advanced → Proceed
@@ -23,25 +34,45 @@ If you have a brand new ESP32 chip without firmware:
 > [!IMPORTANT]
 > The password you set during provisioning is used both for the device's local web interface AND for ScriptO Studio connections. Remember this password!
 
-### 📱 Existing pyDirect Device
+## Existing pyDirect Device
 
 If you already have a device running pyDirect firmware:
 
 1. **Go to [scriptostudio.com](https://scriptostudio.com)**
 2. Click **Connect**
-3. Enter your device's IP address or hostname
+3. Enter your device's IP address or hostname (e.g. `pydirect-xxxx.local`)
 4. Enter the access password (set during initial provisioning)
 5. Click **Connect**
 
-### 📶 Change WiFi on Existing Device
+## Forgot Credentials
+
+If you can't remember your device's hostname or password:
+
+1. **Go to [pydirect.com](https://pydirect.com)**
+2. Connect via USB and click **Connect Device**
+3. Select **Forgot Credentials**
+4. Your device's hostname, password, and WiFi SSID are displayed
+
+## Change WiFi
 
-If you need to reconfigure WiFi on a device:
+To update network settings on an existing device:
 
 1. **Go to [pydirect.com](https://pydirect.com)**
-2. Connect via USB
-3. Click the **WiFi** button
-4. Select a network and enter credentials
-5. Device will reboot and connect to new network
+2. Connect via USB and click **Connect Device**
+3. Select **Change WiFi**
+4. Choose from the list of detected networks
+5. Enter the WiFi password
+6. Device connects to the new network and generates a new certificate
+
+## Re-provision
+
+For a complete fresh start with new certificates:
+
+1. **Go to [pydirect.com](https://pydirect.com)**
+2. Connect via USB and click **Connect Device**
+3. Select **Re-provision**
+4. Enter a new password when prompted
+5. Device generates new certificates and restarts
 
 ## Connection Requirements
 
@@ -62,18 +93,20 @@ This only needs to be done once per device per browser.
 
 ## Next Steps
 
-- **[First ScriptO](../getting-started/first-scripto.md)** - Run your first script
-- **[IDE Overview](../getting-started/ide-overview.md)** - Learn the interface
+- **[First ScriptO](first-scripto.md)** - Run your first script
+- **[IDE Overview](ide-overview.md)** - Learn the interface
 - **[Troubleshooting Connection](../troubleshooting/connection.md)** - If you have issues
 
 ## Troubleshooting
 
 **Can't connect from pydirect.com?**
+
 - Check USB cable supports data (not charge-only)
 - Install USB drivers if needed (CP210x or CH340)
 - Put device in boot mode (hold BOOT, press RESET, release BOOT)
 
 **Can't connect from scriptostudio.com?**
+
 - Verify device is powered and on the network
 - Check the IP address is correct
 - Make sure you're using the password set during provisioning