sentry schema <term>: a no-match search prints the full resource list instead of reporting no match

[sergical]

A search term that matches nothing returns the entire resource listing, byte-identical to what a garbage term returns. There is no signal that the search failed.

Repro

$ sentry schema committers | wc -l
      79
$ sentry schema zzzznomatch | wc -l
      79

Both print the same full table of every resource. committers is not a resource in the schema, and neither is zzzznomatch, but the output gives no way to know that.

Expected

$ sentry schema committers
No resource matches "committers". Run `sentry schema` to browse all resources.

A non-zero exit for a no-match would also let scripts branch on it.

Why it matters

The skill guidance tells agents to reach for sentry schema <resource> to discover endpoints before falling back to sentry api. Returning a plausible-looking 79-line table for a term that matched nothing actively misleads: it reads as "here are your results" rather than "that does not exist". In my case the endpoint genuinely was not in the schema, and the full-list output hid that fact.

Version

0.43.0-dev.1786559401, confirmed against origin/main @ 47ad7e4.