feat(plugins): add embedding provider contract by dutifulbob · Pull Request #84947 · openclaw/openclaw

dutifulbob · 2026-05-21T12:28:02Z

Summary

Embeddings are not only a memory feature.
This adds the first plugin-layer contract for general embedding providers, without moving memory or adding a real provider yet.
It gives future provider plugins a contracts.embeddingProviders manifest key and api.registerEmbeddingProvider(...) registration API so later PRs can bridge memory and add OpenAI-compatible embeddings cleanly.

What Changed

This is the contract plumbing PR only.
It deliberately avoids adding production provider behavior so the new public surface can be reviewed on its own.

Added a generic embedding provider registry and runtime export surface.
Added contracts.embeddingProviders manifest parsing and merge support.
Added api.registerEmbeddingProvider(...) to the plugin API and test API.
Added registry ownership and duplicate-id diagnostics.
Added plugin record, status, loader snapshot, capability runtime, and bundled capability metadata plumbing.
Added the public SDK subpath openclaw/plugin-sdk/embedding-providers for safe read helpers and types; registration stays behind api.registerEmbeddingProvider(...) so manifest ownership is enforced.
Added focused registry, runtime-resolution, plugin-contract, public-SDK-bypass, and loader rollback tests.
Updated plugin manifest, SDK overview, SDK subpath, provider plugin, architecture, and capability docs.

Testing

Latest local checks at fad85638a03657f8354bb19768c109d5270a8354:

node scripts/run-vitest.mjs src/plugins/embedding-provider-runtime.test.ts src/plugins/loader.test.ts src/plugins/loader.runtime-registry.test.ts src/plugins/embedding-providers.test.ts src/plugins/contracts/embedding-provider.contract.test.ts src/plugins/loader-records.test.ts -> passed, 6 files / 172 tests.
node scripts/run-tsgo.mjs -p tsconfig.core.json --incremental --tsBuildInfoFile .artifacts/tsgo-cache/core-embedding-providers.tsbuildinfo -> passed.
node scripts/run-tsgo.mjs -p test/tsconfig/tsconfig.core.test.json --incremental --tsBuildInfoFile .artifacts/tsgo-cache/core-test-embedding-providers.tsbuildinfo -> passed.
node scripts/run-oxlint.mjs src/plugins/embedding-provider-runtime.ts src/plugins/embedding-provider-runtime.test.ts src/plugins/registry.ts src/plugins/loader.test.ts src/plugin-sdk/embedding-providers.ts src/plugins/contracts/embedding-provider.contract.test.ts -> passed.
pnpm plugin-sdk:api:check -> passed.
pnpm plugin-sdk:check-exports -> passed.
node scripts/check-plugin-sdk-subpath-exports.mjs -> passed.
node scripts/check-docs-mdx.mjs docs/plugins/sdk-subpaths.md -> passed.
git diff --check -> passed.

Earlier docs checks on this branch:

node scripts/format-docs.mjs --check -> passed.
node scripts/check-docs-mdx.mjs docs/plugins/manifest.md docs/plugins/sdk-overview.md docs/plugins/sdk-subpaths.md docs/plugins/sdk-provider-plugins.md docs/plugins/architecture.md docs/plugins/adding-capabilities.md -> passed.
node scripts/check-changed.mjs --help accidentally ran the fail-safe changed check before later follow-up commits; it completed all selected lanes successfully, including all-project typecheck, lint shards, and runtime import cycle check.

Risks

The main risk is public SDK surface shape.
This PR adds the registry and API but does not yet migrate memory or any real provider, so runtime behavior should remain unchanged unless a plugin opts into the new API.

Follow-ups

Add a memory bridge from general embeddingProviders to memory embedding providers.
Implement openai-compatible as a general embedding provider after the bridge exists.

Real behavior proof

Behavior addressed: Adds a general plugin contract and registration API for embedding providers; no production provider behavior is enabled in this PR.

Real environment tested: Local OpenClaw source checkout using a temporary real plugin load path and temporary openclaw.json config.

Exact steps or command run after this patch: Ran a node --import tsx proof script that created a temporary plugin with openclaw.plugin.json declaring contracts.embeddingProviders: ["proof-embedding"], loaded that plugin through OpenClaw's plugin registry/status code, and runtime-registered api.registerEmbeddingProvider(...).

Evidence after fix: Terminal output from the proof run:

{
  "configPath": "<temp>/state/openclaw.json",
  "pluginLoadPath": "<temp>/proof-embedding",
  "snapshot": {
    "id": "proof-embedding",
    "status": "loaded",
    "embeddingProviderIds": [
      "proof-embedding"
    ]
  },
  "runtime": {
    "id": "proof-embedding",
    "status": "loaded",
    "embeddingProviderIds": [
      "proof-embedding"
    ]
  },
  "inspect": {
    "shape": "plain-capability",
    "capabilities": [
      {
        "kind": "embedding",
        "ids": [
          "proof-embedding"
        ]
      }
    ]
  },
  "registered": {
    "id": "proof-embedding",
    "ownerPluginId": "proof-embedding",
    "defaultModel": "proof-embedding-v1",
    "transport": "local"
  }
}

Observed result after fix: OpenClaw discovers the manifest-declared embeddingProviders contract, reports the plugin as a plain embedding capability, runtime-registers the adapter, and preserves the owner plugin id on the registered adapter. Focused follow-up regression tests at fad85638a03657f8354bb19768c109d5270a8354 also prove cold manifest resolution through the SDK-backed runtime helper, scoped non-activating loads with active global providers, and that the public SDK subpath cannot bypass manifest-owned registration.

What was not tested: Full GitHub CI is running now that the PR is ready for review.

clawsweeper · 2026-05-21T12:29:32Z

Codex review: needs real behavior proof before merge.

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 adds a generic embeddingProviders manifest contract, api.registerEmbeddingProvider(...), runtime registry and SDK read helpers, docs, package export wiring, and focused tests.

Reproducibility: not applicable. this is a feature PR adding a new plugin contract, not a bug report. Source inspection confirms current main only has memory-scoped embedding provider APIs and manifest contracts.

PR rating
Overall: 🦪 silver shellfish
Proof: 🦪 silver shellfish
Patch quality: 🐚 platinum hermit
Summary: Patch quality looks normal with focused tests and no blocking code findings, but insufficient exact-head real behavior proof keeps it below merge-ready quality.

Rank-up moves:

Add redacted current-head terminal or log proof showing a temporary plugin with contracts.embeddingProviders loading, registering, and appearing in status/inspect output.
Get maintainer-visible approval for the public manifest/API/SDK shape and credential-bearing adapter boundary.

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
Needs stronger real behavior proof before merge: The PR has useful earlier terminal proof, but current-head proof is tests/checks only; add redacted exact-head terminal or log output showing temporary plugin load and api.registerEmbeddingProvider(...), then update the PR body for re-review.

Risk before merge

This creates a new public manifest key, plugin API method, SDK subpath, and adapter shape; changing them after release would break third-party plugins that adopt the contract.
The adapter type includes future remote credential, header, auth-provider, and local path fields, so maintainers should explicitly accept the trust boundary before shipping it as public SDK.
The current-head proof for 41ebd66ab411b438913201c524d8e9921e62ea5a is test/check output only; the non-test temporary-plugin terminal proof in the PR body is useful but not tied to the exact current head.
The memory bridge and concrete OpenAI-compatible provider are separate stacked open PRs at feat(memory-core): consume generic embedding providers #84991 and feat(plugins): add OpenAI-compatible embedding provider #84998, so maintainers need to decide whether the base contract should land alone.

Maintainer options:

Refresh proof and approve the contract (recommended)
Require redacted current-head terminal or log proof for the temporary plugin load/registration path, then have maintainers explicitly accept the public manifest/API/SDK shape before merge.
Accept the SDK commitment now
Maintainers can intentionally merge if they are comfortable stabilizing contracts.embeddingProviders, api.registerEmbeddingProvider(...), and the read-only SDK subpath with the current proof gap noted.
Hold for the embedding stack
Pause this PR if maintainers want to review the base contract together with the memory bridge, deprecation path, and OpenAI-compatible provider follow-ups.

Next step before merge
Manual review is needed for public SDK contract approval, the credential/security boundary, and contributor-supplied current-head proof; there is no narrow automated repair to queue.

Security
Cleared: No concrete executable supply-chain regression was found in the live diff; the remaining security concern is the intentional public credential-bearing adapter boundary.

Review details

Best possible solution:

Land this base contract only after maintainers approve the public API/security boundary and the contributor supplies exact-head real behavior proof; then review the memory bridge and concrete provider PRs separately.

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

Not applicable: this is a feature PR adding a new plugin contract, not a bug report. Source inspection confirms current main only has memory-scoped embedding provider APIs and manifest contracts.

Is this the best way to solve the issue?

Unclear until maintainers approve the public API direction. The implementation matches existing manifest-owned registry patterns, but the stable SDK shape and credential boundary are product/security decisions rather than mechanical correctness questions.

Label changes:

add status: 🚀 automerge armed: This PR is in ClawSweeper's automerge lane. Needs stronger real behavior proof before merge: The PR has useful earlier terminal proof, but current-head proof is tests/checks only; add redacted exact-head terminal or log output showing temporary plugin load and api.registerEmbeddingProvider(...), then update the PR body for re-review.
remove status: 📣 needs proof: Current PR status label is status: 🚀 automerge armed.

Label justifications:

P2: This is a normal-priority plugin SDK feature with limited immediate runtime blast radius but meaningful public API review cost.
merge-risk: 🚨 compatibility: The PR adds a new public manifest key, plugin API method, and SDK subpath that third-party plugins could depend on after release.
merge-risk: 🚨 security-boundary: The public adapter contract includes credential, header, auth-provider, and local-path fields that need explicit trust-boundary acceptance before becoming stable.
rating: 🦪 silver shellfish: Current PR rating is 🦪 silver shellfish because proof is 🦪 silver shellfish, patch quality is 🐚 platinum hermit, and Patch quality looks normal with focused tests and no blocking code findings, but insufficient exact-head real behavior proof keeps it below merge-ready quality.
status: 🚀 automerge armed: This PR is in ClawSweeper's automerge lane. Needs stronger real behavior proof before merge: The PR has useful earlier terminal proof, but current-head proof is tests/checks only; add redacted exact-head terminal or log output showing temporary plugin load and api.registerEmbeddingProvider(...), then update the PR body for re-review.

What I checked:

Current main is memory-scoped: Current main documents only api.registerMemoryEmbeddingProvider(adapter) for memory embedding adapters, so the PR is adding a new generic provider surface rather than fixing an existing generic one. Public docs: docs/plugins/sdk-overview.md. (docs/plugins/sdk-overview.md:372, eb7f3b7b50c5)
Current manifest contract is memory-only: Current main's manifest contract reference lists memoryEmbeddingProviders but no generic embeddingProviders key. Public docs: docs/plugins/manifest.md. (docs/plugins/manifest.md:619, eb7f3b7b50c5)
PR introduces credential-bearing public adapter shape: The PR head defines EmbeddingProviderCreateOptions with remote.apiKey, remote.headers, local model paths, dimensions, and task type, so the public contract has a security and compatibility boundary even before a real provider lands. (src/plugins/embedding-providers.ts:38, 41ebd66ab411)
PR enforces manifest-owned registration: The PR head rejects empty ids, requires contracts.embeddingProviders, rejects duplicate provider ids, records owner metadata, and updates the plugin record with the registered id. (src/plugins/registry.ts:1118, 41ebd66ab411)
Contract tests cover SDK bypass and duplicate ownership: The new contract test asserts the public SDK subpath does not export registry mutators, rejects plugins without the manifest contract, allows declared owners, and rejects duplicate ids. (src/plugins/contracts/embedding-provider.contract.test.ts:10, 41ebd66ab411)
Live diff has no lockfile or dependency package changes: The live PR diff includes package.json only for an SDK export entry and does not include pnpm-lock.yaml or extensions/web-readability/package.json, so the Socket dependency alerts appear stale relative to this exact diff. (package.json:408, 41ebd66ab411)

Likely related people:

Peter Steinberger: Recent main history shows plugin SDK changes by Peter, and the grafted baseline commit that currently owns much of the plugin docs/runtime surface was committed by Peter. (role: recent SDK contributor and baseline committer; confidence: medium; commits: cabb55380f84, ee915cfede0b; files: src/plugin-sdk/entrypoints.ts, docs/plugins/sdk-subpaths.md, src/plugins/memory-embedding-providers.ts)
Dallin Romney: Recent main commit dca9cecaeed9577375988e4ccb3d94023d1c7e57 changed plugin loader/runtime load context code adjacent to the PR's registry and loader changes. (role: recent plugin loader adjacent contributor; confidence: medium; commits: dca9cecaeed9; files: src/plugins/loader.ts, src/plugins/runtime/load-context.ts, src/plugins/providers.runtime.ts)
OpenClaw Contributor: The local shallow/grafted history blames the current memory embedding provider registry and capability runtime files to the grafted baseline commit, so individual original authorship is obscured. (role: introduced current memory embedding and capability runtime baseline in this checkout; confidence: low; commits: ee915cfede0b; files: src/plugins/memory-embedding-providers.ts, src/plugins/capability-provider-runtime.ts, docs/plugins/manifest.md)

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

clawsweeper · 2026-05-21T12:48:33Z

ClawSweeper PR egg

🎁 Pass real behavior proof to wake the egg and unlock a hatchable treat.

Where did the egg go?

The egg game starts only after the PR passes the real-behavior proof check.
Before that, no creature or rarity is rolled. The treat waits for real proof.
This is still just collectible flavor: proof affects review readiness, not creature quality.

dutifulbob · 2026-05-22T03:02:40Z

Current-head proof for `41ebd66`

Behavior addressed: adds the generic plugin-layer embeddingProviders contract, registry/runtime lookup, SDK read helpers, and api.registerEmbeddingProvider(...) registration path. This PR does not add a real production embedding provider.

Real environment tested: local OpenClaw source checkout on the PR head 41ebd66ab411b438913201c524d8e9921e62ea5a.

Exact steps or command run after this patch:

node scripts/run-vitest.mjs src/plugins/embedding-provider-runtime.test.ts src/plugins/loader.test.ts src/plugins/loader.runtime-registry.test.ts src/plugins/embedding-providers.test.ts src/plugins/contracts/embedding-provider.contract.test.ts src/plugins/loader-records.test.ts
node scripts/run-tsgo.mjs -p tsconfig.core.json --incremental --tsBuildInfoFile .artifacts/tsgo-cache/core-embedding-providers-localtest.tsbuildinfo
node scripts/run-tsgo.mjs -p test/tsconfig/tsconfig.core.test.json --incremental --tsBuildInfoFile .artifacts/tsgo-cache/core-test-embedding-providers-localtest.tsbuildinfo
node scripts/run-oxlint.mjs src/plugins/embedding-provider-runtime.ts src/plugins/embedding-provider-runtime.test.ts src/plugins/registry.ts src/plugins/loader.test.ts src/plugin-sdk/embedding-providers.ts src/plugins/contracts/embedding-provider.contract.test.ts
node --max-old-space-size=8192 --import tsx scripts/generate-plugin-sdk-api-baseline.ts --check
node scripts/sync-plugin-sdk-exports.mjs --check
node scripts/check-plugin-sdk-subpath-exports.mjs
node scripts/check-docs-mdx.mjs docs/plugins/sdk-subpaths.md
git diff --check

Evidence after fix:

Focused Vitest passed: 6 files / 172 tests.
Core tsgo passed.
Core test tsgo passed.
Targeted oxlint passed.
Plugin SDK API baseline check passed after refreshing docs/.generated/plugin-sdk-api-baseline.sha256 in 41ebd66ab4.
Plugin SDK export checks passed.
Docs MDX check for docs/plugins/sdk-subpaths.md passed.
git diff --check passed.

Observed result after fix: the generic embedding provider contract and runtime registration path are covered by focused tests, the public SDK subpath remains read-only so plugins cannot bypass manifest ownership, and the generated Plugin SDK API baseline now matches the current public surface at head.

What was not tested: no real embedding model or live embedding endpoint was run for this PR. That belongs to the stacked provider/bridge PRs, especially #84998.

dutifulbob · 2026-05-22T03:08:20Z

@clawsweeper re-review

clawsweeper · 2026-05-22T03:10:00Z

🦞🧹
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/26266178853
Updated: 2026-05-22T03:19:38.697Z

osolmaz · 2026-05-22T03:22:16Z

@clawsweeper automerge

clawsweeper · 2026-05-22T03:24:06Z

🦞✅
Maintainer-approved ClawSweeper automerge is complete.

Approver: osolmaz
Head: 41ebd66ab411
Merge status: merged by ClawSweeper automerge
Merged at: 2026-05-22T03:36:52Z
Merge commit: ae4806ed9adf

What merged:

Merged feat(plugins): add embedding provider contract after ClawSweeper review.

Automerge notes:

PR branch already contained follow-up commit before automerge: chore(plugins): refresh embedding provider sdk baseline
PR branch already contained follow-up commit before automerge: docs(plugins): document embedding provider contract
PR branch already contained follow-up commit before automerge: fix(plugins): restore embedding providers after snapshot loads
PR branch already contained follow-up commit before automerge: fix(plugins): resolve embedding providers from manifests
PR branch already contained follow-up commit before automerge: fix(plugin-sdk): keep embedding provider registry mutators internal
PR branch already contained follow-up commit before automerge: chore(plugin-sdk): refresh embedding provider API baseline

The automerge loop is complete.

Automerge progress:

2026-05-22 03:24:05 UTC review queued 41ebd66ab411 (queued)

2026-05-22 03:36:54 UTC merged 41ebd66ab411 (merged by ClawSweeper automerge)

clawsweeper · 2026-05-22T03:26:32Z

🦞✅
ClawSweeper is pausing this repair loop for human review.

Source: clawsweeper[bot]
Reason: Manual review is needed for public SDK contract approval, the credential/security boundary, and contributor-supplied current-head proof; there is no narrow automated repair to queue.; Cleared: No concrete executable supply-chain regression was found in the live diff; the remaining security concern is the intentional public credential-bearing adapter boundary. (sha=41ebd66ab411b438913201c524d8e9921e62ea5a)

Why human review is needed:
This item has security-sensitive risk. ClawSweeper is pausing instead of making an autonomous change that could affect trust, credentials, permissions, or exposure.

What the maintainer can do as a next step:
If the maintainer accepts the current risk and wants ClawSweeper to continue merge gates, comment @clawsweeper approve. If the security-sensitive detail still needs changes, describe the safe path or push the fix, then comment @clawsweeper automerge. If the risk should not be automated, keep the PR paused for manual review or comment @clawsweeper stop.

I added clawsweeper:human-review and left the final call with a maintainer.

osolmaz · 2026-05-22T03:34:58Z

@clawsweeper approve

Summary: - Merged feat(plugins): add embedding provider contract after ClawSweeper review. Automerge notes: - PR branch already contained follow-up commit before automerge: chore(plugins): refresh embedding provider sdk baseline - PR branch already contained follow-up commit before automerge: docs(plugins): document embedding provider contract - PR branch already contained follow-up commit before automerge: fix(plugins): restore embedding providers after snapshot loads - PR branch already contained follow-up commit before automerge: fix(plugins): resolve embedding providers from manifests - PR branch already contained follow-up commit before automerge: fix(plugin-sdk): keep embedding provider registry mutators internal - PR branch already contained follow-up commit before automerge: chore(plugin-sdk): refresh embedding provider API baseline Validation: - ClawSweeper review passed for head 41ebd66. - Required merge gates passed before the squash merge. Prepared head SHA: 41ebd66 Review: openclaw#84947 (comment) Co-authored-by: Bob <dutifulbob@gmail.com> Co-authored-by: Mariano Belinky <mbelinky@gmail.com> Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com> Approved-by: osolmaz Co-authored-by: osolmaz <2453968+osolmaz@users.noreply.github.com>

openclaw-barnacle Bot added gateway Gateway runtime scripts Repository scripts size: M triage: mock-only-proof Candidate: PR proof only shows tests, mocks, snapshots, lint, typecheck, or CI. labels May 21, 2026

openclaw-barnacle Bot added docs Improvements or additions to documentation proof: supplied External PR includes structured after-fix real behavior proof. and removed triage: mock-only-proof Candidate: PR proof only shows tests, mocks, snapshots, lint, typecheck, or CI. labels May 21, 2026

openclaw-barnacle Bot added size: L and removed size: M labels May 21, 2026

openclaw-barnacle Bot removed the proof: sufficient ClawSweeper judged the real behavior proof convincing. label May 21, 2026

dutifulbob force-pushed the feat/general-embedding-providers branch from abf59e6 to ec86340 Compare May 21, 2026 13:11

osolmaz self-assigned this May 22, 2026

chore(plugin-sdk): refresh embedding provider API baseline

41ebd66

clawsweeper Bot added the clawsweeper:automerge Maintainer opted this PR into bounded ClawSweeper-reviewed automerge label May 22, 2026

clawsweeper Bot added the clawsweeper:human-review Needs maintainer review before ClawSweeper can continue label May 22, 2026

clawsweeper Bot added status: 🚀 automerge armed This PR is in ClawSweeper's automerge lane. and removed status: 📣 needs proof The PR needs real behavior proof before ClawSweeper can clear the contributor ask. labels May 22, 2026

osolmaz approved these changes May 22, 2026

View reviewed changes

clawsweeper Bot removed the clawsweeper:human-review Needs maintainer review before ClawSweeper can continue label May 22, 2026

clawsweeper Bot merged commit ae4806e into openclaw:main May 22, 2026
129 of 131 checks passed

github-actions Bot mentioned this pull request May 22, 2026

📡 Upstream Digest — 2026-05-22 07:37 UTC curtismercier/openclaw-mods#914

Open

clawsweeper Bot mentioned this pull request May 22, 2026

feat(embeddings): add OpenAI-compatible core provider #85269

Merged

dutifulbob mentioned this pull request May 22, 2026

prompt request: require maintainer review for config value additions openclaw/clawsweeper#171

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat(plugins): add embedding provider contract#84947

feat(plugins): add embedding provider contract#84947
clawsweeper[bot] merged 7 commits into
openclaw:mainfrom
dutifulbob:feat/general-embedding-providers

dutifulbob commented May 21, 2026 •

edited

Loading

Uh oh!

clawsweeper Bot commented May 21, 2026 •

edited

Loading

Uh oh!

clawsweeper Bot commented May 21, 2026 •

edited

Loading

Uh oh!

dutifulbob commented May 22, 2026

Uh oh!

dutifulbob commented May 22, 2026

Uh oh!

clawsweeper Bot commented May 22, 2026 •

edited

Loading

Uh oh!

osolmaz commented May 22, 2026

Uh oh!

clawsweeper Bot commented May 22, 2026 •

edited

Loading

Uh oh!

clawsweeper Bot commented May 22, 2026 •

edited

Loading

Uh oh!

osolmaz commented May 22, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Uh oh!

Conversation

dutifulbob commented May 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

What Changed

Testing

Risks

Follow-ups

Real behavior proof

Uh oh!

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

Uh oh!

Uh oh!

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

Uh oh!

Uh oh!

dutifulbob commented May 22, 2026

Current-head proof for 41ebd66

Uh oh!

dutifulbob commented May 22, 2026

Uh oh!

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

Uh oh!

Uh oh!

osolmaz commented May 22, 2026

Uh oh!

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

Uh oh!

Uh oh!

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

Uh oh!

Uh oh!

osolmaz commented May 22, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

dutifulbob commented May 21, 2026 •

edited

Loading

clawsweeper Bot commented May 21, 2026 •

edited

Loading

clawsweeper Bot commented May 21, 2026 •

edited

Loading

Current-head proof for `41ebd66`

clawsweeper Bot commented May 22, 2026 •

edited

Loading

clawsweeper Bot commented May 22, 2026 •

edited

Loading

clawsweeper Bot commented May 22, 2026 •

edited

Loading