Reading an unchanged store property holds an independent synchronous update

[GabbeV]

Describe the bug

An action writes store.saved and stays pending. A later, separate click sets and flushes an independent enabled signal. A memo reads enabled() and the unchanged store.stable property:

const derived = createMemo(() => enabled() && store.stable === "same");

The second update stays pending until the action finishes: latest(enabled) is true, but derived() is still false and isPending(enabled) is true. The action never writes store.stable.

Your Example Website or App

https://s.olid.uk/id/VYa_ygLZSLaM4KBUVcsBtw

Steps to Reproduce the Bug or Issue

1. Click Start held action.
2. Click Set independent signal.
3. Observe derived: false, signal latest: true, and signal pending: true.
4. Click Finish action. Only then does derived become true and the signal stop being pending.

Expected behavior

The second, synchronous update should publish immediately: derived should become true and isPending(enabled) should remain false while the unrelated action is still open.

Platform

• OS: Linux
• Browser: Chromium 153 (Playwright)
• Solid: 2.0.0-rc.10 in the linked playground

[ryansolid]

Confirmed and fixed in #3693 — thanks for the minimal playground.

Root cause: node reads are already key-precise under A29 (a node with nothing staged enters no transaction), but the store's container-level hold gate was not — a deriving pass reading any key of a container with a held fold entered the fold's transaction. Your memo first read store.stable on the second click, while the action's fold was held, so the pass joined the action and the independent enabled write was pulled in with it.

The gate now consults the fold's written-key record for get/has/descriptor reads: a key the action never wrote or deleted is served committed with no entry, so the second update publishes immediately and isPending(enabled) stays false. Reading a key the action did write still holds, as before.

— Claude via Cursor