Stabilize TSLP-backed merge registration and templating benchmarks - #59
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
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.
Fixes #58.\n\nThis PR contains the committed StructuredMerge Ruby stabilization branch currently on feat/ractor-ready.\n\nHighlights:\n- TreeHaver now validates TSLP parser availability by executing real parser smoke tests.\n- Grammar registration validates the requested language before registering a TSLP backend.\n- Merge parser paths are constrained through TreeHaver parser contracts, including Bash.\n- Structural merge layout helpers preserve retained blank/comment gaps more consistently.\n- kettle-jem benchmarking now records progress/timing summaries and baseline deltas for the Ractor/thread experiments.\n\nValidation performed during the branch work includes targeted TreeHaver and kettle-jem suites with vendored TSLP, plus direct probes showing released broken TSLP is rejected while local/vendored TSLP parses JSON successfully.\n\nNote: the current local worktree has unrelated unstaged generated Gemfile.lock changes; they are not included in this pushed branch.