test(mmc-trajectory): ship the regression guards that were only on one machine

plugins/avatasia/mmc-trajectory/.minimax-plugin/plugin.json

@@ -2,7 +2,7 @@
   "schemaVersion": 1,
   "name": "mmc-trajectory",
   "displayName": "会话轨迹",
-  "version": "1.0.0",
+  "version": "1.1.0",
   "description": "按轮次浏览当前会话的模型轨迹：消息流、思考过程、工具调用与结果、token 与耗时统计。",
   "author": "avatasia",
   "icon": "icon.png",

plugins/avatasia/mmc-trajectory/README.md

@@ -6,6 +6,8 @@ Browse the model trajectory of a MiniMax Code conversation: messages, reasoning,
 
 Author: [avatasia](https://github.com/avatasia) · Version: `1.0.0`
 
+Before changing the page, read [docs/LAYERS.md](docs/LAYERS.md): which functional layer a control belongs to, what it may read, and the four questions to answer before implementing a new one. It exists because this page's filter logic grew one feature at a time, and the defects that produced are all traceable to that.
+
 ## Install and use
 
 Copy this entire directory into your active MiniMax Code data directory, including the hidden `.minimax-plugin` directory. By default, `<dataDir>` is the `.minimax` directory in your home folder (`~/.minimax`), so plugins go in `~/.minimax/plugins/`. If you have configured a different data directory, use that directory instead:
@@ -18,11 +20,15 @@ The author directory is only used to group contributions in the community reposi
 
 The page follows the most recent conversation by default and re-reads it every 2.5 seconds, so it stays live while you work; it pauses while the page is hidden. Each read is validated with an HTTP `ETag`: when the session file has not grown, the service answers `304 Not Modified` with no body and the page keeps what it already rendered. An idle tab therefore costs a few bytes per poll instead of the whole trajectory. Use the session picker to switch to any other conversation. No API key and no dependency installation are required — the package is dependency-free and needs no build step.
 
+When the session *has* grown, the poll carries `?since=<cursor>` alongside its validator and the service answers with the tail instead of the whole session: a payload of the same shape plus a `delta` marker, with `turns` holding only the turns that gained records. On a session of 21,000 records that is roughly 20 KB instead of 43 MB. The cursor is the highest `record.index` the page already holds — the same key `raw?index=` answers on — and it travels only with the validator it was taken against, so a session switch or a manual refresh sends the whole payload instead. `stats` and `session` travel whole in every tail: `stats` is an accumulator over all rows, so a tail cannot be added to it. A page that is ahead of the service (which is what a context-generation switch looks like from here) is answered with the whole payload, since a tail from there is empty and an empty tail is indistinguishable from "nothing to add". This saves transfer and the page's parsing, not the service's work — it still reads, parses and serializes the whole session to build the cache entry and to answer `raw`.
+
 ## What it shows
 
 The ledger groups records by turn, following the `turn_id` recorded in the session file. Each record is classified as user, answer, narration, thinking, tool call, tool result, system, or compaction, and each turn header carries that turn's own Token counts and elapsed time. Selecting a record opens a detail panel with summary, raw JSON, tool arguments, tool result, and reasoning, plus a button that hands the record to the Agent's chat input.
 
-**The type chips are the only filter over kinds.** One thing is being filtered — which record kinds are visible — and it is one array in the client, written from exactly three controls: the eight kind buttons, 全部, and 清除筛选. An earlier version also had a row of layer buttons (turn / thinking / call) sitting above the list as presets over those same chips. They were removed, because any preset a reader outgrows becomes a button that contradicts the chips it was supposed to summarise: untick 问答 while leaving 用户 ticked, and the turn button goes dark and claims the conversation is hidden when in fact it was narrowed. One control that cannot drift is worth more than three convenient ones that can. Two further controls cut across kinds instead of over them: a time range, which bounds the ledger to a wall-clock window, and an anomaly filter, whose rules pick out records that are wrong — a failed tool call, a compaction, a turn that never got an answer, an answer that came back empty — rather than records of a particular kind. Neither rewrites the kind array, so every kind chip still answers exactly one question.
+**The type chips are the only filter over kinds.** One thing is being filtered — which record kinds are visible — and it is one array in the client, written from exactly four controls: the eight kind buttons, 全部, 清除筛选, and the anomaly filter. An earlier version also had a row of layer buttons (turn / thinking / call) sitting above the list as presets over those same chips. They were removed, because any preset a reader outgrows becomes a button that contradicts the chips it was supposed to summarise: untick 问答 while leaving 用户 ticked, and the turn button goes dark and claims the conversation is hidden when in fact it was narrowed. One control that cannot drift is worth more than three convenient ones that can. Two further controls cut across kinds instead of over them: a time range, which bounds the ledger to a wall-clock window, and an anomaly filter, whose rules pick out records that are wrong — a failed tool call, a compaction, a turn that never got an answer, an answer that came back empty — rather than records of a particular kind.
+
+**The anomaly filter is the one cut-across control that also rewrites the kind array**, and deliberately so: ticking an anomaly rule calls the same `resetBaseFilters()` the 清除筛选 button calls, which returns kinds to all, clears the search box, drops any brush on the overview strip, and clears the time range. Without that, a reader could tick 工具失败 with 问答 unticked, see nothing, and have no way back except hunting for which of five controls to undo. The cost is stated here because it is a real cost: the chips stop being a filter you keep while you narrow by error — so 「只回答一个问题」 holds for the chips only outside anomaly mode, which is also when they are the only thing still in play. A time range and a search term still never rewrite the kind array.
 
 Naming kinds directly costs one extra click and reaches everything a preset did — tick 用户 *and* 答复 for the conversation, untick both for its absence, and any scattered subset in between, such as only the user's questions or only system records.
 

plugins/avatasia/mmc-trajectory/README.zh-CN.md

@@ -6,6 +6,8 @@
 
 作者：[avatasia](https://github.com/avatasia) · 版本：`1.0.0`
 
+改动这个页面前，先读 [docs/LAYERS.md](docs/LAYERS.md)：一个控件属于哪一层、能读什么、以及实现新功能之前必须先答的四个问题。它存在的原因是这个页面的筛选逻辑是一次加一个功能长出来的，产出的缺陷都能追溯到这一点。
+
 ## 安装与使用
 
 把整个目录（含隐藏的 `.minimax-plugin`）复制到你的 MiniMax Code 活跃数据目录下。默认情况下 `<dataDir>` 是家目录下的 `.minimax`（即 `~/.minimax`），所以插件放在 `~/.minimax/plugins/`。如果你配置过其它数据目录，请用那个目录：
@@ -22,7 +24,9 @@
 
 台账按 `turn_id` 把记录分组，轮次划分完全依据会话文件中记录的 `turn_id`。每条记录被归类为用户、答复、过程、思考、工具调用、工具结果、系统或压缩；每个轮次表头带该轮自己的 token 计数与耗时。选中任意记录会打开详情面板，含摘要、原始 JSON、工具入参、工具结果与思考内容，并提供一个把该记录内容送回 Agent 对话输入框的按钮。
 
-**类型选项是唯一针对「类型」的筛选。** 被过滤的始终只有一件事——哪些记录类型可见——客户端里它是同一个数组，只由三个控件写入：八个类型按钮、「全部」和「清除筛选」。早期版本在列表上方还排了一行图层按钮（轮次 / 思考 / 调用），作为同一批类型选项的快捷预设，已经删除。任何读者能走偏的预设，最终都会变成一个与它本该概括的选项自相矛盾的按钮：只取消「过程」而保留「用户」，轮次按钮就熄灭并声称整个对话已隐藏，而实际上你只是收窄了它。一个不会跑偏的控件，比三个方便的控件更值钱。 另外两个控件并不在类型之上做筛选，而是横跨类型：时间区间把台账限制在一个墙上时钟窗口内；异常筛选挑出的是「出了问题的记录」—— 工具失败、上下文压缩、整轮没有答复、答复是空的 —— 而不是某一类记录。两者都不改写类型数组，所以每个类型选项始终只回答一个问题。
+**类型选项是唯一针对「类型」的筛选。** 被过滤的始终只有一件事——哪些记录类型可见——客户端里它是同一个数组，只由四个控件写入：八个类型按钮、「全部」、「清除筛选」，以及异常筛选。早期版本在列表上方还排了一行图层按钮（轮次 / 思考 / 调用），作为同一批类型选项的快捷预设，已经删除。任何读者能走偏的预设，最终都会变成一个与它本该概括的选项自相矛盾的按钮：只取消「过程」而保留「用户」，轮次按钮就熄灭并声称整个对话已隐藏，而实际上你只是收窄了它。一个不会跑偏的控件，比三个方便的控件更值钱。 另外两个控件并不在类型之上做筛选，而是横跨类型：时间区间把台账限制在一个墙上时钟窗口内；异常筛选挑出的是「出了问题的记录」—— 工具失败、上下文压缩、整轮没有答复、答复是空的 —— 而不是某一类记录。
+
+**异常筛选是唯一一个会改写类型数组的横跨控件，而且是故意的**：勾选任一异常规则时，它调用的是「清除筛选」按钮调的那个 `resetBaseFilters()`，把类型恢复为全选、清空搜索框、丢掉总览条上的刷选、并清掉时间区间。否则读者会勾上「工具失败」而「问答」还取消着，看到一片空白，却不知道该回去改哪一个——一共五个控件可以撤销。代价必须写出来，因为它是真代价：异常模式下类型选项就不再是「一边保留一边按错误收窄」的筛选器 —— 所以「每个类型选项只回答一个问题」这句话只在异常模式之外成立，而异常模式之外也正是类型选项唯一还在起作用的时候。时间区间和搜索词仍然不改写类型数组。
 
 直接点名类型只多花一次点击，却能到达预设原本覆盖的全部范围：勾选「用户」**和**「答复」就是对话，两个都取消就是没有对话，中间任意散落的子集（只看用户提问、只看系统记录）同样可以。