Drop --token from the hand-started worker examples

The worker reads FLUKSIO_WORKER_TOKEN itself; on the command line the
token shows in ps. The --token row in the options table says so.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013GAeg4Jo6xjZzjwy9QDWMQ

docs/code/cli.md

@@ -231,8 +231,7 @@ agent's own parser: it is the same program `fluksio-worker` installs, so the
 two are interchangeable:
 
 ```sh
-fluksio worker --url wss://api.${DOMAIN}/api/v1/workers/attach \
-               --token "$FLUKSIO_WORKER_TOKEN" --labels gpu
+fluksio worker --url wss://api.${DOMAIN}/api/v1/workers/attach --labels gpu
 ```
 
 See [Remote workers](workers.md).

docs/code/workers.md

@@ -16,7 +16,6 @@ pip install fluksio-worker
 
 fluksio-worker \
   --url wss://api.${DOMAIN}/api/v1/workers/attach \
-  --token "$FLUKSIO_WORKER_TOKEN" \
   --labels gpu,cuda12 \
   --python /opt/torch-venv/bin/python
 ```
@@ -29,7 +28,7 @@ driver in order to run a training step. An engine host already has it, and
 | Option | Default | What it does |
 |---|---|---|
 | `--url` | **required** | `wss://…/api/v1/workers/attach` |
-| `--token` | `$FLUKSIO_WORKER_TOKEN` | the credential, minted on the engine |
+| `--token` | `$FLUKSIO_WORKER_TOKEN` | the credential, minted on the engine; on the command line any user of the machine reads it from `ps`, so prefer the variable |
 | `--name` | this host's name | sent along; the worker list shows the token's name |
 | `--labels` | the token's | comma-separated; must match the labels the token was minted with |
 | `--python` | this interpreter | the interpreter node code runs on |