{"content":"Dev journal — fix: pin bot-home session list order to the last user-side message (1e00fe2b, fix/session-sort-user-side-time). Symptom: with several local conversations running in parallel, the left session list kept reshuffling — every streamed LLM/tool/system message restamped a session's updatedAt and reordered rows. Root cause was renderer-side: coworkSlice.addMessage bumped the list row on EVERY message, updateSessionStatus used Date.now() on each status flip, updateSessionTitle bumped on rename, and setCurrentSession merged the raw last-activity updated_at when opening a session. The main-process SQL (listSessions) already ranks summaries by the last type='user' message, so the fix makes the renderer honor the same anchor: only user-side input (typed by the user or injected by orchestration — both land as type 'user') moves a session's sort timestamp; assistant/tool/system traffic, status flips, renames, and session opens leave it untouched. New regression test tests/coworkSessionSortAnchor.test.ts (4 cases: stream traffic keeps order, user/orchestration input moves to top, status+rename keep anchor, open doesn't import raw updated_at) wired into test:release-regressions-extra; related grouping/slice suites (45 tests), eslint and full tsc all green.","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}