fix(mrl): reconcile training lineage identity on canonical main - #307
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-0601
TrainingExampleLineageContractconstruction-identity hardening onto canonicalmainafter #304 merged.This replacement carries only the final intended content from superseded PR #305, rebuilt directly from canonical
mainwithout rebase, force-push, or destructive history rewriting.Repair
TrainingExampleLineageContractweak-referenceable without adding caller-supplied fieldsTrainingExampleV1snapshot before public lineage trust/semantic/hash viewsExact qualified candidate
613f48cd03493e9bb92e8b5328b0d4fd4f37290726d66b718a359f33cc028dc93d9f2fdc8088bae1behind_by=0src/medscale/mesc/_mrl_training_example_lineage_v1.pytests/test_mesc_mrl_training_example_lineage_v1.pyExact-head qualification
CI run
33356665267: PASS.Both Python 3.11 and Python 3.12 lanes passed:
medscale checkCodeQL run
33356665319: PASS.Final exact-head semantic review found no unresolved material defect. GitHub reports no inline review threads or submitted review findings. Qodo remains billing-blocked and CodeRabbit automatic review is disabled for this repository; neither paid review usage nor human review was requested.
Downstream reconciliation
After this becomes canonical, PR #299 must be reconciled so MRL-0602/MRL-0603/MRL-0605 validate the original construction-bound lineage. PR #295 remains downstream of that reconciliation.
Boundary
This is fail-closed lineage-metadata integrity hardening only. It reads no source bytes or corpora, accesses no model/provider/network/GPU/runtime, executes no generation or training, and grants no source/data access, training, promotion, deployment, release, or clinical authority.
Guarded merge is authorized only while canonical
mainremains the stated base and the PR head remains exactly26d66b718a359f33cc028dc93d9f2fdc8088bae1. No force-push, rebase, destructive history rewrite, CI/CodeQL weakening, governance bypass, provider spend, or real-asset access was used.