consolidate-a-scattered-threadlisted

# Consolidate a scattered thread ## Purpose Long-running problems fragment: the truth about one bug ends up spread across a dozen JIRA tickets, PRs, commits, and mailing-list threads, each holding a piece. When a maintainer says *"unclear where to further that conversation,"* the graceful move is not to add one more reply to one more ticket — it's to **do the consolidation for them**. Traverse the whole link graph, read everything, and hand back a map that says where each distinct sub-concern belongs. That turns "where do I continue?" into a delivered artifact the maintainer can act on immediately. This is a communication/navigation skill, not an execution one: its deliverable is a map, not a diff. Its value is that a scarce maintainer no longer has to hold the whole tangle in their head — you did, and you handed it back untangled. ## When to use - A maintainer explicitly signals the discussion has no clear home ("unclear where this should live", "where do we track this?"). - A single problem is visibly spread across many linked tickets / PRs / commits / mail and the concerns in it are conflated. - You've read enough of the graph to see distinct sub-threads the participants haven't separated. ## When NOT to use The problem lives in a single ticket, or nobody has signalled confusion about where it belongs — then just reply in place; an unasked-for map is noise, not help. ## The practice (checklist) - [ ] **Traverse the link graph.** Walk every linked ticket (`ji