Skip to content

fix(cron): keep recovered tool warnings diagnostic#84308

Merged
clawsweeper[bot] merged 3 commits into
mainfrom
clawsweeper/automerge-openclaw-openclaw-84045
May 20, 2026
Merged

fix(cron): keep recovered tool warnings diagnostic#84308
clawsweeper[bot] merged 3 commits into
mainfrom
clawsweeper/automerge-openclaw-openclaw-84045

Conversation

@clawsweeper

@clawsweeper clawsweeper Bot commented May 19, 2026

Copy link
Copy Markdown
Contributor

Makes #84045 merge-ready for the ClawSweeper automerge loop.
The edit pass should inspect the live PR diff, review comments, and failing checks; rebase if needed; keep the contributor branch credited; and stop only when validation is green or an external blocker is proven.

ClawSweeper 🐠 replacement reef notes:

  • Repair fallback: GitHub rejected the repair branch push because it updates workflow files and the ClawSweeper app token does not have workflows permission

Co-author credit kept:

fish notes: model gpt-5.5, reasoning high; reviewed against 8c29020.

@clawsweeper clawsweeper Bot added agents Agent runtime and tooling size: M clawsweeper:automerge Maintainer opted this PR into bounded ClawSweeper-reviewed automerge proof: supplied External PR includes structured after-fix real behavior proof. proof: sufficient ClawSweeper judged the real behavior proof convincing. P2 Normal backlog priority with limited blast radius. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. merge-risk: 🚨 session-state 🚨 May lose, corrupt, stale, or mis-associate session, agent, or context state. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. clawsweeper Tracked by ClawSweeper automation labels May 19, 2026
@clawsweeper clawsweeper Bot mentioned this pull request May 19, 2026
Closed
@openclaw-barnacle openclaw-barnacle Bot removed the proof: supplied External PR includes structured after-fix real behavior proof. label May 19, 2026
@clawsweeper

clawsweeper Bot commented May 19, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

Codex review: passed.

Workflow note: Future ClawSweeper reviews update this same comment in place.

How this review workflow works
  • 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.

Summary
The PR threads middleware tool-error metadata into reply payloads, teaches cron outcome and diagnostics code to keep marked recovered warnings non-fatal, and adds focused regression coverage plus a changelog entry.

Reproducibility: yes. Source inspection shows current main lacks a non-terminal recovered-warning path in cron classification, and the linked source PR includes a terminal runtime probe for the affected cron payload outcome.

PR rating
Overall: 🐚 platinum hermit
Proof: 🦞 diamond lobster
Patch quality: 🐚 platinum hermit
Summary: Strong focused proof and a clean patch make this likely mergeable, with only the internal marker contract left as maintainer-owned merge risk.

Rank-up moves:

  • none
What the crustacean ranks mean
  • 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
  • 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
  • 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
  • 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
  • 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
  • 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
  • 🌊 off-meta tidepool: rating does not apply to this item.

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.

Real behavior proof
Sufficient (terminal): The linked source PR provides after-fix terminal output from a one-shot runtime probe of the cron payload outcome path.

Risk before merge

  • The patch intentionally interprets details.middlewareError as a recovered post-processing marker when successful cron output exists; if a future producer reuses that marker for a truly terminal trailing failure, cron could classify that payload as diagnostic instead of fatal.

Maintainer options:

  1. Accept the middleware recovery marker (recommended)
    Merge after required checks if maintainers agree that details.middlewareError is the internal recovered post-processing marker and should not override otherwise successful cron output.
  2. Narrow the marker before merge
    Ask for a more specific marker or producer-side contract if maintainers want to prevent unrelated middleware errors from becoming non-terminal cron diagnostics.

Next step before merge
No repair lane is needed because exact-head review found no actionable patch defect; automerge should wait on required checks and maintainer acceptance of the marker contract.

Security
Cleared: The diff only touches cron/agent classification, tests, and changelog; it does not change workflows, dependencies, secrets, package resolution, or install scripts.

Review details

Best possible solution:

Land the focused metadata-based cron fix after required checks if maintainers accept the internal middlewareError recovery contract; otherwise narrow the marker before merge.

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

Yes. Source inspection shows current main lacks a non-terminal recovered-warning path in cron classification, and the linked source PR includes a terminal runtime probe for the affected cron payload outcome.

Is this the best way to solve the issue?

Yes. The PR uses an existing internal middleware marker, preserves fatal behavior for unmarked tool errors, and adds focused coverage around cron output, structured delivery, marker propagation, and diagnostics.

Label justifications:

  • P2: This is a focused cron/agent correctness fix with limited blast radius and targeted regression coverage.
  • merge-risk: 🚨 session-state: The diff changes how successful scheduled runs classify status, output, delivery payloads, and diagnostics when a recovered tool warning is present.
  • rating: 🐚 platinum hermit: Current PR rating is 🐚 platinum hermit because proof is 🦞 diamond lobster, patch quality is 🐚 platinum hermit, and Strong focused proof and a clean patch make this likely mergeable, with only the internal marker contract left as maintainer-owned merge risk.
  • status: 🚀 automerge armed: This PR is in ClawSweeper's automerge lane. Sufficient (terminal): The linked source PR provides after-fix terminal output from a one-shot runtime probe of the cron payload outcome path.
  • proof: sufficient: Contributor real behavior proof is sufficient. The linked source PR provides after-fix terminal output from a one-shot runtime probe of the cron payload outcome path.

What I checked:

  • Current-main root cause: Current main computes cron fallback output from payload text and treats a trailing isError payload as fatal unless a later success or presentation-warning exception exists; there is no metadata path for recovered tool warnings. (src/cron/isolated-agent/helpers.ts:205, d7896ed4c981)
  • Tool-result marker propagation: The PR records details.middlewareError === true on lastToolError when the tool result is classified as an error, then marks the synthesized warning payload metadata only after user-facing assistant output exists. (src/agents/pi-embedded-subscribe.handlers.tools.ts:71, 8b8a36e9127c)
  • Cron classification fix: The PR skips marked non-terminal warning payloads when choosing summary/output text and exempts the marked last error from fatal classification only when successful cron output exists and no fatal run-level or failure signal is present. (src/cron/isolated-agent/helpers.ts:205, 8b8a36e9127c)
  • Diagnostics behavior: Cron diagnostics still records the tool warning, but downgrades marked non-terminal tool-warning payload text to warn when the final cron status is ok. (src/cron/run-diagnostics.ts:276, 8b8a36e9127c)
  • Regression coverage: New tests cover final assistant text, structured media-only cron output, embedded-runner metadata creation, and diagnostic severity for marked recovered tool warnings. (src/cron/isolated-agent.helpers.test.ts:43, 8b8a36e9127c)
  • Real behavior proof from source PR: The linked source PR at fix(cron): keep recovered tool warnings diagnostic #84045 includes after-fix terminal output from a one-shot runtime probe showing a marked warning after a media cron payload remains nonfatal and the media payload remains deliverable.

Likely related people:

  • abnershang: Authored the linked source PR for this same cron warning behavior and appears as a co-author on recent current-main cron structured-denial work touching the same files. (role: recent area contributor and source-fix author; confidence: high; commits: 2ac0d85c5c0d, 7f8141ead974; files: src/cron/isolated-agent/helpers.ts, src/agents/pi-embedded-runner/run/payloads.ts, src/agents/pi-embedded-subscribe.handlers.tools.ts)
  • takhoffman: Requested this automerge replacement and is recorded as approver/co-author on recent current-main cron structured-denial work in the same behavior area. (role: reviewer and automerge requester; confidence: medium; commits: 7f8141ead974; files: src/cron/isolated-agent/helpers.ts, src/agents/pi-embedded-subscribe.handlers.tools.ts)

Codex review notes: model gpt-5.5, reasoning high; reviewed against d7896ed4c981.

@clawsweeper clawsweeper Bot added status: 🚀 automerge armed This PR is in ClawSweeper's automerge lane. and removed status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. labels May 19, 2026
@clawsweeper

clawsweeper Bot commented May 19, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

🦞✅
ClawSweeper merged this PR after the passing review.

Source: clawsweeper[bot]
Feedback: structured ClawSweeper verdict: pass (sha=8b8a36e9127c7e147cd02b7d99ded8a47b248147)
Merge status: merged by ClawSweeper automerge
Merged at: 2026-05-20T01:19:52Z
Merge commit: 6048cd43a5ab

What merged:

  • The PR threads middleware tool-error metadata into reply payloads, teaches cron outcome and diagnostics code to keep marked recovered warnings non-fatal, and adds focused regression coverage plus a changelog entry.
  • Reproducibility: yes. Source inspection shows current main lacks a non-terminal recovered-warning path in cr ... fication, and the linked source PR includes a terminal runtime probe for the affected cron payload outcome.

Automerge notes:

  • PR branch already contained follow-up commit before automerge: fix(cron): keep recovered tool warnings diagnostic

The automerge loop is complete.

Automerge progress:

  • 2026-05-20 00:56:14 UTC merge check queued 76e21d19718d (GitHub checks failed: build-artifacts:FAILURE)
  • 2026-05-20 01:13:19 UTC review queued 8b8a36e9127c (after repair)
  • 2026-05-20 01:19:09 UTC review passed 8b8a36e9127c (structured ClawSweeper verdict: pass (sha=8b8a36e9127c7e147cd02b7d99ded8a47b248...)
  • 2026-05-20 01:19:54 UTC merged 8b8a36e9127c (merged by ClawSweeper automerge)

@clawsweeper clawsweeper Bot force-pushed the clawsweeper/automerge-openclaw-openclaw-84045 branch from 8c29020 to d0ae3fc Compare May 19, 2026 23:19
@clawsweeper

clawsweeper Bot commented May 19, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

ClawSweeper PR egg

✨ Hatched: 🥚 common Pearl Review Wisp

        .--^^^^--.           
     .-'  o    o  '-.        
    /       \__/      \      
   |    /\  ____  /\   |     
   |   /  \/____\/  \  |     
    \  \_.------._/  /       
     '._  `----'  _.'        
        '-.____.-'           
       _/|_|  |_|\_          
      /__|      |__\         
       .-----------.         
      '-------------'

Rarity: 🥚 common.
Trait: hums during re-review.
Image traits: location branch lighthouse; accessory tiny test log scroll; palette plum, gold, and soft gray; mood watchful; pose nestled inside a glowing shell; shell glossy opal shell; lighting bright celebratory glints; background small review tokens.
How to hatch it: once this PR reaches status: 👀 ready for maintainer look or status: 🚀 automerge armed, the PR author or a maintainer can comment @clawsweeper hatch to turn this ASCII egg into its generated creature image.
Share on X: post this hatch
Copy: My PR egg hatched a 🥚 common Pearl Review Wisp in ClawSweeper.

What is this egg doing here?
  • Eggs appear after the PR passes real-behavior proof. It is here for vibes, not verdicts: it does not change labels, ratings, merge decisions, or automation.
  • The shell reacts to review momentum: open follow-up work warms it up, re-review makes it wobble, and a clean final review lets it hatch.
  • Hatchable usually means sufficient real-behavior proof, no blocking P0/P1/P2 findings, no security attention needed, and clean correctness.
  • The hatch is seeded from this repository and PR number, so the same PR keeps the same creature; the reviewed head SHA can only change safe visual details.
  • Rarity is just collectible sparkle: 🥚 common, 🌱 uncommon, 💎 rare, ✨ glimmer, and 🌈 legendary.

@clawsweeper clawsweeper Bot force-pushed the clawsweeper/automerge-openclaw-openclaw-84045 branch from d0ae3fc to 76e21d1 Compare May 20, 2026 00:13
@clawsweeper clawsweeper Bot force-pushed the clawsweeper/automerge-openclaw-openclaw-84045 branch from 76e21d1 to 8b8a36e Compare May 20, 2026 01:13
@clawsweeper clawsweeper Bot merged commit 6048cd4 into main May 20, 2026
98 checks passed
@clawsweeper clawsweeper Bot deleted the clawsweeper/automerge-openclaw-openclaw-84045 branch May 20, 2026 01:19
@Haderach-Ram Haderach-Ram mentioned this pull request May 20, 2026
Open
@github-actions github-actions Bot mentioned this pull request May 20, 2026
Open
markfietje pushed a commit to markfietje/openclaw that referenced this pull request May 20, 2026
@clawsweeper @abnershang @Takhoffman
fix(cron): keep recovered tool warnings diagnostic (#84308)
73a2ad2 
Summary:
- The PR threads middleware tool-error metadata into reply payloads, teaches cron outcome and diagnostics code to keep marked recovered warnings non-fatal, and adds focused regression coverage plus a changelog entry.
- Reproducibility: yes. Source inspection shows current main lacks a non-terminal recovered-warning path in cr ... fication, and the linked source PR includes a terminal runtime probe for the affected cron payload outcome.

Automerge notes:
- PR branch already contained follow-up commit before automerge: fix(cron): keep recovered tool warnings diagnostic

Validation:
- ClawSweeper review passed for head 8b8a36e9127c7e147cd02b7d99ded8a47b248147.
- Required merge gates passed before the squash merge.

Prepared head SHA: 8b8a36e9127c7e147cd02b7d99ded8a47b248147
Review: openclaw/openclaw#84308 (comment)

Co-authored-by: abnershang <abner.shang@gmail.com>
Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>
Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com>
Approved-by: takhoffman
Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>
markfietje pushed a commit to markfietje/openclaw that referenced this pull request May 20, 2026
@clawsweeper @abnershang @Takhoffman
fix(cron): keep recovered tool warnings diagnostic (#84308)
8ed63c1 
Summary:
- The PR threads middleware tool-error metadata into reply payloads, teaches cron outcome and diagnostics code to keep marked recovered warnings non-fatal, and adds focused regression coverage plus a changelog entry.
- Reproducibility: yes. Source inspection shows current main lacks a non-terminal recovered-warning path in cr ... fication, and the linked source PR includes a terminal runtime probe for the affected cron payload outcome.

Automerge notes:
- PR branch already contained follow-up commit before automerge: fix(cron): keep recovered tool warnings diagnostic

Validation:
- ClawSweeper review passed for head 8b8a36e9127c7e147cd02b7d99ded8a47b248147.
- Required merge gates passed before the squash merge.

Prepared head SHA: 8b8a36e9127c7e147cd02b7d99ded8a47b248147
Review: openclaw/openclaw#84308 (comment)

Co-authored-by: abnershang <abner.shang@gmail.com>
Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>
Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com>
Approved-by: takhoffman
Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>
@clawsweeper clawsweeper Bot mentioned this pull request May 20, 2026
Closed
3 tasks
SebTardif pushed a commit to SebTardif/openclaw that referenced this pull request May 24, 2026
@clawsweeper @abnershang
@Takhoffman @SebTardif
fix(cron): keep recovered tool warnings diagnostic (openclaw#84308)
2cd3f9a 
Summary:
- The PR threads middleware tool-error metadata into reply payloads, teaches cron outcome and diagnostics code to keep marked recovered warnings non-fatal, and adds focused regression coverage plus a changelog entry.
- Reproducibility: yes. Source inspection shows current main lacks a non-terminal recovered-warning path in cr ... fication, and the linked source PR includes a terminal runtime probe for the affected cron payload outcome.

Automerge notes:
- PR branch already contained follow-up commit before automerge: fix(cron): keep recovered tool warnings diagnostic

Validation:
- ClawSweeper review passed for head 8b8a36e.
- Required merge gates passed before the squash merge.

Prepared head SHA: 8b8a36e
Review: openclaw#84308 (comment)

Co-authored-by: abnershang <abner.shang@gmail.com>
Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>
Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com>
Approved-by: takhoffman
Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>
SebTardif pushed a commit to SebTardif/openclaw that referenced this pull request May 24, 2026
@clawsweeper @abnershang
@Takhoffman @SebTardif
fix(cron): keep recovered tool warnings diagnostic (openclaw#84308)
9f10344 
Summary:
- The PR threads middleware tool-error metadata into reply payloads, teaches cron outcome and diagnostics code to keep marked recovered warnings non-fatal, and adds focused regression coverage plus a changelog entry.
- Reproducibility: yes. Source inspection shows current main lacks a non-terminal recovered-warning path in cr ... fication, and the linked source PR includes a terminal runtime probe for the affected cron payload outcome.

Automerge notes:
- PR branch already contained follow-up commit before automerge: fix(cron): keep recovered tool warnings diagnostic

Validation:
- ClawSweeper review passed for head 8b8a36e.
- Required merge gates passed before the squash merge.

Prepared head SHA: 8b8a36e
Review: openclaw#84308 (comment)

Co-authored-by: abnershang <abner.shang@gmail.com>
Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>
Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com>
Approved-by: takhoffman
Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>
SebTardif pushed a commit to SebTardif/openclaw that referenced this pull request May 24, 2026
@clawsweeper @abnershang
@Takhoffman @SebTardif
fix(cron): keep recovered tool warnings diagnostic (openclaw#84308)
3f7ba8f 
Summary:
- The PR threads middleware tool-error metadata into reply payloads, teaches cron outcome and diagnostics code to keep marked recovered warnings non-fatal, and adds focused regression coverage plus a changelog entry.
- Reproducibility: yes. Source inspection shows current main lacks a non-terminal recovered-warning path in cr ... fication, and the linked source PR includes a terminal runtime probe for the affected cron payload outcome.

Automerge notes:
- PR branch already contained follow-up commit before automerge: fix(cron): keep recovered tool warnings diagnostic

Validation:
- ClawSweeper review passed for head 8b8a36e.
- Required merge gates passed before the squash merge.

Prepared head SHA: 8b8a36e
Review: openclaw#84308 (comment)

Co-authored-by: abnershang <abner.shang@gmail.com>
Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>
Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com>
Approved-by: takhoffman
Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>
github-actions Bot pushed a commit to Desicool/openclaw that referenced this pull request May 24, 2026
@clawsweeper @abnershang @Takhoffman
fix(cron): keep recovered tool warnings diagnostic (openclaw#84308)
9815da3 
Summary:
- The PR threads middleware tool-error metadata into reply payloads, teaches cron outcome and diagnostics code to keep marked recovered warnings non-fatal, and adds focused regression coverage plus a changelog entry.
- Reproducibility: yes. Source inspection shows current main lacks a non-terminal recovered-warning path in cr ... fication, and the linked source PR includes a terminal runtime probe for the affected cron payload outcome.

Automerge notes:
- PR branch already contained follow-up commit before automerge: fix(cron): keep recovered tool warnings diagnostic

Validation:
- ClawSweeper review passed for head 8b8a36e.
- Required merge gates passed before the squash merge.

Prepared head SHA: 8b8a36e
Review: openclaw#84308 (comment)

Co-authored-by: abnershang <abner.shang@gmail.com>
Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>
Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com>
Approved-by: takhoffman
Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>
galiniliev pushed a commit to galiniliev/openclaw that referenced this pull request May 25, 2026
@clawsweeper @abnershang @Takhoffman
fix(cron): keep recovered tool warnings diagnostic (openclaw#84308)
4c96a13 
Summary:
- The PR threads middleware tool-error metadata into reply payloads, teaches cron outcome and diagnostics code to keep marked recovered warnings non-fatal, and adds focused regression coverage plus a changelog entry.
- Reproducibility: yes. Source inspection shows current main lacks a non-terminal recovered-warning path in cr ... fication, and the linked source PR includes a terminal runtime probe for the affected cron payload outcome.

Automerge notes:
- PR branch already contained follow-up commit before automerge: fix(cron): keep recovered tool warnings diagnostic

Validation:
- ClawSweeper review passed for head 8b8a36e.
- Required merge gates passed before the squash merge.

Prepared head SHA: 8b8a36e
Review: openclaw#84308 (comment)

Co-authored-by: abnershang <abner.shang@gmail.com>
Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>
Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com>
Approved-by: takhoffman
Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>
SebTardif pushed a commit to SebTardif/openclaw that referenced this pull request May 26, 2026
@clawsweeper @abnershang
@Takhoffman @SebTardif
fix(cron): keep recovered tool warnings diagnostic (openclaw#84308)
2be9b43 
Summary:
- The PR threads middleware tool-error metadata into reply payloads, teaches cron outcome and diagnostics code to keep marked recovered warnings non-fatal, and adds focused regression coverage plus a changelog entry.
- Reproducibility: yes. Source inspection shows current main lacks a non-terminal recovered-warning path in cr ... fication, and the linked source PR includes a terminal runtime probe for the affected cron payload outcome.

Automerge notes:
- PR branch already contained follow-up commit before automerge: fix(cron): keep recovered tool warnings diagnostic

Validation:
- ClawSweeper review passed for head 8b8a36e.
- Required merge gates passed before the squash merge.

Prepared head SHA: 8b8a36e
Review: openclaw#84308 (comment)

Co-authored-by: abnershang <abner.shang@gmail.com>
Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>
Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com>
Approved-by: takhoffman
Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>
SebTardif pushed a commit to SebTardif/openclaw that referenced this pull request May 26, 2026
@clawsweeper @abnershang
@Takhoffman @SebTardif
fix(cron): keep recovered tool warnings diagnostic (openclaw#84308)
694d6ae 
Summary:
- The PR threads middleware tool-error metadata into reply payloads, teaches cron outcome and diagnostics code to keep marked recovered warnings non-fatal, and adds focused regression coverage plus a changelog entry.
- Reproducibility: yes. Source inspection shows current main lacks a non-terminal recovered-warning path in cr ... fication, and the linked source PR includes a terminal runtime probe for the affected cron payload outcome.

Automerge notes:
- PR branch already contained follow-up commit before automerge: fix(cron): keep recovered tool warnings diagnostic

Validation:
- ClawSweeper review passed for head 8b8a36e.
- Required merge gates passed before the squash merge.

Prepared head SHA: 8b8a36e
Review: openclaw#84308 (comment)

Co-authored-by: abnershang <abner.shang@gmail.com>
Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>
Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com>
Approved-by: takhoffman
Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>
SebTardif pushed a commit to SebTardif/openclaw that referenced this pull request May 26, 2026
@clawsweeper @abnershang
@Takhoffman @SebTardif
fix(cron): keep recovered tool warnings diagnostic (openclaw#84308)
620b8f9 
Summary:
- The PR threads middleware tool-error metadata into reply payloads, teaches cron outcome and diagnostics code to keep marked recovered warnings non-fatal, and adds focused regression coverage plus a changelog entry.
- Reproducibility: yes. Source inspection shows current main lacks a non-terminal recovered-warning path in cr ... fication, and the linked source PR includes a terminal runtime probe for the affected cron payload outcome.

Automerge notes:
- PR branch already contained follow-up commit before automerge: fix(cron): keep recovered tool warnings diagnostic

Validation:
- ClawSweeper review passed for head 8b8a36e.
- Required merge gates passed before the squash merge.

Prepared head SHA: 8b8a36e
Review: openclaw#84308 (comment)

Co-authored-by: abnershang <abner.shang@gmail.com>
Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>
Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com>
Approved-by: takhoffman
Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>
jameslcowan pushed a commit to jameslcowan/openclaw that referenced this pull request Jun 2, 2026
@clawsweeper @abnershang @Takhoffman
fix(cron): keep recovered tool warnings diagnostic (openclaw#84308)
59cdbc3 
Summary:
- The PR threads middleware tool-error metadata into reply payloads, teaches cron outcome and diagnostics code to keep marked recovered warnings non-fatal, and adds focused regression coverage plus a changelog entry.
- Reproducibility: yes. Source inspection shows current main lacks a non-terminal recovered-warning path in cr ... fication, and the linked source PR includes a terminal runtime probe for the affected cron payload outcome.

Automerge notes:
- PR branch already contained follow-up commit before automerge: fix(cron): keep recovered tool warnings diagnostic

Validation:
- ClawSweeper review passed for head 8b8a36e.
- Required merge gates passed before the squash merge.

Prepared head SHA: 8b8a36e
Review: openclaw#84308 (comment)

Co-authored-by: abnershang <abner.shang@gmail.com>
Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>
Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com>
Approved-by: takhoffman
Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>
SYU8384 pushed a commit to SYU8384/openclaw that referenced this pull request Jun 3, 2026
@clawsweeper @abnershang @Takhoffman
fix(cron): keep recovered tool warnings diagnostic (openclaw#84308)
a54865a 
Summary:
- The PR threads middleware tool-error metadata into reply payloads, teaches cron outcome and diagnostics code to keep marked recovered warnings non-fatal, and adds focused regression coverage plus a changelog entry.
- Reproducibility: yes. Source inspection shows current main lacks a non-terminal recovered-warning path in cr ... fication, and the linked source PR includes a terminal runtime probe for the affected cron payload outcome.

Automerge notes:
- PR branch already contained follow-up commit before automerge: fix(cron): keep recovered tool warnings diagnostic

Validation:
- ClawSweeper review passed for head 8b8a36e.
- Required merge gates passed before the squash merge.

Prepared head SHA: 8b8a36e
Review: openclaw#84308 (comment)

Co-authored-by: abnershang <abner.shang@gmail.com>
Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>
Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com>
Approved-by: takhoffman
Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>
sablehead pushed a commit to sablehead/openclaw that referenced this pull request Jun 10, 2026
@clawsweeper @abnershang @Takhoffman
fix(cron): keep recovered tool warnings diagnostic (openclaw#84308)
c365efe 
Summary:
- The PR threads middleware tool-error metadata into reply payloads, teaches cron outcome and diagnostics code to keep marked recovered warnings non-fatal, and adds focused regression coverage plus a changelog entry.
- Reproducibility: yes. Source inspection shows current main lacks a non-terminal recovered-warning path in cr ... fication, and the linked source PR includes a terminal runtime probe for the affected cron payload outcome.

Automerge notes:
- PR branch already contained follow-up commit before automerge: fix(cron): keep recovered tool warnings diagnostic

Validation:
- ClawSweeper review passed for head 8b8a36e.
- Required merge gates passed before the squash merge.

Prepared head SHA: 8b8a36e
Review: openclaw#84308 (comment)

Co-authored-by: abnershang <abner.shang@gmail.com>
Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>
Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com>
Approved-by: takhoffman
Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

agents Agent runtime and tooling clawsweeper:automerge Maintainer opted this PR into bounded ClawSweeper-reviewed automerge clawsweeper Tracked by ClawSweeper automation merge-risk: 🚨 session-state 🚨 May lose, corrupt, stale, or mis-associate session, agent, or context state. P2 Normal backlog priority with limited blast radius. proof: sufficient ClawSweeper judged the real behavior proof convincing. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. size: M status: 🚀 automerge armed This PR is in ClawSweeper's automerge lane.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@abnershang