Repository navigation
fix(preview): match Aegea 11.5 plain font stack - #4
Merged
Merged
Conversation
hvab
marked this pull request as ready for review
October 19, 2026 11:31
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.
Plain preview typography used InterVariable although the supported Aegea 11.5/v4199 plain theme uses its system font stack. The preview now uses the canonical stack; note and small fonts retain inheritance. Plain ZIPs continue to inherit the engine's fonts, and explicit system/Google choices retain their existing behavior.
Refreshed against main 6b69a41, preserving R01 validation, R02/R03/R05 and hvab-blocks v0.3.0. The merge conflict was confined to the progress document. The target remains Aegea 11.5/v4199 at e1d058356e5426bb1878785c6f4ab4e68b6c4995; current development markup, variable names and preview states were checked without adopting its Inter font default.
Validation: clean npm ci; 131/131 tests; targeted font regression 3/3; JavaScript/style lint, full formatting and production build pass. The regression fails on main's unpatched CSS for the intended font-stack assertion. Independent review found no issues; root accepted the minimal source diff and browser smoke. On macOS, EN/light and RU/dark plain computed stacks inherit correctly; explicit Sans-serif/Georgia overrides work; PT Sans in both slots creates one Google CSS link, removed on return to plain. The shell retains its own font stack. These checks do not establish rasterized font identity or live Aegea paired widths/linebreaks. A fresh PHP startup check remains blocked by missing libzip.5.dylib. Published code commit: 8e1685e. CI succeeded for that commit, and PR #4 is mergeable against main 6b69a41. This CI result does not claim coverage for the subsequent documentation-only update. The owner decides whether to merge; unresolved live Aegea parity remains a separate verification limit. No PR merge is authorized as part of this refresh.