2.0.0-beta.20: `latest()` only works once on memos

[AFatNiBBa]

Describe the bug

If you cause a memo to mutate in between two usages of latest(), the second one will ignore the changes

Your Example Website or App

https://stackblitz.com/edit/solidjs-templates-eanyzwnd?file=src%2FApp.tsx

Steps to Reproduce the Bug or Issue

1. Navigate to the example link
2. Press the "Test" button
3. Look at the object that's being logged into the console

Expected behavior

When running

const v1 = m();       // 1
s(1);
const v2 = m();       // 1
const v3 = latest(m); // 3
const v4 = m();       // 1
s(2);
const v5 = m();       // 1
const v6 = latest(m); // 3 (This has not updated!)
flush();
const v7 = m();       // 5
console.log({ v1, v2, v3, v4, v5, v6, v7 });

I expected this to be logged

{
    "v1": 1,
    "v2": 1,
    "v3": 3,
    "v4": 1,
    "v5": 1,
    "v6": 5,
    "v7": 5
}

but I got this instead

{
    "v1": 1,
    "v2": 1,
    "v3": 3,
    "v4": 1,
    "v5": 1,
    "v6": 3, // Wrong!
    "v7": 5
}

Screenshots or Videos

No response

Platform

• OS: Windows
• Browser: Edge (The Chromium one)
• Version: 150.0.4078.65

Additional context

No response

[ryansolid]

Thanks for the clear repro — confirmed and fixed. There were actually two staleness holes here. The dirty queue keeps a 'marked' memo that's only reset when the queue flushes, so the second s(...) write never re-flagged the memo as dirty for mid-tick reads — the first latest(m) marked the queue, computed the speculative value, and every latest(m) after the next write answered from that cached value until flush(). Separately, an untracked latest() call (like in an event handler) had no reading context to trigger the mid-tick pull at all, so the internal shadow computed backing latest() could stay stale even once it was properly re-marked. Both are fixed: writes now invalidate the queue's mark memo, and the latest() read path explicitly pulls its shadow up to date before answering. Your exact sequence now yields { v1: 1, v2: 1, v3: 3, v4: 1, v5: 1, v6: 5, v7: 5 } and is pinned by a regression test. Shipped in 2.0.0-beta.21.