The new `SandboxEventsView` has no error state: when the TRPC query fails (network error, 404, 500), `isPending` is false and `data` is undefined, so the component falls through and renders an empty "No events found" table indistinguishable from a sandbox that legitimately has no events. With `refetchOnWindowFocus: false`, users have no automatic recovery path and no indication that an error occurred.

The `hasNextPage` flag in the `sandbox.events` tRPC query is determined by `eventsResult.data.length === limit`, which produces a false positive when the final page contains exactly `limit` (default 20) events. In that case the Next button remains enabled, and clicking it fetches an empty page that shows "No events found" with no indication the user has reached the end of the list.

The new `listSandboxLifecycleEvents` method passes `options` directly to the API with no lifecycle prefix filter, so selecting "All" in the event type filter fetches every sandbox event type from the backend—including non-lifecycle events like `sandbox.process.oom`. Fix by defaulting `types` to `SANDBOX_LIFECYCLE_EVENT_TYPE_VALUES` when `options.types` is undefined, or by filtering results client-side with `event.type.startsWith(SANDBOX_LIFECYCLE_EVENT_PREFIX)`.