Fix MDX compile error: use marked instead of MDXRemote for Supabase posts

Supabase posts contain raw markdown, not MDX. MDXRemote fails on
standard HTML tags like img. DynamicPostView now uses marked to
render markdown to HTML directly.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: Yushin-L

src/components/posts/DynamicPostView.tsx

@@ -2,7 +2,7 @@
 
 import { useEffect, useState } from "react";
 import { getPublishedPostBySlug } from "@/lib/drafts/published";
-import PostContent from "./PostContent";
+import MarkdownContent from "./MarkdownContent";
 import TagBadge from "./TagBadge";
 import LikeButton from "./LikeButton";
 import CommentSection from "@/components/comments/CommentSection";
@@ -63,7 +63,7 @@ export default function DynamicPostView({ slug }: DynamicPostViewProps) {
           </div>
         </div>
       </header>
-      <PostContent content={post.body} />
+      <MarkdownContent content={post.body} />
       <div className="mt-10 flex items-center justify-center border-t border-stone-200 pt-8">
         <LikeButton postSlug={slug} />
       </div>

src/components/posts/MarkdownContent.tsx

@@ -0,0 +1,21 @@
+"use client";
+
+import { useMemo } from "react";
+import { marked } from "marked";
+
+interface MarkdownContentProps {
+  content: string;
+}
+
+export default function MarkdownContent({ content }: MarkdownContentProps) {
+  const html = useMemo(() => {
+    return marked.parse(content, { async: false }) as string;
+  }, [content]);
+
+  return (
+    <div
+      className="prose prose-stone max-w-none prose-headings:tracking-tight prose-pre:bg-[#1e1e2e] prose-pre:text-[#cdd6f4] prose-a:text-indigo-600 prose-blockquote:border-l-indigo-500"
+      dangerouslySetInnerHTML={{ __html: html }}
+    />
+  );
+}