Greptile Summary

This PR fixes a bug where pluginConfig from openclaw.json was not available inside hook handlers by wrapping each registered handler to inject the config into event.context. The plumbing through createApi → registerHook is correct, but the wrapper mutates the shared event object directly instead of cloning it, which can contaminate other handlers in the same dispatch chain.

• P1: wrappedHandler writes directly to evt.context, which is the same object triggerInternalHook passes to every handler in sequence — non-plugin handlers and other plugins' handlers that fire after the first mutation will see an unexpected pluginConfig key. A shallow spread ({ ...evt, context: { ...evt.context, pluginConfig } }) avoids this entirely.

Confidence Score: 3/5

Hold — the wrapper mutates the shared event context in-place, contaminating other handlers in the same dispatch loop.

One P1 defect: the wrappedHandler mutates the shared event object instead of creating a shallow copy, which causes cross-handler context contamination at runtime. The overall plumbing change is correct and the fix is small, so this does not rise to P0, but the mutation bug needs to be addressed before merging.

src/plugins/registry.ts — specifically the wrappedHandler block around lines 505–510.

This is a comment left during a code review.
Path: src/plugins/registry.ts
Line: 505-510

Comment:
**Shared event object mutated in-place**

`triggerInternalHook` passes the **same** `event` reference to every registered handler sequentially (see `internal-hooks.ts` lines 296–305). Mutating `evt.context` here permanently writes `pluginConfig` onto the live event object before any subsequent handler (including non-plugin internal handlers and other plugins' wrapped handlers) receives it. If Plugin A and Plugin B both hook the same event, Plugin A's value is silently overwritten, and all non-plugin handlers that run after either plugin will see an unexpected `pluginConfig` key that does not belong to their context type.

Shallow-copy the event and its context instead of mutating the incoming object:

```suggestion
      const wrappedHandler: typeof handler = async (evt) => {
        return handler({
          ...evt,
          context: { ...evt.context, pluginConfig },
        });
      };
```

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

_{Reviews (1): Last reviewed commit: "fix: inject pluginConfig into hook handl..." | Re-trigger Greptile}

CI Failure Analysis

Both failing checks are unrelated to this PR:

1. checks-node-agentic-control-plane — Failed with GatewayClientRequestError: device metadata change pending approval. This is a CI runner infrastructure issue (device pairing/approval). The test shard timed out (exit 143) after 422s. Not related to the registry.ts change.

2. checks-node-core — Aggregation gate that failed because the non-dist shard above failed. DIST_SHARD_RESULT: success.

All plugin-adjacent checks passed:

• ✅ checks-fast-contracts-plugins
• ✅ checks-node-agentic-plugins
• ✅ checks-node-agentic-plugin-sdk
• ✅ check-prod-types
• ✅ check-test-types
• ✅ check-lint