Describe OTLP destinations as organization-scoped

[archandatta]

Summary

• describe telemetry destinations as organization-scoped in the README, and note that changing one requires organization-scoped authentication while a project-scoped API key can list, get, and select them
• change the --name help on telemetry destinations create and update, and the create long description, from "unique within the project" to "unique within the organization"

Why

Destinations moved from project scope to organization scope. The API now enforces name uniqueness per organization and returns 403 to project-scoped credentials on create, update, and delete, but the CLI text still described the old per-project model.

Text-only change. No flag names, defaults, or request shapes change.

Testing

• make build
• go test ./cmd/...: all packages pass
• ./bin/kernel telemetry destinations create --help shows the updated text

🤖 Generated with Claude Code

---

Note

Low Risk
Documentation and CLI help text only; no runtime or API client logic changes.

Overview
Updates user-facing docs so OTLP telemetry destinations match the organization-scoped API instead of the old per-project model.

The README Telemetry destinations section now states destinations belong to the org (usable from any project), that create/update/delete need org-scoped auth, and that project-scoped keys can still list, get, and select them. Create help text says destination names are unique within the organization.

Matching CLI help changes on telemetry destinations create and update: the create long description and --name flag strings say organization uniqueness instead of project uniqueness. No flags, defaults, or request behavior change.

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