test(BA-6953): add component tests for the kernel scheduling-history REST v2 endpoints

[jopemachine]

📚 Stacked PRs

• fix(BA-6887): reference the real from_status/to_status columns in kernel history conditions #12857 — BA-6887 fix: kernel history conditions reference the real status columns ✅
• feat(BA-6889): add kernel scheduling-history query conditions and orders #12867 — BA-6889 models: kernel query conditions and orders ✅
• feat(BA-6890): add kernel scheduling-history repository search scope #12868 — BA-6890 repository: kernel search scope and scoped search ✅
• feat(BA-6891): add kernel scheduling-history v2 DTOs and service actions #12869 — BA-6891 DTO + service: kernel v2 DTOs and search actions ✅
• feat(BA-6892): add kernel scheduling-history adapter and REST v2 endpoints #12870 — BA-6892 adapter + REST v2: kernel endpoints ✅
• feat(BA-6883): expose kernel scheduling history over GraphQL v2 #12989 — BA-6883 GraphQL v2: kernel history roots
• feat(BA-6893): add kernel scheduling-history SDK v2 client and CLI commands #12866 — BA-6893 SDK + CLI: kernel commands
• test(BA-6953): add component tests for the kernel scheduling-history REST v2 endpoints #12997 — BA-6953 component tests: kernel REST v2 endpoints ← you are here

Merge in order, bottom-up. Each PR is based on the one above it, so its diff shows only its own layer.

Resolves #12994 (BA-6953)

Summary

• Eight component tests driving both kernel routes through V2SchedulingHistoryClient against a real aiohttp server and DB: /kernels/admin/search and /kernels/scoped/search. The layers below are unit-tested, but nothing exercised the HTTP boundary for these two.
• Covers what tests/component/AGENTS.md scopes to this layer — routing, the auth middleware on each route, and request/response serialization — rather than re-testing filter semantics that tests/unit already owns.
• The directory conftest previously registered only the v1 route tree; it now mounts the v2 sub-registry too, so both suites share one server. The pre-existing v1 tests still pass unchanged.
• kernel_scheduling_history has no writer yet (BA-6852), so the fixture seeds history rows directly, alongside the real kernels / sessions rows the scoped endpoint's existence check needs.

Unlike the existing v1 tests in this directory, which assert only that the response shape is valid against an empty table, these seed data and assert on actual rows — two kernels under one session, three history rows on one and one on the other, so scoping is observable rather than vacuous.

Writing them caught two things that unit tests had not: from_status / to_status must be valid KernelSchedulingPhase members (a "PENDING" seed produced a 500), and SessionRow requires domain_id alongside domain_name.

Test plan

• tests/component/scheduling_history/test_kernel_history_v2.py — 8 passed
• Whole directory including the pre-existing v1 suite — 20 passed
• ruff check / ruff format clean
• BUILD already present in the directory; no new test directory added

🤖 Generated with Claude Code