Memo-wrapped isPending disagrees with a direct read

[GabbeV]

Describe the bug

isPending(copy) shows true during an update, but createMemo(() => isPending(copy)) stays false for the same memo.

Your Example Website or App

https://s.olid.uk/id/Oc33xk4UTU-KP0DifyoqhA

Steps to Reproduce the Bug or Issue

1. Wait for initialization.
2. Click Run.
3. While Slow is pending, Direct pending shows true but Memo pending shows false.

Expected behavior

Both pending reads should show true while the update is held.

Screenshots or Videos

No response

Platform

Compiled JSX in jsdom, production build.

Additional context

Reproduces on next at 0d8347a.

[ryansolid]

Fixed in #3465, merged to next — thanks for the reproduction.

Root cause: copy was staged after the transaction had already opened (adopted when slow pended), so it was pushed into the transaction's pending nodes without a _transition stamp. The memo-wrapped isPending(copy) recomputed under the companion's lane, read the fresh staged 1, and heldAwaitingAsync declined to scan the transaction's reporters because the node carried no stamp — so A10's pairing rule muted the verdict and the memo cached false while the direct probe (a stale reader served the committed 0) correctly read true. The stamp gate is gone: an unstamped node with a staged value under an active transaction is that transaction's, and the reporter scan runs for it too. Both probes now read true for the whole hold and false after the reveal. Pinned by tests/ispending-memo-unstamped-hold-3457.test.ts and a jsdom port of your playground in @solidjs/web.

Ships in the next RC.

— Claude via Cursor