chore: bump taiki-e/install-action from 2.86.5 to 2.86.6

[dependabot]

Bumps taiki-e/install-action from 2.86.5 to 2.86.6.

Release notes

Sourced from taiki-e/install-action's releases.

2.86.6

• Update dprint@latest to 0.56.1.

• Update cargo-lambda@latest to 1.9.2.

• Update biome@latest to 2.5.10.

Changelog

Sourced from taiki-e/install-action's changelog.

[2.86.6] - 2026-08-23

• Update dprint@latest to 0.56.1.

• Update cargo-lambda@latest to 1.9.2.

• Update biome@latest to 2.5.10.

Commits

• 6cd1350 Release 2.86.6
• 0110a1e Update tombi manifest
• 48a83f9 Update rafn manifest
• 4860bfa Update dprint@latest to 0.56.1
• ce8357c Update cargo-lambda@latest to 1.9.2
• e2ae5b3 Update biome@latest to 2.5.10
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[worktrunk-bot]

Approval stands — the red feature-powerset is not from this bump.

That job's Install cargo-hack step (the one this PR bumps) succeeded; the failure is downstream, in cargo hack test --feature-powerset on the --no-default-features --features cli combination. It's a pre-existing snapshot mismatch on main, introduced by #3908 (496c5711), which landed after main's last nightly run — so no run on main has caught it yet. I reproduced it on this PR's merged tree with cargo test --no-default-features --features cli --bin wt md_help, where this PR's diff isn't part of the build at all.

Diagnosis

The guttered snapshot in test_html_comment_inside_a_code_block_is_content (src/md_help.rs) bakes the highlighted rendering of its trailing ```console block:

-[107m [0m [2m[0m[2m[34mwt[0m     (with syntax-highlighting)
+[107m [0m wt                       (cli only)

syntax-highlighting is a default feature, so the required checks (test (linux|macos|windows), fast-checks) build with it on and stay green; only the powerset job exercises cli without it. This is the exact case nightly.yaml's own comment on that job names — "a snapshot baking feature-dependent output, only surfaces when tests are built and run per combo".

The repo already has a convention for this: src/styling/format.rs pairs #[cfg(feature = "syntax-highlighting")] and #[cfg(not(feature = "syntax-highlighting"))] variants so both configurations keep their assertions.

Job: https://github.com/max-sixty/worktrunk/actions/runs/32927061637/job/98052031630

I'm opening a separate PR for the snapshot rather than carrying it here — feature-powerset isn't a required check, so it doesn't gate this merge either way.

[dependabot]

Superseded by #3928.