test(email): add client compatibility fixture matrix - #103
Merged
TheAggressive merged 1 commit intoSep 21, 2026
Merged
Conversation
Add compiled scenarios, per-client structural expectations, limitation records, and deliberate regression checks. Refs #72.
TheAggressive
deleted the
test/issue-72-client-compatibility-fixtures
branch
September 21, 2026 01:37
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.
Summary
Verification
pnpm qa:fastpassed (including 19 JS suites, 133 tests).pnpm testpassed (1,091 PHP tests, 4,995 assertions).git diff --checkpassed.Scope
These are structural regression fixtures. They do not execute client sanitizers or prove visual rendering. The navigation output in #102 still needs coverage from this matrix before that PR is merged.
Closes #72.