docs: record batch two triage fixes

[steipete]

What Problem This Solves

Collect the second triage batch's release notes in one PR so the independently prepared code PRs do not conflict in CHANGELOG.md.

Changes

Update Highlights and record the paired-close repair, both repair timeout fixes, and review-revision display, retaining contributor credit. Released sections are unchanged.

Land after these code PRs:

• fix(repair): time out cluster intake dispatch and target clone #1483
• fix(repair): time out cluster selector OpenAI and gh api calls #1446
• Show review revision in freshness timestamp #1382
• fix(apply): revalidate same-author pairs before closing #1499 (replacement for fix(apply): prevent one-sided paired closes after live drift #1042)

The queue-retry entry already on main is not edited here. Its revert and corrected re-land are owned by #1498 and that repair lane.

Evidence

git diff --check and pnpm run check:docs pass. Local and committed-branch Codex autoreview are clean through P2. Exact head: a8fa43d0c538978a457aa7999eedcb2f446a613f; CI: https://github.com/openclaw/clawsweeper/actions/runs/34248097685. This is documentation-only; executable runtime proofs belong to the linked code PRs.

pnpm outdated --format json found only the coordinated Oxc/tsgolint tooling refresh already tracked in #1318 and newer Node typings outside the Node 24 runtime floor. No additional dependency bump is included. The 2,880-minute release-age policy is retained.

Release and OpenClaw Bay Impact

These batch changes fit a patch. This PR does not authorize a tag, release, publication or deployment. Release preparation remains gated on the remaining autonomous queue and restoration of exact-review workflows after #1497. No Bay data or observer contract changes.

Real Behavior Proof: Rendered Documentation

The exact committed changelog was rendered with the installed markdown-it 15.0.1, the repository's documentation parser, on Node 24.20.0. This exercises the changed documentation artifact; runtime behavior remains proved in the four linked code PRs.

Reproduction from an installed checkout:

git show a8fa43d0c538978a457aa7999eedcb2f446a613f:CHANGELOG.md > "$TMPDIR/batch-two-changelog.md"
node --input-type=module -e 'import fs from "node:fs"; import MarkdownIt from "markdown-it"; process.stdout.write(new MarkdownIt().render(fs.readFileSync(process.argv[1], "utf8")))' "$TMPDIR/batch-two-changelog.md" > "$TMPDIR/batch-two-changelog.html"

Observed after rendering: the heading is <h2>0.3.1 - Unreleased</h2>. All four added notes render as list items with intact contributor credit: paired-close revalidation (@vincentkoc), dispatch/clone deadlines (@SebTardif), selector deadlines (@SebTardif), and revision labels (@elijahfriedman). No note text is lost or interpreted as markup. Comparing the entire released suffix starting at ## 0.3.0 - with parent 9da27d076a542b06751a879eace475ccc134fbff is byte-identical.

Before/after standalone HTML files were generated locally. A separate Git merge-tree check against the post-revert main is conflict-free and does not restore the removed queue-retry entry. Exact-head CI passed: https://github.com/openclaw/clawsweeper/actions/runs/34248097685.

Limits: this proves the release-note artifact renders correctly; it does not claim the four implementation PRs have already merged. The explicit notes-last landing order remains required. No public website deployment, release or publication occurred.

[clawsweeper]

🦞👀
ClawSweeper picked this up.

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

[steipete]

@clawsweeper re-review

Documentation-only head a8fa43d0c538978a457aa7999eedcb2f446a613f passes git diff --check, pnpm run check:docs, and local/committed-branch Codex autoreview through P2. It changes only the Unreleased highlights and four contributor-credited release-note bullets. Released sections are unchanged; the queue-retry/revert lane's note is untouched.

The linked code PRs contain their real runtime proof. Land this PR only after #1483, #1446, #1382, and #1499. CI for this exact head: https://github.com/openclaw/clawsweeper/actions/runs/34248097685. No release, tag or deployment has been performed.

[clawsweeper]

🦞👀
Exact review queued.

Re-review progress:

• State: Complete
• Detail: A newer review tuple already exists; this stale result was superseded.
• Run: https://github.com/openclaw/clawsweeper/actions/runs/34249163812
• Updated: 2026-09-08T16:08:10.984Z

[steipete]

@clawsweeper re-review

The prior review request could not reach review because main's early sparse checkout hid the setup-pnpm local action. #1498 has now reverted that regression. Please review this unchanged prepared head and current body; the runtime proof and clean independent review are already recorded there. This requests review only.

[clawsweeper]

🦞👀
Exact review queued.

Re-review progress:

• State: Complete
• Detail: The durable review result and its route handoff completed.
• Run: https://github.com/openclaw/clawsweeper/actions/runs/34249931068
• Updated: 2026-09-08T16:15:50.439Z

[clawsweeper]

Codex review: needs changes before merge. Reviewed September 8, 2026, 12:18 PM ET / 16:18 UTC.

ClawSweeper review

What this changes

Updates the Unreleased highlights and adds four credited notes covering paired-close checks, repair timeouts, and review-revision display.

Merge readiness

⛔ Needs changes before merge - 1 item remains

The release-note contribution remains useful and has no actionable patch defects. The updated documentation proof resolves the prior proof concern; the four implementation dependencies remain open.

Priority: P3
Reviewed head: a8fa43d0c538978a457aa7999eedcb2f446a613f

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	A focused, correct documentation patch with adequate rendering evidence and an explicit implementation-first landing order.
Proof confidence	🐚 platinum hermit (4/6)	Sufficient (live_output): The captured body records exact-head CHANGELOG.md rendering with markdown-it 15.0.1 on Node 24.20.0, observing intact headings, all four credited bullets, and unchanged released content; this proves the changed documentation artifact without claiming the linked runtime fixes have landed.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Verified	Sufficient (live_output): The captured body records exact-head CHANGELOG.md rendering with markdown-it 15.0.1 on Node 24.20.0, observing intact headings, all four credited bullets, and unchanged released content; this proves the changed documentation artifact without claiming the linked runtime fixes have landed.
Evidence reviewed	5 items	Introduced patch and whitespace validation: The verified parent-to-head diff changes only CHANGELOG.md: five added lines and one removed line, confined to Unreleased highlights and four bullets. The separate git diff --check command completed successfully. Applicable documentation policy: Read AGENTS.md fully and CONTRIBUTING.md. Documentation-only changes use focused documentation validation; the restriction on contributor changelog edits explicitly concerns openclaw/openclaw. No .agents/maintainer-notes directory exists, and the root policy is the applicable scope for this root-level file. Current-main necessity: The fetched main changelog still has the previous highlights and lacks the four proposed bullets. The related implementation PRs remain open in the captured context and in individual live REST checks: #1483, #1446, #1382, and #1499. No merged replacement establishes grounds for closure.
Findings	None	None.
Security	None	None.

How this fits together

ClawSweeper’s changelog collects operator-visible changes for release readers. This PR documents four separately reviewed implementations without changing automation or OpenClaw Bay.

flowchart LR
  A[Four implementation PRs] --> B[Confirm implementations landed]
  B --> C[Unreleased changelog]
  C --> D[Markdown rendering]
  D --> E[Release readers]

Loading

Before merge

• Complete next step (P2) - Land this notes PR only after fix(repair): time out cluster intake dispatch and target clone #1483, fix(repair): time out cluster selector OpenAI and gh api calls #1446, Show review revision in freshness timestamp #1382, and fix(apply): revalidate same-author pairs before closing #1499 have merged.

Agent review details

Security

None.

Review metrics

None.

Technical review

Best possible solution:

Keep the consolidated, credited release notes aligned with the four landed implementations while preserving released history.

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

Not applicable: this PR edits release notes rather than repairing runtime behavior; its exact diff and recorded rendering results are directly inspectable.

Is this the best way to solve the issue?

Yes: consolidating the batch notes avoids competing changelog edits, provided the documented implementations land first.

AGENTS.md: found and applied where relevant.

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

Labels

Label changes:

• add proof: sufficient: Contributor real behavior proof is sufficient. The captured body records exact-head CHANGELOG.md rendering with markdown-it 15.0.1 on Node 24.20.0, observing intact headings, all four credited bullets, and unchanged released content; this proves the changed documentation artifact without claiming the linked runtime fixes have landed.
• add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (live_output): The captured body records exact-head CHANGELOG.md rendering with markdown-it 15.0.1 on Node 24.20.0, observing intact headings, all four credited bullets, and unchanged released content; this proves the changed documentation artifact without claiming the linked runtime fixes have landed.
• remove status: 📣 needs proof: Current PR status label is status: 👀 ready for maintainer look.

Label justifications:

• P3: This is a small release-documentation update with no executable behavior change.
• rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🐚 platinum hermit and patch quality is 🐚 platinum hermit.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (live_output): The captured body records exact-head CHANGELOG.md rendering with markdown-it 15.0.1 on Node 24.20.0, observing intact headings, all four credited bullets, and unchanged released content; this proves the changed documentation artifact without claiming the linked runtime fixes have landed.
• proof: sufficient: Contributor real behavior proof is sufficient. The captured body records exact-head CHANGELOG.md rendering with markdown-it 15.0.1 on Node 24.20.0, observing intact headings, all four credited bullets, and unchanged released content; this proves the changed documentation artifact without claiming the linked runtime fixes have landed.

Evidence

What I checked:

• Introduced patch and whitespace validation: The verified parent-to-head diff changes only CHANGELOG.md: five added lines and one removed line, confined to Unreleased highlights and four bullets. The separate git diff --check command completed successfully. (CHANGELOG.md:10, a8fa43d0c538)
• Applicable documentation policy: Read AGENTS.md fully and CONTRIBUTING.md. Documentation-only changes use focused documentation validation; the restriction on contributor changelog edits explicitly concerns openclaw/openclaw. No .agents/maintainer-notes directory exists, and the root policy is the applicable scope for this root-level file. (AGENTS.md, a8fa43d0c538)
• Current-main necessity: The fetched main changelog still has the previous highlights and lacks the four proposed bullets. The related implementation PRs remain open in the captured context and in individual live REST checks: fix(repair): time out cluster intake dispatch and target clone #1483, fix(repair): time out cluster selector OpenAI and gh api calls #1446, Show review revision in freshness timestamp #1382, and fix(apply): revalidate same-author pairs before closing #1499. No merged replacement establishes grounds for closure. (CHANGELOG.md:121, 2690dafa8c33)
• Updated proof and review continuity: The complete captured body, sourceRevision 15d07aa16f595984f52e3ac253f1143e1c842de0c56d3ff2a611922cf75ecee3, records rendering the exact head with markdown-it 15.0.1 on Node 24.20.0: the Unreleased heading and all four credited list items render intact, and the released suffix matches the parent. This directly addresses the earlier proof request. The prepared screenshots were inspected and belong to the separate revision-display implementation, not this changelog proof. No embedded commands were executed. (CHANGELOG.md:123, a8fa43d0c538)
• Prior changelog maintenance: Current-main history identifies prior changelog work by Peter Steinberger and Vincent Koc. GitHub commit metadata confirms steipete authored the earlier batch-note update at ecdeaf5. Local deeper blame and historical release-blob inspection encountered unavailable-object HTTP 403 failures; no source-line introduction or shipped-release claim relies on those failed reads. (CHANGELOG.md, ecdeaf5561ac)

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.

History

Review history (2 earlier review cycles)

• reviewed 2026-09-08T16:08:34.709Z sha a8fa43d :: needs real behavior proof before merge. :: none
• reviewed 2026-09-08T16:12:50.850Z sha a8fa43d :: needs real behavior proof before merge. :: none

[steipete]

@clawsweeper re-review

The main body now contains after-change documentation proof: native Git supplied exact-head CHANGELOG.md to markdown-it 15.0.1, producing standalone before/after HTML. The Unreleased heading and all four contributor-credited list items render intact; the complete released suffix is byte-identical to the parent. A merge-tree check proves this PR does not restore the reverted retry note.

Exact-head CI passed: https://github.com/openclaw/clawsweeper/actions/runs/34248097685. Local and branch autoreviews remain clean. This is proof of the changed documentation artifact; the four linked runtime fixes still must land first. No implementation, release, or deployment is claimed by these notes.

[clawsweeper]

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event exact_review_queue).
Result: when the review finishes, ClawSweeper will create the durable review comment if needed or update the existing comment in place.

[clawsweeper]

🦞👀
Exact review queued.

Re-review progress:

• State: Complete
• Detail: The durable review result and its route handoff completed.
• Run: https://github.com/openclaw/clawsweeper/actions/runs/34250498433
• Updated: 2026-09-08T16:21:22.539Z