chore(setup): bump gateway LKG to 2026.6.11

[github-actions]

Gateway LKG update

• Previous pinned LKG: 2026.6.10
• Candidate latest: 2026.6.11
• Updated file: src/OpenClaw.SetupEngine/GatewayLkgVersion.cs

This is the standing automation PR used to review and validate gateway LKG bumps before merge.

[clawsweeper]

Codex review: needs maintainer review before merge. Reviewed July 4, 2026, 4:18 AM ET / 08:18 UTC.

Summary
The PR updates GatewayLkgVersion.LkgVersion in the setup engine from 2026.6.10 to 2026.6.11.

Reproducibility: not applicable. this is a maintenance version bump, not a bug report. Source inspection and the PR diff show exactly how the constant affects setup defaults.

Review metrics: 2 noteworthy metrics.

• Diff scope: 1 file, +1/-1. The patch is constrained to the embedded setup LKG constant.
• Default gateway version: 2026.6.10 -> 2026.6.11. This is the runtime-facing setup default maintainers need to validate before merge.

Merge readiness
Overall: 🐚 platinum hermit
Proof: 🌊 off-meta tidepool
Patch quality: 🐚 platinum hermit
Result: ready for maintainer review.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Rank-up moves:

• Run or link AGENTS.md build/shared/tray validation and a Windows/WSL setup smoke for 2026.6.11 before undrafting.

Risk before merge

• [P1] Merging changes the gateway package installed by fresh setup from 2026.6.10 to 2026.6.11, so an upstream installer, WSL setup, pairing, or protocol regression in that candidate would affect new setup until the pin is rolled back.
• [P1] The PR is still draft and the PR body does not show current-head AGENTS.md validation or a Windows/WSL setup smoke for the 2026.6.11 candidate.

Maintainer options:

1. Validate And Promote 2026.6.11 (recommended)
   Run or link the required repository validation plus a Windows/WSL setup smoke for this PR head before undrafting and merging.
2. Accept The Routine Bump
   Maintainers may intentionally merge after deciding the one-line diff, npm latest match, and standing LKG process are sufficient for this candidate.
3. Wait For A Later Candidate
   If 2026.6.11 loses known-good confidence, leave the draft paused until the updater replaces it with a later gateway version.

Next step before merge

• No automated repair is needed; maintainers should validate the 2026.6.11 candidate and decide whether to promote the draft LKG bump.

Security
Cleared: No concrete security or supply-chain regression was found; the diff only advances the official pinned gateway version constant while leaving installer URL, workflow permissions, and dependency sources unchanged.

Review details

Best possible solution:

Keep the LKG constant as the setup source of truth and land this draft only after maintainers accept 2026.6.11 as known-good with current-head setup validation.

Do we have a high-confidence way to reproduce the issue?

Not applicable: this is a maintenance version bump, not a bug report. Source inspection and the PR diff show exactly how the constant affects setup defaults.

Is this the best way to solve the issue?

Yes: updating the single documented LKG constant is the narrowest maintainable path for this standing gateway LKG bump. The merge path should remain validation-gated rather than changing more setup code.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 74604aebafef.

Label changes

Label justifications:

• P3: This is a routine setup LKG maintenance bump with limited blast radius, not an urgent regression.
• merge-risk: 🚨 compatibility: The PR changes the default gateway package installed by setup, so fresh setup compatibility depends on the upstream 2026.6.11 candidate being known-good.
• rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The external-contributor proof gate is not applicable because this is a repository automation PR; setup validation remains a maintainer merge-readiness requirement.

Evidence reviewed

Acceptance criteria:

• [P1] ./build.ps1.
• [P1] dotnet test ./tests/OpenClaw.Shared.Tests/OpenClaw.Shared.Tests.csproj --no-restore.
• [P1] dotnet test ./tests/OpenClaw.Tray.Tests/OpenClaw.Tray.Tests.csproj --no-restore.
• [P1] Windows/WSL setup smoke proving setup installs openclaw 2026.6.11 and pairing still works.

What I checked:

• Repository policy read: AGENTS.md was read fully and its setup/gateway proof guidance applies because this PR changes the gateway setup default; the proof-validation skill was also read as directed by AGENTS.md. (AGENTS.md:1, 74604aebafef)
• Current main pin: Current main still defines GatewayLkgVersion.LkgVersion as 2026.6.10, so the requested bump is not already implemented on the default branch. (src/OpenClaw.SetupEngine/GatewayLkgVersion.cs:6, 74604aebafef)
• PR diff scope: Live PR diff for head 8fd6e0075b4bd4b59a2ad232ca45102230287ea2 changes only the embedded LKG constant from 2026.6.10 to 2026.6.11. (src/OpenClaw.SetupEngine/GatewayLkgVersion.cs:6, 8fd6e0075b4b)
• Setup applies the LKG default: Program.cs applies GatewayLkgVersion.ApplyToConfig(config) after environment overrides, making the constant the default gateway version when no explicit version is configured. (src/OpenClaw.SetupEngine/Program.cs:51, 74604aebafef)
• Installer receives configured version: The install step builds the CLI install command from ctx.Config.Gateway.Version and appends --version, so changing the LKG changes the default package installed by setup. (src/OpenClaw.SetupEngine/SetupSteps.cs:1203, 74604aebafef)
• Standing updater workflow: The workflow resolves npm latest, rewrites only GatewayLkgVersion.cs, and creates or updates a standing draft PR for validation. (.github/workflows/gateway-lkg-update.yml:27, 74604aebafef)

Likely related people:

• ranjeshj: GitHub commit history for GatewayLkgVersion.cs shows this contributor introduced the setup LKG pin and updater workflow, then hardened the updater and tests. (role: introduced LKG pinning behavior; confidence: high; commits: 45df0763e1ca, dcc77f55e2c9, ca8c6772db81; files: src/OpenClaw.SetupEngine/GatewayLkgVersion.cs, .github/workflows/gateway-lkg-update.yml, tests/OpenClaw.SetupEngine.Tests/GatewayLkgVersionTests.cs)
• shanselman: Current-main blame maps the present LKG file and updater workflow snapshot to the v0.6.12 merge/release commit, and older LKG introduction commits list this person as committer. (role: recent area committer; confidence: medium; commits: 4166e0fd63f8, 45df0763e1ca, dcc77f55e2c9; files: src/OpenClaw.SetupEngine/GatewayLkgVersion.cs, .github/workflows/gateway-lkg-update.yml, .github/workflows/ci.yml)
• github-actions[bot]: The current PR and recent merged LKG bumps are authored by the repository automation that maintains this draft branch. (role: standing updater actor; confidence: medium; commits: 8fd6e0075b4b, d08a3e749973, a8c9699f6082; files: src/OpenClaw.SetupEngine/GatewayLkgVersion.cs)

What the crustacean ranks mean

• 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
• 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
• 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
• 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
• 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
• 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
• 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

Review history (1 earlier review cycle)

• reviewed 2026-07-03T08:35:35.928Z sha f962fea :: needs maintainer review before merge. :: none