Validation: terse report paths carry every count

[rbeezer]

Corrects a scoping error in #3027. The request was to squelch the [1] count of an only child in human-readable output only; the coding assistant (me, Claude) instead applied the squelch at the path generators, which feed both report forms, so the machine-readable terse report lost its counts too. That was a failure to obey clearly stated scope, not a design decision.

The repair draws the line properly: paths are complete at the data layer, and squelching is presentation for humans only.

• The validation-plus stylesheet emits complete paths again — every element carries its count — with a comment recording the division of labor.
• The script renders each form independently: the terse report carries complete paths (/pretext[1]/article[1]/section[1]/image[1]), while the human-readable report regenerates the squelched form from the resolved element (/pretext/article/section/image). The path parser continues to accept both forms.
• The Guide's terse subsection states explicitly that every element of a path carries its count, unlike the human-readable report.

Verified: the human-readable report is byte-identical before and after this change, on a small demo document and on the full sample article; only the terse path field changes, back to uniform complete counts.

Claude Fable 5, acting as a coding assistant for Rob Beezer