Session reopen misclassifies branch lineage as reset
Cluster 110552. Data as of
Nothing open on GitHub. Fix merged in #111381 on 15 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #111381. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #111381. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where reopening a parent session incorrectly overwrites or misclassifies branch-child lineage as reset-successor provenance. The fix preserves branch lineage during reopen operations.
Open issues0
Open PRs0
Fixes on record
-
#111381 fix(sessions): reopening a parent no longer rewrites a /branch child as a reset successor (#110552, salvage #110559)
files:
hermes_state_sessions.py,tests/hermes_state/test_hermes_state.py
1 PR closed without merging
From the close comments: closed without comment 1
- #110559 fix(sessions): preserve branch lineage on reopen · closed without comment
Closed issues · 1
- Closed#110552Reset lineage provenance can be misclassified after reopen_session() backfills _reset_from
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #111381
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 15 Sep 2026