mirror of
https://github.com/block/buzz.git
synced 2026-08-18 06:50:31 +02:00
DuncanandWill Pfleger
67045ebbfb
event_is_reply accepted any value in the reply marker's event-id slot, but ingest only honors a marker when the id is exactly 64 ASCII-hex chars. A tag like ["e","bad","","reply"] is stored top-level by ingest yet read as a reply by the workflow, so a trigger_is_reply == false workflow wrongly skipped it. Extract the root/reply marker parse into a shared buzz_core::nip10::parse_thread_markers, gated on the same 64-hex validity. Both the relay ingest resolver and the workflow trigger_is_reply predicate now call it, so a malformed id can no longer diverge the two. Also replaces an argument-free format! in the live e2e probe with a plain string. Co-authored-by: Will Pfleger <pfleger.will@gmail.com> Signed-off-by: Will Pfleger <pfleger.will@gmail.com>