fix(benchmarks): keep the server interpreter symlink intact in both LIBERO schedulers

[wayrise]

Summary

Supersedes and includes #33 — @seveirbian's commit is carried here unchanged, so merging this closes that PR with their authorship intact.

run_eval.sh defaults SERVER_PYTHON=python and expands it with command -v, which inside an activated environment yields .venv/bin/python. That is a symlink for both uv venv and the stdlib python3 -m venv shown in the README. .resolve() follows it to the base interpreter, and starting that binary directly leaves no pyvenv.cfg beside the executable, so CPython never activates the venv and deploy.py comes up without its site-packages.

#33 fixed benchmarks/libero/scheduler.py. benchmarks/libero-plus/scheduler.py carried the identical line — that block is otherwise a copy, differing only in the num_trials default — and benchmarks/libero-plus/run_eval.sh has the same SERVER_PYTHON:-python default, so the bug was equally reachable there. Those two were the only occurrences in the repo.

Verification

On Linux, with a stdlib venv and a module present only in that venv:

interpreter path	sys.prefix	import of the venv-only module
.absolute() → /tmp/x/.venv/bin/python	/tmp/x/.venv	ok
.resolve() → /usr/bin/python3.12	/usr	ModuleNotFoundError

which reproduces the reported failure exactly.

ruff clean, pytest tests/benchmarks/ 66 passed, pre-commit hooks pass.

Note on the comments

Each .absolute() call now carries its own rationale. The existing comment is about keeping alias paths readable in logs and manifests — a different concern that does not cover the interpreter case, and server_python never reaches manifest.json at all. Without a note the call reads like an oversight and is easy to "clean up" back to .resolve().

No regression test is included: the normalization is inline in main(), which then runs _preflight and launches subprocesses, so covering it would require extracting the path handling into its own function first.

🤖 Generated with Claude Code

[SCreatorX]

LGTM. Verified the reasoning: .venv/bin/python is a symlink, so .resolve() hands deploy.py the base interpreter without pyvenv.cfg next to it and the venv site-packages are lost. .absolute() keeps the symlink and still gives an absolute path. The two schedulers are the only places server_python is normalized, and the downstream consumers (_server_command and the _preflight existence check) work with either form. Consistent with how libero_python is already handled. CI lint + tests green.