Rename the entire zulip topic when an MCP issue is renamed. Fixes #1228.

[ghost]

See comment here. Note that I don't have a local dev instance and haven't been able to verify this change myself.

[Mark-Simulacrum]

Thanks! My guess is this is an API change upstream -- I don't recall seeing https://zulip.com/api/update-message#parameter-propagate_mode before. But this seems like the right setting.

[ghost]

I think I may have misunderstood this bug possibly, I added an additional comment on #1228. I think the actual issue is that renaming the topic works but would end up breaking the link left on the MCP?

[ghost]

@Mark-Simulacrum I'm not 100% sure this should be merged based on my last comment, I think my fix may have been premature. (sorry 😿)

[Mark-Simulacrum]

I think this is the right fix, it may just be incomplete -- we definitely want to update the full thread on Zulip, but it may also be the case that the GitHub link to the Zulip topic is not currently updated. I suspect that should just require clicking through the 'stub' thread left by the renaming though; not really different to today.

[ghost]

Ok, cool. I'm also reading through Resolving topics breaks links by changing the topic name! and Provide permalinks to reference streams, topics and messages. right now.

I wonder if just having an additional comment posted by rustbot on the github issue would be sufficient? Editing the original comment with an updated link would be nice, but would also be trickier.

[Mark-Simulacrum]

An additional comment seems OK to me.