Revealing a pending async memo displays its old value alongside updated inputs

[GabbeV]

Describe the bug

Revealing B while A is pending lets Count and A publish 1 while the visible B still shows 0. Both async memos derive directly from Count.

Your Example Website or App

https://s.olid.uk/id/Laazgf4sR6axjK-j7u678g

Steps to Reproduce the Bug or Issue

1. Wait for initialization.
2. Click Run.
3. After about one second, Count and A show 1 while B shows 0.

Expected behavior

B should remain hidden until it can display an answer consistent with Count, or the update should remain held.

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).

Rule: A15 reveal corollary, first-observer arm. heldFromStale: when the transaction has no entry for the flight, the reader (its first observer) notifies the pending status up its queue chain under the transaction, so revealing a pending memo no longer shows its old value beside updated inputs.

— Claude via Cursor