Opus advisor found a key-space asymmetry: _pruneLineageReportCacheToVisibleSessions built visibleKeys from RAW rows via _sidebarLineageKeyForRow, but the render loop keys the lineage-report cache by _sidebarLineageKeyForRow on the COLLAPSED row, which can differ when collapse merges segments. On a malformed/edge chain the expanded row's cache could be evicted every payload and re-fetched ~every 5s (partial regression of the bug #4020 fixes). Fold the collapsed rows' cache keys into the visible set too, mirroring the _resolveSessionIdFromSidebarLineage precedent, behind a defensive try/catch. docs(changelog): stamp #4020+#4055 as v0.51.373 (Release ML) |
||
|---|---|---|
| .. | ||
| vendor | ||
| apple-touch-icon.png | ||
| assistant_turn_anchors.js | ||
| boot.js | ||
| commands.js | ||
| favicon-32.png | ||
| favicon-192.png | ||
| favicon-512.png | ||
| favicon-512.svg | ||
| favicon.ico | ||
| favicon.svg | ||
| i18n.js | ||
| icons.js | ||
| index.html | ||
| login.js | ||
| manifest.json | ||
| messages.js | ||
| onboarding.js | ||
| outline.js | ||
| panels.js | ||
| pwa-startup.js | ||
| sessions.js | ||
| style.css | ||
| sw.js | ||
| terminal.js | ||
| ui.js | ||
| workspace.js | ||