[steipete]

Prepare proc-safe 0.4.2: bump the root, native workspace and crate, the ten platform packages, and the ten exact optional pins together; regenerate Cargo.lock and pnpm-lock.yaml; date the changelog section.

Release notes (pnpm release:notes 0.4.2):

• Darwin census handles concurrent exits: processes already exiting report parentage, process group, owner, and state instead of an incomplete row, and a process reaped while its row is read is omitted instead of returned without identity.

Contains #23 and #25. Rebased onto main after #25 merged, so 0.4.2 also carries the trailing-identity absence fix. The changelog section is dated 2026-10-19, the UTC tag date (same convention as 0.4.0 and 0.4.1), and the two census entries are grouped into one user-facing outcome. cargo update --workspace --offline and pnpm install --frozen-lockfile are no-ops on the rebased tree.

Approved for release by Peter; consumer bump: openclaw/openclaw#176612.

[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	🔄 Running since 2026-10-19T00:02:30.019359Z	2d732d8	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 advances all package and crate versions, native dependency pins, lockfiles, and the changelog to 0.4.2.

Example: A consumer installs @openclaw/proc-safe@0.4.2 on Darwin arm64 after publication.

• Before: The latest release is 0.4.1, which lacks the merged exiting-process topology fix.
• After: The release metadata selects the matching 0.4.2 native package containing that fix.

Review scores

Measure	Result	What it means
Overall readiness	🦐 gold shrimp (3/6)	The release metadata is consistent and source-verified; supporting validation is CI-based rather than a completed release installation.
Proof confidence	🦐 gold shrimp (3/6)	This maintainer-authored PR changes release metadata only; ordinary contributor behavior-proof gating does not apply, and publication verification remains in the unchanged release workflow.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Product

Kind: Maintenance · Worth it: Yes · Fix scope: Complete
User problem: Registry consumers cannot yet install the merged Darwin exiting-process topology fix.
Reason: The supplied maintainer-authored designation establishes direction, and the patch prepares a focused release of a demonstrated fix.

Merge readiness

✅ Ready for maintainer review

Keep this PR open: it correctly prepares an unreleased patch version, and no actionable defect was found.

Priority: P2
Reviewed head: ca63f61d7c797a1a6b03b6dac46163d4ae67e636

Before merge

None.

Findings

None.

Agent review details

How this fits together

Release metadata feeds the protected-tag workflow, which builds native bindings, verifies platform packages, publishes the root package, and checks installed consumers.

flowchart TD
  A[Version manifests and changelog] --> B[Protected tag on main]
  B --> C[Native builds and package checks]
  C --> D[Platform package publication]
  D --> E[Root package publication]
  E --> F[Installed consumer verification]

Loading

Technical review

Best possible solution:

Land the coordinated release preparation through the existing protected-tag release workflow once its native gates pass.

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

This is release preparation; source inspection confirms the version changes and the already-merged fix without executing target code.

Is this the best way to solve the issue?

The coordinated bump follows the existing release validator and previous release pattern without changing runtime behavior or publication safeguards.

AGENTS.md: found and applied where relevant.

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

Provenance checked

• Coordinated package, crate, dependency-pin, and lockfile versions keeps the original intent (90b7b6b: chore(release): prepare 0.4.1 #22 aligned the same release surfaces for 0.4.1; this PR preserves that synchronization for 0.4.2.)
• Dated changelog section keeps the original intent (2f01cbd: fix(inspect): report Darwin topology for exiting processes #23 added the user-facing fix under Unreleased; this PR assigns it to the prepared release while retaining Unreleased.)

Testing

Proof path: none.

Security

None.

Evidence

What I checked:

• Coordinated release diff: The complete introduced diff changes only release versions, ten exact optional dependency pins, corresponding lockfile entries, and the dated changelog heading. (package.json:106, ca63f61d7c79)
• Release remains necessary: Current main remains at 2f01cbd and the latest release is v0.4.1; the 0.4.2 preparation is not on main. (package.json:3, 2f01cbdc3bb8)
• Release-note implementation: fix(inspect): report Darwin topology for exiting processes #23 is merged; current source retains kernel topology for zombie or explicitly exiting records, matching the release note. (native/src/inspect/darwin_census.rs:78, 2f01cbdc3bb8)
• Established release contract: The unchanged validator requires matching root, native workspace, crate, platform versions and pins, plus a dated nonempty changelog; the previous release used the same coordinated change. (scripts/validate-release.mjs:12, 90b7b6b5b715)
• Validation status: The reviewed head has 23 successful checks and one FreeBSD arm64 Node 22 check still running; no failed check is reported, and diff whitespace validation passed. (ca63f61d7c79)

Labels

Label changes:

• add P2: This release makes a merged Darwin census reliability fix available to consumers.
• 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:

• P2: This release makes a merged Darwin census reliability fix available to consumers.
• 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 execution lanes are retired.

Reviewed October 18, 2026, 7:48 PM ET / 23:48 UTC.