release: 0.5.1

[only-cli]

Cuts 0.5.1 and brings the docs up to date with everything merged since 0.5.0.

Version

0.5.1 in package.json, the lockfile, .claude-plugin/plugin.json, the marketplace entry, and the npx --yes @only-cli/oc@... pins inside the skill.

CHANGELOG

Covers 0.5.1 against 0.5.0:

• oc open fails with "Impersonating chrome150 is not supported" (chrome alias → unsupported fingerprint) #40 oc open no longer dies with Impersonating chrome150 is not supported when impers loads a system libcurl-impersonate older than v2.1.0. A refused fingerprint downgrades the way a blocked response already did: chrome to firefox, then plain fetch
• actions: footer advertises fill/submit, which are NotImplemented stubs (and omits find) #44 the actions: footer no longer offers fill and submit, which are still planned and always threw
• actions: footer never offers find, the cheapest way to go deeper on a page #46 find <query> in every footer, after do <n> and before read <n>, matching the skill's cheapest-first order

Docs

• README install note and llms.txt describe the full transport chain: Chrome, then Firefox, then native fetch. Before this they said only that native fetch covers a missing impers.
• The README footer example and the skill were already updated inside feat: offer find in every actions footer #47 and Drop fill and submit from the actions footer, they always throw #45, so no other doc rewrite is needed.
• The README Benchmarks section still says "oc 0.5.0, August 2026", which is the run those numbers came from. The footer now carries 3 or 4 more tokens per render, so a rerun against the published 0.5.1 will shift the per-task rows by that much. That is a follow-up in only-cli/benchmarks once 0.5.1 is on npm, not part of this PR.

Checks

npm test passes 213/213. The skill pin check that the publish workflow enforces on stable releases resolves to @only-cli/oc@0.5.1 only.