[steipete]

Prepare 0.78.1 with Highlights for reliable serve availability on loaded Macs and established direct AWS checkpoint captures before non-waiting success. The Fixed section also includes the independently landed AWS RDS CA re-pin and Azure Sandbox expiry/transport diagnostics. No upgrade action is required.

Included changes: #2845, #2834, #2853, and #2849. Preserve every upstream entry and @galiniliev credit. Earlier released changelog sections remain byte-identical, and all three coordinator package version fields are 0.78.1. This prep changes no CA pins.

Validation: isolated Codex autoreview scoped-clean at P1; attribution and released-history byte comparison passed; package-version assertions and docs-site build passed; git diff checks passed. Exact-head CI is the broad release gate.

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

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-15T13:38:34.742541Z	833518d	New commits

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[clawsweeper]

Codex review: needs maintainer review before merge.

What this changes

This PR finalizes the 0.78.1 changelog and updates all three coordinator package-version fields.

Example: Read the release notes and coordinator package metadata for 0.78.1.

• Before: The availability fix is under Unreleased and package metadata says 0.78.0.
• After: The fix appears in a dated 0.78.1 section and package metadata says 0.78.1.

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	Focused and internally consistent release metadata preparation with no identified patch defect; existing CI remains the landing gate.
Proof confidence	🌊 off-meta tidepool	Not applicable: This established release-owner preparation changes only release notes and package version metadata, with no new runtime behavior to demonstrate.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Product

Kind: Maintenance · Worth it: Yes · Fix scope: Complete
User problem: Users need a versioned patch release containing the merged availability sampling repair.
Reason: The established release owner is preparing a narrowly scoped patch release using the repository's existing process.

Merge readiness

✅ Ready for maintainer review

Keep open: this PR prepares an unreleased patch version, and its release metadata changes are absent from current main. No introduced code defect was identified; the failed Worker image-build check remains unattributed.

Priority: P3
Reviewed head: c5ea1a349b62a6400880b253a57ec67ed9491ecb

Before merge

None.

Findings

None.

Agent review details

How this fits together

Release preparation supplies version metadata and changelog content to the existing packaging and release-note extraction tools.

flowchart LR
  A[Merged fixes] --> B[Unreleased changelog]
  B --> C[Versioned release notes]
  D[Coordinator package metadata] --> E[Release tooling]
  C --> E
  E --> F[Release artifacts]

Loading

Technical review

Best possible solution:

Land the focused release preparation after the existing release checks pass, then follow the documented release sequence.

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

This release preparation reports no new runtime bug; the pinned diff and current main directly establish the outstanding metadata work.

Is this the best way to solve the issue?

The change follows the existing release preparation contract, updates every documented version field, and preserves published history.

AGENTS.md: found and applied where relevant.

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

Provenance checked

• Changelog release section keeps the original intent (b4f5603: The merged availability repair added its user-visible change under Unreleased.)
• Coordinator package versions keeps the original intent (2bd8569: The previous release preparation synchronized the same three version fields to 0.78.0.)

Testing

Proof path: none.

Security

None.

Evidence

What I checked:

• Pinned release preparation diff: The introduced diff changes only the changelog and three version values; dependency resolutions, runtime code, and earlier released changelog sections are unchanged. (CHANGELOG.md:5, c5ea1a349b62)
• Applicable repository policy: The complete root AGENTS.md requires release preparation to finalize the changelog and update worker/package.json plus both root lockfile versions; no nested AGENTS.md or maintainer-notes directory was found. (AGENTS.md, c5ea1a349b62)
• Current main still needs preparation: The default branch remains at the pinned base, where the availability fix is Unreleased and coordinator metadata remains 0.78.0. (worker/package.json:3, b4f560381bf0)
• Underlying fix and recorded verification: fix(serve): retain availability signals on loaded hosts #2845 is merged and records a real loaded-Mac probe returning busy with hostCPU 1; this PR packages that existing fix rather than introducing it. (CHANGELOG.md:13, b4f560381bf0)
• Worker check requires separate diagnosis: The exact-head Worker job passed install, formatting, lint, typechecks, tests, and application builds, then failed Build Node runtime image: https://github.com/openclaw/crabbox/actions/runs/38690844133/job/116276133748. Log retrieval redirected to a blocked storage host, so its cause could not be attributed to this diff or an outside failure. (c5ea1a349b62)
• Feature-history ownership: Repeated release preparations and release-tooling changes establish Peter Steinberger as the primary routing candidate; Vincent Koc also authored the merged 0.76.0 preparation. Following package history reached a missing creation-era object, leaving original introduction unverified. (worker/package.json:3, b4f560381bf0)

Labels

Label changes:

• add P3: This is focused release metadata maintenance with no runtime behavior change.
• add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool 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 focused release metadata maintenance with no runtime behavior change.
• 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.

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 execution lanes are retired.

Reviewed October 15, 2026, 2:23 AM ET / 06:23 UTC.