Materialize launchable verl OPD bundles - #71

Summary

• add transactional bridge materialize for exact student/teacher snapshots, strict immutable identity and regular-file checks, and explicit teacher-adapter merging
• publish launch.sh only after PEFT, Parquet, tokenizer/model, top-k and pinned verl validation; keep distributed execution explicitly untested
• make fresh OPD exports report missing base-model loadability honestly, teach doctor to recompute materialized readiness, and document the offline-first workflow
• add a real tiny-Qwen3/LoRA conformance smoke under official verl v0.8.0 at 7aed6b23

Validation

• ruff check .; ruff format --check .
• mypy src/miniverl scripts
• actionlint 1.7.12
• 2,216 non-GPU/non-network tests passed; 83.69% coverage
• pinned verl conformance: 4 passed, including export -> materialize -> sequential model forwards -> doctor
• network: 13 passed, 3 skipped; GPU: 8 skipped because CUDA was unavailable in the final process
• strict MkDocs and Playwright: 11 pages at 1440, 1024, 820 and 390 px; no exemptions
• wheel/sdist build and Twine passed; clean core and [train,bridge] installs passed; extracted-sdist suite: 2,214 passed
• frozen calculator SHA-256 remains 53fc1d4d5b7adee09618d77ad62d4086ba56b78569832d6fc7c3bcd5c2695bbc; no benchmark file changed

Boundary

launchable: true means the exact pinned config and local artifacts are complete enough to invoke the documented upstream entry point. No distributed verl job ran, and distributed execution and algorithmic parity remain false.