docs(samples): add the scroll-sync stress document, by @Guardiancelte - #516
Merged
Conversation
3,164 lines: 124 headings, 543 table rows, three Mermaid diagrams, code blocks in eight languages, footnotes, math, raw HTML and text in seven scripts. Written to compare Markdown readers, and the document that found both defects fixed in #515 — a table's rows and a rendered diagram report positions the scroll mapping could not read. Authored to @Guardiancelte, who wrote it, reported #205 and retested every round of scroll-sync fixes against it.
This was referenced Aug 7, 2026
PathGao
pushed a commit
that referenced
this pull request
Aug 7, 2026
This reverts commit a33c37d, so that the next commit can add the same file back under the name of the person who wrote it. The squash merge rewrote the author. The pull request carried one commit, authored to @Guardiancelte through his GitHub noreply address; squashing replaced that with the account that opened the pull request, so the file landed with no trace of him in the history and he did not appear in the repository's contributor list. `master` is protected, so the commit could not be amended in place. Net effect of this commit and the next one on the tree: nothing. The file comes back byte for byte. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
PathGao
pushed a commit
that referenced
this pull request
Aug 7, 2026
Learned from #516. The rule is one line; the reason it needs writing down is that the damage is invisible at merge time and unfixable afterwards on a protected branch. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
|
No worries, that is actually my first public commit then ;). Honoured that is for such a cool project. |
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
2 participants
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.
The document @Guardiancelte has been retesting scroll sync against, kept in the repository so the next change to it has the same thing to fail against.
3,164 lines — 124 headings, 543 table rows, three Mermaid diagrams, code blocks in eight languages, footnotes, math, raw HTML and text in seven scripts. It is what found both defects fixed in #515: a table's rows and a rendered diagram report positions the scroll mapping could not read, and neither showed up in a fixture written by the person fixing the bug.
The commit is authored to him, through his GitHub noreply address, because he wrote it — this is his contribution, not ours carrying his file. @Guardiancelte, if you would rather it were not committed here, or not under your name, say so and it comes straight back out.
He also reported #205 and retested every round of fixes against it: #196, #304, #316, #474, and now #515.