[bug?] Short link on share.plannotator.ai is not updated with new annotations.

[grncdr]

The workflow I'm using with teammates right now:

1. team mate sends me a share.plannotator.ai shortlink
2. I add some annotations
3. Click the "export" button
4. Send the short link back to my team mate
5. We realise it's the exact link they sent me in the first place.
6. Remember that the shortened link is "stuck" with the original URL: it doesn't include my annotations.
7. copy the plan markdown
8. paste that into a file
9. open that with plannotator locally
10. manually re-annotate
11. Click "export" again
12. Finally get a link my team mate can use to import my annotations.

It would be super cool if the above worked at step 3 & 4.

[backnotprop]

I will make sure this process works. By the way, there's a beta of a more interactive share process - this one will allow for better importing and exporting as well

https://room.plannotator.ai

[grncdr]

Thanks for the reply, and for plannotator. It's been a massive upgrade for my workflow.

Regarding room.plannotator.ai, we tried it already, but it has a different problem: it's totally disconnected from the LLM harness (or I missed how to make it work). I'd love it if the default local plannotator had a "create room" button that creates a room and subscribes to annotations from that room automatically.

[backnotprop]

PR #1425 fixes the stale-snapshot bug: an imported short link remains visible through initial hydration, then disappears after annotations or other represented content change, so Export cannot send the original immutable paste as if it contained the edits. The fresh full hash URL remains correct, and creating a replacement short link creates a distinct paste without modifying the original.

One limitation remains explicit: for small markdown plans, Export currently hides Create short link while the full URL is at or below the 2048-character threshold. Those sessions get a correct fresh full URL but cannot yet mint a new short link from Export, so the literal short-link return workflow in this issue is only partially resolved. Follow-up #1427 tracks that focused product change. Existing links and payload formats remain compatible.