ci: bump soothfast to v0.3.2

[Verdenroz]

Description

CHANGELOG.md's Unreleased section currently lists Regenerate soothfast outputs (#474) and Regenerate derived artifacts (#473). Both are soothfast-bot commits that exist only to land generated files, so two of the changelog's entries describe the changelog regenerating itself. The cause was upstream and is fixed in v0.3.2, where the generator reads the author alongside the subject and drops the commits its own bot wrote. This repo's entire share of the fix is a version pin.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that causes existing functionality to change)
• Documentation update
• Refactoring (no functional changes)
• Performance improvement

Changes

• Bumped the pinned Verdenroz/soothfast action from 80b18d8831521646b65fec79c6df14d6f763c602 (v0.3.1) to 69e2e9250414bd1dcaa1f45529f1e3fe12c593dd (v0.3.2) at all 13 pin sites: 8 in soothfast.yml, 2 in deploy.yml, 2 in io-probe.yml, 1 in sdk-publish.yml.
• Covered both kinds of pin. Eleven are uses: Verdenroz/soothfast@<sha>; the other two are ref: on the actions/checkout steps in deploy.yml and io-probe.yml that sparse-check-out the action's action/ directory for land.sh. The two kinds are kept in lockstep. A bump driven by a uses: grep alone misses the ref: pins and leaves those workflows running v0.3.1 scripts against a v0.3.2 CLI.
• Left soothfast.toml alone. The generator's default bot author is soothfast-bot[bot], which is what this repo's bot commits are already authored by, so a [changelog] bot-author key would only be one more value to drift.
• Left soothfast.lock, Cargo.toml and Cargo.lock alone. 0.3.1 to 0.3.2 is caret-compatible; only the action SHAs are pinned by hand.

Breaking Changes

None. The composite action and its seven shell scripts are byte-identical between the two tags, so the bump changes the CLI and nothing else. No library, server, or MCP code is touched.

Testing

• Unit tests added/updated
• Integration tests added/updated
• Manual testing performed
• All tests pass (cargo test)

The change is YAML only, so no cargo gate applies and the boxes above stay unticked. What ran, on all four changed workflows:

• python3 -c "import yaml; yaml.safe_load(open(f))" parses each of soothfast.yml, deploy.yml, sdk-publish.yml, io-probe.yml.
• zizmor --no-online-audits over the four reports no findings (27 suppressed).
• prek run --files over the four passes.
• grep -rn '80b18d8831521646b65fec79c6df14d6f763c602' .github/ returns nothing, and grep -ro '69e2e9250414bd1dcaa1f45529f1e3fe12c593dd' .github/ | wc -l returns 13.
• actionlint did not run. It is not installed on the machine this was written on.

The fix itself cannot be verified before merge, since it only shows up when the bot next regenerates the changelog on master. Two things to check then. The Unreleased section should no longer carry Regenerate soothfast outputs or Regenerate derived artifacts under ### 🔧 Internal. The ### 📦 Dependencies section must still list its dependabot entries, Bump debian from ... and Bump rust from .... The filter compares the author string exactly, so dependabot[bot] should survive it; dependabot entries disappearing would mean the filter is over-matching, which is a worse bug than the one this fixes and is grounds to revert.

Documentation

• Code documentation updated (doc comments)
• README updated (if needed)
• CHANGELOG.md updated (if releasing)
• Examples updated (if API changed)

CHANGELOG.md is deliberately not touched here. The Unreleased section is generated, and the bot rewrites it after merge.

Checklist

• Code compiles without warnings (cargo check)
• Tests pass (cargo test)
• Code formatted (cargo fmt)
• Clippy checks pass (cargo clippy)
• Documentation builds (cargo doc --no-deps)
• Commit messages follow Conventional Commits

Related Issues

Closes #480

Third in a stack. Base is ci/bot-land-sdk-regeneration, so this stacks on #487, which stacks on #486, and it merges last. #486 and #487 both rewrite soothfast.yml and deploy.yml, which this also touches.

[soothfast-bot]

soothfast gate

finance-query

ok    finance_query::ticker_quote_then_cached allocs 4 -> 4 (allowed <= 4)
ok    finance_query::ticker_quote_then_cached alloc_bytes 43864 -> 43864 (allowed <= 46057)
ok    finance_query::tickers_batch_quote_then_cached walltime_median_ns 10225.3 -> 10225.3 (+0.0%)
ok    finance_query::tickers_batch_quote_then_cached allocs 16 -> 16 (allowed <= 16)
ok    finance_query::tickers_batch_quote_then_cached alloc_bytes 134810 -> 134810 (allowed <= 141550)
ok    finance_query::translate_dictionary walltime_median_ns 1984.0 -> 1984.0 (+0.0%)
ok    finance_query::translate_dictionary allocs 49 -> 49 (allowed <= 51)
ok    finance_query::translate_dictionary alloc_bytes 2880 -> 2880 (allowed <= 3024)
ok    finance_query::translation_set_backend walltime_median_ns 17.9 -> 17.9 (+0.0%)
ok    finance_query::translation_set_backend allocs 1 -> 1 (allowed <= 1)
ok    finance_query::translation_set_backend alloc_bytes 16 -> 16 (allowed <= 16)
ok    finance_query::translation_translate walltime_median_ns 3540.0 -> 3540.0 (+0.0%)
ok    finance_query::translation_translate allocs 79 -> 79 (allowed <= 82)
ok    finance_query::translation_translate alloc_bytes 6298 -> 6298 (allowed <= 6612)
ok    finance_query::translation_translate_with walltime_median_ns 3499.5 -> 3499.5 (+0.0%)
ok    finance_query::translation_translate_with allocs 77 -> 77 (allowed <= 80)
ok    finance_query::translation_translate_with alloc_bytes 6294 -> 6294 (allowed <= 6608)
ok    finance_query::bt_base_to_htf_index assert complexity: claimed O(n); growth drift x1.24 over sizes [1024, 4096, 16384] (limit x2.5)
ok    finance_query::bt_resample assert complexity: claimed O(n); growth drift x0.94 over sizes [1024, 4096, 16384] (limit x2.5)
ok    finance_query::bt_sma_crossover assert complexity: claimed O(n); growth drift x1.03 over sizes [1024, 4096, 16384] (limit x2.5)
ok    finance_query::capability_name assert alloc: allocs 0 <= 0
ok    finance_query::de_quote assert p99: p99 979431ns <= 3000000ns
ok    finance_query::dispatch_select assert alloc: allocs 0 <= 0
ok    finance_query::ind_patterns assert complexity: claimed O(n); growth drift x0.95 over sizes [1024, 4096, 16384] (limit x2.5)
ok    finance_query::ind_sma assert alloc: allocs 1 <= 1
ok    finance_query::ind_sma assert p99: p99 382402ns <= 1000000ns
ok    finance_query::ind_sma assert complexity: claimed O(n); growth drift x1.01 over sizes [1000, 10000, 100000] (limit x2.5)
ok    finance_query::risk_beta assert alloc: allocs 0 <= 0
ok    finance_query::risk_beta assert complexity: claimed O(n); growth drift x1.02 over sizes [1024, 4096, 16384] (limit x2.5)
ok    finance_query::risk_calmar assert alloc: allocs 0 <= 0
ok    finance_query::risk_historical_var assert alloc: allocs 2 <= 2
ok    finance_query::risk_historical_var assert complexity: claimed O(n log n); growth drift x1.23 over sizes [1000, 10000, 100000] (limit x2.5)
ok    finance_query::risk_max_drawdown assert alloc: allocs 1 <= 1
ok    finance_query::risk_parametric_var assert alloc: allocs 0 <= 0
ok    finance_query::risk_parametric_var assert complexity: claimed O(n); growth drift x1.00 over sizes [1024, 4096, 16384] (limit x2.5)
ok    finance_query::risk_sharpe assert alloc: allocs 0 <= 0
ok    finance_query::risk_sharpe assert complexity: claimed O(n); growth drift x1.00 over sizes [1024, 4096, 16384] (limit x2.5)
ok    finance_query::risk_sortino assert alloc: allocs 0 <= 0
ok    finance_query::risk_sortino assert complexity: claimed O(n); growth drift x1.01 over sizes [1024, 4096, 16384] (limit x2.5)
gate: passed (180 item(s))