While I think you probably wanted to contain the toolpath to not cut the entire block, I decided to turn it into a how-to get the minimal amount of storage space for the output.
Adaptive will most likely never be your friend in the number of lines of code, but there are a few tips that will help there. (I also put them in the notes of the operations/setups)
- Getting rid of the vertical lead-ins. Vertical lead-ins almost always get linearized for adaptives as they aren't on a plane a lot of the times.
- Using Radius output instead of IJK for arcs in the post. as a spindle R value is a lot less then IJK values.
- Using a large/coarse smoothing tolerance. Usually the larger the number for smoothing the more arcs it can fit to your toolpath.
- Checking your plane height's. If all heights are different, so clearance, retract & feed, you get a lot of extra lines in the output you probably don't really need, and if space is limited, setting your height correctly will help a lot.

So by using 2D Contour with the same step-over as your adaptive I could rough it with 6.5kb of file size with your post-processor.
If you can get away with both ways cutting for your material that would be even better;

Down to 4.3kb.
From here getting it down even further just creating a bigger step-over is probably going to be the most effective,
I've attached the file.
I think with the way I used the Stock-Contour selection in some operations you can also deduce how to get the Adaptive Clearing to not machine the whole block of material if you still remain keen on using adaptive.
Laurens Wijnschenk
3DTechDraw
AutoDesk CAM user & Post editor.
Found out the hard way is the best way to win.