docs(cli): clarify port-less mode for local servers

The 'About --port' section already promised that --port is optional
when the server has a connected device, but the operating modes table
only listed port-less attach implicitly via the remote-proxy row.

- State that port-less attach applies to BOTH local and remote.
- Add a 'Local proxy (port-less)' row to the modes table.
- Note that omitting --port without a connected device falls back to
  offline so ELF analysis / compile commands keep working.

Author: W-Mai

Docs/CLI.md

@@ -47,17 +47,20 @@ Options:
 
 ### About `--port`
 
-The serial port belongs to the **WebServer**, not the CLI. When a server is already running and has a device connected, `--port` is not needed — the CLI attaches to the server's existing connection.
+The serial port belongs to the **WebServer**, not the CLI. When a server is already running and has a device connected, `--port` is not needed — the CLI attaches to the server's existing connection. This applies to **both local and remote** servers: as long as `/api/status` reports `connected=true`, you can run device commands without `--port`.
 
 `--port` is only required when:
 - No server is running locally (triggers auto-launch + direct fallback).
-- The remote server has no device connected yet (tells it which port to open).
+- The local or remote server is reachable but has no device connected yet (tells it which port to open).
+
+When `--port` is omitted **and** no server has a connected device, the CLI stays offline so ELF analysis / compile commands keep working without a device.
 
 ## Operating Modes
 
 | Mode | Trigger | Behavior |
 |------|---------|----------|
-| Offline | No `--port`, no server | ELF analysis / compile only |
+| Offline | No `--port`, no server (or server has no device) | ELF analysis / compile only |
+| Local proxy (port-less) | No `--port`, local server already has a device | Attach to server's existing connection |
 | Local proxy | `--port` + local server running | Attach to server, forward device ops |
 | Local auto-launch | `--port` + no local server | Auto-launch server, then proxy |
 | Local direct | `--direct --port` | Open serial directly (bypass server) |

Tools/WebServer/cli/fpb_cli.py

@@ -1188,19 +1188,25 @@ def main():
   fpb_cli.py search firmware.elf gpio
   fpb_cli.py compile patch.c --elf firmware.elf --compile-commands build/compile_commands.json
 
-  # Local device commands — auto-launch/attach to a WebServer:
+  # Local device commands — first time, --port triggers auto-launch:
   fpb_cli.py --port /dev/ttyACM0 info
   fpb_cli.py --port /dev/ttyACM0 inject digitalWrite patch.c --elf firmware.elf
 
+  # Once a local server has the device connected, --port is no longer needed:
+  fpb_cli.py info
+  fpb_cli.py file-stat /etc/init.d/rcS
+
   # Remote control — the device lives on the server, so no --port needed:
   fpb_cli.py --server-url http://192.168.1.20:5500 --token TOKEN info
   # Only pass --port to tell the remote server which port to open if it has none:
   fpb_cli.py --server-url http://192.168.1.20:5500 --token TOKEN --port /dev/ttyACM0 connect
 
 Notes:
-  The serial port belongs to the WebServer, not the CLI. In proxy mode --port
-  is optional and only used to ask the server to open a port when no device is
-  connected yet. --token (or FPB_TOKEN env) is required for remote servers.
+  The serial port belongs to the WebServer, not the CLI. In proxy mode (local
+  or remote) --port is optional whenever the server already has a connected
+  device; it is only required to open a port when no device is connected yet,
+  or for direct/auto-launch on a fresh local environment.
+  --token (or FPB_TOKEN env) is required for remote servers.
   Output is JSON on stdout; pipe to jq for filtering.
   Run 'fpb_cli.py <command> --help' for command-specific options.
         """,