Improve comprehension for running Techniques

[istathar]

Improve the experience for new users by providing slightly more context when they attempt to use the command-line program and don't supply the correct arguments.

Automatic runs that have steps with no effectful function are marked Skip rather than blindly calling them Done. Substeps roll up to the step being Done if any sub-step is Done, otherwise the step gets Skip.

Finally, this lands a considerable refinement to the way that steps are announced when interactively ruuning through a Technique document. The fully qualified path form is important for being able to give the canonical address of a procedure, section, step, or substep but having the full path in the UI trace and especially in the prompt was excessive. In particular, the name of the enclosing top-level entry procedure in a Technique document with sections ended up forming a prefix that was relentless on every line and distracted from a user actually understanding where they were in the document. Before we had

→ /connectivity_check:/VI/check_aws_health:/7 ▶

which was verbose. Instead, this branch changes the display to hide the top-level entry procedure to better show the context

→ VI/check_aws_health:/7 ▶

The fully qualified paths remains in the PFFTT format's record line

2026-06-16T07:20:21.278Z 000019 /connectivity_check:/VI/check_aws_health:/7 Begin

[istathar]

This collided with #117 somewhat, but on merge I reconciled the two appoaches.