Please address the comments from this code review:
## Overall Comments
- Many of the custom memo comparators only check “children” and ignore other props, which can lead to stale renders when those props change—please update the comparators to include all relevant props or remove them if unnecessary.
- Splitting the markdown into separate blocks via marked.lexer may break nested or cross-block constructs (like footnotes or multi-line formatting) – verify that context is preserved or adjust the parsing to handle edge cases.
- The new parseIncompleteMarkdown utility is very regex-heavy and could impact performance on larger inputs—consider refactoring or memoizing its logic to reduce overhead.

## Individual Comments

### Comment 1
<location> `src/hooks/useMarkdown/useMarkdownComponents.tsx:46` </location>
<code_context>
-  const memoSection = useMemo(() => {
-    return (props: any) => <Section showFootnotes={showFootnotes} {...props} />;
-  }, [showFootnotes]);
+  const memeP = useCallback(({ children, ...rest }: any) => {
+    const hasImage = typeof children === 'object';
+    return hasImage ? children : <p {...rest}>{children}</p>;
+  }, []);

</code_context>

<issue_to_address>
The logic for detecting images in memeP may be too broad.

The current check will match arrays and React elements, not just images. Please update the logic to specifically identify image elements to avoid incorrect handling of other content types.
</issue_to_address>

<suggested_fix>
<<<<<<< SEARCH
  const memeP = useCallback(({ children, ...rest }: any) => {
    const hasImage = typeof children === 'object';
    return hasImage ? children : <p {...rest}>{children}</p>;
  }, []);
=======
  const memeP = useCallback(({ children, ...rest }: any) => {
    // Helper to check if a React element is an image
    const isImageElement = (el: any) =>
      el && el.type === 'img';

    let hasImage = false;
    if (Array.isArray(children)) {
      hasImage = children.every(isImageElement);
    } else {
      hasImage = isImageElement(children);
    }

    return hasImage ? children : <p {...rest}>{children}</p>;
  }, []);
>>>>>>> REPLACE

</suggested_fix>

### Comment 2
<location> `src/hooks/useMarkdown/parseIncompleteMarkdown.ts:285` </location>
<code_context>
+
+// Parses markdown text and removes incomplete tokens to prevent partial rendering
+export const parseIncompleteMarkdown = (text: string): string => {
+  if (!text || typeof text !== 'string') {
+    return text;
+  }
+
</code_context>

<issue_to_address>
Returning non-string values from parseIncompleteMarkdown may cause downstream issues.

Downstream consumers may receive non-string values if invalid input is passed. Recommend returning an empty string for invalid input to ensure consistent output type.
</issue_to_address>

<suggested_fix>
<<<<<<< SEARCH
  if (!text || typeof text !== 'string') {
    return text;
  }
=======
  if (!text || typeof text !== 'string') {
    return '';
  }
>>>>>>> REPLACE

</suggested_fix>

### Comment 3
<location> `src/Markdown/components/CodeBlock.tsx:43` </location>
<code_context>
+export const CodeBlock = memo<CodeBlockProps>(
</code_context>

<issue_to_address>
Memoization only on children may miss prop changes affecting rendering.

Include all props that impact rendering in the memoization comparator to prevent outdated renders when those props change.
</issue_to_address>