docs(desktop): note hex64 assumption behind working-thread key split

Co-authored-by: Taylor Ho <taylorkmho@gmail.com>
Signed-off-by: Taylor Ho <taylorkmho@gmail.com>
This commit is contained in:
npub1223z34hd7vtwc6qj4s7flsxkj644nlre2nthu7lrrmkumhu3xddsrx9r6w
2026-07-06 21:35:45 -07:00
co-authored by Taylor Ho
parent 9ebae61c1c
commit 877d369a11
@@ -364,7 +364,8 @@ export const ChannelPane = React.memo(function ChannelPane({
// Thread ingress working badges: derive once per typing update, keyed on a
// stable sorted string so the Set identity (and every memoized row below it)
// only changes when the set of working threads changes — not on each 1s
// typing prune tick or entry-array recreation.
// typing prune tick or entry-array recreation. Splitting on "," is safe
// because thread head ids are hex64 event ids and can never contain commas.
const workingThreadHeadIdKey =
threadScopedBotTypingHeadIdKey(botTypingEntries);
const workingThreadHeadIds = React.useMemo<ReadonlySet<string>>(