Answer architecture round 2, stability round 1 and product-owner round 1: a format string on stdin keeps every byte while JSON or a lone reference drops one newline, an operand's error names stdin, a file or the pipe, {//x} is refused and "{/x}" read as its record, plain echo and a heredoc in the examples, goal 7 reads one command line, decision titles drop argument, and items 157 to 159 filed

CHANGELOG.md

@@ -27,10 +27,11 @@ replacement, and each removed path, column or flag.
   operand: `{/misc.coordinate.lat as lat}{calc(lat * 60)}`. What `New` refuses is listed
   under [Names](README.md#names).
 - First release: the CLI, the library and the shipped data set.
-- The CLI renders the template piped to its stdin, `echo -n '{/sv_SE.person} hihi' |
-  fejkdata`, and takes no path or template as an argument. One newline ending stdin,
-  `\n` or `\r\n`, is dropped. A template of one reference alone, `{/users}`, is the
-  record `users` under `--format`. An argument, or nothing piped in, exits 2.
+- The CLI renders the template on its stdin, `echo '{/sv_SE.person} hihi' | fejkdata`,
+  and takes no operand. A format string keeps every byte, `echo`'s newline included; a
+  JSON template or one reference alone drops one newline ending stdin, `\n` or `\r\n`.
+  One reference alone, `{/users}`, is the record `users` under `--format`. An operand,
+  or nothing piped in, exits 2.
 - Table categories: a category JSON naming a `rows` TSV beside it, with the options
   `key`, `name`, `weight` and `parent`; a path selects a row by key or name,
   `misc.territory[SE]`, and descends to a linked table by name, one path drawing each