C11-C14 are now tied to explicit remote verification instead of leaving the ledger at the intermediate failure state. The mixed-version symbol issue is documented as a caller-sync problem, and the stale C14 expectations are recorded as intentional current contracts rather than open regressions.
Constraint: Local pytest in this workspace is blocked by missing optional runtime dependencies such as orjson, so remote g0034 container tests are the authoritative CPU/unit evidence for these files.
Rejected: Reintroduce cp_shared_kv_mla_prefetch_should_trace_tiny_extend | the current callers no longer import it, and adding a dead compatibility helper would hide sync mistakes.
Confidence: high
Scope-risk: narrow
Directive: Keep C13 validation focused on matching caller/runtime sync; do not resurrect stale helper APIs unless an active caller contract requires them.
Tested: Local py_compile for touched runtime/prefetch/caller/test files; remote caller import check printed CALLER_IMPORT_OK; remote exact C14 set passed 6 passed, 3 warnings; remote three-file suite passed 123 passed, 5 warnings.
Not-tested: CUDA/TAI ETE runtime logs were not rerun in this documentation-only commit.
Co-authored-by: OmX <omx@oh-my-codex.dev>
4f9bb7ce30