remote-execution.md: the capability images are two kinds now — ten on the full
core and five on a torch-free light core for stacks that cannot share a venv —
and the doc says which, why each split was measured rather than assumed, what
the .venv-*.check scripts catch that a bare import cannot, and why the light
core exists (RunPod refuses images above ~10 GB; a specialised image on the
full core carried 7 GB of torch it never used). The 'speaker rides stt' line
was wrong — that image shipped nothing for speaker work — and is fixed. A new
section covers what travels to a pod as environment: the HF token, licence
acceptances, baked-venv paths, OCR engine gates. Surya on a pod is documented
as served by docTR, with the reason. The host backend gets its own section:
always-on and on-demand shapes, what it deliberately lacks, and service_token.

runpod.md: the size line with the numbers behind it, EXITED as a dead pod
rather than a slow pull, container-disk sizing from HF metadata, and the field
table corrected — boot_timeout_s is 900, container_disk_gb grows to fit.

README: the fifteen images and the host backend, one line each.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0182DhR1eFNPQyGmDrpHbedY