Batch on startup, possible glitch/bug

[subwoofer]

I'm not really good at reading the data trace logs, I still get a bit overwhelmed by them, but I spotted something odd in this data log. Engine is started at 28s, at 31s there is a spike of PW that is not followed by a misfire or rich spike.

This could be a bug in the startup code? I can't find the "crank to run" in the heat of the moment, but I imagine it is around 2s someplace. PWs then drop back to batch levels, then quadruple for full sequential after a little while.

Log and msq attached, running 1.3.0 release code (first time in ages I've run production code!)