feat(BA-6883): expose kernel scheduling history over GraphQL v2

[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 ← you are here
• 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

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

Resolves #12852 (BA-6883)

Summary

• Root queries adminKernelSchedulingHistories (super-admin, check_admin_only()) and scopedKernelSchedulingHistories(scope: KernelScope!) (RBAC-resolved), following the adminFoos / scopedFoos convention in api/gql/AGENTS.md rather than the {scope}Foos shape the session / deployment / route slices still use.
• KernelV2.schedulingHistories for walking from a kernel to its history, mirroring AgentV2.sessions. It takes the same filter / order / cursor / offset arguments as the scoped root and injects kernel_id=self.id.
• New types, all with the GQL Python suffix and a suffix-free schema name=: KernelSchedulingHistoryGQL, KernelScopeGQL, KernelSchedulingHistoryFilterGQL, KernelSchedulingHistoryOrderByGQL, KernelSchedulingHistoryOrderFieldGQL, KernelSchedulingHistoryConnectionGQL.
• Kernel history is now orderable by phase, from_status, to_status, result, and attempts as well as the two timestamps. That needed the DTO enum, KERNEL_ORDER_FIELD_MAP, and the GQL enum widened together — the map is keyed by the enum, so they have to stay in step.
• resolve_nodes is backed by a new kernel_history_loader over batch_load_kernel_histories_by_ids; KernelSchedulingHistoryID is the key type end to end. Everything else reuses the adapter from feat(BA-6892): add kernel scheduling-history adapter and REST v2 endpoints #12870 — no new service or repository code.
• added_version uses NEXT_RELEASE_VERSION per api/gql/AGENTS.md.

The history node exposes kernelId / sessionId as scalars and carries no back-reference fields; traversal to the entity goes through KernelV2.schedulingHistories.

SessionV2.kernelHistories from the issue description is intentionally not implemented — a session-wide query needs the action, repository search scope, and RBAC element widened beyond a single kernel, which is service/repository work rather than a GraphQL change.

Test plan

• Schema builds; both roots and the KernelV2 field resolve
• Generated SDL carries the full filter / order / cursor / offset argument set, and no *GQL name leaks into the schema
• Every KernelHistoryOrderField member resolves through resolve_kernel_order
• v2-schema.graphql / supergraph.graphql / openapi.json regenerated
• ruff check / ruff format clean
• Live query against a running manager — blocked: kernel_scheduling_history has no writer (KernelSchedulingHistoryCreatorSpec is called from nowhere), so the table stays empty until BA-6852 lands

🤖 Generated with Claude Code

[Copilot]

Pull request overview

Adds GraphQL v2 access to kernel scheduling history through admin and RBAC-scoped queries.

Changes:

• Adds kernel history GraphQL types, filters, ordering, connections, and resolvers.
• Adds Relay node batch loading through the scheduling-history adapter.
• Regenerates GraphQL schemas and adds a changelog fragment.

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 8 comments.

Show a summary per file

File	Description
schema.py	Registers kernel history query roots.
scheduling_history/types.py	Defines kernel history GraphQL types and inputs.
scheduling_history/resolver.py	Implements admin and scoped queries.
scheduling_history/__init__.py	Exports new GraphQL symbols.
data_loader/data_loaders.py	Adds the kernel history DataLoader.
adapters/scheduling_history/adapter.py	Adds batch loading by history ID.
v2-schema.graphql	Records generated v2 SDL changes.
supergraph.graphql	Records generated federated schema changes.
changes/12989.feature.md	Documents the feature for release notes.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.