fix: close figure diagnostics and render contract gaps - #233
Merged
Conversation
moonweave
marked this pull request as ready for review
July 30, 2026 00:12
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.
What changed
artist_overlapsand informationallegend_data_collisioncontracts.bbox_policybehavior, plus narrow-log minor-label suppression for journal targets.publication-readiness-v1to internal v2 projection and fail-closednot_applicablegeometry semantics.Why
Issues #230, #231, and #232 exposed gaps where diagnostics could miss thin line/text crossings, style geometry contracts were ambiguous, or runtime artifacts could be confused with durable project results. The patch adds evidence and boundary clarity without forcing the LLM to make engine-side subjective decisions.
Validation
git diff --checkpassed.uv/adjustTextare unavailable; those environment-specific paths remain for GitHub Actions validation.Release/tagging is intentionally not included; this PR should run the Windows and macOS CI gates first.