test(editor): state the real byte-integrity invariant for GFM cell whitespace

The comment claimed no non-backslash byte is lost, but GFM legitimately trims
cell-edge and collapsed whitespace, so the test asserts the weaker true invariant:
every byte other than backslashes and that trimmed whitespace survives in order.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Sergey Kozyrenko
2026-07-21 03:59:17 +07:00
co-authored by Claude Fable 5
parent 179c814bb3
commit f5070667de
@@ -184,8 +184,8 @@ describe('generative content-integrity — atoms survive load↔serialize across
// The doc side of the same class: rich-mode typing can put a backslash run right before a pipe in a cell —
// a sequence no markdown load produces (marked's splitter consumes one `\` per escaped pipe). GFM cannot
// encode an odd run + pipe exactly, so the serializer pads it by one backslash; assert over random `\`/`|`
// payloads that the padded save is byte-stable immediately, both cells survive, and no non-backslash byte
// is lost or reordered.
// payloads that the padded save is byte-stable immediately, both cells survive, and every byte other than
// backslashes and cell-edge/collapsed whitespace (which GFM legitimately trims) survives in order.
it(
'typed backslash/pipe cell payloads keep the table intact and converge on the first save',
{ timeout: 30000 },