feat: add browsers telemetry events read command (kernel-go-sdk v0.70.0)

[archandatta]

Summary

Adds kernel browsers telemetry events <id> — reads the paginated telemetry archive for a browser session, alongside the existing live telemetry stream.

Flags:

• --limit (1–100, default 20) — page size
• --all — fetch every page (walks the cursor via the SDK auto-pager); without it you get the first page
• --since / --until (RFC-3339 timestamp or a duration like 5m)
• --categories (repeatable; server-side filter, validated against the event category set incl. monitor)
• -o json (newline-delimited JSON envelopes, matching telemetry stream)

Resolves the identifier (name-or-id) to a session ID via browsers.Get, same as stream. Text output is time \t seq \t [category] \t type.

SDK bump (bundled)

This bumps kernel-go-sdk v0.66.0 → v0.70.0 to pick up the telemetry Events/EventsAutoPaging surface (added when the API endpoint shipped). Bundled into this PR per the repo convention (e.g. 2c06a2c, where a feature carries the SDK bump it needs).

The bump also changed APIKeyService.Get to take a params arg, so cmd/api_keys.go (and its test fake) now pass kernel.APIKeyGetParams{} — an empty value that preserves prior behavior. Unrelated to telemetry, but required for the bump to compile.

Test coverage

Unit tests cover the single-page path: validation (nil telemetry, bad -o, unknown category), browsers.Get error surfacing, param mapping (limit/since/until/categories), multi-event emit, and JSON output.

The --all auto-paging path is not unit-tested: the SDK's OffsetPaginationAutoPager advances via GetNextPage, which requires a live request config, so a hand-built pager can't be driven in a unit test (this is the first CLI consumer of an SDK auto-pager). The loop is a thin for pager.Next() wrapper; the cursor/termination math lives in and is tested by the SDK, and end-to-end paging is exercised by the API-side staging smoke.

Test plan

• go build ./... / go vet ./... / gofmt clean
• go test ./... passing locally (incl. telemetry events + api_keys)
• make lint (golangci-lint) in CI
• Manual: events <id> happy path + headers, --categories, --since/--until, --limit, --all, -o json, unknown id → 404

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit d18dca1. Configure here.}

[cursor]

Inline JSON output flag

Low Severity

The new telemetry events command registers -o/--output with a hand-rolled StringP and custom help instead of addJSONOutputFlag, which centralizes the flag and Output format: json for raw API response wording across CLI commands.

 

^{Triggered by learned rule: Use shared JSON output helpers in CLI commands}

^{Reviewed by Cursor Bugbot for commit d18dca1. Configure here.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	golang/​github.com/​kernel/​kernel-go-sdk@​v0.66.0 ⏵ v0.70.0	+1

View full report

[rgarcia]

reviewed from correctness/qa and CLI surface consistency. make build and make test passed, but I think these need changes before merge.

QA / correctness

• cmd/browsers_telemetry.go:273 — multi-category filtering does not work in real QA. With a telemetry archive containing console, network, and page events, --categories console and --categories network each returned rows, but both --categories console,network and repeated --categories console --categories network returned zero rows. This needs a live/SDK-level fix and a test that covers more than one category.

• cmd/browsers_telemetry.go:263 — --limit accepts invalid values even though the help says 1-100. In QA, --limit -1 exited 0 and returned the default page, and --limit 101 also exited 0. Please validate the range client-side or loosen the help text.

• cmd/browsers_telemetry.go:267 — --since 1s returned Internal_error: failed to read telemetry events with exit 1 on an otherwise valid session, while an empty --until 1h window returned zero rows cleanly. This may be API-side duration handling, but the CLI exposes it directly, so the command should either validate supported duration forms or the endpoint needs to stop returning a 500 for an empty/recent window.

CLI surface consistency

• cmd/browsers.go:2757 — telemetry events omits the --types filter that exists on sibling telemetry stream. Since both commands expose telemetry event envelopes, users will expect the same category/type filtering shape unless there is a clear reason documented in help/docs.

• cmd/browsers.go:2754 — the command uses list-like paging language (--limit, “per page”, “first page”) but exposes no --offset/cursor, and the NDJSON output only prints event items. That makes the default mode non-pageable, unlike the rest of the CLI list surfaces that expose --limit + --offset. Consider exposing a continuation mechanism or framing this as “latest N events” with --all for archive dumps.

• README.md:316 — the README telemetry section documents telemetry stream but not the new recorded telemetry events command. Since this adds a user-facing CLI surface, please document the command, flags, output mode, and how it differs from live streaming.