Greptile Summary

This PR fixes a registry divergence bug where the channel outbound adapter loader (createChannelRegistryLoader in registry-loader.ts) was reading from the unpinned active registry (getActivePluginRegistry()), while the inbound path was already correctly reading from the pinned channel registry (getActivePluginChannelRegistry()). Post-boot operations that call setActivePluginRegistry (config-schema reads, plugin status queries, tool listings, etc.) would replace the active registry with one that lacks channel entries, causing "Outbound not configured for channel: telegram" errors.\n\n- Fix: Two-line change in registry-loader.ts switching getActivePluginRegistry() → getActivePluginChannelRegistry(), aligning outbound resolution with the pinned surface.\n- Cache correctness: The registry !== lastRegistry invalidation logic remains correct — when pinned the reference is stable (cache is never spuriously busted), and when unpinned syncTrackedSurface keeps the channel surface in sync with the active registry.\n- Test coverage: A new regression test pins a telegram adapter registry, replaces the active registry with an empty one, and asserts the adapter is still resolved — directly covering the failure scenario.\n- Scope: Minimal and surgical; no collateral changes.

Confidence Score: 5/5

Safe to merge — minimal two-line fix with a direct regression test and no side-effects.

The change is exactly the right fix: the outbound surface was the only remaining consumer of the unpinned registry, and the patch aligns it with the already-correct inbound path. The cache invalidation logic is unaffected. The new test directly reproduces the reported failure. All existing tests continue to pass per the test plan.

No files require special attention.

This is a comment left during a code review.
Path: src/channels/plugins/registry-loader.ts
Line: 17-20

Comment:
**Cache invalidation still correct with pinned surface**

The `registry !== lastRegistry` check is fine under the new surface. When the channel registry is pinned, `getActivePluginChannelRegistry()` keeps returning the same object reference, so the cache is never spuriously cleared — which is an improvement over the old behaviour where every `setActivePluginRegistry` call (config-schema loads, etc.) would return a new object and bust the cache. When the channel registry is not yet pinned, `syncTrackedSurface` keeps `state.channel.registry` in lock-step with `state.activeRegistry`, so the cache still invalidates on legitimate registry swaps. No issues here, just noting the analysis for reviewers.

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "fix(channels): use pinned channel regist..." | Re-trigger Greptile}

@steipete @vincentkoc — this is a one-line fix for the root cause behind #54745 and #54013.

TL;DR: loadChannelOutboundAdapter was reading from the unpinned active registry instead of the pinned channel registry. After any post-boot loadOpenClawPlugins() call (config schema reads, plugin status queries, tool listings, etc.), the active registry gets replaced and may lack channel outbound adapters — causing Outbound not configured for channel: telegram.

The inbound path (getChannelPlugin) already uses the pinned channel registry. This PR aligns the outbound path to do the same.

Changes:

• registry-loader.ts: getActivePluginRegistry() → getActivePluginChannelRegistry() (2 lines)
• Regression test: pins a telegram adapter, replaces the active registry, asserts the adapter still resolves

All CI green, Greptile 5/5.

Rebased onto latest main — test file auto-merged cleanly despite the channel-pin test refactoring.

Two-line fix: switches outbound adapter resolution from the unpinned active registry to the pinned channel registry, matching what inbound already does. One new test verifies outbound resolves from the pinned registry after an active registry replacement.

@obviyus — this complements the registry reuse work you merged in #56240. The outbound path was the last consumer still reading from the unpinned surface.
@joshavant — plugin registry layer, your subsystem.

All checks green locally: 9/9 channel-pin tests, pnpm check 0 errors.

Landed on main.

• Landed source commit: 16bcd77
• Merge commit: bc9c074

Thanks @GodsBoy.