feat(mrl): reconcile benchmark flags and sealed canary fixture - #310
Merged
Conversation
|
ⓘ Qodo reviews are paused because your trial has ended. Ask your workspace admin to add credits to resume reviews. Manage billing |
Contributor
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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
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.
Summary
Reconcile MRL-0604 benchmark-derived-generation flags and MRL-0606 R2-compatible sealed temporal-canary fixture workflow onto canonical
mainafter MRL-0601/0602/0603/0605 construction-bound identity hardening became canonical.This replacement is rebuilt directly from canonical
4b29a761e82e9fbe95278bcacd644dff40d1315e; it carries only the four intended feature/test files from superseded PR #295 and does not reuse its history or qualification evidence.MRL-0604 reconciliation
TrainingExampleLineageContractinstead of rebuilding from mutable live example fieldsContaminationEvidenceReportandTrainingTransformationBindinginstead of copying live nested fields into new objectsMRL-0606 reconciliation
TemporalCanaryManifestinstead of rebuilding a fresh manifest from mutable live fieldssealed=True,fixture_only=True,can_enter_training=False,can_enter_search=False,can_authorize=FalseExact qualified candidate
4b29a761e82e9fbe95278bcacd644dff40d1315e30a5d8441684d1f474565b1f9080d13ab603819ebehind_by=0src/medscale/mesc/_mrl_benchmark_derived_generation_v1.pysrc/medscale/mesc/_mrl_temporal_canary_fixture_workflow_v1.pytests/test_mesc_mrl_benchmark_derived_generation_v1.pytests/test_mesc_mrl_temporal_canary_fixture_workflow_v1.pyExact-head qualification
CI run
33360892949: PASS.Both Python 3.11 and Python 3.12 lanes passed:
medscale checkCodeQL run
33360892966: PASS. The Python analysis job completed successfully.Final exact-head semantic review found no unresolved material defect. GitHub reports no submitted review findings and no inline review threads. Qodo remains billing-blocked and CodeRabbit automatic review is disabled because the repository is below its automatic-review threshold; neither provider spend nor human review was requested.
Boundary
This work records metadata and runs only the canonical deterministic in-memory fixture path. It performs no benchmark/corpus read, benchmark-derived generation, real model/provider/network/GPU work, training, promotion, deployment, release, or clinical action. MRL-0607 remains separately dependent on canonical MRL-0606.
Guarded merge is authorized only while canonical
mainremains4b29a761e82e9fbe95278bcacd644dff40d1315eand the PR head remains exactly30a5d8441684d1f474565b1f9080d13ab603819e. No force-push, rebase, destructive history rewrite, CI/CodeQL weakening, governance bypass, provider spend, or real-asset access was used.