Everything I could decide myself is decided. What's left needs
you. Each one has a recommendation from Fable — if you agree, pick it and
press Done. "I'm not sure" is a real answer and becomes work for me.
You don't need to open the session — pressing Done sends your answer back and it picks up.
1The unified-thread item you raised 08-29 (work-order links open the person's WHOLE thread, highlighted): you asked to be looped in on the boundary question before anyone builds. What defines the START and END of the highlighted exchange for a given work order?
Fable recommends: Contiguous span: from the first WO-pertaining message to the last, plus everything inside the same conversation segment (the 18-hour idle-gap rule from #6534) — one solid band It reuses the segmentation rule you approved in #6534, satisfies your one-band rule from #6537, and a misclassified message inside the span still shows — your own reason for full-thread-plus-highlight over a hard filter. Tried first, unsuccessfully: Scoped the mechanics: Message.sourceConversationId, messagePertainsToWorkOrder, the #6534 idle-gap segmenter and #6537's coalesceHighlightRuns all exist — the boundary rule is the only open design input, exactly the question you said to bring to you. NOT auto-resolving this one: you explicitly reserved it.