basalt-26.3.2-rc-20260916: sql/tests: TestSplitAtTableBoundary failed

sql/tests.TestSplitAtTableBoundary failed on basalt-26.3.2-rc-20260916 @ 024cf0f74e8abea8b9fe2f4a05441dac7dc66c41:

=== RUN   TestSplitAtTableBoundary
    test_log_scope.go:172: test logs captured to: outputs.zip/logTestSplitAtTableBoundary3333006503
    test_log_scope.go:82: use -show-logs to present logs inline
    test_server_shim.go:168: automatically injected a shared process virtual cluster under test; see comment at top of test_server_shim.go for details.
    table_split_test.go:53: condition failed to evaluate within 3m45s: from table_split_test.go:60: expected range start key /Tenant/10/Table/106; got /Tenant/10/Table/84
        
        goroutine dump: /mnt/engflow/worker/work/2/exec/bazel-out/k8-fastbuild/testlogs/pkg/sql/tests/tests_test/shard_16_of_16_run_1_of_3/test.outputs/goroutine_dump_2328100483.txt
    panic.go:694: -- test log scope end --
test logs left over in: outputs.zip/logTestSplitAtTableBoundary3333006503
--- FAIL: TestSplitAtTableBoundary (1042.73s)

Parameters:

• attempt=1
• race=true
• run=1
• shard=16

Start with TestSplitAtTableBoundary in sql/tests/table_split_test.go, especially the condition at line 60, and review the linked test report and captured logs. Reproduce the race-enabled failure and determine why the expected range start key /Tenant/10/Table/106 is instead /Tenant/10/Table/84; done means the test passes reliably across the affected branches.