Name camoufox only, and stop describing video as half-shipped

[JWriter20]

Two unrelated corrections to public-facing copy.

Holo does not belong in a public repo

The end-to-end browser benchmark published a second row — Holo 152.0.3 | 1 / 3 — in README.md and docs/performance.md. Holo is the private camoufox fork; naming it here, with a version number and a measured solve rate, discloses both that it exists and how it performs. The public integration is camoufox, and that is the only browser this repo should name.

The row is removed, not relabelled. Those numbers were measured on Holo, and moving them under the camoufox heading would be publishing a benchmark figure for a run that never happened. The prose leaned on there being two rows ("both runs", "the difference between the two rows"), so it is rewritten for one. The IP-reputation caveat survives — it was always the more useful half.

Exposure, checked rather than assumed

Surface	Result
npm captchakraken@2.6.0 README	clean — no mention
PyPI captchakraken@2.6.0 description	clean — no mention
captchakraken.com (/, /docs, /pricing, /contact)	clean
Public repo working tree	2 files — fixed here
Public repo git history	present in 8928149, and this PR cannot reach it

That last row is the one worth a decision. The mention is public in 8928149 and stays public unless that history is rewritten — which on a repo that is a submodule of CaptchaKrakenFinetune, and that people have cloned, is a disruptive operation. Flagging it rather than doing it.

Video challenges have shipped, in both halves

The feature table said "🟡 Video challenges — driver support ships; the adapter setup.sh installs skips them", and three other places sold video as a reason to watch the repo. All of that predates v1.2:

• setup.sh installs CaptchaKraken-Lora-v1.2 / captcha-v12, pinned to models.json latest by python/tests/test_setup_sh_model_ids.py
• that model is prompt generation 2, and generation 2 is the one that has a video prompt — generation 1's is None, which is why the old caveat was true when written
• the hosted API serves the same captcha-v12, and docs/hosted-api.md already bills a video response at 10 credits
• both ports: types.ts carries videoSolveEnabled / videoBurstDurationMs, and the JS driver runs the solve through the bundled Python CLI

roadmap.md already said 🟢 shipped and was the only file that had kept up — though it opened with "the driver half has shipped", accurate when the model half was outstanding and misleading now.

Roadmap pointers corrected while here: they promised "smaller models", which is not on the roadmap. The one ⚪ planned item is more captcha types.

All relative links verified to still resolve.

[JWriter20]

✓ Tier 3 driver-gate — pass

Aggregate: 0.807 · 6/10 families passing · 17 pair(s) not solved

Port	Pairs solved
js	0.841
python	0.773

Vendor family	Solve rate
botdetect	1.000
geetest	0.643
hcaptcha	0.865
lemin	1.000
mtcaptcha	1.000
prosopo	1.000
recaptcha	0.250
tencent	0.000
yandex	1.000
yidun	1.000