[diegosouzapw]

Summary

This is the wave-2/3 checkpoint of the CI UI Kit migration (KEA-7886). All 11 lotes are integrated on feat/new-uikit (95ff9c2f), and this branch adds the release/v3.8.53 back-merge. I validated it with:

• the full battery and a production build on the .113;
• the whole e2e suite in both themes, plus axe;
• a smoke of 73 routes in light 1440, dark 1440 and light 390, with axe on each route.

No adapter or cross-lote break turned up. The integration left two test reds, both realigned here with the assertion unchanged:

• a new test:unit red caused by lote 6's markup change;
• an inherited a11y race that now fails every time on the integrated tree.

⚠️ base-red inherited: #17219

Commits

SHA	What	Why
07292564	Merge origin/release/v3.8.53 (e8f4a829)	Back-merge, 0 conflicts. It brings #17853 (vite 8.3.5), #17316 (hono), #17314 (follow-redirects), #17352 (MCP server 2.3.1), #17845 (README i18n mirrors) and #17226 (streaming finalizers). Both sides touched package-lock.json, so I checked it: the root entry matches package.json, the release bumps and the kit deps are all present, and npm ls --package-lock-only reports the same 12 optional-peer errors as the release's own lockfile.
3ae3744a	test(e2e): a11y settings waits for the general redirect before axe	/dashboard/settings redirects to /general as a client navigation about 330 ms after load, and that navigation destroys axe's evaluate context. The test was flaky in wave 1 and fails 3/3 now. It now waits for the URL and the load. Route, spec and helper are identical to the release. Verified on the .113 with 3 runs and no retries: 5/5 each time.
7b3491ff	test(dashboard): pool wizard's exclusive checkbox is the Checkbox adapter	Lote 6 moved PoolWizard's raw checkbox to the Checkbox adapter, so the source-level test that pinned type="checkbox" went red. It passes on the release. The same assertion now checks the adapter import plus <Checkbox … checked={exclusive}>. Result is 15/15, and it fails if the binding breaks.

Validation (head 07292564; the two test commits verified as described above)

Gate	Host	Result
lint, typecheck:core, open-sse-typecheck, dashboard-typecheck (194 within baseline), ui-icu (933 978 msgs / 67 catalogs)	.113	all rc 0
test:vitest	.113	56/56 files, 588/588 tests
test:vitest:ui	.113	3 files / 17 tests failed with 5 s timeouts (modelsCombosCatalog, api-key-routing-editor, radar-guided-setup-action). All 3 pass alone with 60 s budgets, so the cause is load.
test:unit	.113	55 054 pass / 52 fail. Of the 52, 34 are environment (onnx host npm ×17, provenance needs .git ×17) and 17 are load or the copy without .git. Those were already classified in wave 1, or pass locally. The remaining 1 is quota-pool-wizard, a migration red fixed in 7b3491ff.
build	.113	rc 0, "Turbopack build encountered 232 warnings" (= base)
e2e, full suite (35 specs)	.113	light 112 passed / 5 failed / 36 skipped; dark 113 passed / 5 failed / 36 skipped (theme probed). The 5 failures are the group-b-* specs, which hard-code http://localhost:20128 while the run used port 20189 — an environment issue, identical on the release.
axe (a11y.spec)	.113	After 3ae3744a: login 0/1, dashboard 1/4, providers 1/3, settings 0/5. Lote 5a cleared the settings select-name/label violations.
cycles 14 (= baseline), ui-kit-snapshot, tracked-artifacts, vi parity 5/5, docs-all, key completeness (advisory: 111 keys × 64 locales)	local	green
smoke: 73 routes × 3 captures + axe	local dev	0 error boundaries; 0 page overflow except /landing at 390 px; 0 Material spans on every lote route (only /landing, which no lote owns, has 13)

Leftovers for F4 (screen-level, inherited, or out of scope; not fixed here)

• Contrast:
  • ProviderSummaryCard /N denominators (still present from wave 1);
  • console-log timestamps (#484f58);
  • context engine rows;
  • profile badges, which also have 23 raw buttons.
• Raw buttons on /runtime and /search-tools.
• The onboarding stepper still overflows at 390 px.
• /landing is legacy and was in no lote.
• Inherited runtime issues:
  • MCP/A2A t.rich passes functions into {code} placeholders (React "Functions are not valid as a React child");
  • not-found inside the dashboard hits MISSING_MESSAGE publicSystem;
  • the relay curl example causes a hydration mismatch off port 20128.

Screenshots are at _artifacts/ckpt2-<route>-{light,dark,390}.png. The full report is in the private tasks repo at reports/uikit/wave2-checkpoint.md.