Skip to content

v2.1.0

  • v2.1.0
  • 1880b42

  • Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature.
    GPG key ID: B5690EEEBB952194
    Verified
    Learn about vigilant mode

  • Choose a tag to compare

    View all tags
Validator v2.1.0: runtime contract on claim and delivery load (#361)
  • v2.1.0
  • 1880b42

  • Choose a tag to compare

    View all tags

  • Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature.
    GPG key ID: B5690EEEBB952194
    Verified
    Learn about vigilant mode
@that-guy-wade that-guy-wade tagged this 03 Oct 07:47 
* Validator v2.0.42: runtime contract on claim and delivery load (oro-env-runtime 3.1.0)

- Pin oro-env-runtime 3.1.0 and oro-sdk 2.1.0.
- Load deliveries with the runtime's check_epoch plus the existing sha256 and
  roster binding. A delivery whose runtime contract differs from this
  runtime's RUNTIME_CONTRACT, or that declares none, is refused with that
  reason. The tool and verifier version labels no longer gate loading.
- Send RUNTIME_CONTRACT on work claims; the Backend hands out only work
  delivered for that contract.
- The runtime's task model no longer carries generator fields: the local
  runner identifies race rows by their grader alone, and the environment
  preflight reads accepted keys from the delivered rows.
- Rebuild the bundled local-test pack with runtime contract 1.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* Pin oro-sdk 3.0.0

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* build(validator): lock oro-env-runtime 3.1.0 and oro-sdk 3.0.0

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* chore(validator): pin oro-env-runtime 3.2.0

Runtime 3.2.0 keeps runtime contract 1 and adds four grading fixes. The
lock is regenerated once 3.2.0 is on PyPI.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* test(local): the bundled pack's verifier identity is a label

Runtime 3.2.0 labels its verifier 0.4.1 while the bundled pack was sealed
with 0.4.0. Only the runtime contract gates loading, so the test no longer
requires the two labels to match.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* refactor(validator): drop the verifier version label; pin oro-sdk 4.0.0

oro-env-runtime 3.2.0 removes VERIFIER_VERSION and the Backend no longer
returns verifier_version (oro-sdk 4.0.0). The runtime contract is the only
compatibility gate, so the validator stops importing, echoing and printing
the label: PACK_VERSION_IDENTITIES, episode provenance and the local report.

The bundled local-test pack is resealed without contracts.verifier
(662a99ca -> 06d63140; same tasks, rows and checksums otherwise).

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* refactor(validator): drop the tool contract version label

oro-env-runtime 3.2.0 removes TOOL_CONTRACT_VERSION and the Backend no
longer returns tool_contract_version (oro-sdk 4.0.0). The runtime contract
is the only compatibility gate, so the label goes from the validator too:

- PACK_VERSION_IDENTITIES and the episode pack provenance.
- The policy view agents receive and the binding problem files carry:
  both now hold only session_id for the session. Step responses no longer
  echo it.
- The session call no longer checks it. An agent that still sends the key
  is accepted; the key is ignored.

The bundled local-test pack is resealed without contracts.tools
(06d63140 -> 90169a07; same tasks, rows and checksums otherwise).

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* build(validator): lock oro-env-runtime 3.2.0 and oro-sdk 4.0.0

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Assets 2
Loading