docs: prepare 0.15.2 unreleased notes

[steipete]

Prepare the next patch release notes for safer Messages bridge startup and reliable local validation. The Unreleased section is ordered by user impact and carries contributor credit for #274, #276, and #277, plus the subprocess capture repair in #279.

This is the only PR in this batch that edits CHANGELOG.md. Land it after #279, #277, #274, and #276. The audio preparation fix in #278 remains outside these notes until inline Messages playback has inspectable proof on a bridge-enabled Mac.

Dependency recheck found the Swift packages, SwiftLint, and existing Actions pins current. Retain the proven shared release-workflow hotfix pin; today's new release-workflows release needs separate release-pipeline validation. Recommend patch v0.15.2 after the prepared fixes land and main CI passes. No version tag or release has been created.

The proof comment records combined validation and exact-head CI. Version stamping, a dated release section, signed/notarized universal macOS artifacts, Linux packaging, and Homebrew handoff remain gated by release authorization.

[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 changes before merge. Reviewed September 7, 2026, 4:32 AM ET / 08:32 UTC.

ClawSweeper review

What this changes

Adds an Unreleased changelog section covering bridge startup improvements and two local test reliability fixes, with contributor credits.

Merge readiness

⛔ Needs changes before merge - 1 item remains

The notes are focused and consistent with the described fixes, but their four prerequisite PRs remain open in the supplied snapshot. Current main does not contain this section, and the collaborator-authored PR remains useful.

Priority: P3
Reviewed head: 2a91a1b626f71f9db4c6dea4a5fbb4001c7ad6f1

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	Focused, readable release notes with no actionable patch defect; the stated prerequisite landing order remains applicable.
Proof confidence	🌊 off-meta tidepool	Not applicable: This collaborator-authored changelog PR introduces no runtime behavior; native proof for the described fixes belongs to their implementation PRs.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Not applicable	Not applicable: This collaborator-authored changelog PR introduces no runtime behavior; native proof for the described fixes belongs to their implementation PRs.
Evidence reviewed	6 items	Policy and repository identity: The origin identifies openclaw/imsg. The full root AGENTS.md was read and its focused-change and validation guidance applied. No maintainer-notes directory appeared in the inspected .agents tree. Complete introduced change: The pinned comparison contains only nine added changelog lines: an Unreleased heading, a highlight, and four entries. No executable code, dependency, workflow, version, or permissions change is introduced. Explicit landing dependencies: The captured PR body requires landing after #279, #277, #274, and #276. All four are open and unmerged in the supplied GitHub context. Their descriptions support the corresponding changelog entries; audio work is explicitly excluded.
Findings	None	None.
Security	None	None.

How this fits together

The changelog communicates imsg changes to users and feeds release preparation. Unreleased entries become dated release notes only when the corresponding changes and release preparation are ready.

flowchart LR
  A[Related fix PRs] --> B[Unreleased changelog]
  B --> C[Release preparation]
  C --> D[Dated version section]
  D --> E[Published release notes]

Loading

Before merge

• Complete next step (P2) - Land after test: drain CLI subprocess output before waiting for exit #279, fix: make RPC send tests independent of host bridge availability #277, fix: serialize Messages bridge launches across processes #274, and fix: make bridge launch readiness timeout configurable #276, as specified in the PR body.

Agent review details

Security

None.

Review metrics

None.

Technical review

Best possible solution:

Keep the release notes aligned with the fixes actually landed, retaining Unreleased status until authorized version preparation.

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

Not applicable: this PR changes release-note prose only; the underlying fixes belong to separate PRs.

Is this the best way to solve the issue?

Yes: one consolidated Unreleased section is a narrow approach consistent with existing changelog practice and the explicitly stated landing order.

AGENTS.md: found and applied where relevant.

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

Labels

Label changes:

• add P3: This is a focused release-documentation update with no runtime changes.
• 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. Not applicable: This collaborator-authored changelog PR introduces no runtime behavior; native proof for the described fixes belongs to their implementation PRs.

Label justifications:

• P3: This is a focused release-documentation update with no runtime changes.
• 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. Not applicable: This collaborator-authored changelog PR introduces no runtime behavior; native proof for the described fixes belongs to their implementation PRs.

Evidence

What I checked:

• Policy and repository identity: The origin identifies openclaw/imsg. The full root AGENTS.md was read and its focused-change and validation guidance applied. No maintainer-notes directory appeared in the inspected .agents tree. (AGENTS.md:1, 2a91a1b626f7)
• Complete introduced change: The pinned comparison contains only nine added changelog lines: an Unreleased heading, a highlight, and four entries. No executable code, dependency, workflow, version, or permissions change is introduced. (CHANGELOG.md:3, 2a91a1b626f7)
• Explicit landing dependencies: The captured PR body requires landing after test: drain CLI subprocess output before waiting for exit #279, fix: make RPC send tests independent of host bridge availability #277, fix: serialize Messages bridge launches across processes #274, and fix: make bridge launch readiness timeout configurable #276. All four are open and unmerged in the supplied GitHub context. Their descriptions support the corresponding changelog entries; audio work is explicitly excluded. (2a91a1b626f7)
• Current main and release boundary: The fetched main revision carries v0.15.1 and lacks the proposed Unreleased section. Its launcher still passes a fixed 15-second readiness timeout, consistent with the timeout change remaining in a separate open PR. (Sources/IMsgCore/MessagesLauncher.swift, 646ea7af9616)
• Release contract: Release documentation requires a dated section and aligned version files for an actual release. This PR deliberately prepares Unreleased prose without stamping or dispatching a release, so those later release requirements are not defects in this patch. (docs/RELEASING.md:18, 2a91a1b626f7)
• Release-note routing history: Available changelog history repeatedly lists Peter Steinberger for release preparation and user-impact summaries, including the current main release commit. Deeper blame and patch inspection encountered an unavailable Git object and failed network resolution, so no source-line introduction attribution is asserted. (CHANGELOG.md, 646ea7af9616)

Likely related people:

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

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.

[steipete]

Verification for notes head 2a91a1b626f71f9db4c6dea4a5fbb4001c7ad6f1:

The prepared set was applied together over main 646ea7af9616dc3e6406d86aa269bf4fb1b07a76 in this order: #279 at aa6a1d3, #277 at 0a214f1, #274 at 78b3dae, and #276 at 0034547. No merges were performed. After validation the temporary patches were removed, leaving this PR with only CHANGELOG.md.

• Combined make test: 753 Swift tests passed (442 CLI and 311 core), plus documentation and native helper tests.
• Combined make lint: passed with 17 size warnings and zero serious violations. git diff --check: passed.
• The combined built CLI was signed with the matching Developer ID. Version output, a read-only real Messages chat query, and the missing-database error path all passed; private chat fields were withheld and error stdout stayed empty.
• Every prepared code/test branch and this notes-only branch passed independent autoreview at P0–P2. The notes passed both local and committed-branch review.
• The four changelog bullets cover the prepared changes since v0.15.1 without editing a released section. Runtime/package checks found no dependency bumps needed.

Exact notes-head macOS/Linux CI: https://github.com/openclaw/imsg/actions/runs/34100842659.

Land #279, #277, #274, and #276 before this PR. Recommend patch v0.15.2 once main CI is green and the release is authorized. #278 remains excluded pending inspectable inline Messages playback on an authorized bridge-enabled host. Version stamping, publication, notarization, and Homebrew updates have not been performed.