[erikdarlingdata]

This is a CI-only merge train. Do not merge it. Each member lands as its own squash once this train's CI is green.

Base: dev 843218d. Train head: e0fb24f, tree 9dbfe904f.

Members, in landing order:

• lane-orders: the PostgreSQL rig recipe also creates the darling database, as CI does #5292 docs/lane-orders-darling-database, head 1d67bfc, train commit 20fb955
• Web charts: show the queries, blocking or deadlocks at the clicked time (#5230) #5286 feat/5230-chart-at-this-time, head df2061c, train commit 01a884b
• Balance the Lite test shards by recorded test time instead of class-name hash (part of #5208) #5280 ci/5208-duration-aware-shards, head 79d56e1, train commit 5bac8c8
• Darling store: an hourly row-count ledger for query_stats (V164) (part of #4605) #5289 feat/4605-hour-ledger, head 80265f8, train commit e0fb24f

What this train's CI has to show:

• Balance the Lite test shards by recorded test time instead of class-name hash (part of #5208) #5280 changes how the Lite test shards are cut. The gate's notice names a timing run, and its artifact list names all four timing files. Every shard passes the artifact-set check, prints "cut by duration" with the same plan id, and finishes close to the others. The "Shard packer self-test" step passes on shard 0.

#5290 is stacked on #5289 but is not in this train. It changes three files that #5289 adds, so its squash conflicts with #5289's. It will merge dev after this train lands and ride the next train.

No combined local build was run. Each member's own tests ran on its branch before it was handed over. No member changes the tools/list budget.

[erikdarlingdata]

Train 29 landed: all four members are on dev as their own squashes, and dev's tree matches this train's (9a089ff).