- Stack: Next.js 14 App Router, React 18, Tailwind CSS, Vitest, React Testing Library
- Main routes:
/,/results/[jobId],/workbench/mock,/api/jobs,/api/jobs/[jobId] - Job data persists through
DBOT_RUNTIME_FILEordata/runtime/jobs.json
npm run dev- start the local Next.js appnpm test- run the Vitest suitenpm run lint- run Next.js lintnpm run build- run the production buildnpm run typecheck- runnext build >/dev/null && tsc --noEmit
- Run
npm run buildandnpm run typechecksequentially, not in parallel, because both write.next. - Prefer
npmcommands here;package-lock.jsonis present and the repo scripts are defined inpackage.json. - Preserve the current stage order:
Discover,Partition,Extract,Generate,Validate. - Preserve the export tab names:
DESIGN.md,Design JSON,Tailwind v4,CSS Variables,Design Tokens. - Keep the one-main-
DESIGN.mdplus partition-appendix policy unchanged. - Keep crawling shallow and same-origin. Current evidence capture is HTML-first; Batch 9 explicitly excluded browser rendering and external stylesheet fetching.
- Failed jobs and partial-coverage resume both use the existing
GET /api/jobs/[jobId]?retry=1surface. /workbench/mockis fixture-backed only; live jobs should continue through the persisted job flow.
- Latest completed handoff in-repo is Batch 9: lightweight visual hints in crawled pages, evidence-backed palette/typography derivation, and page-role-based component preview labels.
- The documented next step is Batch 10: improve visual-hint fidelity by parsing bounded same-origin stylesheet references without changing the route, result, or workbench contracts.
pages/_app.tsxandpages/_document.tsxare compatibility shims for build stability.- The repo is currently not initialized as a git repository.