fix(cron): preserve current-session delivery intent by steipete · Pull Request #139491 · openclaw/openclaw

steipete · 2026-09-05T23:07:11Z

What Problem This Solves

Fixes incorrect delivery outcomes for current-session agent-turn automations. A dashboard/WebChat report could be marked Not delivered merely because an unrelated external channel was configured. Conversely, an explicitly requested destination could be silently treated as local delivery when no channel could be selected.

Why This Change Was Made

The delivery resolver now receives the job's existing current-session intent, so it does not invent an external route from unrelated host configuration. A shared delivery-intent check combines the normalized plan with the resolved source route: an explicit or remembered external destination remains owed even when resolution fails. Preview and completion use the same check, and completion receives the plan prepared before inference rather than re-reading job configuration afterward.

The conversation report is committed in both cases. A local-only report completes delivery; an unresolved explicit external request retains its delivery error. Command announcements keep their strict external path. No configuration, schema, protocol, or stored representation changes are introduced. Production code shrinks by three lines.

User Impact

Current-session reports finish successfully in their bound conversation when no external delivery was requested. Requested destinations remain visible as delivery failures if channel selection cannot resolve them. Preview and run history agree about the outcome, while the report remains available in chat.

Evidence

The original real Gateway/dashboard before capture shows the report in chat but a false Telegram missing-target failure with one unrelated configured channel. The repair has storage/resolver coverage for dashboard and WebChat, zero/one/two configured channels, explicit channel/recipient/account/thread settings including thread zero, unavailable actual external routes, and command announcements.

Independent review exposed the explicit-destination side of the same invariant. Nine new cases failed before the correction; the three completion cases verified the durable report before failing on the omitted delivery error. The full final four-file test selection then passed 204 tests. Canonical core/services test types, targeted lint, formatting, and the runtime/metadata build passed.

The first CI run stalled in a recipient test because its metadata-only fake plugin triggered real plugin bootstrap. The fixture now uses the existing activated outbound adapter while retaining the same configured account and assertions. A cold call-through probe observed three bootstrap calls before and zero after; the original 20 cases passed with a fresh cache. No timeout, assertion, or production loader was weakened.

The runtime build uses sourcePerformance, not full SDK/package output. All external APIs in the real Gateway/browser proof are synthetic and local; no authenticated cloud-provider or real external-message claim is made. The original before proof used packaged-plugin staging; subsequent runtime proof uses supported source staging after an earlier package preflight hit its existing 120-second timeout before Gateway execution.

The runtime-validated production commit is a3bef6a3b2cd1755287155dffa52be96a9758c9e, rebased onto 61690da40bd436684311adec59d69bae3b0e383d to inherit the unrelated upstream CI correction in #139519. The complete four-file selection passed 204 tests again on this clean head, as did canonical core/services type checks and the runtime/metadata build. Fresh managed P0–P2 review is scoped-clean. The seven production owners remain unchanged on fetched main e284dad94f9c26cf91f0ce69a392890c7bb6de1e.

This completes the no-external-route behavior of #131975 and preserves the opposite explicit-destination obligation. It is separate from creation-time capture of an explicitly selected channel in #138185.

Fresh real Gateway/dashboard flows on that exact built head verified both outcomes: route-less report with one unrelated Telegram channel → report retained, Delivered, completion succeeded; explicit recipient with zero channels → report retained, Not delivered, completion failed with the channel-resolution error. Each made one synthetic provider request and zero external sends. Both drivers verified their actual HOME, state, config, OAuth, XDG and announced log-file paths were inside their owned temporary roots.

attachment-2939456438.mp4

attachment-758333510.mp4

Current head 6288cf4e58df835fbffbd7ee9858b737e6d32900 contains test-only CI corrections relative to the runtime-tested production commit above. Production is byte-identical. CI exposed two additional direct dispatcher fixtures in CLI suppression and Gateway background-completion coverage that needed the prepared plan. The complete caller audit covers all five construction owners. Those two files passed 31 tests and their owning type checks; the complete candidate passed managed P0–P2 review.

CI also caught an incoming-main lint-suppression inventory omission from #139483. While the temporary inventory correction was being validated, #139576 removed the suppression at its source. The final branch therefore leaves that inventory unchanged; the superseded entry was removed and that deletion independently reviewed. The original three fixture/guard checks totalled 35 passing tests, and current CI verifies composition with the upstream cleanup. No assertions, timeouts, production fallback, or helper behavior were weakened.

A later Linux CI failure occurred after the native JSON-report test had written its report but encountered strict process-group cleanup. Its broad spawnSync mock had been reset to return undefined, also affecting Linux process-inspection probes. The fixture now calls Node's actual implementation by default and retains the explicit report-unit overrides. All seven report-helper tests, root-test types, and selected static/lint checks passed, followed by scoped-clean P0–P2 review. Strict cleanup and its deadlines are unchanged. The historical group member was not recorded; no specific descendant is blamed. Exact-head CI supplies the remaining Linux proof.

clawsweeper · 2026-09-05T23:07:14Z

🦞👀
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 · 2026-09-05T23:15:20Z

Codex review: needs maintainer review before merge. Reviewed September 5, 2026, 10:06 PM ET / September 6, 2026, 02:06 UTC.

ClawSweeper review

What this changes

Preserves current-session automation delivery intent across routing, previews, and completion reporting, with regression coverage and a native process-probe fixture correction.

Merge readiness

✅ Ready for maintainer review

The fix remains necessary: current main and the latest release retain the affected fallback. No actionable introduced defect remains, and the previous suppression-inventory finding is resolved.

Priority: P2
Reviewed head: 6288cf4e58df835fbffbd7ee9858b737e6d32900

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	A focused owner-level repair with meaningful regression coverage and preserved real Gateway proof; no blocking findings remain.
Proof confidence	🦞 diamond lobster (5/6) ✨ media proof bonus	Sufficient (recording): The supplied real Gateway/dashboard runs exercise the changed resolver and completion owner on production-identical code, retaining reports while distinguishing local Delivered from unresolved explicit Not delivered. Prior sufficient recording evidence is preserved; media could not be re-inspected in this environment.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Verified	Sufficient (recording): The supplied real Gateway/dashboard runs exercise the changed resolver and completion owner on production-identical code, retaining reports while distinguishing local Delivered from unresolved explicit Not delivered. Prior sufficient recording evidence is preserved; media could not be re-inspected in this environment.
Evidence reviewed	9 items	Current main still needs the repair: The fetched main resolver still selects a configured channel when the conversation has no route and checks external obligation using only the resolved channel. Latest release retains the affected behavior: The same fallback and channel-only obligation check remain in v2026.9.2; its annotated tag resolves to the supplied release commit. Canonical routing and completion repair: The introduced resolver guard excludes unrelated configured channels only for current-session jobs without explicit coordinates. Completion retains unresolved explicit-delivery errors after the conversation commit; runtime and preview use the same decision.
Findings	None	None.
Security	None	None.

How this fits together

Scheduled agent turns produce reports for their bound conversations. Cron delivery combines requested destinations with session routing, commits the report, and records whether an external send is still owed.

flowchart TD
  A[Scheduled agent turn] --> B[Prepared delivery intent]
  C[Conversation route] --> D[Resolve destination]
  B --> D
  D --> E[Commit conversation report]
  E --> F{External delivery owed?}
  F -->|No| G[Delivered]
  F -->|Yes| H[Send or record delivery error]

Before merge

None.

Agent review details

Security

None.

PR surface

Source -3, Tests +219, Docs +2. Total +218 across 15 files.

View PR surface stats

Area	Files	Added	Removed	Net
Source	7	40	43	-3
Tests	7	248	29	+219
Docs	1	2	0	+2
Config	0	0	0	0
Generated	0	0	0	0
Other	0	0	0	0
Total	15	290	72	+218

Review metrics

None.

Root-cause cluster

Relationship: fixed_by_candidate
Canonical: #139488
Summary: This PR owns the candidate repair for the dashboard delivery-outcome issue.

Members:

canonical: [Bug]: Dashboard current-session automations falsely fail delivery with an unrelated channel configured #139488 - The linked open issue supplies the exact reproduction and expected behavior.
partial_overlap: fix(cron): current-session automations fail with "Channel is required" on webchat-only gateways #131975 - Merged work established local completion for gateways without configured channels.
adjacent_distinct: fix(cron): keep channel-only continuations in their originating thread #138185 - Repairs origin capture during job creation rather than runtime delivery-obligation classification.

Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.

Technical review

Best possible solution:

Keep one prepared delivery-intent decision shared by preview and completion, preserving conversation reports and explicit destination failures.

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

Yes: current source supports the documented dashboard reproduction with one unrelated configured channel. This review did not execute it; the supplied real Gateway evidence records before/after outcomes.

Is this the best way to solve the issue?

Yes: carrying existing session intent into the canonical resolver addresses the cause without adding configuration, storage formats, or a competing delivery path.

AGENTS.md: found and applied where relevant.

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

Labels

Label justifications:

P2: Repairs misleading automation delivery outcomes while the completed report remains available in the conversation.
rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🦞 diamond lobster and patch quality is 🐚 platinum hermit.
status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (recording): The supplied real Gateway/dashboard runs exercise the changed resolver and completion owner on production-identical code, retaining reports while distinguishing local Delivered from unresolved explicit Not delivered. Prior sufficient recording evidence is preserved; media could not be re-inspected in this environment.
proof: sufficient: Contributor real behavior proof is sufficient. The supplied real Gateway/dashboard runs exercise the changed resolver and completion owner on production-identical code, retaining reports while distinguishing local Delivered from unresolved explicit Not delivered. Prior sufficient recording evidence is preserved; media could not be re-inspected in this environment.
proof: 🎥 video: Contributor real behavior proof includes video or recording evidence. The supplied real Gateway/dashboard runs exercise the changed resolver and completion owner on production-identical code, retaining reports while distinguishing local Delivered from unresolved explicit Not delivered. Prior sufficient recording evidence is preserved; media could not be re-inspected in this environment.

Evidence

What I checked:

Current main still needs the repair: The fetched main resolver still selects a configured channel when the conversation has no route and checks external obligation using only the resolved channel. (src/cron/isolated-agent/delivery-target.ts:196, e915ac8ec5be)
Latest release retains the affected behavior: The same fallback and channel-only obligation check remain in v2026.9.2; its annotated tag resolves to the supplied release commit. (src/cron/isolated-agent/delivery-target.ts:196, 3928bad9badf)
Canonical routing and completion repair: The introduced resolver guard excludes unrelated configured channels only for current-session jobs without explicit coordinates. Completion retains unresolved explicit-delivery errors after the conversation commit; runtime and preview use the same decision. (src/cron/isolated-agent/delivery-target.ts:195, 6288cf4e58df)
Proof remains bound to production code: Comparison with runtime-tested a3bef6a shows only three test files changed afterward; cron production and documentation are identical. (6288cf4e58df)
Preserved real Gateway proof: The captured body at sourceRevision 02c5e2af5b4d4dc8bb6bf697b8d5c05275f09ba26505c4a76fd5633aced3ca8f reports two real isolated Gateway/dashboard flows: local-only delivery becomes Delivered with an unrelated Telegram channel; an unresolved explicit recipient remains Not delivered. Both retain the report and observe zero external sends. Recordings: https://github.com/user-attachments/assets/f47c4282-7c8b-4665-a36a-0af8cbd098b7 and https://github.com/user-attachments/assets/2fb48a1e-3161-4c44-80ec-e51cdbdb58f6. Attachment retrieval failed during this review, so the prior sufficient assessment and captured observations are preserved without claiming fresh media inspection. (a3bef6a3b2cd)
Prior finding resolved: The final introduced diff leaves the suppression inventory unchanged, and inspection finds no obsolete native-drain entry. The previous review's attachment-access limitation is not a new contributor action. (test/scripts/lint-suppressions.test.ts, 6288cf4e58df)

Likely related people:

jalehman: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)
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 (5 earlier review cycles)

reviewed 2026-09-05T23:14:00.277Z sha e8a77b8 :: needs maintainer review before merge. :: none
reviewed 2026-09-06T00:49:01.332Z sha a3bef6a :: needs maintainer review before merge. :: none
reviewed 2026-09-06T01:21:00.790Z sha 691fb48 :: blocked before merge. :: [P2] Remove the obsolete native-drain suppression entry
reviewed 2026-09-06T01:28:58.309Z sha dfd69ae :: needs maintainer review before merge. :: none
reviewed 2026-09-06T01:59:15.281Z sha 6288cf4 :: blocked before merge. :: none

steipete · 2026-09-06T00:45:16Z

@clawsweeper re-review

The final repair at a3bef6a now preserves both sides of current-session delivery intent. An unrelated configured channel does not create an external obligation; explicit recipient/account/thread coordinates retain their delivery error when channel selection fails. Preview and completion share the prepared-plan decision, and the conversation report remains committed in both cases.

All 204 focused tests, canonical core/services type checks, runtime build, and fresh managed P0–P2 review passed. Two refreshed real Gateway/dashboard flows on this exact clean head prove Delivered for local-only intent and Not delivered for an unresolved explicit recipient, with reports retained and zero external sends. Inspected synthetic recordings are in the updated PR body. Production delta is -3 lines. The CI fixture now uses the existing activated outbound adapter; no timeout or assertion was weakened. The rebase also inherits the unrelated upstream CI assertion correction in #139519.

clawsweeper · 2026-09-06T00:45:24Z

🦞🧹
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.

Re-review progress:

State: Complete
Detail: The durable review result and its route handoff completed.
Run: https://github.com/openclaw/clawsweeper/actions/runs/34002341764
Updated: 2026-09-06T00:50:48.451Z

Carry the normalized delivery plan through CLI suppression and Gateway background-completion fixtures. Preserve their assertions and the existing runtime requirement. Record the existing native drain capture suppression introduced by #139483 in the intentional inventory, without changing its receiver semantics.

Upstream #139576 now observes the native drain without an unbound-method suppression. Remove the obsolete inventory entry so the combined CI tree matches current main.

Default the shared spawnSync mock to Node so Linux cleanup probes remain observable. Preserve the explicit report-unit overrides and strict process-tree checks.

steipete · 2026-09-06T02:14:26Z

Merged via squash.

Prepared head SHA: 6288cf4e58df835fbffbd7ee9858b737e6d32900
Landed commit: dca06c94c14d1726207ed934bbeaebf1572ed0c2

* commit '6c55a99226ed0611ca088004c81b00fb296f1f71': (182 commits) test(ui): scope dashboard settings setup to the top frame (openclaw#139618) refactor(skills): share pending proposal creation (openclaw#139617) fix(release): accept frozen targets before worker bundles (openclaw#136699) fix(gateway): preserve percent sequences in media filenames (openclaw#139508) fix: preserve current update availability alongside update history (openclaw#139501) feat(diagnostics): expose garbage collection duration metrics (openclaw#139592) fix(ui): keep Logbook timestamps clear of the activity stripe (openclaw#139539) fix(ui): keep Swarm outcomes visible after completion (openclaw#139490) test: check file accessibility without runtime-specific return values (openclaw#139590) refactor(sdk): keep helper types private (openclaw#139601) fix(cron): preserve current-session delivery intent (openclaw#139491) fix: prevent browser profile permission hangs in Doctor (openclaw#139612) fix(agents): repair storage-failure test fixture after failover owner move (openclaw#139531) fix(cli): keep note text with Windows and Unicode line endings (openclaw#139512) fix(agents): keep isolated completion context on its admitted generation (openclaw#139607) fix: avoid declaration builds during source-server updates (openclaw#139392) fix(models): keep discovered models after catalog refresh failures (openclaw#139357) fix(gateway): record a transcript notice when a run fails before replying (openclaw#139439) refactor(ios): reuse shared integer conversion (openclaw#139581) fix(sessions): prevent database lock failures during reclamation (openclaw#139469) ...

* commit 'refs/openclaw/tasks/pr-135167-main-latest': test(ui): scope dashboard settings setup to the top frame (#139618) refactor(skills): share pending proposal creation (#139617) fix(release): accept frozen targets before worker bundles (#136699) fix(gateway): preserve percent sequences in media filenames (#139508) fix: preserve current update availability alongside update history (#139501) feat(diagnostics): expose garbage collection duration metrics (#139592) fix(ui): keep Logbook timestamps clear of the activity stripe (#139539) fix(ui): keep Swarm outcomes visible after completion (#139490) test: check file accessibility without runtime-specific return values (#139590) refactor(sdk): keep helper types private (#139601) fix(cron): preserve current-session delivery intent (#139491) fix: prevent browser profile permission hangs in Doctor (#139612) fix(agents): repair storage-failure test fixture after failover owner move (#139531) fix(cli): keep note text with Windows and Unicode line endings (#139512) fix(agents): keep isolated completion context on its admitted generation (#139607) fix: avoid declaration builds during source-server updates (#139392) fix(models): keep discovered models after catalog refresh failures (#139357) fix(gateway): record a transcript notice when a run fails before replying (#139439)

* fix(cron): keep dashboard current-session delivery in its conversation * fix(cron): retain unresolved explicit delivery failures * test: complete cron delivery fixtures and CI inventory Carry the normalized delivery plan through CLI suppression and Gateway background-completion fixtures. Preserve their assertions and the existing runtime requirement. Record the existing native drain capture suppression introduced by openclaw#139483 in the intentional inventory, without changing its receiver semantics. * test: drop superseded drain suppression entry Upstream openclaw#139576 now observes the native drain without an unbound-method suppression. Remove the obsolete inventory entry so the combined CI tree matches current main. * test: keep native process probes in report fixture Default the shared spawnSync mock to Node so Linux cleanup probes remain observable. Preserve the explicit report-unit overrides and strict process-tree checks.

openclaw-barnacle Bot added docs Improvements or additions to documentation size: M maintainer Maintainer-authored PR labels Sep 5, 2026

steipete self-assigned this Sep 5, 2026

steipete marked this pull request as ready for review September 5, 2026 23:07

steipete added 2 commits September 5, 2026 17:20

fix(cron): keep dashboard current-session delivery in its conversation

2badb11

fix(cron): retain unresolved explicit delivery failures

a3bef6a

steipete force-pushed the codex/qa-current-cron-origin-20260905 branch from e8a77b8 to a3bef6a Compare September 6, 2026 00:43

steipete changed the title ~~fix(cron): avoid false delivery failures for dashboard automations~~ fix(cron): preserve current-session delivery intent Sep 6, 2026

clawsweeper Bot added the proof: 🎥 video Contributor real behavior proof includes video or recording evidence. label Sep 6, 2026

openclaw-barnacle Bot added gateway Gateway runtime cli CLI command changes labels Sep 6, 2026

test: drop superseded drain suppression entry

dfd69ae

Upstream #139576 now observes the native drain without an unbound-method suppression. Remove the obsolete inventory entry so the combined CI tree matches current main.

clawsweeper Bot removed rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. merge-risk: 🚨 automation 🚨 May affect CI, automerge, proof capture, label sync, or maintainer automation. labels Sep 6, 2026

test: keep native process probes in report fixture

6288cf4

Default the shared spawnSync mock to Node so Linux cleanup probes remain observable. Preserve the explicit report-unit overrides and strict process-tree checks.

clawsweeper Bot added proof: 🎥 video Contributor real behavior proof includes video or recording evidence. and removed proof: 🎥 video Contributor real behavior proof includes video or recording evidence. labels Sep 6, 2026

steipete merged commit dca06c9 into main Sep 6, 2026
183 checks passed

steipete deleted the codex/qa-current-cron-origin-20260905 branch September 6, 2026 02:14

Haderach-Ram mentioned this pull request Sep 6, 2026

Ecosystem Digest — 2026-09-06 Haderach-Ram/openclaw-radar#133

Open

This was referenced Sep 6, 2026

fix(sdk): preserve replay order for late run subscribers #139563

Merged

test(reports): deduplicate native process census setup #139596

Merged

steipete mentioned this pull request Sep 6, 2026

fix(gateway): reconcile pairing lifecycle after token removal #139421

Merged

clawsweeper Bot mentioned this pull request Sep 8, 2026

WebChat sessionTarget:current automation attempts spurious external Google Chat delivery, generating false delivery-failed alerts #141940

Closed

This was referenced Oct 6, 2026

fix(cron): keep channel-only continuations in their originating thread #138185

Open

fix(cron): deliver isolated results to their creating conversation #167363

Merged

Navigation Menu

Repository navigation

fix(cron): preserve current-session delivery intent - #139491

fix(cron): preserve current-session delivery intent#139491
steipete merged 5 commits into
mainfrom
codex/qa-current-cron-origin-20260905

steipete commented Sep 5, 2026 •

edited

Loading

Uh oh!

clawsweeper Bot commented Sep 5, 2026 •

edited

Loading

Uh oh!

clawsweeper Bot commented Sep 5, 2026 •

edited

Loading

Security

PR surface

Review metrics

Root-cause cluster

Technical review

Labels

Evidence

Rating scale

Workflow

History

Uh oh!

steipete commented Sep 6, 2026

Uh oh!

clawsweeper Bot commented Sep 6, 2026 •

edited

Loading

Uh oh!

Uh oh!

steipete commented Sep 6, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

steipete commented Sep 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What Problem This Solves

Why This Change Was Made

User Impact

Evidence

Uh oh!

clawsweeper Bot commented Sep 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

ClawSweeper review complete

Uh oh!

clawsweeper Bot commented Sep 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

ClawSweeper review

What this changes

Merge readiness

Review scores

Verification

How this fits together

Before merge

Security

PR surface

Review metrics

Root-cause cluster

Technical review

Labels

Evidence

Rating scale

Workflow

History

Uh oh!

steipete commented Sep 6, 2026

Uh oh!

clawsweeper Bot commented Sep 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

steipete commented Sep 6, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

steipete commented Sep 5, 2026 •

edited

Loading

clawsweeper Bot commented Sep 5, 2026 •

edited

Loading

clawsweeper Bot commented Sep 5, 2026 •

edited

Loading

clawsweeper Bot commented Sep 6, 2026 •

edited

Loading