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

ClawSweeper review

What this changes

Updates the Setup Engine's default gateway package version from 2026.6.11 to 2026.7.1-2 for installs that do not specify an explicit gateway version.

Merge readiness

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

Keep this draft open. The centralized LKG pin is a narrow implementation, but the requested gateway version has not yet been supported by the release-owner disposition and current-head Windows/WSL acceptance evidence required before a default setup package can be promoted.

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

Review scores

Measure	Result	What it means
Overall readiness	🧂 unranked krab (1/6)	The patch is clean and appropriately narrow, but it lacks the real supported-path evidence required to establish a new last-known-good gateway default.
Proof confidence	🧂 unranked krab (1/6)	Needs real behavior proof before merge: The PR body and provided discussion contain no after-fix, current-head Windows/WSL evidence for the exact 2026.7.1-2 package. Before merge, add redacted live setup and gateway-health output, including the installed version and pairing result. 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 PR body and provided discussion contain no after-fix, current-head Windows/WSL evidence for the exact 2026.7.1-2 package. Before merge, add redacted live setup and gateway-health output, including the installed version and pairing result. 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	4 items	Proposed default-package change: The latest PR head changes only the centralized LkgVersion constant from 2026.6.11 to 2026.7.1-2, so this value becomes the implicit package selection for setup paths without an explicit version. Release-owner review requirement: The maintainer review says the earlier 2026.7.1 candidate had an unresolved upstream complete-startup-failure report and asks for a disposition plus current-head Windows/WSL easy-setup evidence against the exact promoted version. Current PR state: The PR remains a draft and its latest provided update contains no redacted setup, installed-version, 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 a default gateway package version when setting up or repairing the app-managed WSL gateway. That selected package must start successfully, pass gateway health checks, and support tray connection and pairing before users can complete setup.

flowchart LR
  A[Setup or repair request] --> B[Gateway version selection]
  B --> C[Default LKG package pin]
  C --> D[WSL gateway installation]
  D --> E[Gateway health check]
  E --> F[Tray connection and pairing]
  F --> G[Usable Windows node]

Loading

Decision needed

Question	Recommendation
Should 2026.7.1-2 become the default gateway package after the upstream startup report is dispositioned and the supported Windows/WSL acceptance matrix succeeds?	Validate then promote: Collect the exact-version Windows/WSL setup, health, pairing, repair, and rollback evidence, record the upstream-report disposition, then merge the centralized pin.

Why: A last-known-good promotion is a release-readiness decision: source review can confirm the pin location, but it cannot establish that the selected external gateway package is safe for the supported installation and recovery paths.

Before merge

• Resolve merge risk (P1) - Promoting this LKG changes the default package used by fresh setup and repair paths. If 2026.7.1-2 fails to start or pair in the supported WSL environment, users can be blocked during setup or left with a broken managed gateway.
• Resolve merge risk (P1) - The unresolved upstream startup report has not been dispositioned for the exact promoted package, so the existing LKG safety claim is not yet established.
• Complete next step (P2) - A release owner must decide whether the exact gateway package has sufficient supported-path acceptance evidence; this is not a narrow code repair that an automated worker can safely perform.

Agent review details

Security

None.

Review metrics

Metric	Value	Why it matters
Default package pin	1 file changed, 1 version constant replaced	A one-line default controls fresh setup and repair package selection, so runtime acceptance matters more than diff size.

Merge-risk options

Maintainer options:

1. Add supported-path acceptance evidence (recommended)
   Keep the PR as a draft until a release owner posts redacted current-head proof for the exact package and resolves the upstream startup report.
2. Retain the current LKG
   Pause this promotion and continue defaulting to 2026.6.11 until the candidate has a documented last-known-good result.

Technical review

Best possible solution:

Retain the one-line centralized pin only after a release owner records the upstream-report disposition and attaches current-head, redacted evidence that 2026.7.1-2 completes fresh setup, health checks, pairing, repair, and rollback on the supported Windows/WSL path.

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

Not applicable. This PR promotes a default package version rather than reporting a reproducible defect; the relevant question is whether the candidate succeeds on the supported real setup path.

Is this the best way to solve the issue?

Unclear. Keeping the default in the single GatewayLkgVersion constant is the right implementation shape, but the candidate package cannot be considered last known good until the requested release evidence exists.

AGENTS.md: found and applied where relevant.

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

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 PR body and provided discussion contain no after-fix, current-head Windows/WSL evidence for the exact 2026.7.1-2 package. Before merge, add redacted live setup and gateway-health output, including the installed version and pairing result. 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 rating: 🐚 platinum hermit: Current PR rating is rating: 🧂 unranked krab, so this older rating label is no longer current.
• remove status: 👀 ready for maintainer look: Current PR status label is status: 📣 needs proof.

Label justifications:

• P2: This is a bounded default-package promotion whose failure could disrupt setup and repair, but no current user-facing regression is established.
• merge-risk: 🚨 availability: Changing the LKG may cause the managed gateway to fail startup or health checks on supported setup paths.
• 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 PR body and provided discussion contain no after-fix, current-head Windows/WSL evidence for the exact 2026.7.1-2 package. Before merge, add redacted live setup and gateway-health output, including the installed version and pairing result. 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:

• Proposed default-package change: The latest PR head changes only the centralized LkgVersion constant from 2026.6.11 to 2026.7.1-2, so this value becomes the implicit package selection for setup paths without an explicit version. (src/OpenClaw.SetupEngine/GatewayLkgVersion.cs:6, dd643fcce965)
• Release-owner review requirement: The maintainer review says the earlier 2026.7.1 candidate had an unresolved upstream complete-startup-failure report and asks for a disposition plus current-head Windows/WSL easy-setup evidence against the exact promoted version.
• Current PR state: The PR remains a draft and its latest provided update contains no redacted setup, installed-version, gateway-health, pairing, repair, or rollback evidence for 2026.7.1-2. (dd643fcce965)
• Repository validation policy: The repository policy requires setup and gateway-related changes to carry the required build and test closeout, gateway-aware proof where applicable, and real behavior evidence in the PR before publication. (AGENTS.md:1, f50af187865c)

Likely related people:

• shanselman: Provided the concrete package-readiness review for this promotion, including the upstream startup-risk disposition and required Windows/WSL acceptance matrix. (role: release-readiness reviewer; confidence: high; files: src/OpenClaw.SetupEngine/GatewayLkgVersion.cs)
• vincentkoc: Was explicitly notified alongside the release-readiness reviewer for this automated gateway-LKG promotion, indicating relevant area involvement, though the provided context does not establish a specific ownership commit. (role: likely adjacent setup-area owner; confidence: low; files: src/OpenClaw.SetupEngine/GatewayLkgVersion.cs)

Rank-up moves

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

• Post redacted current-head proof for fresh setup, health checks, tray pairing, repair, and rollback using exactly 2026.7.1-2.
• Record the release-owner disposition for the upstream gateway startup-failure report before promoting this package.

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 (10 earlier review cycles; latest 8 shown)

• 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
• reviewed 2026-07-20T08:26:34.507Z sha 755b49f :: 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.