This is a comment left during a code review.
Path: test/helpers/agents/openclaw-owned-tool-runtime-contract.ts
Line: 69-72

Comment:
**Incomplete test isolation — `adjustedParamsByToolCallId` not cleared**

`resetOpenClawOwnedToolHooks` resets the global hook runner and active plugin registry, but leaves the module-level `adjustedParamsByToolCallId` map in `pi-tools.before-tool-call.ts` untouched. This map is populated by `wrapToolWithBeforeToolCallHook` and consumed by `runAgentHarnessAfterToolCallHook`. In the "does not double-wrap" Codex test, `runAgentHarnessAfterToolCallHook` is fire-and-forget (`void`) with no `vi.waitFor` assertion, so the entry for `run-wrapped:call-wrapped` may remain in the map after `afterEach` clears everything else. Future tests that reuse the same `runId:callId` pair would silently consume a stale adjusted-params entry, producing wrong `after_tool_call` `params` without any obvious failure signal. The fix is to call `__testing.adjustedParamsByToolCallId.clear()` (already exported under `__testing`) or export a dedicated reset from `pi-tools.before-tool-call.ts`.

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

---

This is a comment left during a code review.
Path: test/helpers/agents/openclaw-owned-tool-runtime-contract.ts
Line: 48-66

Comment:
**Silent hook gap when `installCodexToolResultMiddleware` is used alone**

`installCodexToolResultMiddleware` calls `setActivePluginRegistry` — a completely separate global state store from the one `installOpenClawOwnedToolHooks` sets via `initializeGlobalHookRunner`. A test that calls only `installCodexToolResultMiddleware` will have no `before_tool_call` or `after_tool_call` hooks registered, with no error or assertion to catch it. This is a footgun for future contract-test authors extending this fixture: they could write a middleware-focused test, forget the companion `installOpenClawOwnedToolHooks` call, and the hook assertions would simply never fire. Consider adding a guard in `installCodexToolResultMiddleware` that warns when the global hook runner is null, or documenting the required pairing clearly in JSDoc.

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

---

This is a comment left during a code review.
Path: src/agents/openclaw-owned-tool-runtime-contract.test.ts
Line: 92-100

Comment:
**`as never` casts suppress type-safety on the test event boundary**

Both `handleToolExecutionStart` and `handleToolExecutionEnd` are called with `ctx as never` and the event object `as never`. If either function's signature changes (e.g., a required field is added to the context or the event discriminant expands), TypeScript will not catch the mismatch here, silently making the test an out-of-date fixture rather than a failing contract guard. The `createToolHandlerCtx` helper could be typed to the actual context type these handlers accept, even if that requires adding any missing optional fields with sensible test defaults.

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