lyuksovannyy b05d1a274c Never match a date separator as a summary anchor ...

Date separators are local MessageObjects that live in the same
ChatActivity.messages list as real messages, and ChatActivity builds them
with messageOwner.id left at 0 (their stable ids come from a separate
dateObjectsStableIds space, so they never collide with injected cards).

find_index_for_anchor scanned for an exact id match without requiring a
positive id, so looking up anchor 0 returned the index of the first
separator and would have placed a card against a divider rather than a
message. loaded_message_ids had the matching flaw: it recorded the
separators' 0, which made a summary with anchor id 0 look restorable.

Reject non-positive anchors outright and keep separators out of the loaded
id set. Every real chat interleaves separators, so the harness now models
them: they must not be picked as the insertion point, must not satisfy an
anchor-loaded check, and summaries anchored on real messages must still
restore correctly with separators in between.

2026-09-19 16:54:25 +02:00

..

bundle.py

Initial commit

2026-09-12 02:03:47 +00:00

devclient.py

Initial commit

2026-09-12 02:03:47 +00:00

release.py

Fall back to the runner token when the org secret is absent

2026-09-13 00:20:58 +02:00

verify_bundle.py

Never match a date separator as a summary anchor

2026-09-19 16:54:25 +02:00