@theokit/sdk-memory 0.5.2-next.1 → 0.5.3

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.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,59 @@
1
1
  # Changelog — @theokit/sdk-memory
2
2
 
3
+ ## 0.5.3
4
+
5
+ ### Patch Changes
6
+
7
+ - [#570](https://github.com/usetheokit/theokit-sdk/pull/570) [`64ff1f8`](https://github.com/usetheokit/theokit-sdk/commit/64ff1f8e072725dbc4d4dbbb5f82e6f1bca6141e) Thanks [@usetheodev](https://github.com/usetheodev)! - The memory index moves with a relocated store — the note this package's consumers never got ([#562](https://github.com/usetheokit/theokit-sdk/issues/562))
8
+
9
+ This is documentation, not behaviour. The change shipped in `@theokit/sdk@5.0.0` and is already
10
+ live for anyone on that version; what did not ship is any way for a `@theokit/sdk-memory` consumer
11
+ to find out. Its `0.5.2` section is empty — no dependency lines, no prose — so the release that
12
+ carried a privacy-relevant change reached its most directly affected audience with zero signal.
13
+
14
+ **Why this package's readers are the audience.** `@theokit/sdk-memory` owns the markdown store and
15
+ re-exports `memoryIndexRoot` (`src/internal/store/markdown-store.ts`). Someone reading this
16
+ CHANGELOG to decide whether a version is safe to take is exactly the person the note was written
17
+ for.
18
+
19
+ ## What changed in the behaviour
20
+
21
+ `memory.directory` now moves the search index with the store, except into the Claude Code CLI's own
22
+ directory ([#554](https://github.com/usetheokit/theokit-sdk/issues/554)).
23
+
24
+ The index is not a pointer. `chunks.text` holds the fact TEXT — FTS5/BM25 needs it to search — and
25
+ `files.path` holds the store's absolute path. **A copy of the index is a copy of the memory,
26
+ readable with `strings`.**
27
+
28
+ Leaving it at `<cwd>/.theokit/memory/.index/` while the facts moved meant an operator who pointed
29
+ `directory` at one personal store had that store's contents written into *every repository the
30
+ agent ran in*, untracked and un-ignored. Recall worked throughout, so nothing looked wrong; what
31
+ was wrong was where the data landed.
32
+
33
+ ```
34
+ before /tmp/my-store/fact.md facts move
35
+ /any-project/.theokit/memory/.index/memory.sqlite ← and the content follows here
36
+
37
+ after /tmp/my-store/fact.md
38
+ /tmp/my-store/.index/memory.sqlite ← one store, one index
39
+ ```
40
+
41
+ The Claude Code CLI's directory is unchanged, on its own argument: that CLI has no index format, so
42
+ a binary there is an artefact the partner does not understand inside a directory it owns
43
+ (`docs/memory-decisions.md` § 1). The fix narrows the behaviour to match that argument rather than
44
+ reversing the decision.
45
+
46
+ ## What this does not do
47
+
48
+ **The `0.5.2` section is not edited.** A published entry is a record of what shipped, and rewriting
49
+ it would make the record disagree with the tarball on npm. The note arrives in the next version
50
+ instead, which is later than it should have been and is the honest way to be late.
51
+
52
+ If you are on `0.5.2` the behaviour above is already what you have, through the `@theokit/sdk` you
53
+ resolve — this entry only tells you so.
54
+
55
+ ## 0.5.2
56
+
3
57
  ## 0.5.2-next.1
4
58
 
5
59
  ### Patch Changes
package/dist/index.cjs CHANGED
@@ -2312,6 +2312,10 @@ Object.defineProperty(exports, "lanceStoragePath", {
2312
2312
  enumerable: true,
2313
2313
  get: function () { return memoryStore.lanceStoragePath; }
2314
2314
  });
2315
+ Object.defineProperty(exports, "memoryIndexRoot", {
2316
+ enumerable: true,
2317
+ get: function () { return memoryStore.memoryIndexRoot; }
2318
+ });
2315
2319
  Object.defineProperty(exports, "memoryMdPath", {
2316
2320
  enumerable: true,
2317
2321
  get: function () { return memoryStore.memoryMdPath; }