fix(crawl-jobs): include complete page content and details in job query
Problem Description
In CrawlJobRepository.findById, the Prisma query previously specified a restrictive select projection for related pages (id, url, normalizedUrl, contentHash, wordCount, status, statusCode, title, crawledAt).
This projection omitted critical crawled data fields such as content, markdown, and htmlContent, preventing the API and frontend from accessing and viewing the actual crawled content of pages within a crawl job.
Proposed Changes
src/modules/crawl-jobs/crawl-job.repository.ts
- Replaced the restricted projection
pages: { select: { ... } }withpages: true. - Ensured all page entity fields (including parsed content, markdown, error logs, and metadata) are retrieved when fetching a job by ID.