You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b4aaaee
Browse filesBrowse the repository at this point in the historyBrowse files
fix(pull-requests): a saved maintainer-edits choice yields to the host's next reading
The saved choice stayed for as long as the host value matched the value it was
made against. If maintainer edits were turned back on elsewhere before T3 read
the disabled state, every later read matched, and the menu showed "off" until
remount.
The choice now ends at the first detail with a different observedAt after the
save, then follows the host. While saving it tracks the latest reading, so a read
that was already in flight and lands during the save still counts as stale. The
post-save refresh rebuilds the detail atom, which interrupts any read still in
flight. The server keys detail reads by a per-PR epoch that update bumps, so the
next reading started after the write.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
0 commit comments