sb-dev-merge-dependabotlisted

# Merge SpecBind Dependabot updates This is a maintenance workflow for the SpecBind repository itself. It is not installed into consumer projects. A request to inspect or assess updates is read-only; merge, close, commit, and push only when the user asks to incorporate or otherwise act on the PRs. ## Establish the current set Start from a clean, synchronized `main` and preserve unrelated worktree changes. Confirm `origin` instead of assuming the repository owner, then use the available GitHub integration or authenticated `gh` to list open PRs authored by Dependabot. Read each selected PR's body, changed files, commits, merge state, and complete check rollup. Classify each PR by the surface it changes and the compatibility question it raises. For Cargo updates, inspect direct feature selection, release notes for breaking changes, affected code paths, `Cargo.toml`, and `Cargo.lock`. For a Rust toolchain update, inspect `rust-toolchain.toml`, workspace `rust-version`, and the corresponding contributor documentation. Do not treat a green historical check as proof against the current `main`. Choose an order that makes failures attributable. Updates sharing a manifest or lockfile are merged one at a time, normally from the smallest and least risky change to the largest compatibility surface. State any update that needs a product or compatibility decision before mutating GitHub. ## Refresh and merge one PR at a time Before each merge: 1. Update or rebase the PR branch onto t