ENG-3201 Fix eval auto-upload for metadata-linked environments

[d42me]

Summary

• reuse the env push content hash implementation when comparing local envs against the platform
• stop falsely marking metadata-linked local environments as ahead when their content matches the upstream
• add regression coverage for hash parity and in-sync metadata-linked env resolution

Testing

• pytest packages/prime/tests/test_verifiers_bridge.py packages/prime/tests/test_hosted_eval.py packages/prime/tests/test_eval_billing.py -q

---

Note

Medium Risk
Changes environment version/hash resolution and makes prime eval auto-upload fail fast when the local environment isn’t published or can’t be linked, which can alter user workflows. Risk is moderate due to reliance on API response shapes and new error/exit paths.

Overview
Fixes environment/version handling so metadata-linked local environments are no longer incorrectly marked as “ahead” when their content matches the hub, by reusing prime env push’s compute_content_hash and enriching @latest env details with content_hash from the /versions endpoint when missing.

Updates prime env status to display latest version/hash via a shared extract_env_version_summary helper, and changes prime eval passthrough to refuse pushing results when the local env diverges/unpublished (and improves messaging when no upstream is found). Adds regression tests for hash parity, remote detail enrichment, in-sync resolution, and new eval failure behavior, plus a retry loop in the sandbox command timeout test for transient 502s.

^{Written by Cursor Bugbot for commit 62e061e. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}