claude-code-sessions 0.16.2__tar.gz → 0.16.4__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (37) hide show
  1. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/LICENSE +21 -21
  2. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/PKG-INFO +52 -2
  3. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/README.md +51 -1
  4. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/claude_code_sessions.egg-info/PKG-INFO +52 -2
  5. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/claude_code_sessions.egg-info/SOURCES.txt +3 -0
  6. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/claude_code_sessions.py +828 -61
  7. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/claude_code_sessions_gui.py +320 -32
  8. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/pyproject.toml +50 -50
  9. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/tests/test_alignment.py +144 -144
  10. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/tests/test_cli.py +172 -172
  11. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/tests/test_containment.py +71 -71
  12. claude_code_sessions-0.16.4/tests/test_data_root.py +515 -0
  13. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/tests/test_discovery.py +48 -48
  14. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/tests/test_encoding.py +41 -41
  15. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/tests/test_engine.py +274 -274
  16. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/tests/test_golden.py +18 -18
  17. claude_code_sessions-0.16.4/tests/test_gui_destination.py +249 -0
  18. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/tests/test_helpers.py +39 -39
  19. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/tests/test_journal.py +87 -87
  20. claude_code_sessions-0.16.4/tests/test_journal_reroot.py +926 -0
  21. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/tests/test_plan_move.py +152 -29
  22. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/tests/test_rows.py +73 -73
  23. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/tests/test_scaffold.py +18 -18
  24. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/tests/test_sync.py +10 -3
  25. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/tests/test_transcripts.py +24 -24
  26. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/claude_code_sessions.egg-info/dependency_links.txt +0 -0
  27. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/claude_code_sessions.egg-info/entry_points.txt +0 -0
  28. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/claude_code_sessions.egg-info/top_level.txt +0 -0
  29. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/setup.cfg +0 -0
  30. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/tests/test_anonymize.py +0 -0
  31. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/tests/test_commands.py +0 -0
  32. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/tests/test_converge.py +0 -0
  33. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/tests/test_duplicate_transcripts.py +0 -0
  34. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/tests/test_gui_models.py +0 -0
  35. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/tests/test_recover.py +0 -0
  36. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/tests/test_retitle.py +0 -0
  37. {claude_code_sessions-0.16.2 → claude_code_sessions-0.16.4}/tests/test_undo.py +0 -0
@@ -1,21 +1,21 @@
1
- MIT License
2
-
3
- Copyright (c) 2026 Craig Stoller
4
-
5
- Permission is hereby granted, free of charge, to any person obtaining a copy
6
- of this software and associated documentation files (the "Software"), to deal
7
- in the Software without restriction, including without limitation the rights
8
- to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
- copies of the Software, and to permit persons to whom the Software is
10
- furnished to do so, subject to the following conditions:
11
-
12
- The above copyright notice and this permission notice shall be included in all
13
- copies or substantial portions of the Software.
14
-
15
- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
- IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
- FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
- AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
- LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
- OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
- SOFTWARE.
1
+ MIT License
2
+
3
+ Copyright (c) 2026 Craig Stoller
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: claude-code-sessions
3
- Version: 0.16.2
3
+ Version: 0.16.4
4
4
  Summary: Unofficial tool for Claude Code sessions on disk: make a session visible under your other Claude account on the same machine, or move one between project folders. Command line or GUI. Journaled, reversible, fails closed.
5
5
  Author: Craig Stoller
6
6
  License: MIT
@@ -620,11 +620,13 @@ window.
620
620
  | Platform | Status | Mutations |
621
621
  |---|---|---|
622
622
  | Windows 11 + Claude Desktop | verified 2026-07-31; sync end-to-end incl. live continuation 2026-08-03; sync-undo drift refusal live 2026-08-04 | read-only + mutations |
623
+ | Windows 11 + Claude Desktop 2.42304.2 (user data moved to `%LOCALAPPDATA%\Claude-Data`) | from 0.16.3: read-only paths probed 2026-10-19 against the moved store. 0.16.2 and earlier find no store | read-only + mutations, `--apply` not yet verified on this build |
623
624
  | macOS / Linux desktop | unverified | **read-only only** - desktop-store mutations refuse, with no override |
624
625
  | CLI-only sessions (any OS) | transcript layout verified | mutations allowed via `--transcript-only` |
625
626
 
626
627
  The dates are measurements against specific builds - most recently Claude Desktop
627
- 2.42304.0.0 (Microsoft Store MSIX install) and Claude Code CLI 2.1.302. On 2026-10-14 the
628
+ 2.42304.2.0 (Microsoft Store MSIX install) for the read-only paths, and 2.42304.0.0 with Claude
629
+ Code CLI 2.1.302 for the last `--apply` runs. On 2026-10-14 the
628
630
  read-only paths were verified against a real Desktop 2.x store, build 2.37337.1.0 (`list`,
629
631
  `doctor`, `alignment`, `recover` without `--apply`, and a `converge` dry run): the row format
630
632
  had only gained keys, and every row this tool had written under 1.x was still present, some
@@ -633,6 +635,18 @@ already re-saved by the new app. Later on 2026-10-14 a `converge --apply` ran ag
633
635
  present and `doctor` reported none vanished. On 2026-10-17 two more `converge --apply` runs
634
636
  went through against 2.42304.0.0 with the app closed, with the same result. That build moved
635
637
  the browser-extension helper, which the running-app guard follows from 0.16.1 (see Roadmap).
638
+ On 2026-10-19, 2.42304.2.0 moved the app's whole user-data folder, session store included,
639
+ from the package's `LocalCache\Roaming\Claude` to `%LOCALAPPDATA%\Claude-Data\claude_<pkg>`,
640
+ and left the helper where it was. 0.16.2 and earlier report the store absent there. 0.16.3
641
+ reads the moved store and still finds the helper. Its read-only paths (`doctor`, `alignment`
642
+ and a `converge` dry run) were checked against the moved store the same day. 0.16.3 has one
643
+ known gap: rows this tool created before the move are journaled at their old paths, so
644
+ `doctor` reports them as "no longer on disk" although they moved with the store, and advises
645
+ running `new-row` again; for the same reason `undo` cannot reverse an operation from before
646
+ the move. 0.16.4 reads those paths under the moved store: `doctor` checks
647
+ the rows where they now are, and `undo` and `recover` treat such an operation as they did
648
+ before the move. A row in a store the tool cannot read at all is listed by `doctor` apart, not
649
+ counted in its exit code, and `undo` refuses it.
636
650
  The on-disk format has changed once already during this tool's own development; treat a
637
651
  much newer build as unverified territory.
638
652
 
@@ -992,6 +1006,42 @@ window into `journaled`/`completed`/`rolled_back`.
992
1006
  opt-in is on and a helper still counts, the note says why; and the opt-in's wording, in this
993
1007
  README, the window's checkbox and the command's help, says Chrome or Edge, since either can
994
1008
  launch the helper. Three constants left unused since the August anti-fabrication fix are gone.
1009
+ - **0.16.3 finds the session store where Desktop 2.42304.2 moved it.** That build moved the
1010
+ app's whole user-data folder out of the Microsoft Store package, from
1011
+ `%LOCALAPPDATA%\Packages\Claude_<pkg>\LocalCache\Roaming\Claude` to
1012
+ `%LOCALAPPDATA%\Claude-Data\claude_<pkg>`, and left a 0-byte file in the old folder naming
1013
+ the new one. 0.16.2 looked only in the old places, so `doctor` and `alignment` reported no
1014
+ store and `converge` planned nothing. This release reads the moved folder first. When a
1015
+ package's data has moved, its old folder is never read, and a store still sitting there is
1016
+ named in `doctor` rather than read beside the new one. The browser-extension helper did not
1017
+ move. The guard had found it two folders up from the store, which after the move is a
1018
+ folder where no helper lives, so the signed-helper opt-in would have stopped working again
1019
+ without a word. Helper locations are now listed on their own. The CLI the app spawns moved
1020
+ with the data, and the guard recognises it at its new path. When no store is found and the
1021
+ app's marker names a folder this version does not know, `doctor` says so instead of
1022
+ reporting a bare absence, and when the folder the data moved to cannot be listed, discovery
1023
+ reports an error rather than falling back to the old store. One gap remains: operations
1024
+ from before the move are journaled at their old paths, so `doctor` lists the rows this tool
1025
+ created then as no longer on disk although they moved with the store, and `undo` cannot
1026
+ reverse those operations (see the compatibility matrix). Until that is fixed, judge a
1027
+ `converge --apply` by `alignment`.
1028
+ - **0.16.4 follows the journal and the window's saved destination across the data move.**
1029
+ Every operation journals the rows it touched by absolute path, so an entry written before
1030
+ Desktop 2.42304.2 moved its data names a folder that now holds only the app's marker. 0.16.3
1031
+ read those paths as written: `doctor` reported every row this tool had created as no longer
1032
+ on disk and exited 1, 320 rows on the machine where this was found, and `undo` and `recover`
1033
+ of those operations refused, misreported, or for a `move` ended in an unhandled error. This
1034
+ release maps a recorded path under the old store to the same place under the moved one as it
1035
+ reads the journal, and writes nothing back to it. On that machine `doctor` now finds all 320
1036
+ rows and exits 0. Before `undo` or `recover` acts on a journaled row, the row must resolve
1037
+ inside a store that discovery found; a row in a store the tool cannot read is listed by
1038
+ `doctor` apart, not counted in its exit code, and `undo` refuses it. `undo` of a `sync` now
1039
+ says what it reversed instead of a bare "undone". The window had the same trouble with its
1040
+ saved sync destination, a full store path, so every plan was refused with Apply off. It now
1041
+ sets a saved destination that is proven gone aside and asks for a new one. "Change
1042
+ destination" keeps the saved value until another is picked, so a cancelled pick loses
1043
+ nothing, and no plan goes into a different store without a pick. A saved store whose account
1044
+ is now signed in is named as such, and the candidate holding the saved ids is marked.
995
1045
  - Platform rows above move from "unverified" to "verified" as contributors confirm the store
996
1046
  paths and behavior on their own machines.
997
1047
 
@@ -590,11 +590,13 @@ window.
590
590
  | Platform | Status | Mutations |
591
591
  |---|---|---|
592
592
  | Windows 11 + Claude Desktop | verified 2026-07-31; sync end-to-end incl. live continuation 2026-08-03; sync-undo drift refusal live 2026-08-04 | read-only + mutations |
593
+ | Windows 11 + Claude Desktop 2.42304.2 (user data moved to `%LOCALAPPDATA%\Claude-Data`) | from 0.16.3: read-only paths probed 2026-10-19 against the moved store. 0.16.2 and earlier find no store | read-only + mutations, `--apply` not yet verified on this build |
593
594
  | macOS / Linux desktop | unverified | **read-only only** - desktop-store mutations refuse, with no override |
594
595
  | CLI-only sessions (any OS) | transcript layout verified | mutations allowed via `--transcript-only` |
595
596
 
596
597
  The dates are measurements against specific builds - most recently Claude Desktop
597
- 2.42304.0.0 (Microsoft Store MSIX install) and Claude Code CLI 2.1.302. On 2026-10-14 the
598
+ 2.42304.2.0 (Microsoft Store MSIX install) for the read-only paths, and 2.42304.0.0 with Claude
599
+ Code CLI 2.1.302 for the last `--apply` runs. On 2026-10-14 the
598
600
  read-only paths were verified against a real Desktop 2.x store, build 2.37337.1.0 (`list`,
599
601
  `doctor`, `alignment`, `recover` without `--apply`, and a `converge` dry run): the row format
600
602
  had only gained keys, and every row this tool had written under 1.x was still present, some
@@ -603,6 +605,18 @@ already re-saved by the new app. Later on 2026-10-14 a `converge --apply` ran ag
603
605
  present and `doctor` reported none vanished. On 2026-10-17 two more `converge --apply` runs
604
606
  went through against 2.42304.0.0 with the app closed, with the same result. That build moved
605
607
  the browser-extension helper, which the running-app guard follows from 0.16.1 (see Roadmap).
608
+ On 2026-10-19, 2.42304.2.0 moved the app's whole user-data folder, session store included,
609
+ from the package's `LocalCache\Roaming\Claude` to `%LOCALAPPDATA%\Claude-Data\claude_<pkg>`,
610
+ and left the helper where it was. 0.16.2 and earlier report the store absent there. 0.16.3
611
+ reads the moved store and still finds the helper. Its read-only paths (`doctor`, `alignment`
612
+ and a `converge` dry run) were checked against the moved store the same day. 0.16.3 has one
613
+ known gap: rows this tool created before the move are journaled at their old paths, so
614
+ `doctor` reports them as "no longer on disk" although they moved with the store, and advises
615
+ running `new-row` again; for the same reason `undo` cannot reverse an operation from before
616
+ the move. 0.16.4 reads those paths under the moved store: `doctor` checks
617
+ the rows where they now are, and `undo` and `recover` treat such an operation as they did
618
+ before the move. A row in a store the tool cannot read at all is listed by `doctor` apart, not
619
+ counted in its exit code, and `undo` refuses it.
606
620
  The on-disk format has changed once already during this tool's own development; treat a
607
621
  much newer build as unverified territory.
608
622
 
@@ -962,6 +976,42 @@ window into `journaled`/`completed`/`rolled_back`.
962
976
  opt-in is on and a helper still counts, the note says why; and the opt-in's wording, in this
963
977
  README, the window's checkbox and the command's help, says Chrome or Edge, since either can
964
978
  launch the helper. Three constants left unused since the August anti-fabrication fix are gone.
979
+ - **0.16.3 finds the session store where Desktop 2.42304.2 moved it.** That build moved the
980
+ app's whole user-data folder out of the Microsoft Store package, from
981
+ `%LOCALAPPDATA%\Packages\Claude_<pkg>\LocalCache\Roaming\Claude` to
982
+ `%LOCALAPPDATA%\Claude-Data\claude_<pkg>`, and left a 0-byte file in the old folder naming
983
+ the new one. 0.16.2 looked only in the old places, so `doctor` and `alignment` reported no
984
+ store and `converge` planned nothing. This release reads the moved folder first. When a
985
+ package's data has moved, its old folder is never read, and a store still sitting there is
986
+ named in `doctor` rather than read beside the new one. The browser-extension helper did not
987
+ move. The guard had found it two folders up from the store, which after the move is a
988
+ folder where no helper lives, so the signed-helper opt-in would have stopped working again
989
+ without a word. Helper locations are now listed on their own. The CLI the app spawns moved
990
+ with the data, and the guard recognises it at its new path. When no store is found and the
991
+ app's marker names a folder this version does not know, `doctor` says so instead of
992
+ reporting a bare absence, and when the folder the data moved to cannot be listed, discovery
993
+ reports an error rather than falling back to the old store. One gap remains: operations
994
+ from before the move are journaled at their old paths, so `doctor` lists the rows this tool
995
+ created then as no longer on disk although they moved with the store, and `undo` cannot
996
+ reverse those operations (see the compatibility matrix). Until that is fixed, judge a
997
+ `converge --apply` by `alignment`.
998
+ - **0.16.4 follows the journal and the window's saved destination across the data move.**
999
+ Every operation journals the rows it touched by absolute path, so an entry written before
1000
+ Desktop 2.42304.2 moved its data names a folder that now holds only the app's marker. 0.16.3
1001
+ read those paths as written: `doctor` reported every row this tool had created as no longer
1002
+ on disk and exited 1, 320 rows on the machine where this was found, and `undo` and `recover`
1003
+ of those operations refused, misreported, or for a `move` ended in an unhandled error. This
1004
+ release maps a recorded path under the old store to the same place under the moved one as it
1005
+ reads the journal, and writes nothing back to it. On that machine `doctor` now finds all 320
1006
+ rows and exits 0. Before `undo` or `recover` acts on a journaled row, the row must resolve
1007
+ inside a store that discovery found; a row in a store the tool cannot read is listed by
1008
+ `doctor` apart, not counted in its exit code, and `undo` refuses it. `undo` of a `sync` now
1009
+ says what it reversed instead of a bare "undone". The window had the same trouble with its
1010
+ saved sync destination, a full store path, so every plan was refused with Apply off. It now
1011
+ sets a saved destination that is proven gone aside and asks for a new one. "Change
1012
+ destination" keeps the saved value until another is picked, so a cancelled pick loses
1013
+ nothing, and no plan goes into a different store without a pick. A saved store whose account
1014
+ is now signed in is named as such, and the candidate holding the saved ids is marked.
965
1015
  - Platform rows above move from "unverified" to "verified" as contributors confirm the store
966
1016
  paths and behavior on their own machines.
967
1017
 
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: claude-code-sessions
3
- Version: 0.16.2
3
+ Version: 0.16.4
4
4
  Summary: Unofficial tool for Claude Code sessions on disk: make a session visible under your other Claude account on the same machine, or move one between project folders. Command line or GUI. Journaled, reversible, fails closed.
5
5
  Author: Craig Stoller
6
6
  License: MIT
@@ -620,11 +620,13 @@ window.
620
620
  | Platform | Status | Mutations |
621
621
  |---|---|---|
622
622
  | Windows 11 + Claude Desktop | verified 2026-07-31; sync end-to-end incl. live continuation 2026-08-03; sync-undo drift refusal live 2026-08-04 | read-only + mutations |
623
+ | Windows 11 + Claude Desktop 2.42304.2 (user data moved to `%LOCALAPPDATA%\Claude-Data`) | from 0.16.3: read-only paths probed 2026-10-19 against the moved store. 0.16.2 and earlier find no store | read-only + mutations, `--apply` not yet verified on this build |
623
624
  | macOS / Linux desktop | unverified | **read-only only** - desktop-store mutations refuse, with no override |
624
625
  | CLI-only sessions (any OS) | transcript layout verified | mutations allowed via `--transcript-only` |
625
626
 
626
627
  The dates are measurements against specific builds - most recently Claude Desktop
627
- 2.42304.0.0 (Microsoft Store MSIX install) and Claude Code CLI 2.1.302. On 2026-10-14 the
628
+ 2.42304.2.0 (Microsoft Store MSIX install) for the read-only paths, and 2.42304.0.0 with Claude
629
+ Code CLI 2.1.302 for the last `--apply` runs. On 2026-10-14 the
628
630
  read-only paths were verified against a real Desktop 2.x store, build 2.37337.1.0 (`list`,
629
631
  `doctor`, `alignment`, `recover` without `--apply`, and a `converge` dry run): the row format
630
632
  had only gained keys, and every row this tool had written under 1.x was still present, some
@@ -633,6 +635,18 @@ already re-saved by the new app. Later on 2026-10-14 a `converge --apply` ran ag
633
635
  present and `doctor` reported none vanished. On 2026-10-17 two more `converge --apply` runs
634
636
  went through against 2.42304.0.0 with the app closed, with the same result. That build moved
635
637
  the browser-extension helper, which the running-app guard follows from 0.16.1 (see Roadmap).
638
+ On 2026-10-19, 2.42304.2.0 moved the app's whole user-data folder, session store included,
639
+ from the package's `LocalCache\Roaming\Claude` to `%LOCALAPPDATA%\Claude-Data\claude_<pkg>`,
640
+ and left the helper where it was. 0.16.2 and earlier report the store absent there. 0.16.3
641
+ reads the moved store and still finds the helper. Its read-only paths (`doctor`, `alignment`
642
+ and a `converge` dry run) were checked against the moved store the same day. 0.16.3 has one
643
+ known gap: rows this tool created before the move are journaled at their old paths, so
644
+ `doctor` reports them as "no longer on disk" although they moved with the store, and advises
645
+ running `new-row` again; for the same reason `undo` cannot reverse an operation from before
646
+ the move. 0.16.4 reads those paths under the moved store: `doctor` checks
647
+ the rows where they now are, and `undo` and `recover` treat such an operation as they did
648
+ before the move. A row in a store the tool cannot read at all is listed by `doctor` apart, not
649
+ counted in its exit code, and `undo` refuses it.
636
650
  The on-disk format has changed once already during this tool's own development; treat a
637
651
  much newer build as unverified territory.
638
652
 
@@ -992,6 +1006,42 @@ window into `journaled`/`completed`/`rolled_back`.
992
1006
  opt-in is on and a helper still counts, the note says why; and the opt-in's wording, in this
993
1007
  README, the window's checkbox and the command's help, says Chrome or Edge, since either can
994
1008
  launch the helper. Three constants left unused since the August anti-fabrication fix are gone.
1009
+ - **0.16.3 finds the session store where Desktop 2.42304.2 moved it.** That build moved the
1010
+ app's whole user-data folder out of the Microsoft Store package, from
1011
+ `%LOCALAPPDATA%\Packages\Claude_<pkg>\LocalCache\Roaming\Claude` to
1012
+ `%LOCALAPPDATA%\Claude-Data\claude_<pkg>`, and left a 0-byte file in the old folder naming
1013
+ the new one. 0.16.2 looked only in the old places, so `doctor` and `alignment` reported no
1014
+ store and `converge` planned nothing. This release reads the moved folder first. When a
1015
+ package's data has moved, its old folder is never read, and a store still sitting there is
1016
+ named in `doctor` rather than read beside the new one. The browser-extension helper did not
1017
+ move. The guard had found it two folders up from the store, which after the move is a
1018
+ folder where no helper lives, so the signed-helper opt-in would have stopped working again
1019
+ without a word. Helper locations are now listed on their own. The CLI the app spawns moved
1020
+ with the data, and the guard recognises it at its new path. When no store is found and the
1021
+ app's marker names a folder this version does not know, `doctor` says so instead of
1022
+ reporting a bare absence, and when the folder the data moved to cannot be listed, discovery
1023
+ reports an error rather than falling back to the old store. One gap remains: operations
1024
+ from before the move are journaled at their old paths, so `doctor` lists the rows this tool
1025
+ created then as no longer on disk although they moved with the store, and `undo` cannot
1026
+ reverse those operations (see the compatibility matrix). Until that is fixed, judge a
1027
+ `converge --apply` by `alignment`.
1028
+ - **0.16.4 follows the journal and the window's saved destination across the data move.**
1029
+ Every operation journals the rows it touched by absolute path, so an entry written before
1030
+ Desktop 2.42304.2 moved its data names a folder that now holds only the app's marker. 0.16.3
1031
+ read those paths as written: `doctor` reported every row this tool had created as no longer
1032
+ on disk and exited 1, 320 rows on the machine where this was found, and `undo` and `recover`
1033
+ of those operations refused, misreported, or for a `move` ended in an unhandled error. This
1034
+ release maps a recorded path under the old store to the same place under the moved one as it
1035
+ reads the journal, and writes nothing back to it. On that machine `doctor` now finds all 320
1036
+ rows and exits 0. Before `undo` or `recover` acts on a journaled row, the row must resolve
1037
+ inside a store that discovery found; a row in a store the tool cannot read is listed by
1038
+ `doctor` apart, not counted in its exit code, and `undo` refuses it. `undo` of a `sync` now
1039
+ says what it reversed instead of a bare "undone". The window had the same trouble with its
1040
+ saved sync destination, a full store path, so every plan was refused with Apply off. It now
1041
+ sets a saved destination that is proven gone aside and asks for a new one. "Change
1042
+ destination" keeps the saved value until another is picked, so a cancelled pick loses
1043
+ nothing, and no plan goes into a different store without a pick. A saved store whose account
1044
+ is now signed in is named as such, and the candidate holding the saved ids is marked.
995
1045
  - Platform rows above move from "unverified" to "verified" as contributors confirm the store
996
1046
  paths and behavior on their own machines.
997
1047
 
@@ -14,14 +14,17 @@ tests/test_cli.py
14
14
  tests/test_commands.py
15
15
  tests/test_containment.py
16
16
  tests/test_converge.py
17
+ tests/test_data_root.py
17
18
  tests/test_discovery.py
18
19
  tests/test_duplicate_transcripts.py
19
20
  tests/test_encoding.py
20
21
  tests/test_engine.py
21
22
  tests/test_golden.py
23
+ tests/test_gui_destination.py
22
24
  tests/test_gui_models.py
23
25
  tests/test_helpers.py
24
26
  tests/test_journal.py
27
+ tests/test_journal_reroot.py
25
28
  tests/test_plan_move.py
26
29
  tests/test_recover.py
27
30
  tests/test_retitle.py