Answer architecture round 3, stability round 2, product-owner round 2 and prose round 1: the CLI renders exactly the template on stdin and adds nothing, --separator defaults to empty, whitespace around JSON is dropped, a lone reference under --format allows one newline, a blank stdin is refused, an unexpected argument names the spelling to use, and the prose names one lone reference

namefence.go

@@ -68,8 +68,7 @@ func rendersInside(nodes []node, t *template) bool {
 // template reaches the binder through fields. A single read as a calc operand stands where a calc
 // could not read the spelling, a reference or a path. So {/misc.coordinate.lat as lat}{calc(lat * 60)}
 // stands, since {calc(/misc.coordinate.lat * 60)} does not compile.
-// Where the spelling would be a whole struct tag, that entry point refuses it and names the bare
-// path.
+// A whole struct tag of that spelling is refused, naming the bare path.
 func (b *nameBinding) refuseSingleRead(uses []nameUse) error {
 	if len(uses) == 0 {
 		panic(invariant.Broken("name %q has no read at resolve, though its compile found one", b.name))