fyaic · veil-chow-fyaic · Sep 8, 2026 · Sep 8, 2026
@@ -93,11 +93,11 @@ to distinguish setup, pending advice and observed results; stop in both tasks
 to stop both directions. These are natural-language requests, not slash commands
 or a separate control service.
 
-No browser is required for collaboration. The optional
-[setup-text helper](https://fyaic.github.io/threadmesh/) saves manual template
-editing only: it does not run agents, connect tasks, show live status or stop
-them. You still paste/send both setups in Codex. It is neither a demo nor a
-hosted version of ThreadMesh.
+The website helper has been removed. The product target is **install once,
+choose which tasks may collaborate, then work normally in your agent**. The
+manual workflow above is an experimental fallback, not that finished install
+experience. Desktop plugin installation and adoption by existing tasks remain
+unverified; a working CLI sample does not close this gap.
 
 Another real case: A changed an API contract; original B updated its own client
 and tests, retaining the earlier timeout and cursor-encoding decisions.

@@ -84,9 +84,9 @@ B 早已知道按钮名称不能改。明确配对后，只向 A 提出普通业
 已发送。在任务里说“检查 ThreadMesh 状态”，区分本端设置、待发建议和已观察到的结果；
 要停止双向协作，在两个任务中分别说停止。这些是自然语言请求，不是斜杠命令或独立控制服务。
 
-协作不需要浏览器。可选的[设置提示词辅助工具](https://fyaic.github.io/threadmesh/)
-只省去手工改模板：它不运行 Agent、不连接任务、不显示实时状态，也不能停止它们。
-你仍需在 Codex 中分别粘贴发送。它不是功能演示，也不是 ThreadMesh 云端版本。
+网页辅助工具已经移除。产品目标是**安装一次，选择允许协作的任务，然后在 Agent 中
+正常工作**。上面的手动流程只是实验性备用路径，不等于已完成的安装即用体验。
+桌面插件安装后接入已有任务仍未验收；CLI 示例能运行，不能代替这个结果。
 
 另一个真实案例：A 修改 API 约定后，原 B 自己更新客户端和测试，同时保留此前的
 超时、特殊游标编码约定。[页面检查与实际 API 协作记录 →](docs/09-reviews/2026-09-08-pairing-helper-acceptance.md)

@@ -16,12 +16,13 @@ policy layer; A2A, Cotal, ACP, or harness-native APIs may supply transport.
 **Current order, confirmed by the user:** independent first use → visible local
 status and stop → demonstrated relay savings → a real user case → DeepSeek and
 quota handoff. Work happens in original local agent conversations. The website
-is an optional setup-text utility, not the product runtime, control plane or
-demonstration. Do not expand it into a dashboard to substitute for native value.
+helper is removed, including its code, browser-only tests and deployment workflow.
+**Install once → select allowed tasks → ordinary work → useful receiver result**
+is the first-use target. Manual prompt setup is a fallback, not completion.
 
 | Order | User outcome | Remaining acceptance |
 |---|---|---|
-| 1 | An ordinary Codex desktop user gets a useful result without maintainer help | One independent user's original pair, using the public guide; record actual setup steps, first blocker and B's own correct result. Maintainer and subagent runs do not count. |
+| 1 | Install ThreadMesh and get a useful result inside Codex without maintainer help | A supported installation path, readable activation and explicit task selection, with no website/form, source checkout, hand-edited JSON or long setup-prompt relay. Then verify an independent user's pair and B's own correct result. Existing-task adoption must be tested separately from new-task pickup. |
 | 2 | Know what happened and stop safely | In-task readiness/pending/result/stop explanations; never confuse idle with configured or sent with done. Guidance is being improved; persistent receipt/control and simultaneous-input safety remain open (#135/#136). |
 | 3 | Less relaying than native-only use | A small matched case counts setup actions, manual relays, correct edits and unwanted contact. No new benchmark framework; keep optional guidance small if it adds no benefit. |
 | 4 | Others can understand and reproduce the value | A consented real native recording and independent case, followed by relevant community sharing. No recreated conversation or promised star count. |
@@ -34,11 +35,10 @@ separate open tracks, not new prerequisites for this desktop-first alpha.
 
 ### Completed evidence — do not repeat as a new gate
 
-**Setup simplification shipped:** the bilingual [no-install pairing helper](https://fyaic.github.io/threadmesh/)
-generates separate setups from two chat links and a chosen topic. Users still
-paste/send and wait for both confirmations; it is not an automatic connection.
-Browser checks and a second original-task API/client case passed with the
-generated prompts. [Actual screenshot and receiver-owned results](docs/09-reviews/2026-09-08-pairing-helper-acceptance.md).
+**Retired experiment:** the website generated setup text but did not meet the
+installation-first requirement. Its source and deployment are removed; the
+[historical API/client result](docs/09-reviews/2026-09-08-pairing-helper-acceptance.md)
+remains valid bounded evidence, not a current website feature.
 
 **Completed this slice:** [public workflow + chat-link pairing](docs/09-reviews/2026-09-08-native-deep-link-acceptance.md),
 both original tasks enabled, ordinary request triggering A's chosen advice,

@@ -9,12 +9,11 @@ a new model, an MCP server or a polling daemon.
 
 ## No-terminal workflow
 
-**Work in the original Codex tasks. No website needs to stay open.** The setup
-below is an instruction to each task, not registration with a hosted service.
-If editing the template is inconvenient, the optional
-[setup-text helper](https://fyaic.github.io/threadmesh/) prepares the two strings
-locally in your browser. It cannot observe or control collaboration and is not
-a live demo. [What the helper was actually tested for](../09-reviews/2026-09-08-pairing-helper-acceptance.md).
+**Work in the original Codex tasks.** The website helper has been removed from
+the product and source. The manual setup below remains an experimental fallback,
+not the intended install-once experience. The skill-only plugin is packaged,
+but installation followed by adoption in existing tasks is not yet validated.
+No website, form, hosted registration or new account is required.
 
 Choose two disposable existing Codex tasks with useful prior context. For
 example, a brand task maintains approved product facts; a website task already

@@ -1,7 +1,13 @@
 # Pairing helper and original-task API handoff
 
-**Outcome:** the [no-install pairing helper](https://fyaic.github.io/threadmesh/)
-is live. Its generated setup was used in the original two Codex validation
+**Retired experiment:** the website was removed from source and deployment on
+September 8 at the user's request. It only generated setup text and did not meet
+the install-and-use product goal. This record preserves the tests as history,
+not instructions to visit a live service. The removed source is recoverable at
+[the pre-removal revision](https://github.com/fyaic/threadmesh/tree/a8c66e2472fd78db447ee4c8eed17c4453ca76a2/web/connect).
+The native skill, original-task results and private evidence are retained.
+
+**Original outcome:** its generated setup was used in the original two Codex validation
 tasks. After an ordinary API change request, A chose to contact original B;
 B updated its own client and tests while preserving earlier decisions.
 
@@ -13,7 +19,7 @@ native messaging and continuation; ThreadMesh supplies optional scoped guidance.
 
 ![Actual published pairing helper, Chinese desktop view](../assets/pairing-helper-public.png)
 
-This is an actual screenshot of the published helper with empty inputs, not a
+This is a historical screenshot of the then-published helper with empty inputs, not a
 native handoff screenshot or a staged conversation. The page accepts two copied
 local chat links, a limited topic, advice mode and explicit consent. Three topic
 presets cover product facts/copy, API/client changes and retained preferences.

@@ -8,8 +8,10 @@ Date: 2026-09-07. Starting revision: `19a9b13`.
 The controlled public-source original-pair gate below is **complete**, including
 the [API/client case](../09-reviews/2026-09-08-pairing-helper-acceptance.md).
 Remaining immediate work is independent first use and understandable status/
-stop in original Codex tasks. The website is optional template assistance,
-not a local agent demonstration or a control service. No new website platform.
+stop in original Codex tasks. The website experiment is removed from source
+and deployment. The current first-use target is installation, explicit task
+selection and ordinary work without a web form or long setup-prompt relay.
+The manual recipe remains a fallback, not the installation acceptance.
 
 Audience correction: Codex is the primary client. Do not split the critical path
 equally across Codex and ZCode, or require Codex users to install Pi. A Codex-only

@@ -2,8 +2,10 @@
 
 ## Current product update — 2026-09-08
 
-**Local native work is the product entry; the website is optional template
-assistance.** Follow the [new ordered acceptance](../../ROADMAP.md#active-priority--existing-desktop-clients-2026-09-08):
+**Install-and-use local collaboration is the product target; the website helper
+has been removed from source and deployment.** The manual recipe remains only
+an experimental fallback. Plugin installation and existing-task adoption are
+still unverified, not replaced by a form or CLI sample. Follow the [new ordered acceptance](../../ROADMAP.md#active-priority--existing-desktop-clients-2026-09-08):
 independent first use → visible local status/stop → measured relay savings →
 real user case → DeepSeek and quota continuation. No independent GUI success,
 persistent desktop control service or native-only advantage is claimed.
@@ -19,11 +21,9 @@ this is not an instant or generally reliable state service. [Result and limits](
 
 ### Last completed evidence
 
-**The no-install pairing helper is now public:** [open it](https://fyaic.github.io/threadmesh/),
-paste two chat links and choose a topic; copy the separately generated setups.
-Chinese/English, browser interaction and clipboard-failure handling were tested.
-Users still paste/send both setups themselves. The page neither reads chats nor
-connects tasks. Its exact generated prompts also passed a second original-task
+**Retired website experiment:** its source/deployment and website-only tests are
+removed at the user's request. Historical browser evidence is retained, not
+offered as a current entry. Its exact generated prompts passed a second original-task
 case: A chose to send an API change; B updated its own client and tests while
 retaining timeout/encoding decisions. Business handoff: about 70 seconds;
 setup separately 31/23 seconds. Both stopped. [Screenshot, tests and case evidence](../09-reviews/2026-09-08-pairing-helper-acceptance.md).

@@ -5,7 +5,7 @@ adoption or proof of incremental value over the host's native capability.
 
 | Recent case | Public record | Retained private originals |
 |---|---|---|
-| Browser pairing helper + original Codex API receiver, passed | [Actual helper screenshot, generated setup and 70-second API handoff](../09-reviews/2026-09-08-pairing-helper-acceptance.md) | Generated prompts and selected original setup/business/stop turn items |
+| Original Codex API receiver, passed; website helper since removed | [Historical setup screenshot and 70-second API handoff](../09-reviews/2026-09-08-pairing-helper-acceptance.md) | Generated prompts and selected original setup/business/stop turn items |
 | Codex public workflow + chat-link pair, passed | [Actual setup, 61-second business handoff, B's own diff and final stop](../09-reviews/2026-09-08-native-deep-link-acceptance.md) | Original selected setup/business/stop App Server turn items and verified artifacts |
 | Codex desktop prior-context pair | [Actual exchange, B's diff and reduced audit](codex-native-2026-09-07/README.md) | Complete A/B native exports, original tasks and files |
 | Codex public-entry readiness attempt, not accepted | [Recovered results, rejected inventory limits and unchanged artifacts](../09-reviews/2026-09-07-native-public-entry.md) | Empty desktop reads and recovered official App Server turn records retained separately |

@@ -7,10 +7,10 @@
 
 ## 免终端工作流
 
-**直接在原来的 Codex 任务中工作，不需要保持任何网页打开。** 下面的设置是发给
-各任务的指令，不是在云服务中注册。不方便手改模板时，可选的
-[设置提示词辅助工具](https://fyaic.github.io/threadmesh/)只在浏览器里生成两段文字，
-不能观察或控制协作，也不是实时演示。[它实际验证了什么](../09-reviews/2026-09-08-pairing-helper-acceptance.md)。
+**直接在原来的 Codex 任务中工作。** 网页辅助工具已从产品和源码中移除。
+下面的手动设置只保留为实验性备用路径，不是目标中的“一次安装即可使用”。
+Skill-only 插件已有打包结构，但安装后接入已有任务仍未完成验证。
+不需要网页、填表、云端注册或新账号。
 
 选择两个已有上下文、没有业务副作用的 Codex 测试任务。例如，一个维护品牌信息，
 另一个维护网页，且已经约定按钮名称必须保留 **Create my workspace**。