wren node: untrained targets left out of the prompt, a read beside a held-back set goes on whole

docs/reference/node-types.md

@@ -409,7 +409,8 @@ goes unanswered.
 `reply` says what was set, as "Kitchen light on, living room heating to 21 °C
 in 5 minutes.", and answers a read from the target's current value, as
 "Outdoor temperature is 6.2 °C.", with `apply` off too, since a read writes
-nothing. A read of a target nothing has written yet goes on to `unhandled`. Each record in `actions` contains `message`, `value`,
+nothing. A read beside a set that `apply` holds back is not answered, so the
+whole command goes on. A read of a target nothing has written yet goes on to `unhandled`. Each record in `actions` contains `message`, `value`,
 `applied`, `delay_s`, `call` as wren writes it, such as
 `set(kitchen_light, true)`, and that call's `confidence`. Keep `apply=false`
 while checking how the model reads commands.
@@ -421,8 +422,8 @@ Redis, and not otherwise.
 A model knows the targets it was trained on: their names, types, `values`,
 `range`, descriptions and which are readings. A target wired since, or
 described otherwise since, is one it never learnt. The node then reads
-degraded, naming such targets and asking for the model to be retrained, and a
-call on one is never applied. wren's demo model knows the 20 targets of its
+degraded, naming such targets and asking for the model to be retrained. They
+are left out of the model's prompt, so a command on one goes on. wren's demo model knows the 20 targets of its
 [demo home](https://github.com/stroblme/wren/blob/main/wren/home.json), so
 it runs without that warning only on ports named and described as there. A
 `model` the artifact store does not have or cannot read also reads degraded,