[ray-update-2.56.0] Update entity-recognition-with-llms to Ray 2.56.0

[cursor]

Summary

Bump entity-recognition-with-llms to Ray 2.56.0.

Changes

• BUILD.yaml cluster_env.image_uri: anyscale/ray-llm:2.55.1-py311-cu128 → anyscale/ray-llm:2.56.0-py312-cu130.
• templates/entity-recognition-with-llms/containerfile FROM: same bump.
• Forced py311→py312 + cu128→cu130 jump. anyscale/ray-llm:2.56.0 on Docker Hub only publishes py312-cu130 (no py311-cu128 variant); this matches the forced-variant handling used for every other ray-llm-based template on this Ray version (see [ray-update-2.56.0] Update langchain-agent-ray-serve to Ray 2.56.0 #884, [ray-update-2.56.0] Update llm_batch_inference_vision to Ray 2.56.0 #887, [ray-update-2.56.0] Update llm_finetuning to Ray 2.56.0 #889, [ray-update-2.56.0] Update multi_agent_a2a to Ray 2.56.0 #892). Tag verified on Docker Hub.
• No python_depset.lock for this template (no entry in dependencies/template.depsets.yaml), so the image bump is the whole change.

Tests / validation

• Local: pre-commit run --all-files — passed. python ci/validate_build_yaml.py — passed.
• CI: Buildkite template-test build #506 — passed on commit dee61081 (~44 min end-to-end; a first attempt was auto-cancelled at ~13 min into training due to a Buildkite agent shutdown, and the retry ran the full ~34 min LoRA SFT training cleanly on the new py312-cu130 base).

Publish

• BUILDKITE_API_TOKEN on this Cursor Cloud agent lacks the write_builds scope required to trigger tmpl-publish via API (create_build returns Your access token doesn't have the write_builds scope). Please trigger the publish manually after merge — tmpl-publish pipeline, branch master, message entity-recognition-with-llms; then unblock input-tmpl-name with tmpl-name=entity-recognition-with-llms, tmpl-branch=main, tmpl-commit=HEAD per publish-to-backend.md.

[svc-template-updater]

/test-template entity-recognition-with-llms