Address the following comment on examples/trpc-prisma-firecrawl/prisma/schema.prisma at line 47:

<comment>Use Prisma&#39;s Json type for JSON fields to preserve type-safety instead of storing serialized JSON in String.</comment>

<file context>
@@ -0,0 +1,54 @@
+  allowExternalLinks Boolean @default(false)
+  
+  // Results
+  pages       String?  // Store array of scraped pages as JSON string
+  totalPages  Int      @default(0)
+  
</file context>

Address the following comment on examples/trpc-prisma-firecrawl/prisma/schema.prisma at line 26:

<comment>Use Prisma&#39;s Json type for JSON fields to preserve type-safety instead of storing serialized JSON in String.</comment>

<file context>
@@ -0,0 +1,54 @@
+  content     String?
+  markdown    String?
+  html        String?
+  metadata    String?  // Store additional metadata as JSON string
+  
+  // Error information
</file context>

Address the following comment on examples/trpc-prisma-firecrawl/README.md at line 98:

<comment>Wrap mutation payload under `input` for tRPC HTTP requests; current curl example will not match expected input shape.</comment>

<file context>
@@ -0,0 +1,197 @@
+
+#### Crawl a Website
+```bash
+curl -X POST http://localhost:3000/trpc/crawl.crawlUrl \
+  -H &quot;Content-Type: application/json&quot; \
+  -d &#39;{&quot;baseUrl&quot;: &quot;https://example.com&quot;, &quot;maxPages&quot;: 5}&#39;
</file context>

Address the following comment on examples/trpc-prisma-firecrawl/README.md at line 74:

<comment>tRPC mutation body should be wrapped under `input`; posting the raw fields will not match tRPC’s expected request shape.</comment>

<file context>
@@ -0,0 +1,197 @@
+
+#### Scrape a URL
+```bash
+curl -X POST http://localhost:3000/trpc/scrape.scrapeUrl \
+  -H &quot;Content-Type: application/json&quot; \
+  -d &#39;{&quot;url&quot;: &quot;https://example.com&quot;, &quot;includeMarkdown&quot;: true}&#39;
</file context>

Address the following comment on examples/trpc-prisma-firecrawl/src/routers/crawl.ts at line 86:

<comment>Use TRPCError with NOT_FOUND instead of a generic Error so clients receive a proper tRPC error code.</comment>

<file context>
@@ -0,0 +1,123 @@
+      });
+
+      if (!job) {
+        throw new Error(&#39;Job not found&#39;);
+      }
+
</file context>

Address the following comment on examples/trpc-prisma-firecrawl/src/client-example.ts at line 72:

<comment>Prefer nullish coalescing over || so a valid length of 0 doesn’t trigger the fallback.</comment>

<file context>
@@ -0,0 +1,83 @@
+      console.log(&#39;- Status:&#39;, jobDetails.status);
+      console.log(&#39;- Created:&#39;, jobDetails.createdAt);
+      console.log(&#39;- Title:&#39;, jobDetails.title);
+      console.log(&#39;- Content length:&#39;, jobDetails.content?.length || 0, &#39;characters&#39;);
+    }
+
</file context>

Address the following comment on examples/trpc-prisma-firecrawl/src/client-example.ts at line 58:

<comment>If error exists but is undefined, this will log &quot;undefined&quot; instead of a fallback; use nullish coalescing to ensure a meaningful message.</comment>

<file context>
@@ -0,0 +1,83 @@
+      console.log(&#39;Total pages:&#39;, crawlResult.job.totalPages);
+      console.log(&#39;Status:&#39;, crawlResult.job.status);
+    } else {
+      console.log(&#39;Crawl failed:&#39;, &#39;error&#39; in crawlResult ? crawlResult.error : &#39;Unknown error&#39;);
+    }
+
</file context>

Address the following comment on examples/trpc-prisma-firecrawl/src/client-example.ts at line 29:

<comment>If error exists but is undefined, this will log &quot;undefined&quot; instead of a fallback; use nullish coalescing to ensure a meaningful message.</comment>

<file context>
@@ -0,0 +1,83 @@
+      console.log(&#39;Title:&#39;, scrapeResult.job.title);
+      console.log(&#39;Status:&#39;, scrapeResult.job.status);
+    } else {
+      console.log(&#39;Scrape failed:&#39;, &#39;error&#39; in scrapeResult ? scrapeResult.error : &#39;Unknown error&#39;);
+    }
+
</file context>

Address the following comment on examples/trpc-prisma-firecrawl/src/client-example.ts at line 76:

<comment>Use logger.error instead of console.error for error logging, and pass structured context (&quot;&lt;message&gt;&quot;, { error }) rather than multiple arguments.</comment>

<file context>
@@ -0,0 +1,83 @@
+    }
+
+  } catch (error) {
+    console.error(&#39;❌ Error:&#39;, error);
+  }
+}
</file context>