docs: clarify evidence applicability and boundary limitations

docs/javascript-application-workflows.md

@@ -412,8 +412,13 @@ when the object is an array element, nested inside mixed object/array
 containers, or assigned to a previously declared identifier. Saving the getter
 result in an alias does not make its old field values immutable. Known array
 indices include holes; an element after a spread has only a minimum possible
-index. Unrelated properties and known array prefixes remain precise, and a
-getter read without a write does not invalidate the receiver's fields.
+index. For these returned-reference writes, unrelated properties and known
+array prefixes remain precise. Getter invocation has separate effects: a
+property read can invoke a getter that mutates its receiver without any write
+through the returned value. Current analysis can miss these invocation effects
+and retain a stale receiver-field literal
+([#6669](https://github.com/morluto/rea/issues/6669)); absence of a later write
+does not establish getter purity.
 Nested callable returns are not assigned to their parent callable. Projected
 graph observations carry source ranges but never source text.