[betegon]

sentry schema now discovers API capabilities from OpenAPI metadata and real CLI command paths, including log, trace, and alert metrics. Ambiguous queries return candidates with context instead of silently choosing the first endpoint; exact lookups keep their JSON shape.

Reuses command introspection and schema generation, with tests for API/CLI growth and compatibility.

Examples:

# Finds Explore's dataset=logs as well as feature-flag audit logs
sentry schema logs

# Uses the CLI relationship and explains the dataset=logs selector
sentry schema log list

# Resolves the alias to trace list: dataset=spans, is_transaction:true
sentry schema trace ls

# Maps metric alert inspection to getOrganizationDetector
sentry schema alert metrics view

# Returns matching list operations instead of choosing the first one
sentry schema issues list

# Exact lookup still returns one endpoint object, without match metadata
sentry schema listOrganizationEvents --json

Validation: typecheck, lint, and schema tests pass. The full local suite is not green: an unchanged installer test fails on macOS, and asset-catalog tests require the unavailable actool.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
sentry-local	Skipped		Oct 26, 2026 3:20pm UTC

[sentry-warden]

Method-prefixed exact IDs return an array instead of one endpoint object

sentry schema GET listOrganizationEvents (and similar METHOD + operationId/fn lookups) resolves as kind: "endpoints", so --json emits a one-element array instead of the bare endpoint object exact lookups are documented to keep.

Evidence

• resolveIdentifierLookup(query) matches the raw string only, so GET listOrganizationEvents never hits the single-endpoint branch.
• searchEndpoints() strips the method, exact-matches listOrganizationEvents, and returns a plain one-element list with no match metadata.
• resolveResourceQuery() then always wraps any searchEndpoints() hit as { kind: "endpoints" }, including that single exact result.
• Path and bare-identifier exact paths still return { kind: "endpoint" }; tests cover those shapes but not METHOD + operationId.

_{Identified by Warden · code-review · Y6V-GWQ}