test(rich-markdown-editor): assert code-like pastes are claimed but preserved byte-for-byte

The gate is intentionally lenient — a precise CommonMark-emphasis matcher would risk missing real
emphasis. Over-claiming is safe because the strict parser (marked) preserves non-markdown exactly;
assert the handler claims the paste and returns the input unchanged, not just that no mark is added.

Author: waleedlatif1

apps/sim/app/workspace/[workspaceId]/files/components/file-viewer/rich-markdown-editor/markdown-paste.test.ts

@@ -143,12 +143,13 @@ describe('markdown paste', () => {
     ['space-flanked asterisks', 'area = 5 * width * height'],
     ['python args and kwargs', 'def foo(*args, **kwargs): pass'],
     ['snake_case identifiers', 'call user_name and file_path_here'],
-  ])('does not emphasize %s (strict CommonMark)', (_label, text) => {
+  ])('claims %s but leaves it byte-for-byte literal (strict CommonMark)', (_label, text) => {
     editor = mount()
-    paste(editor, text)
+    expect(paste(editor, text)).toBe(true)
     const json = JSON.stringify(editor.getJSON())
     expect(json).not.toContain('"type":"italic"')
     expect(json).not.toContain('"type":"bold"')
+    expect(editor.getText()).toBe(text)
   })
 
   it('parses markdown-shaped plain text even when an HTML sibling is present', () => {