chore(setup): bump gateway LKG to 2026.7.1-2

[github-actions]

Gateway LKG update

• Previous pinned LKG: 2026.6.11
• Candidate latest: 2026.7.1-2
• 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 20, 2026, 4:26 AM ET / 08:26 UTC.

Summary
The PR changes GatewayLkgVersion.LkgVersion from 2026.6.11 to 2026.7.1-2, which changes the gateway package setup selects when no explicit version is configured.

Reproducibility: not applicable. This PR promotes a default package version rather than reporting a standalone defect. The relevant proof is an exact-version supported-path acceptance matrix, not a generic bug reproduction.

Review metrics: 1 noteworthy metric.

• Version-selection surface: 1 file changed; 1 line added, 1 removed. That single default controls the package setup chooses whenever users do not provide an explicit gateway version.

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:

• [P2] Attach or link redacted current-head acceptance evidence for exactly 2026.7.1-2, including setup, health, pairing, repair, and rollback.
• Record whether the upstream startup report is fixed, inapplicable to the supported Windows/WSL path, or an accepted release risk.

Risk before merge

• [P1] Merging would make 2026.7.1-2 the default gateway package for fresh and repair setup paths, so an unresolved startup regression or untested upgrade path could leave supported setup unavailable at runtime.
• [P1] The supplied review context does not establish whether the candidate revision resolves or is unaffected by the upstream startup concern; release-owner acceptance is still required.

Maintainer options:

1. Verify the promoted package first (recommended)
   Keep the draft until the release owner has exact-version supported-path proof and an explicit disposition of the upstream startup concern.
2. Accept the LKG promotion risk
   Merge the centralized pin now only if the release owner explicitly accepts the absence of the requested acceptance evidence.

Next step before merge

• [P2] The remaining blocker is a release-owner package-readiness decision backed by real supported-path evidence, not a narrow mechanical repair an automated worker can safely perform.

Maintainer decision needed

• Question: Should 2026.7.1-2 be accepted as the setup LKG after reviewing exact-version supported-path evidence and the upstream startup-report disposition?
• Rationale: An LKG promotion is a release-readiness judgment: the one-line code change is mechanically sound, but only a release owner can decide whether the observed candidate behavior is sufficient to become the default installed version.
• Likely owner: shanselman — The existing release-readiness review establishes the decision criteria and is the strongest available routing signal.
• Options:
  • Require exact-version acceptance proof (recommended): Keep the PR draft until a release owner reviews redacted fresh-install, health, pairing, repair, and rollback evidence for 2026.7.1-2 and records the upstream-report disposition.
  • Accept the operational risk: Approve the pin without the requested acceptance matrix, explicitly accepting that setup may select a package not yet proven on the supported Windows/WSL path.

Security
Cleared: The one-line exact-version pin does not add code execution, dependencies, permissions, secrets handling, or package-source changes.

Review details

Best possible solution:

Retain the single centralized pin, but merge it only after a release owner verifies and records redacted current-head acceptance for exactly 2026.7.1-2 across fresh setup, gateway health, tray pairing, repair/rerun, and rollback.

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

Not applicable: this PR promotes a default package version rather than reporting a standalone defect. The relevant proof is an exact-version supported-path acceptance matrix, not a generic bug reproduction.

Is this the best way to solve the issue?

Yes, conditionally: one centralized exact pin is the narrowest maintainable version-selection mechanism. It is not yet the best merge path until the release owner confirms the candidate’s real setup behavior and upstream-report disposition.

AGENTS.md: found and applied where relevant.

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

Label changes

Label changes:

• add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
• remove rating: 🦐 gold shrimp: Current PR rating is rating: 🐚 platinum hermit, so this older rating label is no longer current.

Label justifications:

• P2: This is a bounded release-readiness update with a credible but not yet demonstrated setup-availability impact.
• merge-risk: 🚨 availability: The changed default can cause fresh or repaired setup to install a gateway package that fails to start on the supported path.
• 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: This standing automation PR is bot-authored, so contributor proof is not the applicable gate; nevertheless, the release-owner review correctly requires current-head supported-path setup evidence before merging. Any posted evidence should redact private endpoints, IP addresses, and credentials.

Evidence reviewed

What I checked:

• Centralized LKG pin: The PR changes only the setup engine’s central default version constant, from 2026.6.11 to 2026.7.1-2. (src/OpenClaw.SetupEngine/GatewayLkgVersion.cs:6, 755b49fdfecc)
• Existing release-readiness hold: The July 17 review asks to retain the draft until a release owner disposes of the upstream startup concern and supplies current-head Windows/WSL acceptance evidence covering fresh setup, gateway health, pairing, repair, and rollback. (59ac51a40614)
• Current-head continuity: The PR head was force-pushed to 755b49fdfeccbb402b63d6073898eb1fab711529 on July 20, 2026; the supplied body still contains only the version-bump description and no included acceptance artifact for that head. (src/OpenClaw.SetupEngine/GatewayLkgVersion.cs:6, 755b49fdfecc)

Likely related people:

• shanselman: The recorded review defines the remaining acceptance boundary and calls for release-owner disposition before this LKG promotion lands. (role: release-readiness reviewer; confidence: medium; commits: 59ac51a40614; 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 (9 earlier review cycles; latest 8 shown)

• reviewed 2026-07-14T13:02:37.381Z sha 4fb72d6 :: found issues before merge. :: [P1] Pin only an exact published gateway package
• reviewed 2026-07-14T13:28:35.352Z sha 4fb72d6 :: found issues before merge. :: [P1] Pin only an exact published gateway package
• reviewed 2026-07-14T13:51:48.088Z sha 4fb72d6 :: needs maintainer review before merge. :: none
• reviewed 2026-07-16T02:47:13.961Z sha 3308e38 :: needs maintainer review before merge. :: none
• reviewed 2026-07-16T08:15:11.028Z sha 59ac51a :: needs maintainer review before merge. :: none
• reviewed 2026-07-17T08:13:27.385Z sha 0a7c3d7 :: needs maintainer review before merge. :: none
• reviewed 2026-07-18T08:07:35.296Z sha ba9053e :: needs maintainer review before merge. :: none
• reviewed 2026-07-19T08:12:24.382Z sha a30863e :: needs maintainer review before merge. :: none

[shanselman]

GitHub Copilot maintainer-assistant review — this is automated feedback, not a comment written personally by Scott.

Reviewed head: 59ac51a4061488aa4f7dcc1466bec3b76301f017

The one-line implementation is correct, but an LKG promotion means “last known good,” not merely “latest published.” The candidate 2026.7.1 currently has an unresolved upstream report of complete gateway startup failure after upgrade, and this draft has no current-head Windows/WSL easy-setup acceptance evidence. The prior signed Windows installer promotion did not exercise this exact gateway pin.

Please keep this draft until a release owner supplies both:

1. a disposition for the upstream startup report (fixed, proven inapplicable to Ubuntu/WSL, or accepted with a documented rationale); and
2. current-head Windows acceptance against exactly 2026.7.1.

Suggested acceptance matrix:

• fresh easy setup into a clean app-owned WSL distro;
• gateway starts and passes health checks;
• tray connects and pairing/device-token flow completes;
• repair/re-run against an existing managed distro;
• uninstall/rollback leaves no broken state;
• required repository build, shared tests, and tray tests report real non-zero counts.

Please include the exact installed gateway version and redacted setup/gateway-health output in the PR. Once that evidence is present, the centralized one-line pin is the right implementation and should be straightforward to land.

[clawsweeper]

ClawSweeper status: review started.

I am starting a fresh review of this pull request: chore(setup): bump gateway LKG to 2026.7.1-2 This is item 1/1 in the current shard. Shard 0/1.

This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking.

Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted.