[BREAKING] refactor: rename GpuPlatformInfo.gpus to .devices

[kaiitunnz]

Purpose

GpuPlatformInfo.gpus reads awkwardly at every call site (gpu.gpus). Rename to devices so the access reads naturally as gpu.devices. Hard rename — no compat shim, the wire format breaks; coordinate with a full server+worker restart and flush any cached worker registry entries in Redis on deploy.

Changes

• src/shared/tasks/worker_message.py, src/server/schemas/node.py, sdk/src/flowmesh/models/workers.py — rename GpuPlatformInfo.gpus field to devices.
• src/worker/hw.py — rename local gpus accumulator and GpuPlatformInfo(...) kwarg.
• src/server/dispatcher/worker_selector.py, src/server/registries/worker.py, src/server/services/metrics.py — update all .gpus reads to .devices; rename matching local vars where the read flows straight in.
• tests/worker/test_hw.py, tests/server/dispatcher/test_worker_selector.py, tests/server/registries/test_worker_registry.py, tests/sdk/test_models.py — update attribute reads and constructor kwargs.

Design

The model is mirrored across three packages (shared, server.schemas, flowmesh-sdk) and tests/sdk/test_schema_compat.py asserts the server↔SDK schemas stay in sync, so all three renames ship together. Local variables named gpus that hold a list[GpuInfo] are renamed to devices only where the read site or write site benefits from the consistency; standalone list[GpuInfo] locals that are not field-sourced were left as-is.

Wire-format compatibility is intentionally not preserved — the repo is pre-release and adding a Pydantic alias would leave the misleading field name in API docs.

Test Plan

uv run pytest tests/sdk tests/server tests/worker/test_hw.py --ignore=tests/worker/test_mp_executor_cleanup_gpu.py
uv run pre-commit run --all-files

Test Result

Not run locally — relying on CI. Refactor is mechanical and was verified by grep: no \.gpus or gpus= references to the renamed field remain (other *gpus hits are unrelated names like available_gpus, n_gpus).

---

Pre-submission Checklist

• I have read the contribution guidelines.
• I have run pre-commit run --all-files and fixed any issues.
• I have added or updated tests covering my changes (if applicable).
• I have verified that uv run pytest tests/ passes locally.
• If I changed shared schemas or proto definitions, I have checked downstream compatibility across Server and Worker.
• If I changed the SDK or CLI, I have verified the affected packages work (uv sync --all-packages --group ci --frozen).
• If this is a breaking change, I have prefixed the PR title with [BREAKING] and described migration steps above.
• I have updated documentation or config examples if user-facing behavior changed.

[timzsu]

LGTM.