[Proteina-Complexa] Setup docs overstate required credentials and mislabel DATA_PATH

Two setup-config inaccuracies trip up new (UV) users:

• GITLAB_TOKEN sits in the top "Credentials" block as if required, but it's Docker-only (env/docker-ops.sh registry login; skipped when absent). A live WANDB_ENTITY placeholder also caused an "entity not found" 404 (username ≠ entity; blank = account default).
• LOCAL_DATA_PATH/DATA_PATH is labeled as holding target_data/, but shipped targets use repo-relative target_path:; $DATA_PATH is only a fallback (binder_eval_utils.py:256). Design needs no real DATA_PATH.

Severity: Low · Status: fixed in .env_example; upstream docs open

Steps to reproduce

1. Follow the setup docs / fill .env as written, on the UV runtime.
2. → users think a GITLAB_TOKEN is required; the entity placeholder 404s W&B; users think a real DATA_PATH is required just to run design.

Fix

Mark GITLAB_TOKEN Docker-only, comment out WANDB_ENTITY, and clarify DATA_PATH is a training/fallback path. (Done locally in .env_example.)

Environment

NVIDIA A100 80GB PCIe · driver 565.57.01 · CUDA 12.7 · repo branch dev @ 916eaae · UV runtime.

Start with the shipped .env_example and the upstream setup docs, then check env/docker-ops.sh for GITLAB_TOKEN usage and binder_eval_utils.py:256 for DATA_PATH fallback behavior. Done means the docs mark GITLAB_TOKEN as Docker-only, leave WANDB_ENTITY commented out, and explain that DATA_PATH is only a training/fallback path rather than required for design.