PR #78151: fix: discover generation providers with active registry

• Repository: openclaw/openclaw
• Author: bryce-d-greybeard
• State: closed | merged: False
• Link: https://github.com/openclaw/openclaw/pull/78151

Description (problem / solution / changelog)

Fixes #78141.

Summary

• keep image/video/music generation provider list resolution from short-circuiting on the active plugin registry
• merge active generation providers with manifest-scoped loaded providers so an active provider like xai does not hide allowlisted bundled fal
• add a regression test for active xai plus allowlisted fal resolving both providers

Tests

• PATH="/tmp/openclaw-pnpm-shim:$PATH" pnpm test src/plugins/capability-provider-runtime.test.ts
• PATH="/tmp/openclaw-pnpm-shim:$PATH" pnpm test src/plugins/capability-provider-runtime.test.ts src/image-generation/provider-registry.test.ts src/agents/tools/image-generate-tool.test.ts
• git diff --check
• PATH="/tmp/openclaw-pnpm-shim:$PATH" pnpm exec oxfmt --check src/plugins/capability-provider-runtime.ts src/plugins/capability-provider-runtime.test.ts
• PATH="/tmp/openclaw-pnpm-shim:$PATH" node scripts/check-changed.mjs

Changed files

• src/plugins/capability-provider-runtime.test.ts (modified, +60/-0)
• src/plugins/capability-provider-runtime.ts (modified, +12/-3)

PR #78175: [AI-assisted] fix(image): discover allowlisted fal provider

• Repository: openclaw/openclaw
• Author: brokemac79
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/78175

Description (problem / solution / changelog)

Summary

Fixes #78141 by letting generation provider discovery merge enabled manifest-backed providers even when another generation provider is already active.

Root Cause

resolvePluginCapabilityProviders returned the active registry immediately for non-memory capabilities when no requested-provider collector existed. Image, video, and music generation providers had no collector, so an already-active provider such as xai could hide another enabled/allowlisted provider such as fal from image_generate action=list and provider lookup.

Changes

• Continue manifest-backed loading for image, video, and music generation providers even when active providers already exist.
• Preserve the active-only fast path for other capability families.
• Add a regression that starts with active xai and verifies allowlisted fal is merged into image-generation provider discovery.

Validation

• corepack pnpm test src/plugins/capability-provider-runtime.test.ts src/image-generation/provider-registry.test.ts src/agents/tools/image-generate-tool.test.ts
• corepack pnpm exec oxfmt --check --threads=1 src/plugins/capability-provider-runtime.ts src/plugins/capability-provider-runtime.test.ts CHANGELOG.md
• corepack pnpm check:changed
• git diff --check

Real behavior proof

Behavior or issue addressed: image_generate provider discovery no longer stops at an already-active image provider; enabled manifest-backed providers such as fal can be discovered and listed alongside the active provider.

Real environment tested: Windows local checkout at [email protected] on branch fix-fal-image-provider-discovery.

Exact steps or command run after this patch: Ran corepack pnpm test src/plugins/capability-provider-runtime.test.ts src/image-generation/provider-registry.test.ts src/agents/tools/image-generate-tool.test.ts, targeted oxfmt --check, corepack pnpm check:changed, and git diff --check.

Evidence after fix: Terminal capture from the focused capability/image-generation command showed 3 Vitest shards passing: provider registry 3 tests, image-generate tool 29 tests, and capability-provider runtime 39 tests. The new regression constructs an active registry containing xai, a manifest/loaded registry containing fal, and plugins.allow: ["fal", "xai"]; after the patch resolvePluginCapabilityProviders({ key: "imageGenerationProviders" }) returns provider ids ["xai", "fal"] and scopes the fallback load to ["fal", "xai"].

Observed result after fix: The resolver includes fal instead of returning only the active xai provider, while all focused provider/image-generation tests and changed-file checks passed locally.

What was not tested: I did not run a live gateway with real FAL credentials or call the external fal image-generation API.

Changed files

• CHANGELOG.md (modified, +1/-0)
• src/plugins/capability-provider-runtime.test.ts (modified, +56/-0)
• src/plugins/capability-provider-runtime.ts (modified, +16/-6)