# Verification log (V1 to V18)
Unit 1 start-migration. Rows are filled in the step named in the plan (section 3.2). Status: OK, BLOCKED, DEVIATION, open.
## Resolved versions (Step 4, 2026-10-31)
| Package | Version | Note |
|---|---|---|
| `@tanstack/react-start` | 1.169.4 | added exact (pnpm wrote no caret) |
| `@tanstack/react-router` | 1.170.46 | was `^1.170.39` (resolved 1.170.39); raised to Start's own version, see note 1 |
| `@tanstack/router-core` | 1.171.39 | one copy for router and Start |
| `@tanstack/start-plugin-core` | 1.171.55 | transitive |
| `@tanstack/router-plugin` | 1.168.48 | transitive only (inside Start); the direct devDependency was removed |
| `playwright-core` | 1.55.0 | devDependency, exact |
| `zod` (4.x, transitive) | 4.6.7 | via override, see note 2 |
| `vite` | 8.3.1 | unchanged |
Notes:
1. With only `@tanstack/react-start` added, pnpm kept two router copies (`react-router` 1.170.39 for the app and 1.170.46 for Start). The plan's fallback (raise `@tanstack/react-router` to the spike's 1.170.46) removes the second copy. No peer conflict was reported.
2. `pnpm audit:deps` failed after adding Start: high advisory GHSA-mrhx-c7xc-m3w5 (zod < 4.6.6) through `@tanstack/start-plugin-core` and `router-generator`. Fixed by a patch bump only, with a scoped override in `web/pnpm-workspace.yaml` (`zod@4: ^4.6.6`, same pattern as the existing seroval overrides); zod 3 (Chakra CLI, Lighthouse) is not touched. Afterwards `pnpm audit:deps`: no known vulnerabilities. The main session should decide whether it accepts this extra override (BR-BLD-11 only names the seroval overrides as "stay").
3. `seroval` and `seroval-plugins` overrides still apply (`pnpm why seroval`: 1.7.3, both router-core copies).
## Table
| V# | Point | Step | Outcome | Evidence | Status |
|---|---|---|---|---|---|
| V1 | Custom `src/client.tsx` hydrates with Start; `startSentry()` before hydration | 4 | Start picks `src/client.tsx` by name (default entry `client` in `srcDirectory`); it replaces the default entry, whose body is `startTransition(() => hydrateRoot(document, ))`. `startSentry()` runs at module level before that call. | Build output `dist/client/assets/index-*.js` contains `hydrateRoot` and the Sentry loader (`sentryClient-*.js` dynamic import). Chrome (playwright-core, system Chrome, static server, no CSP yet): `/`, `/over-mij`, `/contact`, `/contact?pakket=gezin` hydrate with no console error or warning. Not proven here: that Sentry initialises (only on the test and production hostnames, so a no-op on 127.0.0.1); unit tests of `monitoring/` cover that. | OK |
| V2 | `RouterProvider` in jsdom renders `shellComponent` | 5 | Yes, Router calls the root `shellComponent` (`Match.js`: `ShellComponent = route.isRoot && route.options.shellComponent`). React 19 treats `html`/`head`/`body` as singletons, so no `` lands in the RTL container (container has 0 html/head/body), but it sets `lang="nl"` on `document.documentElement` and wraps `ChakraProvider` a second time. Variant used: `renderApp` replaces the root route's `shellComponent` by a test shell (`HeadContent` + children) on its router instance; production code untouched. | Probe test (removed) printed `shellComponent: function`, `html=0 head=0 body=0`, `document.documentElement lang=nl`. All 888 tests pass with the test shell (with the real shell, 45 of 46 in `app.test.tsx` passed; the one failure was the `/$` register test). | OK |
| V3 | Inline scripts per real page | 4 (first look), 13 (final) | Per page (12 files) the inline executable scripts are: (a) router scroll restoration, 613 chars, no attributes, same body everywhere; (b) Start bootstrap `data-tsr-stream-part=""`, 916 to 1349 chars, differs per page; (c) boundary `document.currentScript.remove();/*$tsr-stream-boundary*/`, 56 chars, same everywhere. `/contact` has two more (lazy form Suspense): `` (57 chars) and the React completion runtime `$RB=[];$RV=function(a){...` (845 chars). No `$RC` seen on other pages. External: `