v0.35.2 lwconf, doc and deploy update

doc/architecture.md

@@ -254,8 +254,8 @@ never a key:
 - `value`, `at` and `group` read a node's value and sort problems by node.
 
 The engine's calls take strings (`lwconf.js` writes objects as JSON) and
-answer `{"value": ...}` or `{"error", "path", "pipeline", "node", "key"}`, as
-far as the engine places the refusal:
+answer `{"value": ...}` or `{"error", "path", "pipeline", "node", "key",
+"ask"}`, as far as the engine places the refusal:
 
 - `schema()`: what `lw --schema` prints.
 - `preset(name, values, dirs)`: a preset's pipelines; `values` maps a key to
@@ -273,7 +273,8 @@ far as the engine places the refusal:
   - `set` (`node`, `key`, `values`), `unset` (`node`, `key`)
 - `dirs` answers whether a path a preset names is a directory,
   `{"/var/log/app.log": false}`; unanswered, a path ending in `/` is one, one
-  with a glob a pattern, and any other is refused at `path`.
+  with a glob a pattern, and any other is refused at `path` with `ask` naming
+  it: answer it in `dirs` and call again.
 - Pipelines are a JSON list in the file's shape (`name`, `flow`,
   `plugin_sources`, `plugin_sinks`); a misspelled key is refused. A node is
   `{role, id, index}`: a source's or sink's id, a filter's index.

doc/cli.md

@@ -457,8 +457,9 @@ WebAssembly; `t` runs them under the screen and shows what flows.
 
 - Start: the pipelines `lw` would run with the same options (`-c FILE`,
   pipeline flags, `LOGWISP_SOURCE`, a discovered file); with none but the
-  built-in pipe, the preset menu (or `empty`). A pasted `lw` command line
-  replaces the pipelines, in the preset menu too.
+  built-in pipe, the preset menu (or `empty`). A pasted `lw` command line of
+  pipeline flags, or the `lw` part of `... | lw ...`, replaces the
+  pipelines, in the preset menu too.
 - Screen: the pipeline bar on top; SOURCES, FLOW and SINKS side by side
   from 64 columns, stacked below; each source and sink a tinted bar with its
   type, whether it listens or dials, and a summary; the four flow stages in

doc/configuration.md

@@ -172,8 +172,8 @@ Options, each as type and default:
   timestamp; the `raw` format shows neither.
 - `include_stats` (bool, `false`): add `type = "heartbeat"`, `beat_count` and,
   from the second beat, the measured `interval_ms` as fields.
-- `format` (string, `txt`): `txt`, `json` or `raw`; no effect: heartbeats go
-  through the flow's `format`.
+- `format` (string, `txt`): `txt`, `json` or `raw`, kept for older files:
+  heartbeats go through the flow's `format`.
 
 Heartbeats are ordinary entries with source `heartbeat` and level `INFO`. They
 are generated after the flow's filter and rate-limit stages, so filters do not

doc/networking.md

@@ -209,8 +209,8 @@ preamble, headers, and entry encoding.
   - `PROXY header: …` — malformed, too long, or incomplete after 10 s.
   - `PROXY header from a peer outside proxy_from` — at the first read, after
     the connection opened: list the proxy in `proxy_from`.
-- `acl: allow entry "...": not of the listener's family` at startup — an IPv4
-  entry on an IPv6 `host`, or the reverse: each family's listener takes its own.
+- `acl: allow entry "...": IPv4, and the listener's host is IPv6` at startup,
+  or the reverse: each family's listener takes its own.
   Behind `proxy_from` or `trusted_proxies`, `allow` and `deny` take both;
   `proxy_from` its own.