[betegon]

Adds a data-only @sentry/api/operations export so discovery tools can use the metadata shipped with their installed SDK. Function names come from the generated SDK; original operation IDs, query enums and inherited parameters come from the same release's OpenAPI document. Missing or ambiguous mappings fail the build.

import { operations } from "@sentry/api/operations";

const logQueries = operations.filter(operation =>
  operation.queryParameters.some(parameter =>
    parameter.name === "dataset" && parameter.enum?.includes("logs"),
  ),
);
// Includes listOrganizationEvents without importing the HTTP client.

CLI command relationships and search policy stay in Toolkit #1658. The catalog complements the type-only operation map in #102; it does not change request execution or root exports.

Validated: build, typecheck, 166 Bun tests and 2 Node tests. New coverage exercises real SDK regeneration as endpoints/enums grow, original versus normalized IDs, and packed imports/types without client or validator dependencies.

Closes #109 (subissue of v1.0 #93).