[undergroundrap]

The WO22/WO23 list timing envelope includes work around the native Cargo listing call, so the existing timing cannot distinguish that call from argument construction and admission/validation work. Add one optional report-only nested -list-cargo-capture interval around each of the 29 existing guarded Cargo listing calls (16 WO22 and 13 WO23, including distinct B14 identities).

The child timer reports whether the capture call returned or threw. A returned nonzero process result remains completed for this interval and can still fail parent list acceptance. Missing or failed diagnostics preserve request arguments, exceptions, negative causes, refusal credit, restoration, cleanup and target selection. WO24 and fallback routes gain no new child interval. The second file maintains focused synthetic regression controls; no CI gate, workflow or consumer changes.

Validation: independent source review passed. One separately approved source-selected in-memory synthetic run passed 73 cases, 448 assertions and 128 simulated capture requests. Returned Hooks cover 63 cases/260 marker attempts; the final 10 cases produced 40 marker records without Hooks. The complete all-case hook total and raw event arrays for the 29 mapping cases are unavailable.

These results do not establish real marker clocks/filesystem behavior, the legacy positive-frequency assertion outside the projection, whole-helper/Full invocation, platform execution, compiler flags, CPU attribution or a speedup. No local real Hum/Cargo/rustc/JIT validation was run for this candidate. This draft requests the ordinary required hosted Windows/Ubuntu Full PR cycle under the separately approved exact-candidate local-Full substitution; hosted results remain pending.