[worktrunk-bot]

Weekly CI pin bump. Only worktrunk drifted since last week — every other baptiste0928/cargo-install pin (cargo-affected 0.4.0, cargo-insta 1.48.0, cargo-nextest 0.9.143, cargo-llvm-cov 0.9.0, cargo-msrv 0.19.3, cargo-udeps 0.1.61, lychee 0.24.2), plus setup-nu 0.115.1 and the .codex/cloud.sh / setup-web pins (pre-commit 4.6.2, PowerShell 7.6.5), is already at the latest upstream release.

• worktrunk =0.75.0 → =0.76.0 (3 sites: ci.yaml ×2, nightly.yaml)

Compatibility: worktrunk 0.76.0 declares rust-version = 1.97, matching the pinned toolchain (rust-toolchain.toml channel 1.97.0), so it builds under baptiste0928/cargo-install.

This is the wt that runs the suite (wt hook pre-merge) on all three platforms, so it goes on its own PR — its own matrix is the only place the bump gets tested. The 0.76.0 breaking changes are in wt switch --execute argv handling, retired commit.generation config keys, and the library API; none of them touch wt hook pre-merge.

Checks that found no drift

• MSRV/toolchain: current stable is 1.98.1, so latest−1 is 1.97, already what Cargo.toml, tests/helpers/wt-perf/Cargo.toml, and rust-toolchain.toml pin. The nightly-2026-08-01 pins in nightly.yaml are ~5 weeks old, inside the three-month window.
• Runner images: ubuntu-24.04, macos-26, and windows-2025 each still equal their -latest label in the actions/runner-images availability table; ubuntu-24.04-arm and macos-26-intel follow those rows. Ubuntu 26.04 is badged preview, so not a bump target.
• dependabot.yaml typescript ignore: npm view @astrojs/check peerDependencies.typescript is still ^5.0.0 || ^6.0.0 against a current typescript major of 7, so the major-version ignore entry stays (fix(docs): pin typescript to ^6 so npm ci resolves #3877).