[vincentkoc]

What Problem This Solves

A failed published OpenClaw installation stops the native macOS lifecycle check without showing the install error in Actions logs.

User Impact

Maintainers can diagnose the failed installation before retrying a release. This changes CI diagnostics only.

Why This Change Was Made

Apply the existing bounded error summary to the published-install step. It replaces the temporary-state and home paths and retains the complete log privately with mode 0600. Service diagnostics and the lifecycle gate are unchanged.

Evidence

• Reproduced in the native macOS job of release preparation CI: the published-install command returned 1, and the underlying error was retained only on the ephemeral runner.
• The diff changes one condition. Existing native-Gateway Python checks and the real macOS lifecycle job provide remote validation.
• This exposes the installation error; it does not claim to fix its cause.

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

What this changes

This PR prints a bounded, path-redacted error summary when the native macOS check fails to install published OpenClaw.

Example: The macOS lifecycle check's published OpenClaw installation exits with code 1.

• Before: Actions shows the exit code and a generic failure while the underlying error remains in a private runner log.
• After: Actions also shows the final 2,000 characters of the installation error, replacing the test-state and home paths.

Review scores

Measure	Result	What it means
Overall readiness	🦐 gold shrimp (3/6)	The patch is minimal and source-correct, with limited direct evidence for the newly exposed diagnostic path.
Proof confidence	🦐 gold shrimp (3/6)	This maintainer-authored PR is outside the ordinary contributor proof gate; the supplied historical failure establishes context, but inspected evidence does not demonstrate the changed failure-output branch.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Product

Kind: Bug fix · Worth it: Yes · Fix scope: Complete
User problem: Maintainers cannot see the installation error when the native macOS lifecycle check fails before service validation.
Reason: The existing area owner authored this narrowly scoped repair, which makes a failed CI step diagnosable at negligible maintenance cost.

Merge readiness

✅ Ready for maintainer review

Keep open: this maintainer-authored PR makes a useful, narrowly scoped diagnostic improvement absent from current main; no introduced correctness defect was found.

Priority: P3
Reviewed head: e267a0c04994c5fd6a653a4446e64df45981dd90

Before merge

None.

Findings

None.

Tests

• Missing end-to-end proof: No inspected after-change output demonstrates a failed published installation printing the bounded, path-redacted summary.

Agent review details

How this fits together

The macOS CI lifecycle script invokes the candidate OCM CLI to install published OpenClaw and validate launchd behavior; failed commands produce private logs and selected public diagnostic summaries.

flowchart LR
  A[macOS CI job] --> B[Lifecycle validation script]
  B --> C[OCM published installation]
  C --> D[Captured command output]
  D --> E[Private complete log]
  D --> F[Bounded redacted Actions summary]

Loading

Technical review

Best possible solution:

Retain this minimal extension of the existing diagnostic owner without changing installation behavior or weakening the lifecycle gate.

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

Current-main source shows that the published-install call uses start rather than service, so its nonzero exit bypasses the public error summary.

Is this the best way to solve the issue?

The one-condition extension is the smallest complete fix for the stated diagnostic gap and preserves the existing summary and failure-handling implementation.

AGENTS.md: found and applied where relevant.

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

Provenance checked

• Public native macOS failure summaries keeps the original intent (c146e17: chore(tests): exercise provider roundtrips through native Gateways #929 introduced bounded, path-sanitized service summaries to expose readiness failures while retaining complete private logs.)

Testing

Proof path: none.

Security

None.

Evidence

What I checked:

• Exact introduced change: The sole changed condition extends the existing service-error summary to the published-install label; truncation, path replacement, private-log permissions, and failure propagation remain unchanged. (scripts/validate-native-gateway-macos.py:115, e267a0c04994)
• Existing owner and diagnostic intent: chore(tests): prove published Gateway lifecycle on macOS #920 established the native macOS lifecycle check, and chore(tests): exercise provider roundtrips through native Gateways #929 added bounded, path-sanitized service summaries to expose readiness failures without publishing complete private logs; both were authored by vincentkoc. (scripts/validate-native-gateway-macos.py:115, c146e179d8a2)
• Reported failure and inspection limit: The linked pre-change job confirms failure of the native macOS lifecycle step: https://github.com/openclaw/ocm/actions/runs/42144276535/job/127651869970. Its detailed log download redirected to a blocked Azure host, so the reported install-error trace could not be independently inspected. (e9a829bc04d0)
• Review policy and validation scope: The complete root AGENTS.md was applied; no scripts subtree AGENTS.md, maintainer-notes directory, or pr-simplify skill was present. At inspection, 12 head checks passed and the Linux/macOS test jobs were still running; existing native-Gateway Python tests cover shutdown observation rather than this diagnostic branch. (AGENTS.md:1, e267a0c04994)

Preflight source

Source unknown. Source comparison at the observed PR snapshot only. Completion is self-reported; body, policy, tests, execution, and report bytes are not verified.

Labels

Label changes:

• add P3: This improves maintainer-facing CI diagnostics without changing installed application behavior.
• 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 improves maintainer-facing CI diagnostics without changing installed application behavior.
• 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.

Rank-up moves

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

• Capture a failed published-install run showing the bounded summary and path replacement, with sensitive output redacted.

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 November 5, 2026, 8:54 PM ET / November 6, 2026, 01:54 UTC.