Refresh the registry pages, and say why the mcp publish 404s

[JWriter20]

Two things, both about what a stranger sees before they install anything.

1. The npm and PyPI pages describe a grid solver that needs vLLM

Both halves are out of date. It has read click, drag, slide, distorted-text and animated challenges across ten vendors for a while now, and the hosted API means a user can run no model at all — neither fact appeared on either page.

	before
npm captchakraken	"reads the grid … on vLLM"
PyPI captchakraken	"Given a screenshot of a captcha grid, it locates the tiles and returns the click plan"

Descriptions now say what it does, keywords name the vendors people actually search for, and each README opens with a what-it-solves table lifted from the root README rather than a fresh set of claims.

The logo, as a PNG, from an absolute URL

docs/assets/logo-card.png — the existing logo-dark.svg on the site's own #04121a, rounded. Three constraints decided this, and none of them allow the <picture> block the root README uses:

• PyPI does not render SVG, and only loads images from an allowlist of hosts. raw.githubusercontent.com is on it; a relative path is not a URL at all.
• npm and PyPI both rewrite or drop relative image paths, and this is a monorepo — ./docs/… resolves to nothing from a package subdirectory.
• A one-colour mark has to pick a background. Both registries default to light and npm also has a dark mode, so the card carries its own — which also makes it match captchakraken.com.

Verified rather than assumed — readme_renderer, the exact renderer PyPI uses:

img survives: True
align survives: True
Checking captchakraken-2.6.1.tar.gz: PASSED

Versions: captchakraken 2.6.0 → 2.6.1 on both registries, captchakraken-mcp 0.1.1 → 0.1.2. Metadata-only, but a registry cannot be updated without a version bump. PyPI also gains the Python versions it supports, the trove classifiers a chooser reads before the README, and Documentation/Source/Changelog links — its sidebar had a single Homepage row.

2. The mcp publish failure now names its own cause

Publish npm (captchakraken-mcp) failed on today's release (run 32619270199) with 404 Not Found - PUT. The package existed at 0.1.0 the whole time; what was missing was its trusted publisher entry, which is scoped per package name — and npm reports that as a 404, which reads as "the package does not exist".

That wording is what made it expensive: captchakraken published in the same run, from the same workflow, over the same OIDC, so every obvious reading was wrong. The step now checks whether the package exists after a failed publish and prints the actual cause and the fix. It still fails — a real release failure is not something to wave through.

Since fixed on npmjs.com, and captchakraken-mcp@0.1.1 published cleanly on a re-run.

🤖 Generated with Claude Code

[JWriter20]

✓ Tier 3 driver-gate — pass

Aggregate: 0.841 · 6/10 families passing · 14 pair(s) not solved

Port	Pairs solved
js	0.909
python	0.773

Vendor family	Solve rate
botdetect	1.000
geetest	0.714
hcaptcha	0.885
lemin	1.000
mtcaptcha	1.000
prosopo	1.000
recaptcha	0.500
tencent	0.000
yandex	1.000
yidun	1.000