chore: prepare first MSIX release of OpenClaw 2026.9.9

[RomneyDa]

Problem and outcome

OpenClaw 2026.9.9 is live on npm latest. Reset the packaging rebuild revision from 1 to 0 for its first MSIX, as required by the release policy. Stable selection remains unchanged; no runtime, identity, signing, or baseline changes.

Derived candidate: v2026.9.9-msix.0, MSIX 2026.9.900.0, newer than published 2026.9.8-msix.1 (2026.9.801.0). Upstream v2026.9.9 resolves to bcfc88812a35243893585dbeca87ca41b48272ca.

Validation

Head: 3562275e1725664fb845a809dfc3ea285b62da08

• Passed locally: release-identity suite, 55 source-selection tests, workflow-package-version suite, git diff --check.
• Signing-input suite passed locally after setting the process-scoped $env:TEMP to the system temporary directory; its initial attempt could not start because that Windows environment variable is unset on macOS.
• Exact-head Windows CI passed: host quality/tests, NativeAOT CLI, all policy suites, x64/ARM64 payloads and MSIX composition, both bundles, and all 13 installed-package upgrade scenarios. Run 37764034499.
• Installed Store evidence: baseline 2026.9.800.0 upgraded to candidate 2026.9.900.0, reserved package family unchanged, localStateRetained: true, status Ok. Evidence is retained as openclaw-gateway-msix-upgrade-evidence-store-bundle in that run; all 13 upgrade evidence artifacts are retained.
• CodeQL passed. ClawSweeper completed for this exact head with no findings; its initially pending end-to-end proof is now satisfied by the completed CI run. Maintainer inspection confirms the diff changes only the existing rebuild revision owner.
• No package installation or live Gateway changes performed locally. Official signing/publication is intentionally unrun in PR CI. After merge, dispatch the official publication workflow from main, binding payload to verified upstream bcfc88812a35243893585dbeca87ca41b48272ca while identity follows stable. Publication is not performed by this PR.

Risk

One policy value changes. Release identity remains derived by the existing owner; the official workflow revalidates immutable source and all signing inputs before Azure login. Existing immutable upgrade baselines remain intact.

[clawsweeper]

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

ClawSweeper review complete

ClawSweeper finished reviewing this revision. The review result is being finalized.

View the workflow run.

[clawsweeper]

Codex review: needs maintainer review before merge. Reviewed October 8, 2026, 6:36 AM ET / 10:36 UTC.

ClawSweeper review

What this changes

Reset the packaging rebuild revision to 0 for the first MSIX release of OpenClaw 2026.9.9.

Example: Prepare an MSIX from OpenClaw v2026.9.9

• Before: The existing policy derives v2026.9.9-msix.1 with package version 2026.9.901.0.
• After: This PR derives v2026.9.9-msix.0 with package version 2026.9.900.0.

Review scores

Measure	Result	What it means
Overall readiness	🦐 gold shrimp (3/6)	The patch is focused and consistent with policy, but release-specific Windows evidence is still incomplete.
Proof confidence	🦐 gold shrimp (3/6)	Not applicable: This member-authored release-policy PR is outside the external-contributor proof gate; reported local suites support the identity change, while repository-required Windows composition and upgrade evidence remain pending. No stored-data format changes.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Product

Kind: Maintenance · Worth it: Yes
User problem: The first Windows package for a new upstream release should use the documented initial packaging revision.
Reason: This focused maintenance change follows an existing release-owner decision and adds no new product surface.

Merge readiness

✅ Ready for maintainer review

This PR follows the established release policy and has no identified patch defect. It remains necessary because main still uses revision 1; exact-head Windows composition and upgrade validation are pending.

Priority: P3
Reviewed head: 3562275e1725664fb845a809dfc3ea285b62da08

Before merge

None.

Findings

None.

Tests

• Missing end-to-end proof: Exact-head x64/ARM64 package composition and the installed-package upgrade matrix remain pending, including currently installed Store version ordering and LocalState retention. The reviewer ran no artifact-producing validation.

Agent review details

How this fits together

The Windows release workflow combines the selected upstream OpenClaw version with a packaging revision to derive MSIX versions and release tags. Existing validation checks the resulting packages before signing or publication.

flowchart LR
 A[Stable OpenClaw version] --> C[Release identity calculation]
 B[Reviewed packaging revision] --> C
 C --> D[MSIX packages and bundles]
 D --> E[Windows upgrade validation]
 D --> F[Signing input validation]
 F --> G[Authorized publication from main]

Loading

Technical review

Best possible solution:

Keep release identity in its existing owner and use the established Windows validation and main-only publication workflow for this release.

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

Not applicable: this is release preparation, and source confirms the requested identity calculation.

Is this the best way to solve the issue?

Yes: resetting the existing policy value is the narrowest change and follows the previously recorded release-owner direction.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning medium; reviewed against 40d5bcbc4aae.

Provenance checked

• release-policy.json: msixRevision keeps the original intent (chore: release OpenClaw 2026.9.8 with Windows recovery fixes #165: Revision 1 identified a packaging rebuild of OpenClaw 2026.9.8; future upstream releases were explicitly required to reset the revision to 0.)

Testing

Proof path: unit tests only. Added test files: 0.

Security

None.

Evidence

What I checked:

• Introduced change: The pinned introduction diff changes only msixRevision from 1 to 0; source selection, identities, publishers, and baselines remain unchanged. (release-policy.json:4, 3562275e1725)
• Existing release contract: The release guide explicitly requires revision 0 for a new upstream tag's first package and a reviewed reset after a previous rebuild. (docs/release-process.md:28, 3562275e1725)
• Version ordering: The existing calculation uses patch × 100 plus correction × 10 plus revision, making 2026.9.900.0 newer than the published 2026.9.801.0 without changing the versioning owner. (scripts/Get-MSIXReleaseIdentity.ps1:54, 3562275e1725)
• Prior owner decision: chore: release OpenClaw 2026.9.8 with Windows recovery fixes #165 introduced revision 1 for the 2026.9.8 rebuild and explicitly states that future upstream releases must reset it to 0. (release-policy.json:4, 40d5bcbc4aae)
• Current main and feature history: Main retains revision 1. File history identifies Dallin Romney as a recurring contributor to release policy and release identity; the preceding commit's raw record has a recorded parent. (release-policy.json:4, 40d5bcbc4aae)
• Stable source verification: A read-only request to https://registry.npmjs.org/openclaw/latest returned version 2026.9.9, corroborating the release trigger; the response did not supply gitHead.

Likely related people:

• Dallin Romney: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)

Labels

Label changes:

• add P3: This is a one-value release-preparation update that preserves the existing versioning and signing contracts.
• add rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🦐 gold shrimp and patch quality is 🐚 platinum hermit.
• add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR.

Label justifications:

• P3: This is a one-value release-preparation update that preserves the existing versioning and signing contracts.
• rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🦐 gold shrimp and patch quality is 🐚 platinum hermit.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR.

Rating scale

6/6 🦀 challenger crab · 5/6 🦞 diamond lobster · 4/6 🐚 platinum hermit · 3/6 🦐 gold shrimp · 2/6 🦪 silver shellfish · 1/6 🧂 unranked krab. Overall follows the weaker of proof and patch quality; ✨ marks media proof (a screenshot, video, or linked artifact) that directly shows the changed behavior.

Workflow

ClawSweeper edits this one comment on every review. Comment @clawsweeper re-review for a fresh review only; repair and merge need explicit maintainer commands such as @clawsweeper autofix or @clawsweeper automerge.