I think the “Status” line just displays the last comment in the g-code.
G-code, and therefor CM has no idea how many “passes” are in the file. It’s just a bunch of linear moves to an XYZ position. I suppose it could consider a “pass” anything between 2 rapid moves. For a simple pocket or contour path this might be useful. For a detailed V carve, or 3D path you may end up with thousands of “passes”.
I think a persistant “Path name” & “Tool Name” might be more useful. ??
The controllers don’t really know what “pass“ they are on. They run directly on the g code which basically tells it to go from point a to point be at preset speed over and over again.