Doctor: expose gateway runtime findings by giodl73-repo · Pull Request #97075 · openclaw/openclaw

giodl73-repo · 2026-06-26T17:52:44Z

Summary

adds opt-in structured core Doctor checks for core/doctor/gateway-health and core/doctor/gateway-daemon
maps gateway reachability and local daemon service state into HealthFinding records
redacts sensitive Gateway URL material before emitting the gateway health finding target
keeps real Gateway service install/start/restart behavior in the existing legacy Doctor run path

Behavior

default doctor --lint does not run these checks because both are defaultEnabled: false
explicit --only core/doctor/gateway-health, --only core/doctor/gateway-daemon, or --all can surface the findings
no config, plugin, or SDK public contract changes

Validation

node scripts/run-vitest.mjs run src/flows/doctor-core-checks.runtime.test.ts src/flows/doctor-core-checks.test.ts src/flows/doctor-health-contributions.test.ts --reporter=verbose (99 passed)
pnpm exec oxfmt --check src/flows/doctor-core-checks.runtime.ts src/flows/doctor-core-checks.runtime.test.ts
pnpm exec oxlint src/flows/doctor-core-checks.runtime.ts src/flows/doctor-core-checks.runtime.test.ts
node scripts/plugin-sdk-surface-report.mjs --check
git diff --check
node scripts/run-tsgo.mjs -p test/tsconfig/tsconfig.test.src.json --incremental --tsBuildInfoFile .artifacts/tsgo-cache/test-src.tsbuildinfo
pnpm tsgo:core

Real behavior proof

Local source CLI, Windows worktree, no local Gateway service running:

node scripts/run-node.mjs doctor --lint --json --only core/doctor/gateway-daemon
- exit code: 1
- result: ok:false, checksRun:1, one core/doctor/gateway-daemon warning: Gateway service is not installed.
node scripts/run-node.mjs doctor --lint --json --only core/doctor/gateway-health
- exit code: 1
- result: ok:false, checksRun:1, one core/doctor/gateway-health warning: Gateway is not reachable: connect ECONNREFUSED 127.0.0.1:18789

Focused regression proof on current head covers a remote Gateway URL containing userinfo and a sensitive query token. The structured finding target is redacted as wss://***:***@gateway.example.test/rpc?token=***&safe=value, and the serialized findings do not contain the original userinfo or token value.

Attempted default node scripts/run-node.mjs doctor --lint --json, but the local source command timed out in this fresh worktree. The new checks are default-disabled and covered by focused lint-flow tests plus explicit --only CLI proof above.

Follow-up Fix

Head 981ba1906fa4ae27d9e20c3c99646fd9ebbf02b2 also points remote Gateway health findings at gateway.remote.url instead of the nonexistent gateway.url, covering both prepare-failure and unreachable findings.

giodl73-repo · 2026-06-26T17:53:32Z

@clawsweeper please review current head 1507359 for the opt-in gateway health/daemon structured findings slice. Focus areas: default-disabled lint behavior, read-only runtime probing, no service mutation in structured checks, and no public SDK/plugin/config surface change. Validation/proof is in the PR body.

clawsweeper · 2026-06-26T17:53:45Z

🦞👀
ClawSweeper assist is taking a look at your question.

I queued a lightweight read-only assist pass. It will post a separate answer comment and will not edit the durable ClawSweeper review comment or trigger close, merge, repair, label, or branch changes.

Request: please review current head 1507359 for the opt-in gateway health/daemon structured findings slice. Focus areas: default-disabled lint behavior, read-only runtime probing, no service mutation in structured checks, and no public SDK/plugin/config surface change. Validation/proof is in the PR body.

clawsweeper · 2026-06-26T17:54:05Z

Codex review: needs maintainer review before merge. Reviewed June 27, 2026, 8:16 PM ET / 00:16 UTC.

Summary
Adds two opt-in structured Doctor lint checks for Gateway reachability and local daemon state, maps legacy Gateway Doctor contributions to those check IDs, and adds focused tests.

PR surface: Source +197, Tests +195. Total +392 across 5 files.

Reproducibility: not applicable. This PR adds opt-in diagnostic capability rather than fixing a reproduced bug. The changed behavior is covered by PR-body terminal output, focused tests, a human review validation run, and the passing Real behavior proof check.

Review metrics: 1 noteworthy metric.

Structured Doctor Checks: 2 added, 2 default-disabled. Maintainers should notice the new Gateway diagnostics are selectable with --only or --all while preserving default doctor --lint behavior.

Stored data model
Persistent data-model change detected: migration/backfill/repair: src/flows/doctor-core-checks.runtime.test.ts, migration/backfill/repair: src/flows/doctor-core-checks.runtime.ts, migration/backfill/repair: src/flows/doctor-core-checks.test.ts, migration/backfill/repair: src/flows/doctor-core-checks.ts, migration/backfill/repair: src/flows/doctor-health-contributions.ts, unknown-data-model-change: src/flows/doctor-core-checks.runtime.test.ts, and 3 more. Confirm migration or upgrade compatibility proof before merge.

Merge readiness
Overall: 🦞 diamond lobster
Proof: 🦞 diamond lobster
Patch quality: 🦞 diamond lobster
Result: ready for maintainer review.

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

Next step before merge

No ClawSweeper repair lane is needed; the remaining action is ordinary maintainer review and required-check merge handling.

Security
Cleared: No concrete security or supply-chain regression was found; the diff does not touch workflows, dependencies, lockfiles, or package scripts, and sensitive Gateway URL targets use the shared redactor with regression coverage.

Review details

Best possible solution:

Land the default-disabled structured Gateway Doctor checks after maintainer review, while keeping service install/start/restart mutation in the legacy Doctor contribution path.

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

Not applicable: this PR adds opt-in diagnostic capability rather than fixing a reproduced bug. The changed behavior is covered by PR-body terminal output, focused tests, a human review validation run, and the passing Real behavior proof check.

Is this the best way to solve the issue?

Yes: this is the best fit for the stated goal because it uses existing Gateway probe/service-state helpers, keeps checks default-disabled and read-only, and leaves service repair policy in the legacy Doctor contribution path.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 7bbd09047bd7.

Label changes

Label justifications:

P3: This is an opt-in Doctor diagnostics addition with limited blast radius and no default config, SDK, plugin, migration, or workflow surface change.
rating: 🦞 diamond lobster: Overall readiness is 🦞 diamond lobster; proof is 🦞 diamond lobster and patch quality is 🦞 diamond lobster.
status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (terminal): The PR body includes after-fix terminal output for both explicit Gateway checks plus redacted remote URL proof, and the Real behavior proof check passed on the current head.
proof: sufficient: Contributor real behavior proof is sufficient. The PR body includes after-fix terminal output for both explicit Gateway checks plus redacted remote URL proof, and the Real behavior proof check passed on the current head.

Evidence reviewed

PR surface:

Source +197, Tests +195. Total +392 across 5 files.

View PR surface stats

Area	Files	Added	Removed	Net
Source	3	198	1	+197
Tests	2	197	2	+195
Docs	0	0	0	0
Config	0	0	0	0
Generated	0	0	0	0
Other	0	0	0	0
Total	5	395	3	+392

What I checked:

Repository policy applied: Root AGENTS.md was read fully and applied; no scoped AGENTS.md exists for src/flows, and src/gateway/AGENTS.md was read before judging imported Gateway helpers. (AGENTS.md:15, 7bbd09047bd7)
PR head adds read-only Gateway collectors: The Gateway health collector builds probe details, calls probeGatewayStatus, treats reachable auth-gated probes as clean, and redacts the emitted target; the daemon collector skips remote mode and reads service state without install/start/restart calls. (src/flows/doctor-core-checks.runtime.ts:70, 1b00f70e3c02)
New checks are opt-in: Both new structured checks are registered with defaultEnabled: false and added to the converted Doctor check list, preserving default doctor --lint selection behavior. (src/flows/doctor-core-checks.ts:763, 1b00f70e3c02)
Legacy contributions stay mapped: The existing Gateway health and daemon Doctor contributions gain healthCheckIds while retaining runGatewayHealthChecks and runGatewayDaemonHealth as their legacy run functions. (src/flows/doctor-health-contributions.ts:1634, 1b00f70e3c02)
Current main selection contract: Current main skips default-disabled checks unless --only selects them or includeAllChecks is true, so default doctor --lint is not expanded by this PR's default-disabled checks. (src/flows/doctor-lint-flow.ts:38, 7bbd09047bd7)
Current main mutation owner: Current main's maybeRepairGatewayDaemon owns install/start/restart prompts and service mutation, which supports keeping the new structured collectors read-only. (src/commands/doctor-gateway-daemon-flow.ts:187, 7bbd09047bd7)

Likely related people:

giodl73-repo: Authored recent merged structured Doctor findings slices in the same core Doctor check/contribution mapping area before this Gateway slice. (role: recent area contributor; confidence: high; commits: 36722014efa3, 1bdde6695030, cb4244fe15e3; files: src/flows/doctor-core-checks.ts, src/flows/doctor-core-checks.runtime.ts, src/flows/doctor-health-contributions.ts)
steipete: Current-main blame for the legacy Gateway Doctor contribution and Gateway service/probe helper APIs used by this PR points to recent adjacent work by Peter Steinberger. (role: recent adjacent contributor; confidence: medium; commits: 56259606d15f; files: src/flows/doctor-health-contributions.ts, src/daemon/service.ts, src/gateway/call.ts)
galiniliev: Submitted a detailed live review of this PR's Gateway/Doctor boundary, alternatives, validation, and no-blocking-findings verdict. (role: reviewer; confidence: medium; commits: 981ba1906fa4; files: src/flows/doctor-core-checks.runtime.ts, src/flows/doctor-core-checks.ts, src/flows/doctor-health-contributions.ts)

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.

clawsweeper · 2026-06-26T17:56:02Z

ClawSweeper assist: This needs a full correctness review to verify the current head 1507359e10 against those focus areas. From the supplied PR context, the slice appears scoped to 5 Doctor files and the PR body claims the intended safeguards, but I cannot fully validate implementation correctness from the truncated patches alone.

Evidence:

Head SHA is 1507359e10258ada32a36afdcda711e9e2797c40 on Doctor: expose gateway runtime findings #97075.
New structured check IDs are core/doctor/gateway-health and core/doctor/gateway-daemon.
Tests assert both checks are opt-in with defaultEnabled: false.
Runtime code imports probe/read APIs: probeGatewayStatus, buildGatewayProbeConnectionDetails, readGatewayServiceState, and resolveGatewayService.
PR validation includes focused Vitest files, tsgo, oxfmt, oxlint, plugin-sdk-surface-report.mjs --check, and git diff --check.
PR body says no config, plugin, or SDK public contract changes and includes explicit --only CLI proof for both gateway checks.

Suggested next action: Use @clawsweeper review on #97075 for the full current-head correctness review.

Source: #97075 (comment)
Assist reasoning: low.

giodl73-repo · 2026-06-26T18:19:48Z

@clawsweeper re-review

Current head 6cbbcf9b0c42795c3540f918f7bc516f45dadbb4 addresses the P1 raw Gateway URL finding by redacting the core/doctor/gateway-health finding target with the shared sensitive URL redactor. Added focused regression coverage for a remote Gateway URL containing userinfo plus a sensitive query token, and refreshed PR body validation/proof.

Validation:

node scripts/run-vitest.mjs run src/flows/doctor-core-checks.runtime.test.ts src/flows/doctor-core-checks.test.ts src/flows/doctor-health-contributions.test.ts --reporter=verbose (99 passed)
pnpm exec oxfmt --check src/flows/doctor-core-checks.runtime.ts src/flows/doctor-core-checks.runtime.test.ts
pnpm exec oxlint src/flows/doctor-core-checks.runtime.ts src/flows/doctor-core-checks.runtime.test.ts
node scripts/plugin-sdk-surface-report.mjs --check
git diff --check
node scripts/run-tsgo.mjs -p test/tsconfig/tsconfig.test.src.json --incremental --tsBuildInfoFile .artifacts/tsgo-cache/test-src.tsbuildinfo
pnpm tsgo:core

clawsweeper · 2026-06-26T18:19:51Z

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

giodl73-repo · 2026-06-26T20:49:00Z

@clawsweeper re-review

Current head 981ba1906fa4ae27d9e20c3c99646fd9ebbf02b2 addresses the remaining diagnostic-path finding: remote Gateway health findings now point at gateway.remote.url for both prepare-failure and unreachable paths, with the focused assertion updated.

Validation:

node scripts/run-vitest.mjs run src/flows/doctor-core-checks.runtime.test.ts src/flows/doctor-core-checks.test.ts src/flows/doctor-health-contributions.test.ts --reporter=verbose (99 passed)
pnpm exec oxfmt --check src/flows/doctor-core-checks.runtime.ts src/flows/doctor-core-checks.runtime.test.ts
pnpm exec oxlint src/flows/doctor-core-checks.runtime.ts src/flows/doctor-core-checks.runtime.test.ts
node scripts/plugin-sdk-surface-report.mjs --check
git diff --check

clawsweeper · 2026-06-26T20:49:02Z

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

galiniliev

This PR adds opt-in structured Doctor findings for Gateway reachability and local daemon state, while leaving the existing Doctor contribution path in charge of service install/start/restart behavior. That matters because these checks become selectable by doctor --lint --only and --all, so the structured path must stay read-only and avoid leaking Gateway URL material.

Findings: none blocking.

LOC: +395/-3 (5 files)

By: Gio Della-Libera (@giodl73-repo, acct 2025-09-30) | OpenClaw: 187 PRs, 14 issues, 138 commits/12mo | GitHub: 6437 commits, 221 PRs, 29 issues, 17 reviews/12mo

Behavior reviewed: adds core/doctor/gateway-health and core/doctor/gateway-daemon as defaultEnabled: false structured checks, maps the existing doctor:gateway-health and doctor:gateway-daemon contributions to those IDs, and keeps normal doctor execution on the legacy contribution functions.

Best-fix verdict: best. The implementation puts the structured lint-only behavior in src/flows/doctor-core-checks.runtime.ts and wires it through src/flows/doctor-core-checks.ts/src/flows/doctor-health-contributions.ts, which matches the existing split between contribution-owned Doctor behavior and non-mutating lint checks. It does not duplicate service mutation logic or move Gateway repair policy into lint.

Alternatives considered:

Reuse runGatewayHealthChecks directly from the structured check: rejected because that path updates Doctor flow state, emits terminal notes, and can trigger legacy follow-on behavior rather than returning pure HealthFinding records.
Add repair hooks to the new daemon check: rejected because src/commands/doctor-gateway-daemon-flow.ts still owns install/start/restart prompts and platform repair policy.
Make the checks default-enabled: rejected because Gateway probing and service inspection would change default doctor --lint cost/side effects; defaultEnabled: false preserves the current default selection contract in src/flows/doctor-lint-flow.ts.

Code read: src/flows/doctor-core-checks.runtime.ts, src/flows/doctor-core-checks.ts, src/flows/doctor-health-contributions.ts, src/flows/doctor-lint-flow.ts, src/commands/doctor-lint.ts, src/commands/doctor-gateway-health.ts, src/commands/doctor-gateway-daemon-flow.ts, src/gateway/call.ts, src/gateway/connection-details.ts, src/cli/daemon-cli/probe.ts, src/gateway/probe.ts, src/commands/gateway-health-auth-diagnostic.ts, src/daemon/service.ts, src/daemon/service-runtime.ts, and adjacent tests.

Evidence map:

Changed surface: structured Doctor health checks and contribution mapping.
Runtime entry point: runDoctorLintCli resolves contribution health checks, then runDoctorLintChecks skips default-disabled checks unless --only or --all selects them.
Owner boundary: Gateway service mutation remains in maybeRepairGatewayDaemon; the new daemon structured check only calls readGatewayServiceState.
Caller/callee: createGatewayHealthCheck and createGatewayDaemonCheck call the runtime collectors; the collectors call buildGatewayProbeConnectionDetails/probeGatewayStatus and resolveGatewayService/readGatewayServiceState respectively.
Sibling invariant: existing default-disabled checks such as session locks/state integrity use the same selection model.
Security-sensitive path: unreachable Gateway findings redact the target with redactSensitiveUrlLikeString, and the connection-detail builder already redacts display text for unsafe URL errors.

Validation run on PR head 981ba1906fa4ae27d9e20c3c99646fd9ebbf02b2 in /tmp/openclaw-pr-97075:

node scripts/run-vitest.mjs run src/flows/doctor-core-checks.runtime.test.ts src/flows/doctor-core-checks.test.ts src/flows/doctor-health-contributions.test.ts --reporter=verbose -> 99 passed.
/home/galini/GitHub/openclaw4/node_modules/.bin/oxfmt --check src/flows/doctor-core-checks.runtime.ts src/flows/doctor-core-checks.runtime.test.ts -> passed.
/home/galini/GitHub/openclaw4/node_modules/.bin/oxlint src/flows/doctor-core-checks.runtime.ts src/flows/doctor-core-checks.runtime.test.ts -> passed.
git diff --check origin/main...HEAD -> passed.

CI spot check: live PR metadata shows Real behavior proof, runner-admission, actionlint, and Socket PR alerts succeeded at the current head. The PR is still draft, so this is a correctness review, not a merge-ready signal.

Remaining uncertainty: I did not run a real local Gateway service or remote Gateway instance from this environment. The PR body and CI real-behavior proof cover explicit CLI --only checks; my local proof covers the structured selection, redaction, daemon skip, and read-only service-state logic.

giodl73-repo · 2026-06-27T23:03:03Z

@clawsweeper re-review

Current head e381ff4d11bef1c7b08b352ac6d8c0084d98cf73 rebases the gateway runtime structured findings slice onto current main after #96171 merged. The rebase was clean and the PR diff is unchanged at 5 files, +395/-3.

Prior addressed findings remain in place:

Gateway health finding targets use the shared sensitive URL redactor, including userinfo/token query coverage.
Remote Gateway health findings point at gateway.remote.url for prepare-failure and unreachable paths.
The checks remain opt-in via defaultEnabled: false; default doctor --lint behavior is unchanged.
Structured Gateway checks remain read-only; service install/start/restart behavior stays in the legacy Doctor contribution path.

Validation before rebase remains applicable to the unchanged diff:

focused gateway runtime/core/contribution Vitest (99 passed)
changed-file oxfmt --check
changed-file oxlint
core tsgo
test-source tsgo
node scripts/plugin-sdk-surface-report.mjs --check
git diff --check

Post-rebase hosted checks are green/skipped, including Real behavior proof.

clawsweeper · 2026-06-27T23:03:06Z

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

giodl73-repo · 2026-06-28T00:18:07Z

Merged via squash.

Prepared head SHA: 1b00f70e3c025fbb8db301c9921b447574ecd1ba
Landed commit: 3630d502eb9be9e1be7c685efbb6cd80b445fdcc

* feat(doctor): expose gateway runtime findings * fix(doctor): redact gateway health targets

openclaw-barnacle Bot added size: M maintainer Maintainer-authored PR labels Jun 26, 2026

giodl73-repo force-pushed the doctor-gateway-runtime-structured-findings branch from 6cbbcf9 to 981ba19 Compare June 26, 2026 20:48

galiniliev assigned steipete Jun 26, 2026

galiniliev reviewed Jun 26, 2026

View reviewed changes

giodl73-repo force-pushed the doctor-gateway-runtime-structured-findings branch from 981ba19 to e381ff4 Compare June 27, 2026 22:26

clawsweeper Bot added rating: 🦞 diamond lobster Very strong PR readiness with only minor maintainer review expected. and removed rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. labels Jun 27, 2026

giodl73-repo marked this pull request as ready for review June 27, 2026 23:53

giodl73-repo added 2 commits June 27, 2026 17:05

feat(doctor): expose gateway runtime findings

777c8bf

fix(doctor): redact gateway health targets

1b00f70

giodl73-repo force-pushed the doctor-gateway-runtime-structured-findings branch from e381ff4 to 1b00f70 Compare June 28, 2026 00:06

giodl73-repo merged commit 3630d50 into openclaw:main Jun 28, 2026
95 checks passed

giodl73-repo deleted the doctor-gateway-runtime-structured-findings branch June 28, 2026 00:18

github-actions Bot mentioned this pull request Jun 28, 2026

🦞 OpenClaw 生态日报 2026-06-28 zx0828/big_model_radar#189

Open

giodl73-repo mentioned this pull request Jun 28, 2026

Doctor: expose auth profile findings #97125

Merged

Haderach-Ram mentioned this pull request Jun 28, 2026

Ecosystem Digest — 2026-06-28 Haderach-Ram/openclaw-radar#64

Open

github-actions Bot mentioned this pull request Jun 28, 2026

📡 Upstream Digest — 2026-06-28 02:41 UTC curtismercier/openclaw-mods#1163

Open

github-actions Bot pushed a commit to Desicool/openclaw that referenced this pull request Jun 28, 2026

Doctor: expose gateway runtime findings (openclaw#97075)

a2c3590

* feat(doctor): expose gateway runtime findings * fix(doctor): redact gateway health targets

clawsweeper Bot mentioned this pull request Jun 28, 2026

fix(config): prune orphan model refs when provider is missing #97375

Open

QiuYuang pushed a commit to QiuYuang/openclaw that referenced this pull request Jul 1, 2026

Doctor: expose gateway runtime findings (openclaw#97075)

96c2956

* feat(doctor): expose gateway runtime findings * fix(doctor): redact gateway health targets

chenyangjun-xy pushed a commit to chenyangjun-xy/openclaw that referenced this pull request Jul 1, 2026

Doctor: expose gateway runtime findings (openclaw#97075)

0b01fb9

* feat(doctor): expose gateway runtime findings * fix(doctor): redact gateway health targets

chenyangjun-xy pushed a commit to chenyangjun-xy/openclaw that referenced this pull request Jul 3, 2026

Doctor: expose gateway runtime findings (openclaw#97075)

c9c2b58

* feat(doctor): expose gateway runtime findings * fix(doctor): redact gateway health targets

Uh oh!

Uh oh!

Conversation

giodl73-repo commented Jun 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Behavior

Validation

Real behavior proof

Follow-up Fix

Uh oh!

giodl73-repo commented Jun 26, 2026

Uh oh!

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

Uh oh!

Uh oh!

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

Uh oh!

Uh oh!

clawsweeper Bot commented Jun 26, 2026

Uh oh!

giodl73-repo commented Jun 26, 2026

Uh oh!

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

Uh oh!

Uh oh!

giodl73-repo commented Jun 26, 2026

Uh oh!

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

Uh oh!

Uh oh!

galiniliev left a comment

Choose a reason for hiding this comment

Uh oh!

giodl73-repo commented Jun 27, 2026

Uh oh!

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

Uh oh!

Uh oh!

Uh oh!

giodl73-repo commented Jun 28, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

giodl73-repo commented Jun 26, 2026 •

edited

Loading

clawsweeper Bot commented Jun 26, 2026 •

edited

Loading

clawsweeper Bot commented Jun 26, 2026 •

edited

Loading

clawsweeper Bot commented Jun 26, 2026 •

edited

Loading

clawsweeper Bot commented Jun 26, 2026 •

edited

Loading

clawsweeper Bot commented Jun 27, 2026 •

edited

Loading