Non-strict torch.export traces through torch_function and dispatcher/proxy machinery, so a raw Triton kernel launch is invisible as a stable export operator. The trace falls into Triton's runtime and the argument binder tries to specialize tensor arguments via data_ptr(), which fake/functional tensors cannot expose. Users then saw a generic data...