I'm going to explore the different available operations more tomorrow, but appreciate the suggestions.
As I'm acclimating to PATH, I've thought a bit about what the price is in the learning curve--that is, what aspects are complicated about getting started with PATH. I've spent a week, and feel like I'm able to do about 80% of what I need comfortably, with a couple buttons/options I haven't figured out yet. I'm so gratified by the experience of seeing a design realized, such that in the time predicted by my simulation, I could see and hold what I had modeled.
In my initial design, I successfully exercised the following in PATH-WB:
I defined Tools in the Tool-Library.
I created a JOB, defining the destination for the output GCode file, selecting the Post-Processor.
I exported TOOL-CONTROLLERS from the Tool-Library to the Job, and configured FEEDS and SPEEDS, and gave a meaningful name to each. In this JOB, I chose to define a single TOOL-CONTOLLER per tool, but I could have defined multiple controllers--for example, for Roughing, then Finishing passes.
In varying order, I exercised the following PATH Operations:
5. Dressing up the Pocket-Operation
6. Issuing Full-Stops for tool changes
7. Setting a fixture to specify G55 coordinates
8. 3D Pocketing using a ball nose endmill
9. Generated a feature from an iterative design step that allowed me to face my part where my endmill could cut what was in essence a combination of internal and external cuts, without suffering the bit radius corner penalty where my path allowed me to cut into air.
10. Inserted Custom GCode.
11. I explored, understood, but opted not to use here the Dogbone dress up operation.
12. I didn't use, but understood the Comment operation.
While still clearly a novice, I did learn that: it's important to me to have a Strategy. I start with my initial sketch oriented on XY aligned to how it sits in G55 coordinate system on my table, using homing and probe switches to determine XYZ, Pad it to finished height, etc... I try to avoid having to rework the 3D model to limit making FC angry or disoriented. I save iterations fairly frequently. In Path, where multiple options exist to accomplish an Operation, I've learned best to choose the simplest. For example, I attempted a pass at filleting the contour of the two pockets by selecting all of its 16 faces, but missed one corner--my messup. The next pass, I selected the pocket floor, selected Contour Cut on a Face, and specified the bit radius offset in the Pass Extension. I start with my largest tool, face my stock, then cut whatever material I can, program stops for manual tool changes, moving to successively smaller tools as needed.
I need to design and cut the Pick-Out to mate with this Mold next, and it's a subset of what I've done so far, so I'm confident it will be straightforward to do now.
First, I'll try to adapt my Post Processor as suggested, then fix this Job to remove my Custom GCode to tidy things up.
I'm curious if it's a good idea to model my vacuum table, including shoulder screw inserts to accurately depict my ficture, and may try. I think it will be helpful in helping visualize the job--including possible obstacles, but I assume there's a penalty to be paid in extra file size.