chore(deps): bump clap_complete from 4.6.9 to 4.6.11

[dependabot]

Bumps clap_complete from 4.6.9 to 4.6.11.

Commits

• 2cb76fd chore: Release
• 0b00b8d docs: Update changelog
• 3443000 Merge pull request #6526 from bonnefoa/fix-completion-escape
• a1b6be7 fix(clap_complete): Fix value escape in zsh completion
• face9e8 test(complete): Add completion test without arg's help
• 88053ab test(complete): Re-enable complete tests
• e6adcc2 chore(release): Simplify replacements
• 13f2db5 chore: Release
• 3304fea docs: Update changelog
• 7b2ad34 Merge pull request #6521 from r-near/feat/derive-deferred-initialization
• Additional commits viewable in compare view

[github-actions]

Thanks @dependabot[bot] for taking the time to contribute.

This repository is observing a maintainer-managed PR intake gate in dry-run mode, so this pull request is staying open. This note helps maintainers prepare the allowlist before any enforcement is considered.

Please read CONTRIBUTING.md for the expected contribution shape. A maintainer can grant recurring PR access by commenting /lgtm on a pull request.

[Hmbown]

Brought this branch up to date with main (green since ccbef2c) so CI runs against a base that passes; the earlier red lanes were inherited from the red main this PR was opened on. Merging once the re-run is green.

---

Generated by Claude Code

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[claude]

Claude finished @Hmbown's task in 49s —— View job

---

Claude's review of #6342 (chore(deps): bump clap_complete 4.6.9 → 4.6.11)

• Gather context (diff, AGENTS.md/CLAUDE.md rules)
• Review the Cargo.lock diff for this dependency bump
• Post findings

Scope: Cargo.lock only (+19/−19), no Cargo.toml changes. Root manifest pins clap_complete = "4.5" (Cargo.toml:57), so 4.6.11 is satisfied by the existing caret constraint — no manifest edits needed.

What changed:

• clap_complete 4.6.9 → 4.6.11 (upstream fix: zsh completion value escaping, clap-rs/clap#6526).
• The remaining 18 changed lines are windows-sys dependency-edge re-pins (various crates shifting between 0.52.0 / 0.59.0 / 0.60.2 / 0.61.2). All of these version numbers already existed as separate [[package]] blocks on main before this PR — this is Cargo's resolver re-picking among already-present, semver-compatible versions during the lockfile regen, not new dependencies or version bumps. No functional risk.

Review against the custom checklist:

1. Correctness bugs — none; this is a lockfile-only diff, nothing to compile against.
2. Provider/model/route safety (EPIC v0.8.65 EPIC: Separate provider facts, model facts, offerings, and route resolution #2608) — not applicable, no source changes.
3. Reuse/simplification — n/a.
4. Tests — n/a for a lockfile bump; nothing new to cover.
5. Security — patch release, no advisory tied to this bump; upstream change is a completion-escaping fix, not security-sensitive to this repo's code.

No issues found. This is a safe, routine dependency bump.

[codewhale-agent]

Codewhale review did not run

codewhale review --pr 6342 (provider: deepseek) could not reach the model: Review pass 1/1 request failed: Responses API request failed: LLM error: HTTP 402: Insufficient Balance; no partial review was accepted or posted; publication: n.
This is a provider funding/config problem, not a finding about this PR. The check stays advisory; a maintainer with secret access needs to fund or rotate the review key (see .github/workflows/codewhale-review.yml). Re-run the workflow after that.

[Hmbown]

Test (ubuntu-latest) is red for a reason outside this bump. One test failed out of 16169 (job):

runtime_api::tests::terminal_routes_serve_a_live_engine_session_over_http
  assertion `left == right` failed
    left:  "printf 'terminal-route-proof\\n'\r\n$ terminal-route-proof\r\n$ "
    right: "printf 'terminal-route-proof\\n'\r\n$ terminal-route-proof\r\n"

The captured PTY byte stream carried the shell's next prompt ($ ) after the command output, so the exact-equality assertion tripped on timing, not on content. This PR only bumps clap_complete (shell-completion generation), which is not on the terminal-route path; the same test passed on main and on every other dependabot branch updated today. Re-running the failed job once; the exact-stream assertion is the thing to make robust, separately.

---

Generated by Claude Code

[Hmbown]

Superseded by #6391, now merged, which lands this same bump (clap_complete 4.6.9 to 4.6.11).

This branch was CONFLICTING against main, so the change was applied directly as the minimal two-line lockfile edit (version + checksum).

Worth recording for next time: running cargo update -p clap_complete --precise 4.6.11 against this lockfile also re-resolves windows-sys away from the unified 0.61.2 back to a scattered 0.42.0 / 0.52.0 / 0.59.0 / 0.60.2 across seventeen crates. That regression was discarded and only the clap_complete lines applied.

Thanks, dependabot.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.