ToolExecutedEvent

POST event (tool-runtime 0.5, event-driven retrofit): a tool call finished, successfully or via a cache short-circuit. Dispatched by {@see \Milpa\ToolRuntime\ToolRegistry::call()} as `tool.executed` — pure notification, readonly, no slot (per the family's pre/post convention: `*ing` events are stoppable, `*ed` events are audit-only). {@see \Milpa\ToolRuntime\ToolAuditLogger} subscribes to this event to log every call; other listeners (metrics, tracing, ...) may subscribe alongside it without touching {@see \Milpa\ToolRuntime\ToolRegistry}. **Cache-hit visibility invariant.** When a `tool.executing` listener short-circuits via `InterceptionSlot::shortCircuit()`, the tool's real callback never runs — but this event MUST still fire, with {@see $cacheServed} `true`. A cache hit that is invisible to `tool.executed` listeners (audit, metrics) is a blind spot, not an optimization; see {@see \Milpa\ToolRuntime\ToolRegistry::call()} for where this is guaranteed.

public function __construct(string $name, Milpa\ToolRuntime\Contracts\ToolContext $ctx, array $args, Milpa\ToolRuntime\ToolResult $result, bool $cacheServed = false):

Parameters