Update README.md and DOCUMENTATION.md examples to include --password parameter for wssshc

- Fixed obsolete command line examples that were missing the required --password parameter
- Updated all wssshc usage examples in both files

DOCUMENTATION.md

@@ -223,7 +223,7 @@ wssshd --host HOST --port PORT --domain DOMAIN [--debug]
 #### Command Line Options
 
 ```bash
-wssshc --server-ip IP --port PORT --id ID [--interval SEC] [--debug]
+wssshc --server-ip IP --port PORT --id ID --password PASS [--interval SEC] [--debug]
 ```
 
 - `--server-ip IP`: wssshd server IP address (required)
@@ -402,7 +402,7 @@ curl -I https://localhost:9898
 **Solutions**:
 ```bash
 # Check client registration
-./wssshc --server-ip <ip> --port 9898 --id <client_id>
+./wssshc --server-ip <ip> --port 9898 --id <client_id> --password <password>
 
 # Verify client appears in wssshd logs
 tail -f wssshd.log
@@ -456,7 +456,7 @@ Enable debug output for detailed troubleshooting:
 ./wssshd --debug --host 0.0.0.0 --port 9898 --domain example.com
 
 # wssshc debug
-./wssshc --debug --server-ip <ip> --port 9898 --id client1
+./wssshc --debug --server-ip <ip> --port 9898 --id client1 --password <password>
 
 # wsssh debug
 ./wsssh --debug ssh user@client.example.com

README.md

@@ -139,7 +139,7 @@ man wsscp     # SCP wrapper
 On the client machine you want to access through:
 
 ```bash
-./wssshc --server-ip <daemon_ip> --port 9898 --id myclient
+./wssshc --server-ip <daemon_ip> --port 9898 --id myclient --password mysecret
 ```
 
 ### 3. Connect via SSH
@@ -281,7 +281,7 @@ Certificates are created with:
 Each client machine must be registered with wssshd using a unique ID:
 
 ```bash
-./wssshc --server-ip <daemon_ip> --port <port> --id <unique_id>
+./wssshc --server-ip <daemon_ip> --port <port> --id <unique_id> --password <password>
 ```
 
 The client will maintain a persistent WebSocket connection to the daemon.