[github-actions]

Prepares v0.4.10, bumped by cargo release patch.

The version and the changelog are the whole diff. Merging this tags
v0.4.10 and starts the release, which builds the binaries and
plays the strength match against the previous release.

Close it without merging to call the release off, nothing has been
tagged or published yet.

[github-actions]

Speed against 2c7f326c

Measured on AMD EPYC 9V45 96-Core Processor.
Both sides built with rustc 1.99.1 (58cf8f9c3 2026-10-13).

Both sides built and run on this runner in this job, the way
scripts/speed.sh measures a perf commit. Each round runs
both sides on a layout of its own, the same compiled code with
its code and data shuffled and moved, so the 95% interval carries
where the code landed as well as the run. The verdict holds the
interval against a 1% threshold. The default layout, the one a
release ships, is measured after as a diagnostic. The node
counts are the search's: they move when the search does, and a
speed change leaves them alone.

round     base nps  candidate nps  change
    1      5498252        5492227   -0.1%
    2      5551994        5525994   -0.5%
    3      5390858        5219425   -3.2%
    4      5352429        5473006   +2.3%
    5      5389748        5399873   +0.2%
    6      5421372        5649100   +4.2%
    7      5359390        5324781   -0.6%
    8      5179140        5309087   +2.5%
    9      5237360        5344982   +2.1%
   10      5356326        5235098   -2.3%
   11      5382984        5399986   +0.3%
   12      5473312        5521885   +0.9%
   13      5480749        5575054   +1.7%
   14      5708210        5434809   -4.8%
   15      5541749        5422663   -2.1%
   16      5691294        5333521   -6.3%
   17      5660868        5673535   +0.2%
   18      5962632        5911028   -0.9%
   19      5571975        5078137   -8.9%
   20      4792800        4826710   +0.7%
   21      5064492        4998328   -1.3%
   22      5090033        5131216   +0.8%
   23      5112753        5070095   -0.8%
   24      5261547        5264298   +0.1%
   25      5142788        5194924   +1.0%
   26      5166378        5109033   -1.1%
   27      5058998        5127735   +1.4%
   28      4928639        5026911   +2.0%
   29      5091759        5008492   -1.6%
   30      5163330        4934628   -4.4%
   31      5075237        5050704   -0.5%
   32      5236482        4938380   -5.7%
   33      5214547        5196196   -0.4%
   34      5047829        5009920   -0.8%
   35      4746155        5105009   +7.6%
   36      5124727        5110800   -0.3%
   37      5159085        5469335   +6.0%
   38      6424850        5811756   -9.5%
   39      6244571        6238045   -0.1%
   40      6319563        6148634   -2.7%

             nodes    time  median nps  faster half
base       9312660  1.75 s     5306988      5639156
candidate  9312660  1.76 s     5286692      5572965
change                           -0.4%        -1.2%

paired change -0.4%, 95% interval -1.4% to +0.4%
diagnostic, on the default layout alone +0.6%, 95% interval -2.5% to +4.1%, 13 rounds

not resolved: the interval reaches past ±1.0% without clearing it, so
more rounds are needed to say either way

Speed: -0.4% (bench nps, 95% interval -1.4% to +0.4%, 40 interleaved rounds over shuffled layouts vs 2c7f326c)

The instructions each side's bench executed, counted under
cachegrind. The count repeats to within a few hundred
instructions, so a small change here is a real one, but it
prices instructions only: cache misses, mispredicted branches
and where the code lands are the speed's to show.

instructions against 2c7f326c, one cachegrind run a side, bench

             instructions    nodes  per node
base       13,159,581,790  9312660    1413.1
candidate  13,159,581,778  9312660    1413.1
change             -0.00%             -0.00%

within ±0.7%, as far as edits not made for speed have moved the count