Existing and newly revealed latest readers display different values

[GabbeV]

Describe the bug

A newly revealed call to value() displays 1 while an existing call to the same getter still displays 0. value calls latest(count); its async derivation is still pending.

Your Example Website or App

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

Steps to Reproduce the Bug or Issue

1. Wait for initialization.
2. Click Run.
3. After half a second, Late shows 1 while Value and Details still show 0.

Expected behavior

The existing and newly revealed calls to the same latest getter should display the same published value.

Screenshots or Videos

No response

Platform

• OS: Windows
• Browser: Firefox

Additional context

Reproduces on next at 0d8347a.

[ryansolid]

Fixed in 5fa224a via #3479 (GabbeV hold-consistency batch 2).

Ruling applied: a held lane is a micro-transition from the outside — a render effect off the lane is a stale reader of it and sees the committed value, publishes now, entangles nothing, and re-runs at the release; latest() follows the same rule. readsHeldCommitted (lanes.ts) from read()'s override arm and latestRead; the release re-run rides the lane's render queue. A follow-up commit on the PR also stages an optimistic derivation as an override.

— Claude via Cursor