Add configurable English note output - #26
Open
basbun wants to merge 1 commit into
Open
Conversation
basbun
marked this pull request as ready for review
August 25, 2026 10:55
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.
Adds end-to-end English output while preserving zh-CN as the backward-compatible default.\n\nHighlights:\n- language-aware note schema, metadata fields, figure labels, and analytical-flow heading\n- localized paper-type planning contracts and figure placement guidance\n- English-aware grounding, note linting, and Formal Save validation\n- configuration through DEEPPAPERNOTE_OUTPUT_LANGUAGE=en or --language en\n- English documentation and regression tests\n\nValidation:\n- 826 passed, 1 skipped\n- skill quick validation passed\n- plugin validation passed\n- five real English dissertation notes passed every lint gate with no warnings