The challenge repository currently carries a Python validation script that mirrors parts of Agentics bundle validation. This duplicated logic has already drifted from the Rust source of truth for execution modes, resource profiles, image policy, and executor fields.\n\nFollow-up: reuse existing Rust validation from Agentics, or expose a small Rust validation binary/library that this repository can invoke in CI. Once that path exists, remove or heavily shrink scripts/validate_challenges.py so challenge CI does not carry a second copy of the platform contract.\n\nContext from Agentics review on 2026-05-21: the Python validator needs temporary fixes for coexecuted_benchmark direct validation, piped_stdio validation_session, supported image policy, CUDA metadata, and executor result_file, but the durable direction should be shared Rust validation.
The challenge repository currently carries a Python validation script that mirrors parts of Agentics bundle validation. This duplicated logic has already drifted from the Rust source of truth for execution modes, resource profiles, image policy, and executor fields.\n\nFollow-up: reuse existing Rust validation from Agentics, or expose a small Rust validation binary/library that this repository can invoke in CI. Once that path exists, remove or heavily shrink scripts/validate_challenges.py so challenge CI does not carry a second copy of the platform contract.\n\nContext from Agentics review on 2026-05-21: the Python validator needs temporary fixes for coexecuted_benchmark direct validation, piped_stdio validation_session, supported image policy, CUDA metadata, and executor result_file, but the durable direction should be shared Rust validation.