Add verl-style override workflow - #68

Summary

• accept ordered override files, repeatable --set values, and trailing verl-style key=value assignments without Hydra or shell evaluation
• preserve duplicate/precedence provenance and require value-bound acceptance for acknowledgement-required one-GPU reinterpretations
• publish a reduced, attributed official-field compatibility fixture/report and document the supported config workflow in English and Chinese

Compatibility evidence

• reduced official profile subset: 82 fields
• exact: 23
• semantically conformant: 16
• locally reinterpreted: 22
• informational only: 18
• unsupported: 3
• unsupported advantage-estimator and FSDP-offload semantics remain fail-closed

Validation

• pytest -q -m "not gpu and not network" --cov=miniverl: 2,188 passed, 9 skipped, 21 deselected; 85.03% branch coverage
• pytest -q -m gpu: 8 passed on RTX 4080
• pytest -q -m network: 13 passed, 2 skipped
• focused config/product tests: 42 passed, 1 skipped
• Ruff check/format, mypy, actionlint, strict MkDocs, generated artifacts, Markdown/link checks, Playwright at 1440/1024/820/390 px, build/Twine and package-resource checks passed
• frozen calculator result SHA-256 remains 53fc1d4d5b7adee09618d77ad62d4086ba56b78569832d6fc7c3bcd5c2695bbc

This PR does not add an algorithm, change a scientific result, or claim distributed verl compatibility.