fix(journal): re-publish only changed declarations

topoSortAffected followed declared dependencies even when they were not in the affected set, so reevaluateDependents re-evaluated and re-published variables that had not changed. This could also overwrite a value just set via /set with the declaration's own expression.

docs/variable-store-plan.md

@@ -109,14 +109,16 @@ The items below are still open.
   (#1) for declarations/modifiers and through `dispatchError` for `/set` and
   `/roll`.
 
-### 7. `topoSortAffected` re-evaluates untouched declarations — low
+### 7. `topoSortAffected` re-evaluates untouched declarations — ✅ fixed
 
 - **Where:** in `var-reactivity.ts`, the visit condition
   `affected.has(dep) || declExprs.has(dep)` pulls declared dependencies that are
   not in `affected` into the result.
 - **Symptom:** `reevaluateDependents` re-evaluates and re-publishes variables
-  that did not change. Mostly harmless, but noisy.
-- **Fix:** only visit/topologically order keys in `affected`.
+  that did not change. Mostly harmless, but noisy — and a re-evaluated
+  declaration could overwrite a value that had just been `/set`.
+- **Fixed:** the visit condition now only follows dependencies in `affected`,
+  so a cascade re-evaluates exactly the changed variable's dependents.
 
 ### 8. Failed `initReactivity` leaves partial state — ✅ fixed