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 28, 2026, 4:14 AM ET / 08:14 UTC.

ClawSweeper review

What this changes

Updates the Setup Engine's default gateway package version from 2026.6.11 to 2026.7.1-2, affecting fresh setup and repair flows that install the standard gateway.

Merge readiness

⛔ Blocked until real behavior proof is added - 3 items remain

Keep this PR open for release-owner review. The centralized pin change is narrow, but the provided discussion still requires a disposition for the upstream startup report and current-head Windows/WSL acceptance evidence before a package can be promoted as last known good. Likely related people: shanselman is the strongest routing candidate from the documented acceptance review.

Priority: P2
Reviewed head: f57118955f038324e399d5b6e10f88179e7f533c
Owner decision: Required. See Decision needed.

Review scores

Measure	Result	What it means
Overall readiness	🧂 unranked krab (1/6)	The implementation is focused, but it is not merge-ready because the required real behavior evidence for an LKG promotion is absent.
Proof confidence	🧂 unranked krab (1/6)	Needs real behavior proof before merge: The provided PR body and review context contain no current-head real Windows/WSL acceptance proof for 2026.7.1-2; add redacted live setup and gateway-health output, including pairing and repair behavior, before merge. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Needs proof	Needs real behavior proof before merge: The provided PR body and review context contain no current-head real Windows/WSL acceptance proof for 2026.7.1-2; add redacted live setup and gateway-health output, including pairing and repair behavior, before merge. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.
Evidence reviewed	3 items	Centralized version pin: The proposed branch changes only the Setup Engine's centralized LKG constant from 2026.6.11 to 2026.7.1-2; setup and repair therefore share the same promotion point. Maintainer acceptance gate: A collaborator review on July 17, 2026 states that LKG means last known good, identifies an unresolved upstream startup report, and asks for current-head Windows/WSL easy-setup acceptance before promotion. Current PR evidence is insufficient: The PR body identifies the candidate version and changed file, but provides no redacted current-head setup, gateway-health, pairing, repair, or rollback evidence for 2026.7.1-2.
Findings	None	None.
Security	None	None.

How this fits together

The Setup Engine selects the pinned gateway version when it provisions or repairs the app-managed WSL gateway. That gateway must start, pass health checks, and pair with the Windows tray before users can use the connected node.

flowchart LR
  A[Fresh setup or repair] --> B[Setup Engine]
  B --> C[Gateway LKG version]
  C --> D[Gateway install source]
  D --> E[WSL gateway starts]
  E --> F[Health and pairing checks]
  F --> G[Windows tray connection]

Loading

Decision needed

Question	Recommendation
Should 2026.7.1-2 replace the current gateway LKG before its upstream startup concern is resolved or explicitly accepted and the Windows/WSL acceptance matrix is evidenced?	Hold the existing LKG pending acceptance: Keep the current default until the startup report receives a documented disposition and current-head Windows/WSL evidence demonstrates setup, health, pairing, repair, and rollback.

Why: This is a release-promotion decision: the one-line code change cannot establish that the candidate is last known good for supported setup and repair environments.

Before merge

• Resolve merge risk (P1) - Promoting an unaccepted gateway as the default LKG could make fresh setup or repair install a version that fails to start, health-check, or complete tray pairing on the supported Windows/WSL path.
• Complete next step (P2) - A release owner must decide whether the candidate satisfies the LKG bar after reviewing the upstream report and current-head acceptance evidence; this is not a mechanical code repair.

Agent review details

Security

None.

Review metrics

Metric	Value	Why it matters
Promotion surface	1 file changed, 1 added, 1 removed	One centralized constant affects both setup and repair installs, so a small diff has broad runtime consequences.

Merge-risk options

Maintainer options:

1. Complete the LKG acceptance gate (recommended)
   Before merge, attach redacted current-head Windows/WSL proof for exactly 2026.7.1-2 and document the disposition of the upstream startup report.
2. Pause this promotion
   Keep the current LKG if the release owner cannot yet establish that the candidate is reliable across setup and repair paths.

Technical review

Best possible solution:

Keep the existing LKG until a release owner records a disposition for the upstream startup concern and attaches redacted current-head acceptance evidence for 2026.7.1-2 across fresh setup, repair, pairing, and rollback.

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

Not applicable as a bug reproduction. The review concerns whether a release candidate is sufficiently proven as the default LKG, and the supplied PR evidence does not demonstrate the required supported Windows/WSL behavior.

Is this the best way to solve the issue?

Unclear. A centralized one-line pin is the narrowest implementation, but promoting this specific version is not the best path until release acceptance evidence and the upstream startup-report disposition are available.

AGENTS.md: found and applied where relevant.

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

Labels

Label changes:

• add rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🧂 unranked krab and patch quality is 🐚 platinum hermit.
• add status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask. Needs real behavior proof before merge: The provided PR body and review context contain no current-head real Windows/WSL acceptance proof for 2026.7.1-2; add redacted live setup and gateway-health output, including pairing and repair behavior, before merge. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.
• remove status: 👀 ready for maintainer look: Current PR status label is status: 📣 needs proof.
• remove rating: 🦐 gold shrimp: Current PR rating is rating: 🧂 unranked krab, so this older rating label is no longer current.

Label justifications:

• P2: This is a bounded default-version promotion with meaningful setup reliability impact, but no confirmed current-user outage.
• merge-risk: 🚨 availability: The new default gateway version may prevent the gateway from starting or becoming healthy during setup or repair.
• rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🧂 unranked krab and patch quality is 🐚 platinum hermit.
• status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask. Needs real behavior proof before merge: The provided PR body and review context contain no current-head real Windows/WSL acceptance proof for 2026.7.1-2; add redacted live setup and gateway-health output, including pairing and repair behavior, before merge. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.

Evidence

What I checked:

• Centralized version pin: The proposed branch changes only the Setup Engine's centralized LKG constant from 2026.6.11 to 2026.7.1-2; setup and repair therefore share the same promotion point. (src/OpenClaw.SetupEngine/GatewayLkgVersion.cs:6, f57118955f03)
• Maintainer acceptance gate: A collaborator review on July 17, 2026 states that LKG means last known good, identifies an unresolved upstream startup report, and asks for current-head Windows/WSL easy-setup acceptance before promotion. (59ac51a40614)
• Current PR evidence is insufficient: The PR body identifies the candidate version and changed file, but provides no redacted current-head setup, gateway-health, pairing, repair, or rollback evidence for 2026.7.1-2. (src/OpenClaw.SetupEngine/GatewayLkgVersion.cs:6, f57118955f03)

Likely related people:

• shanselman: Authored the documented LKG acceptance review defining the required upstream disposition and Windows/WSL proof before release promotion. (role: recent reviewer; confidence: high; files: src/OpenClaw.SetupEngine/GatewayLkgVersion.cs)

Rank-up moves

Optional improvements that raise the rating; they are not merge blockers.

• Document the upstream startup-report disposition from the release owner.
• Attach redacted current-head evidence for fresh setup, health checks, tray pairing, repair/re-run, and rollback using exactly 2026.7.1-2.

Rating scale

Score	Internal tier	Crab rank	Meaning
6/6	S	🦀 challenger crab	Exceptional readiness
5/6	A	🦞 diamond lobster	Very strong readiness
4/6	B	🐚 platinum hermit	Good normal PR; ordinary maintainer review
3/6	C	🦐 gold shrimp	Useful, but confidence is limited
2/6	D	🦪 silver shellfish	Proof or implementation needs work
1/6	F	🧂 unranked krab	Not merge-ready
N/A	NA	🌊 off-meta tidepool	Rating does not apply

Overall follows the weaker of proof and patch quality.
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.

Workflow

• 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.

History

Review history (13 earlier review cycles; latest 8 shown)

• 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
• reviewed 2026-07-20T08:26:34.507Z sha 755b49f :: needs maintainer review before merge. :: none
• reviewed 2026-07-25T08:11:20.975Z sha dd643fc :: needs maintainer review before merge. :: none
• reviewed 2026-07-26T08:13:03.271Z sha 1d1b709 :: needs maintainer review before merge. :: none
• reviewed 2026-07-27T08:41:09.549Z sha 73d016d :: 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.