The picker names conversations and their runs, the ledger keeps rows only for the groups the reader is on, the body is sent as bytes, and the caches that hold them are bounded

plugins/avatasia/mmc-trajectory/.gitignore

@@ -11,4 +11,10 @@ __pycache__/
 # mid-mutation is caught on the next one instead of being inferred from whatever the source looks
 # like afterwards. The snapshot is machine-specific bookkeeping and this directory is the package
 # that ships to readers, so it must never be tracked.
-tests/.shipped-snapshot.json
+tests/.shipped-snapshot.json
+
+# Derived artifacts. The runtime writes the search segments under its own data dir, which is
+# outside this package; the runtime refuses a data dir that lands in here (see `start()` in
+# miniapp/node/server.mjs). This entry is the second half of that rule: if a caller ever got
+# through, the directory must not be tracked and must not be part of what ships.
+trajectory-artifacts/

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

@@ -2,7 +2,7 @@
   "schemaVersion": 1,
   "name": "mmc-trajectory",
   "displayName": "会话轨迹",
-  "version": "1.2.0",
+  "version": "1.3.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.2.0`
+Author: [avatasia](https://github.com/avatasia) · Version: `1.3.0`
 
 ### Before you change this page
 
@@ -131,7 +131,8 @@ 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.
+- The session picker is **two selects in a cascade**. The upper one, 「会话」, lists conversations only — the sessions whose parent, followed up the chain, is a conversation. A session with no parent is one of them, and so is one whose parent names no session, whose parent chain ends in a cycle, or whose parent is itself a run: the layer follows the chain rather than the one column, and a row that ends up in the conversation layer carries no parent. The lower one, 「子代理」, lists the runs of the conversation that was picked: it is **empty by default**, it has values once a conversation is picked, and it is empty and disabled while the page follows the newest conversation. Measured on this machine, 13 of the 20 rows were sub-agent runs, so a reader could not tell which row was their own conversation; those 13 runs were also where that conversation actually happened. Nothing is hidden, only moved — the runs are not rows of the conversation list any more, they are rows of the run list under it, and the conversation list is now the twenty most recent conversations rather than the twenty most recent sessions of any kind. Every run is listed, most recently active first, and pressing one switches the page to it. The layer is decided by the chain of parents, which is independent of the 「定时 / 任务 / 轻量」 markers. The parent's name is still not written out: the parent id comes down with the row, and the page groups by that one id rather than doing a lookup that could fail quietly. Picking a run shows **that run's own trajectory** — a run is a session with its own transcript, and the parent's transcript does not contain its turns — and the conversation select stays on its parent.
+- The picker also says what a session **is**, not only what it is called: a scheduled run carries 「定时」, a background task 「任务」, and a lightweight conversation 「轻量」 — the markers come from the runtime's own record of the session, not from anything this app checks — so none of them can be mistaken for a conversation you wrote. They stay in the list and stay selectable — a marker is a marker, not a filter. The conversation the runtime database reports as current comes first, then the sessions of its own workspace, then the rest; the workspace path and the raw purpose string are compared on the server and never reach the page.
 - 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.2.0`
+作者：[avatasia](https://github.com/avatasia) · 版本：`1.3.0`
 
 ### 动手改这个页面前
 
@@ -117,7 +117,8 @@ MiniMax Code 不会告诉 Mini App 是哪段对话打开了它的页面：传给
 - 单个 `messages.jsonl` 最多读取 64 MB。更大的会话会被截断，页面会明确说明。
 - 台里没有用虚拟滚动，每一行都是真实的 DOM 元素。页面默认只展示最新 200 条，窗口条上的按钮可以切到全量；全量是可选的，因为它很贵 —— 在这个会话上约 9,900 条、约 5.7 万个元素，每 2.5 秒轮询重建一次，实测会直接卡死页面。总览条正下方的吸顶窗口栏提供三个显式控件：「总览轴」「向上加载更早的 200 条」，以及在最新 200 条与全量之间切换的那一个按钮（它写的是按下去会变成什么，默认为「显示全部」，全量时为「显示最新 200 条」；当前窗口由右边的计数条报告，两者回答的是不同问题）。「总览轴」只改总览条的横轴——等宽（每条记录一样宽，完全忽略时间）或真实时间轴（宽度等于该记录的真实耗时）；它不筛选、不排序，台账里的行和页面上的任何计数都不变。「向上加载更早的 200 条」每点一次就多加一页，轮询不会把已经加宽的窗口重置回去；点切换按钮也不会自动滚动页面，读者正在看的那一行会留在原地。
 - 会话选择器里的 `messageCount` / `turnCount` 是从文件的有界前缀估算的；精确值以选中会话后展示的为准。
-- 会话选择器里，被运行时从另一个会话派生出来的会话标为「子会话」，但不写父会话的名字：分支一定比派生它的会话新，而列表按最近活动取前 30 个，父会话通常已经掉出这个窗口。静默失败的查找，最终会让列表声称一个它看不见的东西。
+- 会话选择器是**级联的两个下拉框**。上面那个「会话」只列主会话 —— 沿父链往上走、终点是一段主会话的那些。父会话为空的是主会话；父会话指向一个不存在的会话、父链成环、或者父本身是子代理的，也是主会话 —— 层级看的是链，不是那一列，而落到会话层的行不带父会话。下面那个「子代理」只列所选那段对话的子代理，**默认是空**，选中主会话之后才有值，跟随最新时是空的且不可选。实测本机 20 行里有 13 行是子代理，读者根本分不出哪一行是自己的对话，而那 13 行恰恰就是这段对话真正发生的地方。它们没有被藏起来，只是从「平铺在会话里」变成「会话列表下面的子代理列表」：会话列表现在列的是最近 20 段主会话，而不是最近 20 个任意种类的会话；子代理有多少列多少，按各自最后一次活跃的时间倒序，最活跃的排在最上面，点其中一条就切到那一条。层级由父链决定，与「定时 / 任务 / 轻量」那套标记互相独立。父会话的名字仍然不写：父 id 由服务端随这一行带下来，页面按同一个 id 归组，不做一次可能悄悄失败的查找。选了子代理就显示**那一次运行自己的**轨迹 —— 每个子代理是一段独立的会话，有自己的 transcript，父会话的轨迹里并不包含它的轮次；此时上面那个下拉框停在它的父会话上。
+- 会话选择器不只说会话**叫什么**，还说它**是什么**：定时任务标「定时」，后台任务标「任务」，轻量会话标「轻量」（标记来自运行时对会话自己的记录，不是这个应用检查出来的），于是它们不会被误认成你自己开的对话。它们仍然在列表里、仍然可以选 —— 标记是标记，不是过滤。运行时库报告为当前的那段对话排在最前，然后是同一工作区的会话，再然后是其它；工作区路径和 purpose 原文只在服务端比较，不会发到页面。
 - 浅色主题的 token 覆盖已验证（页面用到的每个 `--mcode-*` 变量在两套主题下都有定义），但渲染外观未做视觉检查；功能验收是在深色系统偏好下进行的。
 
 ## 测试环境