mmc-trajectory: 退役记录索引、落下来鲜度层、总览条按像素列聚合，并从段格式里去掉两个只写不读的字段

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

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

plugins/avatasia/mmc-trajectory/README.md

@@ -4,7 +4,7 @@ English | [简体中文](README.zh-CN.md)
 
 Browse the model trajectory of a MiniMax Code conversation: messages, reasoning, tool calls and their results, Token usage, and per-turn timing.
 
-Author: [avatasia](https://github.com/avatasia) · Version: `1.1.0`
+Author: [avatasia](https://github.com/avatasia) · Version: `1.2.0`
 
 ### Before you change this page
 
@@ -131,6 +131,7 @@ The runtime database is opened in read-only mode. If it is missing, unreadable,
 - A single `messages.jsonl` is read up to 64 MB. Larger sessions are truncated and the page says so.
 - The ledger does not use virtual scrolling; every rendered row is a real element. The page therefore opens on the newest 200 records, and the window bar button switches to the whole session. The button names what pressing it will do, not the current state: 「显示全部」 at the default and 「显示最新 200 条」 once everything is showing, while the count beside it reports what is on screen. That full view is opt-in for a reason: on a 9,900-record session it is roughly 57,000 elements rebuilt every 2.5s poll, which was measured to freeze the page rather than be read. 「向上加载更早的 N 条」 widens the window in steps and a poll does not undo it. A sticky window bar under the overview strip offers that choice behind four explicit controls: switch the strip between equal width and a real time axis, load 200 earlier records, jump back to the latest 200, and show everything. "Show everything" builds every record in the session into the DOM at once and gets noticeably slower on large sessions; incoming records do not knock it back down to 200.
 - `messageCount` and `turnCount` in the session picker are estimates derived from a bounded prefix of the file; exact values come from the selected session.
+- A session the runtime spawned from another one is marked 「子会话」 in the picker. The parent is deliberately not named: a branch is always newer than the session that spawned it, so its parent has usually aged out of the most-recent-N window this list is built from, and a lookup that fails quietly is how a picker ends up asserting something it cannot see.
 - Light theme token coverage is verified — every `--mcode-*` token the page consumes is defined for both themes — but its rendered appearance was not visually checked; the page was exercised under a dark system preference.
 
 ## Tested environment

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

@@ -4,7 +4,7 @@
 
 按轮次浏览一段 MiniMax Code 对话的模型轨迹：消息流、思考过程、工具调用与结果、token 消耗与每轮耗时。
 
-作者：[avatasia](https://github.com/avatasia) · 版本：`1.1.0`
+作者：[avatasia](https://github.com/avatasia) · 版本：`1.2.0`
 
 ### 动手改这个页面前
 
@@ -117,6 +117,7 @@ MiniMax Code 不会告诉 Mini App 是哪段对话打开了它的页面：传给
 - 单个 `messages.jsonl` 最多读取 64 MB。更大的会话会被截断，页面会明确说明。
 - 台里没有用虚拟滚动，每一行都是真实的 DOM 元素。页面默认只展示最新 200 条，窗口条上的按钮可以切到全量；全量是可选的，因为它很贵 —— 在这个会话上约 9,900 条、约 5.7 万个元素，每 2.5 秒轮询重建一次，实测会直接卡死页面。总览条正下方的吸顶窗口栏提供三个显式控件：「总览轴」「向上加载更早的 200 条」，以及在最新 200 条与全量之间切换的那一个按钮（它写的是按下去会变成什么，默认为「显示全部」，全量时为「显示最新 200 条」；当前窗口由右边的计数条报告，两者回答的是不同问题）。「总览轴」只改总览条的横轴——等宽（每条记录一样宽，完全忽略时间）或真实时间轴（宽度等于该记录的真实耗时）；它不筛选、不排序，台账里的行和页面上的任何计数都不变。「向上加载更早的 200 条」每点一次就多加一页，轮询不会把已经加宽的窗口重置回去；点切换按钮也不会自动滚动页面，读者正在看的那一行会留在原地。
 - 会话选择器里的 `messageCount` / `turnCount` 是从文件的有界前缀估算的；精确值以选中会话后展示的为准。
+- 会话选择器里，被运行时从另一个会话派生出来的会话标为「子会话」，但不写父会话的名字：分支一定比派生它的会话新，而列表按最近活动取前 30 个，父会话通常已经掉出这个窗口。静默失败的查找，最终会让列表声称一个它看不见的东西。
 - 浅色主题的 token 覆盖已验证（页面用到的每个 `--mcode-*` 变量在两套主题下都有定义），但渲染外观未做视觉检查；功能验收是在深色系统偏好下进行的。
 
 ## 测试环境