feat: backend-neutral depth-domain release v0.4.0 - #3
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.
Introduces the backend-neutral candidate contract and hierarchical selective decision layer; native CellTypist, popV, SingleR, scANVI, custom-reference and opt-in LLM runners; three governed depth-domain Atlas scopes; donor-locked downgrade-only calibration; lung multi-lineage OOF acceptance evidence; and a hash-verified v0.4.0 governance freeze. Scientific boundary: the lung artifact demonstrates addressability, not accuracy; the calibration is donor-independent but not independent-cohort; the five-cohort evidence release remains incomplete/not claim-ready with unavailable methods and missing folds retained. Local Ruff, 10 release/domain tests, build, Twine, plugin bundle, wheel install and installed governance verification passed; the full local suite timed out at 15 minutes without a reported assertion failure, so merge and tagging remain gated on GitHub CI.