Repository navigation
Document model-assisted Java Encoder review workflow - #248
Merged
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.
Change
Add first-party MODELS.md development and review instructions for Java Encoder. The review workflow covers parser boundaries, streaming, exact output, Java 8 and packaged compatibility, taglib parity, private vulnerability handling, and the existing CI and release controls. References use “operator.”
Compatibility and validation
Documentation only; no runtime or public API changes. Verified all 13 local links, Markdown fences and whitespace; git diff --cached --check passed. Runtime tests were not run locally for this documentation-only change; required CI applies.
AI assistance: Codex drafted and checked this guidance. The listed model lineup does not claim that those reviews ran.