Release v0.3.0-beta.1 · only-cli/oc

Beta. Install with npm install -g @only-cli/oc@beta.

Highlights

JSON APIs render as pages (#3). An endpoint that answers with JSON becomes one numbered item per record, so oc open on a search API reads like a results page. The renderer keeps the fields that vary between items, states once what every item shares, names the fields empty everywhere, and points at oc raw for the rest. 30 Stack Exchange results land in about 960 tokens against 5,543 for the raw body.
Stack Overflow search (#3). search <query> through the Stack Exchange API. Each result prints its question_id, which the existing question <id> feed reads in full, since the question's own HTML page answers a bot challenge instead of the question.
Cloud documentation shortcuts (#11). AWS (guide, page, cli), Google Cloud (docs, page, gcloud), and Microsoft Learn (azure, doc, cli), each with search <query>. Microsoft Learn has a real search API; AWS and Google Cloud render search client-side with no feed, so theirs go through DuckDuckGo with a baked-in site: filter.
JSON is a readable content type on both transports. The native-fetch path used to reject anything that was not HTML or XML, while the impers path never checked at all, so one URL could render two ways depending on which client got it.
Plugin marketplace install path and a discoverable web-browsing skill.
CI hardening: CodeQL, dependency review, npm provenance, and OpenSSF Scorecard.

fill, submit, and back are still not implemented. They were labelled v0.2 in the help output, which shipped without them; they now read (planned).
The bundled skill still pins @only-cli/oc@0.2.0. That pin is what agents execute, so it moves when 0.3.0 is stable rather than at beta.