Repository navigation
Verify framework document keys after shared parser migration - #145
Merged
Merged
Conversation
Up to standards ✅🟢 Issues
|
|
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.



LoadDensity now delegates document parsing to ActionCore, so the source-text assertion for
.get("load_density"fails despite an unchanged document contract. Verify each framework through its publicexecute_files()in an isolated child process with only a recording command registered: the profile's key, a bare list, and rejection of an unrelated key. The branch includes the current main baseline to retain stable version 1.0.36 on dev.Validation: complete local unit suite, 5036 passed and 4 skipped; 28 metadata-probe tests against existing framework versions; four cases against current LoadDensity and ActionCore source; Ruff and git diff --check passed. CI validates fresh dependencies across Python 3.10–3.14 and both platform smoke jobs before merging.