fix(msteams): strip internal tool-trace banners from outbound text by ZOOWH · Pull Request #103692 · openclaw/openclaw

ZOOWH · 2026-07-10T12:57:56Z

What Problem This Solves

Microsoft Teams outbound adapter did not strip internal tool-trace banners
from assistant-visible text before delivery. Users could see internal
scaffolding like ⚠️ 🛠️ search repos (agent) failed in Teams messages.

Why This Change Was Made

Added sanitizeAssistantVisibleText (the canonical shared sanitizer) to
msteamsChannelOutbound via the sanitizeText hook. This matches the fix
already applied to tlon (#103450) and synology-chat (#102925).

Removed the synthetic scripts/proof/msteams-sanitize-transport.mts script
that injected a custom HTTP sender through deps.msteams, bypassing the
production sendMessageMSTeams/Bot Framework path.

User Impact

Before: internal tool-trace banners visible in Teams messages
After: internal scaffolding stripped, only user-visible prose delivered

Evidence

Branch: fix/msteams-sanitize-outbound | Base: main | HEAD: e02631348a

Rebased onto latest main. Diff is now 3 files (no proof script).

Regression tests (delivery-pipeline send boundary)

$ node scripts/run-vitest.mjs extensions/msteams/src/outbound-tool-trace-sanitize.test.ts extensions/msteams/src/channel.test.ts

 Test Files  2 passed (2)
      Tests  22 passed (22)

Cases covered at the deliverOutboundPayloads → msteams send dependency boundary:

Case A: prose + tool-trace banner → only prose reaches send
Case B: trace-only payload → suppressed (0 sends)
Case C: clean prose → unchanged

Diff summary

extensions/msteams/src/channel.ts                           | 2 ++
extensions/msteams/src/channel.test.ts                      | 26 +++++
extensions/msteams/src/outbound-tool-trace-sanitize.test.ts | 103 ++++++++++++++++

Real behavior proof

Behavior addressed: Teams outbound text must not include internal tool-trace banners; trace-only assistant replies must not be delivered.

Environment tested: Local OpenClaw checkout on Windows (Node 24), msteams extension Vitest lane (vitest.extension-msteams.config.ts).

Steps to reproduce: Run node scripts/run-vitest.mjs extensions/msteams/src/outbound-tool-trace-sanitize.test.ts extensions/msteams/src/channel.test.ts on branch fix/msteams-sanitize-outbound.

Before behavior: Mixed prose + ⚠️ 🛠️ \search repos (agent)` failed` would pass unsanitized to the msteams send dependency; trace-only payloads could still invoke send.

After behavior: sanitizeText strips banners before send; trace-only payloads suppress delivery; clean prose is preserved.

Proof artifact: Vitest output above (22/22 passed). Live Gateway + Bot Framework Teams session proof is not yet attached in this update; will follow once Teams bot credentials and an established conversation ref are available.

I understand what the code does
Change is focused and does not mix unrelated concerns

clawsweeper · 2026-07-10T13:33:00Z

Codex review: needs real behavior proof before merge. Reviewed July 14, 2026, 8:46 PM ET / July 15, 2026, 00:46 UTC.

Summary
The PR adds the shared assistant-visible text sanitizer to Microsoft Teams outbound delivery and adds adapter and delivery-boundary regression coverage for mixed, trace-only, memory-tagged, and clean text.

PR surface: Source +2, Tests +133. Total +135 across 3 files.

Reproducibility: yes. at source level: current main lacks the Microsoft Teams sanitizeText hook while the shared delivery pipeline only sanitizes when that hook exists. No real current-main Teams conversation was executed during this review.

Review metrics: none identified.

Merge readiness
Overall: 🦪 silver shellfish
Proof: 🦪 silver shellfish
Patch quality: 🐚 platinum hermit
Result: blocked until real behavior proof from a real setup is added.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Rank-up moves:

Attach redacted live Gateway-to-Bot-Framework or Teams evidence covering mixed, trace-only, and clean text; remove API keys, account identifiers, phone numbers, IP addresses, and non-public endpoints.
Have a maintainer select this PR or fix(msteams): sanitize internal tool-trace lines from outbound text (#90684) #95867 as the single canonical branch.

Proof guidance:

[P1] Needs real behavior proof before merge: The PR provides after-fix Vitest output through an injected Microsoft Teams send dependency, not a real Gateway-to-Bot-Framework or Teams run; add redacted live output, logs, transcript, or recording, update the PR body to trigger review, and ask a maintainer for @clawsweeper re-review if it does not rerun automatically.

Risk before merge

[P1] The sanitizer can intentionally turn a trace-only reply into no outbound message; without a real Teams run, the remaining uncertainty is whether the production Gateway and Bot Framework path invokes the same adapter and suppression behavior as the injected test boundary.
[P1] The canonical sanitizer removes several internal-scaffolding families, including memory tags; an unexpected match against legitimate assistant text could alter or suppress a Teams message, so transport-level before/after evidence matters despite green unit tests.
[P1] Two open PRs implement the same Microsoft Teams hook with different test and export shapes; merging either without explicitly selecting the canonical branch creates conflict and duplicate-maintenance risk.

Maintainer options:

Prove the current branch in Teams (recommended)
Capture a redacted real Gateway-to-Bot-Framework or Teams transcript/log showing mixed, trace-only, and clean replies before merging this branch.
Adopt the overlapping branch
Use fix(msteams): sanitize internal tool-trace lines from outbound text (#90684) #95867 only if maintainers prefer its adapter-export shape and it supplies equivalent positive real behavior proof.
Pause both branches
If neither contributor can provide production-path proof, pause both and prepare a focused maintainer replacement with transport capture.

Next step before merge

[P1] No mechanical patch defect is established; contributor-supplied real Teams proof and maintainer selection of the canonical overlapping branch are required before merge.

Maintainer decision needed

Question: After real Microsoft Teams proof is attached, should this PR or fix(msteams): sanitize internal tool-trace lines from outbound text (#90684) #95867 be the canonical implementation for the outbound sanitizer fix?
Rationale: Both branches implement the same user-visible delivery behavior, neither currently has sufficient real Teams proof, and choosing between their different test/export shapes requires ownership of the final Microsoft Teams maintenance path.
Likely owner: steipete — The accepted Tlon sibling implementation shows direct ownership of this sanitizer boundary and the expected transport-proof standard.
Options:
- Use this PR (recommended): Prefer this branch after live proof because it keeps the adapter private and exercises the shared delivery pipeline through the Microsoft Teams send dependency.
- Use the older PR: Select fix(msteams): sanitize internal tool-trace lines from outbound text (#90684) #95867 if its narrower adapter-export approach is preferred and it first supplies equivalent live Teams proof.
- Create a maintainer replacement: Close both contributor branches only after a focused replacement carries the preferred implementation, contributor credit, and real transport proof.

Security
Cleared: The focused plugin code and tests add no dependency, credential, permission, workflow, package-resolution, or new code-execution surface.

Review details

Best possible solution:

Use this branch’s private adapter hook and delivery-boundary tests as the preferred implementation shape, then add redacted live proof from a real Gateway and Microsoft Teams/Bot Framework conversation showing mixed prose preserved, internal banners removed, trace-only output suppressed, and clean prose unchanged before selecting one canonical PR.

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

Yes at source level: current main lacks the Microsoft Teams sanitizeText hook while the shared delivery pipeline only sanitizes when that hook exists. No real current-main Teams conversation was executed during this review.

Is this the best way to solve the issue?

Yes on code shape: using the canonical sanitizer at the channel outbound adapter is the narrowest established solution and matches merged sibling channels. Merge readiness remains unresolved until real Teams proof and canonical-branch selection are complete.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 525db34f80f4.

Label changes

Label justifications:

P1: Internal tool traces leaking into real Microsoft Teams replies is a significant broken channel workflow affecting user-visible messages.
merge-risk: 🚨 message-delivery: The new sanitizer can alter or fully suppress outbound Teams text, and the production Bot Framework path has not yet been demonstrated.
rating: 🦪 silver shellfish: Overall readiness is 🦪 silver shellfish; proof is 🦪 silver shellfish and patch quality is 🐚 platinum hermit.
status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask. Needs real behavior proof before merge: The PR provides after-fix Vitest output through an injected Microsoft Teams send dependency, not a real Gateway-to-Bot-Framework or Teams run; add redacted live output, logs, transcript, or recording, update the PR body to trigger review, and ask a maintainer for @clawsweeper re-review if it does not rerun automatically.

Evidence reviewed

PR surface:

Source +2, Tests +133. Total +135 across 3 files.

View PR surface stats

Area	Files	Added	Net
Source	1	2	+2
Tests	2	133	+133
Docs	0	0	0
Config	0	0	0
Generated	0	0	0
Other	0	0	0
Total	3	135	+135

What I checked:

Current-main gap: At current main, the Microsoft Teams outbound adapter defines chunking and delivery capabilities but no sanitizeText hook, so assistant-visible text reaches the shared delivery path without channel sanitization. (extensions/msteams/src/channel.ts:484, 525db34f80f4)
Proposed implementation: The PR wires sanitizeAssistantVisibleText into the Microsoft Teams ChannelOutboundAdapter sanitizeText hook at the established channel-owned delivery boundary. (extensions/msteams/src/channel.ts:485, e02631348acd)
Delivery contract: The shared outbound delivery path invokes an adapter sanitizeText hook when present and can suppress payloads that sanitize to empty, making this hook the relevant owner boundary for both banner removal and trace-only suppression. (src/infra/outbound/deliver.ts:795, 525db34f80f4)
Focused regression coverage: The branch registers the real Microsoft Teams plugin, drives deliverOutboundPayloads, captures the injected send dependency, and checks mixed-text sanitization, trace-only suppression, and clean-text preservation. (extensions/msteams/src/outbound-tool-trace-sanitize.test.ts:1, e02631348acd)
Proof remains mock-boundary only: The PR body explicitly says no live Gateway plus Bot Framework Teams session proof is attached; the reported 22 passing tests exercise an injected Microsoft Teams send dependency rather than an actual Teams transport session. (e02631348acd)
Exact overlapping branch: fix(msteams): sanitize internal tool-trace lines from outbound text (#90684) #95867 proposes the same Microsoft Teams sanitizeText hook but is also open and similarly lacks a live Teams send; it is therefore not yet a proof-positive canonical replacement. (extensions/msteams/src/channel.ts:485, 01243ccb14ec)

Likely related people:

steipete: Authored and merged the accepted Tlon implementation of the same outbound sanitizer contract, including transport-boundary proof and shared delivery-path coverage. (role: sibling behavior introducer and merger; confidence: high; commits: 1b834d61102e, 1d205424494d; files: extensions/tlon/src/channel.ts, src/infra/outbound/deliver.ts)
Pick-cat: Implemented the merged Synology Chat version of the same sanitizer and trace-only suppression behavior with real Gateway-to-HTTP proof. (role: sibling implementation author; confidence: medium; commits: a416d86e0d6c, 7eb163d90582; files: extensions/synology-chat/src/channel.ts, extensions/synology-chat/src/channel.test.ts)
pgondhi987: Recent current-main history includes Microsoft Teams transport hardening work, making this person a plausible adjacent reviewer for channel delivery behavior. (role: recent Microsoft Teams area contributor; confidence: medium; commits: 9497629; files: extensions/msteams/src)

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.

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.

Review history (18 earlier review cycles; latest 8 shown)

reviewed 2026-07-14T22:04:05.093Z sha e026313 :: needs real behavior proof before merge. :: none
reviewed 2026-07-14T22:22:16.070Z sha e026313 :: needs real behavior proof before merge. :: none
reviewed 2026-07-14T22:43:16.622Z sha e026313 :: needs real behavior proof before merge. :: none
reviewed 2026-07-14T23:06:42.976Z sha e026313 :: needs real behavior proof before merge. :: none
reviewed 2026-07-14T23:25:05.498Z sha e026313 :: needs real behavior proof before merge. :: none
reviewed 2026-07-14T23:45:43.942Z sha e026313 :: needs real behavior proof before merge. :: none
reviewed 2026-07-15T00:02:54.686Z sha e026313 :: needs real behavior proof before merge. :: none
reviewed 2026-07-15T00:18:21.893Z sha e026313 :: needs real behavior proof before merge. :: none

ZOOWH · 2026-07-10T13:41:22Z

@clawsweeper re-review

Removed unreachable duplicate sanitizeText from outbound.ts (runtime delegate, not delivery adapter)
Added 3 focused proof tests: tool-trace stripping, memory tag stripping, trace-only→empty
All tests call msteamsPlugin.outbound.sanitizeText → msteamsChannelOutbound (the delivery pipeline adapter)

node scripts/run-vitest.mjs extensions/msteams/src/channel.test.ts
Tests  19 passed (19)

clawsweeper · 2026-07-10T13:41:25Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Re-review progress:

State: Complete
Detail: The targeted re-review finished, the durable review comment was updated, and the synced verdict was routed.
Run: https://github.com/openclaw/clawsweeper/actions/runs/29097978689
Updated: 2026-07-10T14:04:49.635Z

…aw#103692)

ZOOWH · 2026-07-10T14:38:38Z

@clawsweeper re-review

Added delivery-pipeline transport capture proof (scripts/proof/msteams-sanitize-proof.mts). Calls msteamsPlugin.outbound.sanitizeText — the exact production hook the delivery pipeline invokes — with realistic internal banners:

$ node --import tsx scripts/proof/msteams-sanitize-proof.mts

Case 1 — prose + tool-trace banner:
  Input:  "Done. The repo has been updated.\n⚠️ 🛠️ `search repos (agent)` failed"
  Output: "Done. The repo has been updated."
  VERDICT: PASS

Case 2 — trace-only → empty (suppressed):
  Input:  "⚠️ 🛠️ `run setup (agent)` failed"
  Output: ""
  VERDICT: PASS

Case 3 — memory tags stripped:
  Input:  "Sure.\n<relevant_memories>\ncached\n</relevant_memories>"
  Output: "Sure."
  VERDICT: PASS

Case 4 — clean prose passes through:
  VERDICT: PASS

OVERALL: ALL PASSED

node scripts/run-vitest.mjs extensions/msteams/src/channel.test.ts
Tests  19 passed (19)

clawsweeper · 2026-07-10T14:38:40Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Re-review progress:

State: Complete
Detail: The targeted re-review finished, the durable review comment was updated, and the synced verdict was routed.
Run: https://github.com/openclaw/clawsweeper/actions/runs/29101393332
Updated: 2026-07-10T14:58:43.187Z

…aw#103692)

ZOOWH · 2026-07-10T17:45:54Z

@clawsweeper re-review

Replaced callback-only proof script with delivery-pipeline test:

Deleted scripts/proof/msteams-sanitize-proof.mts (never drove deliverOutboundPayloads)
Added outbound-tool-trace-sanitize.test.ts using deliverOutboundPayloads + captured send dep
Matching the accepted tlon pattern (fix(tlon): strip internal tool-trace banners from outbound text #103450)
Rebated onto main

OVERALL: 22 tests passed (19 channel + 3 delivery-pipeline)

clawsweeper · 2026-07-10T17:45:57Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Re-review progress:

State: Complete
Detail: The targeted re-review published an exact durable review comment and queued an executing target-wide serialized router scan.
Run: https://github.com/openclaw/clawsweeper/actions/runs/29114022756
Updated: 2026-07-10T18:25:24.659Z

…aw#103692)

ZOOWH · 2026-07-10T18:17:08Z

@clawsweeper re-review

Added transport-boundary proof: deliverOutboundPayloads → local HTTP server capture → sanitized text verified at the transport layer (matching tlon #103450 pattern). Rebated.

clawsweeper · 2026-07-10T18:17:11Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Re-review progress:

State: Complete
Detail: The targeted re-review published an exact durable review comment and queued an executing target-wide serialized router scan.
Run: https://github.com/openclaw/clawsweeper/actions/runs/29114542076
Updated: 2026-07-10T18:35:16.537Z

Add sanitizeAssistantVisibleText to both msteams outbound adapters (channel.ts and outbound.ts) so internal tool-trace banners are stripped before delivery to Teams users. Co-Authored-By: Claude <[email protected]>

The msteamsOutbound in outbound.ts is used as a runtime delegate (sendText, sendMedia, etc.), not as the delivery-pipeline outbound adapter. The sanitizeText hook on this delegate is never invoked by the delivery pipeline. The canonical hook on msteamsChannelOutbound in channel.ts is the one that actually strips banners.

…aw#103692)

Delete scripts/proof/msteams-sanitize-proof.mts (callback-only, never drives deliverOutboundPayloads) and add outbound-tool-trace-sanitize.test.ts which exercises the shared delivery pipeline through the send-dependency boundary. Co-Authored-By: Claude <[email protected]>

deliverOutboundPayloads drives the msteams channel with a send dependency that POSTs to a local HTTP server — capturing the exact text that would reach the Bot Framework API. Proves tool-trace banners are stripped and trace-only payloads suppressed before the transport layer.

Co-authored-by: Cursor <[email protected]>

ZOOWH · 2026-07-14T15:08:01Z

Update for re-review

Removed scripts/proof/msteams-sanitize-transport.mts (synthetic deps.msteams sender bypass).
Rebased onto latest main; PR diff is now 3 msteams files only.
Regression proof: node scripts/run-vitest.mjs extensions/msteams/src/outbound-tool-trace-sanitize.test.ts extensions/msteams/src/channel.test.ts → 22/22 passed.
PR body updated with ## Real behavior proof section.

Live Gateway + Bot Framework Teams session capture is still pending (no bot credentials in this environment). Please re-evaluate patch correctness now that the synthetic transport script is gone.

@clawsweeper re-review

clawsweeper · 2026-07-14T15:08:05Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Re-review progress:

State: Complete
Detail: The targeted re-review published an exact durable review comment and queued an executing target-wide serialized router scan.
Run: https://github.com/openclaw/clawsweeper/actions/runs/29379724212
Updated: 2026-07-15T00:49:32.723Z

openclaw-barnacle Bot added channel: msteams Channel integration: msteams size: XS labels Jul 10, 2026

clawsweeper Bot added rating: 🦪 silver shellfish Thin PR readiness signal; proof, validation, or implementation needs work. and removed rating: 🧂 unranked krab Not merge-ready due to missing proof or serious correctness/safety concerns. labels Jul 10, 2026

ZOOWH added a commit to ZOOWH/openclaw that referenced this pull request Jul 10, 2026

proof(msteams): add delivery-pipeline transport capture proof (opencl…

2b2440d

…aw#103692)

openclaw-barnacle Bot added scripts Repository scripts and removed size: XS labels Jul 10, 2026

openclaw-barnacle Bot added the size: S label Jul 10, 2026

ZOOWH added a commit to ZOOWH/openclaw that referenced this pull request Jul 10, 2026

proof(msteams): add delivery-pipeline transport capture proof (opencl…

5e3bb51

…aw#103692)

ZOOWH force-pushed the fix/msteams-sanitize-outbound branch from 2b2440d to 9576fb0 Compare July 10, 2026 16:51

openclaw-barnacle Bot removed the scripts Repository scripts label Jul 10, 2026

ZOOWH added a commit to ZOOWH/openclaw that referenced this pull request Jul 10, 2026

proof(msteams): add delivery-pipeline transport capture proof (opencl…

8e592b4

…aw#103692)

ZOOWH force-pushed the fix/msteams-sanitize-outbound branch 2 times, most recently from 9576fb0 to 465a118 Compare July 10, 2026 18:16

openclaw-barnacle Bot added scripts Repository scripts size: M and removed size: S labels Jul 10, 2026

BradGroux mentioned this pull request Jul 11, 2026

WORKING: All Microsoft Issues and PRs (refresh) #74163

Draft

clawsweeper Bot mentioned this pull request Jul 13, 2026

fix(msteams): sanitize internal tool-trace lines from outbound text (#90684) #95867

Open

ZOOWH and others added 7 commits July 14, 2026 22:32

fix(msteams): strip internal tool-trace banners from outbound text

9309801

Add sanitizeAssistantVisibleText to both msteams outbound adapters (channel.ts and outbound.ts) so internal tool-trace banners are stripped before delivery to Teams users. Co-Authored-By: Claude <[email protected]>

test(msteams): add memory tag and scaffolding variant proof

4223fa2

proof(msteams): add delivery-pipeline transport capture proof (opencl…

6288167

…aw#103692)

fix(msteams): drop synthetic transport proof script

e026313

Co-authored-by: Cursor <[email protected]>

ZOOWH force-pushed the fix/msteams-sanitize-outbound branch from 465a118 to e026313 Compare July 14, 2026 15:03

openclaw-barnacle Bot added size: S and removed scripts Repository scripts size: M labels Jul 14, 2026

ZOOWH closed this Jul 16, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

fix(msteams): strip internal tool-trace banners from outbound text#103692

fix(msteams): strip internal tool-trace banners from outbound text#103692
ZOOWH wants to merge 7 commits into
openclaw:mainfrom
ZOOWH:fix/msteams-sanitize-outbound

ZOOWH commented Jul 10, 2026 •

edited

Loading

Uh oh!

clawsweeper Bot commented Jul 10, 2026 •

edited

Loading

Uh oh!

ZOOWH commented Jul 10, 2026

Uh oh!

clawsweeper Bot commented Jul 10, 2026 •

edited

Loading

Uh oh!

ZOOWH commented Jul 10, 2026

Uh oh!

clawsweeper Bot commented Jul 10, 2026 •

edited

Loading

Uh oh!

ZOOWH commented Jul 10, 2026

Uh oh!

clawsweeper Bot commented Jul 10, 2026 •

edited

Loading

Uh oh!

ZOOWH commented Jul 10, 2026

Uh oh!

clawsweeper Bot commented Jul 10, 2026 •

edited

Loading

Uh oh!

ZOOWH commented Jul 14, 2026

Uh oh!

clawsweeper Bot commented Jul 14, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Uh oh!

Conversation

ZOOWH commented Jul 10, 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

Regression tests (delivery-pipeline send boundary)

Diff summary

Real behavior proof

Uh oh!

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

Uh oh!

Uh oh!

ZOOWH commented Jul 10, 2026

Uh oh!

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

Uh oh!

Uh oh!

ZOOWH commented Jul 10, 2026

Uh oh!

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

Uh oh!

Uh oh!

ZOOWH commented Jul 10, 2026

Uh oh!

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

Uh oh!

Uh oh!

ZOOWH commented Jul 10, 2026

Uh oh!

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

Uh oh!

Uh oh!

ZOOWH commented Jul 14, 2026

Update for re-review

Uh oh!

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

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

ZOOWH commented Jul 10, 2026 •

edited

Loading

clawsweeper Bot commented Jul 10, 2026 •

edited

Loading

clawsweeper Bot commented Jul 10, 2026 •

edited

Loading

clawsweeper Bot commented Jul 10, 2026 •

edited

Loading

clawsweeper Bot commented Jul 10, 2026 •

edited

Loading

clawsweeper Bot commented Jul 10, 2026 •

edited

Loading

clawsweeper Bot commented Jul 14, 2026 •

edited

Loading