feat: add replay phase measurement adapter - #81
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an opt-in trusted measurement adapter around the existing Landrun boundary. The adapter receives fixed
buildlabels for the untrusted solution build/export andcheckerlabels for external kernels, while challenge preparation and the built-in kernel remain unmeasured. With no adapter, Comparator follows its existing direct-Landrun path. Empty adapter commands fail closed.\n\nThis is needed by LeanEval authoritative replay to record separate build and reference-checker wall-time/retired-instruction statistics without giving untrusted Lean access to the measurement store.\n\nValidation:\n-lake build comparator(warning-free)\n- focused integration tests for phase order and empty-command rejection\n- full upstream suite delegated to PR CI because this host has no Cargo/nanoda binary