agentus 0.11.4 → 0.12.0

package/README.md

@@ -57,7 +57,7 @@ background process comes back as a turn of its own), an **ACP session that write
 cockpit-side failure is diagnosable afterwards), and a **DeepSeek web backend** (search +
 extract on the model key) — come from the fork's integration build instead. That is a five-line install:
 [§ Which Hermes to run](docs/installation.md#which-hermes-to-run) — currently the tag
-`agentus/v0.22.0/merge-20261023-0640`, on Hermes `v0.22.0`.
+`agentus/v0.22.0/merge-20261023-0852`, on Hermes `v0.22.0`.
 
 The first slot you start will use the Hermes home **your own agent already uses**
 (`~/.hermes`) unless the backend row names another one — see "HERMES_HOME" below.

package/README.zh-CN.md

@@ -51,7 +51,7 @@ web bundle、配套 APK —— 然后直接退出，不启动任何东西）。
 以及 **DeepSeek 的 web 后端**（搜索 + 正文抓取，共用模型 key）—— 来自 fork 的集成构建（tag）。
 装法就五行：
 [§ 该跑哪份 Hermes](docs/installation.zh-CN.md#该跑哪份-hermes) —— 当前是 tag
-`agentus/v0.22.0/merge-20261023-0640`，基座 Hermes `v0.22.0`。
+`agentus/v0.22.0/merge-20261023-0852`，基座 Hermes `v0.22.0`。
 
 你启动的第一个 slot 会使用**你自己的 agent 已经在用的**那个 Hermes home（`~/.hermes`），除非后端那一行
 指定了另一个 —— 见下面的「HERMES_HOME」。

package/docs/installation.md

@@ -60,7 +60,7 @@ ref and gets rebuilt, while a tag never moves — so pin the tag. The `agentus/`
 ours apart from upstream's own tags (`v0.22.0`, `v0.22.0+canary.*`), and the timestamp in the
 last segment sorts, so "newest" is a `sort -V`.
 
-**Current integration build: `agentus/v0.22.0/merge-20261023-0640`** — the newest tag on the fork,
+**Current integration build: `agentus/v0.22.0/merge-20261023-0852`** — the newest tag on the fork,
 built on Hermes `v0.22.0`. This line is for orientation only, not the source of truth: the
 `TAG=$(…)` step below resolves the newest one on every run, so read it there if this sentence
 ever looks stale.

package/docs/installation.zh-CN.md

@@ -52,7 +52,7 @@ agentus/<hermes 内部版本>/merge-<YYYYMMDD-HHMM>
 tag。`agentus/` 这个前缀也把它和上游自己的 tag（`v0.22.0`、`v0.22.0+canary.*`）分开；最后一段是时间戳，
 可排序，所以「最新」就是一次 `sort -V`。
 
-**当前集成构建：`agentus/v0.22.0/merge-20261023-0640`** —— fork 上最新的那个 tag，基座 Hermes
+**当前集成构建：`agentus/v0.22.0/merge-20261023-0852`** —— fork 上最新的那个 tag，基座 Hermes
 `v0.22.0`。这行只为一眼看个大概，不是权威：下面的 `TAG=$(…)` 每次都会自己解析出最新，觉得这行过期就
 以它为准。
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agentus",
-  "version": "0.11.4",
+  "version": "0.12.0",
   "description": "Multi-session web cockpit for ACP-speaking coding agents (Qoder CLI / Hermes). UI has no intelligence — the agent lives in spawned CLI subprocesses.",
   "license": "Apache-2.0",
   "repository": {

package/packages/server/src/acp/session-manager.ts

@@ -1387,9 +1387,14 @@ export class SessionManager {
       // The agent has the block (a cancelled turn still received it): NOW the boundary is spent.
       settleVoice();
       this.#finalizePlan(sessionId, terminalState);
+      // Turn END is the second and last ordering event of a turn (issue #50): start moved the session,
+      // this settles it where the conversation now is. Mid-turn rows deliberately do NOT touch — see
+      // #touch.
+      this.#touch(s);
       this.#emit({ t: "turn-end", sessionId, stopReason: res?.stopReason, durationMs: Date.now() - turnStartedAt });
     } catch (err) {
       this.#finalizePlan(sessionId, "failed");
+      this.#touch(s);
       this.#emit({ t: "turn-end", sessionId, error: errMessage(err), durationMs: Date.now() - turnStartedAt });
     } finally {
       s.busy = false;
@@ -2308,7 +2313,8 @@ export class SessionManager {
           toolCallId: String(u.toolCallId ?? ""), createdAt: Date.now(),
         });
         if (up.isNew) {
-          this.#touch(live, up.message.createdAt);
+          // No clock move (issue #50): a tool call is work inside a turn, not a reason for the session to
+          // jump to the top of the rail. The turn's start and end are the only two moves it gets.
           this.#emit({ t: "message", message: up.message });
         }
         return;
@@ -2403,9 +2409,10 @@ export class SessionManager {
       if (msg.kind === "agent" || msg.kind === "thought") {
         const r = this.#store.appendTextChunk({ ...msg, kind: msg.kind });
         if (r.delta || r.isNew) {
-          // A row that did NOT move is not activity. A re-attach replays blocks we already hold, and
-          // touching the clock for those is what made every resumed session read 「刚刚」 at once.
-          this.#touch(live, r.message.createdAt);
+          // A row that did NOT move is not activity. Neither is one that DID move — a long reply arrives
+          // as dozens of chunks, and touching per chunk re-sorted the rail on every token (issue #50:
+          // three sessions in parallel swapped places continuously). Only the turn's start/end move the
+          // clock; see #touch.
           // One message = one row, so a row that GREW keeps its seq. A client that deduplicated frames
           // by seq therefore dropped every chunk after the first one (measured: a phone bubble showing
           // "不是" with the rest of the reply nowhere, and the next frame landing in an empty bubble).
@@ -2422,7 +2429,7 @@ export class SessionManager {
         return;
       }
       const stored = this.#store.appendMessage(msg);
-      this.#touch(live, stored.createdAt);
+      // Plan/other state rows are mid-turn noise for ordering (issue #50): stored, emitted, no clock move.
       this.#emit({ t: "message", message: stored });
     }
   }
@@ -2831,7 +2838,18 @@ export class SessionManager {
   /** Keep `lastAt` on the session ITSELF, not only on the list projection. A single-session
    *  payload (status change, title update, a rename response) built from `info` used to arrive
    *  without the field, so the client's copy dropped it and that session fell back to creation
-   *  order — the rail stopped moving a session up the moment you talked to it. */
+   *  order — the rail stopped moving a session up the moment you talked to it.
+   *
+   *  WHO may move the clock is the whole of issue #50. The rail sorts on this field, so every writer
+   *  is a potential re-sort the operator sees. Allowed: the operator's own prompt (he said something),
+   *  the END of a turn (the conversation settled somewhere new), and an approval request (the session
+   *  is now blocked on a human — a real state change, and rare). NOT allowed, and this is what used to
+   *  make the rail jitter: every agent text chunk, every tool call, plan/state rows, usage frames.
+   *  A long reply arrives as dozens of chunks; touching per chunk meant three parallel sessions swapped
+   *  places continuously, with rows moving out from under the pointer.
+   *
+   *  A turn therefore moves its session at most twice — start and end — and its position inside the
+   *  turn is frozen, which is what a reader can actually follow. */
   #touch(live: LiveSession, at = Date.now()): void {
     live.info.lastAt = at;
     // …and persist it: `lastAt` on the live object is only the projection the sockets see. The rail