[sdairs]

Add read-only cloud org notifications (Beta), exposing limit, cursor, severity, type, resource ID/type and inclusive RFC 3339 date filters. JSON preserves page entries and cursor metadata, including an empty opaque cursor; human output safely renders sparse entries. Route through a domain-local CloudClient wrapper and declare the notification workflow's permissions.

Fixes #1108. Refs #1088. Depends on the immediately preceding notifications API layer, which closes the drift issue. This is the final new layer in native stack #1095 above #1099. All parameters of the new library method are exposed; no method is intentionally omitted.

Validation: five focused unit tests and five real-binary subprocess tests pass, covering OAuth, filters, pagination, empty/sparse human output, errors and local date/range validation. Parent/leaf help was inspected and the authentication reference documents page-by-page reads. No paid provisioning or credentials creation was attempted.

Stack dependency: #1104. Final API coverage: #1104; final CLI layer: #1105.

Combined-stack validation at dc45f645f20fa7b0d3639d732531d947726b68a5: cargo fmt --all --check; both CLI Clippy configurations; cargo check -p clickhousectl --no-default-features; API/analyzer all-target Clippy; cargo check --workspace --all-features; 817 API/analyzer tests; 2,351 CLI tests; 96 Python/classifier tests. All passed. Live/resource-creating tests retain their existing ignore gates. No paid Cloud integration label or provisioning lifecycle was triggered.

Exact-head CI at dc45f645f20fa7b0d3639d732531d947726b68a5: full CLI job, format, MSRV and Cloud integration decision pass. The final live-spec dry run still reports zero actionable drift. Live suites were not selected for this CLI-only layer.

---

Note

Low Risk
Read-only CLI and documentation with local validation; no writes, auth changes, or provisioning paths.

Overview
Adds a read-only Beta clickhousectl cloud org notifications command to page through organization notifications via the Cloud API.

The command exposes limit, cursor, severity, --type, resource-id, resource-type, and inclusive RFC 3339 from-date / to-date filters. It is classified as a read (OAuth-friendly), registers NOTIFICATION_GET_LIST in org permissions, and calls a new CloudClient::list_notifications wrapper. JSON returns result with optional limit and nextCursor; human output prints a markdown table (sparse fields as -) and prints the next cursor as a safely escaped JSON string.

Unit and subprocess tests cover flag parsing, validation, HTTP query forwarding, pagination, errors, and table rendering. docs/reference/authentication.md documents pagination and filter behavior alongside notification-types.

^{Reviewed by Cursor Bugbot for commit dc45f64. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

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

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

[cursor]

Human timestamps skip RFC 3339 format

Low Severity

Human tables render created_at via or_absent on the raw DateTime, so chrono Display (2026-10-07 09:30:00 UTC) is used instead of RFC 3339. Other list tables in this CLI, including invitations in the same module, map timestamps with to_rfc3339(), and --json still emits RFC 3339, so the same instant appears in two formats.

 

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