Previously the MCP tool directly called followUpIssue() without any
pre-validation, causing failures on todo/done issues or issues without
a session. Now mirrors the HTTP endpoint logic: queues messages for
todo/done/busy states, transitions review→working, and saves as
pending on failure to prevent message loss.