memgineering 0.2.0 → 0.2.1

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
@@ -11,6 +11,20 @@ language the reader wants. The bilingual rule the monorepo applies to
11
11
 
12
12
  ## [Unreleased]
13
13
 
14
+ ## [0.2.1] — 2026-08-09
15
+
16
+ ### Fixed
17
+
18
+ - **The language warning no longer fires on a query that worked.** On a brain
19
+ holding notes in more than one language, `recall "배포"` returned the Korean
20
+ note it was looking for and was told, above the result, that the query could
21
+ not reach the brain. A query that reached a note you wrote reached the brain,
22
+ whatever script it was in. It now stays quiet in that case, and still speaks
23
+ when everything that came back was `01_BASE/` scaffolding — which `init`
24
+ writes in English for everybody, so matching it is not evidence the query
25
+ landed. Found by using 0.2.0 against a real brain; a single-language fixture
26
+ could not produce it.
27
+
14
28
  ## [0.2.0] — 2026-08-09
15
29
 
16
30
  The record can say why, and you can see what a memory is actually worth.
@@ -46,9 +60,8 @@ The record can say why, and you can see what a memory is actually worth.
46
60
  however it is worded — and the old zero-result footer suggested broader
47
61
  wording, the one remedy that cannot work. Four testers hit this and came
48
62
  within one command of telling their user the brain held nothing on a subject
49
- it had notes about. The warning also appears above results, because the
50
- failure is rarely a clean zero: a couple of English scaffolding notes match
51
- and look like an answer.
63
+ it had notes about. It appears above results too, since the failure is rarely
64
+ a clean zero: a couple of scaffolding notes match and look like an answer.
52
65
  - **`use` with no argument now says which brain you are on**, and how it
53
66
  resolved — by pointer, by containment, or by being the only one linked. Its
54
67
  own help had always promised this; it reported only whether a pointer file
package/dist/index.js CHANGED
@@ -4603,7 +4603,10 @@ function recallCommand() {
4603
4603
  conflicts: result.conflicts
4604
4604
  },
4605
4605
  human: () => {
4606
- const otherScript = unreachableScript(query, built.entries);
4606
+ const reachedSomethingWritten = rows.some(
4607
+ ({ card }) => !(byId.get(card.id)?.path ?? "").startsWith("01_BASE/")
4608
+ );
4609
+ const otherScript = reachedSomethingWritten ? null : unreachableScript(query, built.entries);
4607
4610
  const sayWhy = () => {
4608
4611
  printHuman(
4609
4612
  c.yellow(
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "memgineering",
3
- "version": "0.2.0",
3
+ "version": "0.2.1",
4
4
  "private": false,
5
5
  "description": "One memory for the AI you connect. Recall, remember, and revise a brain your agents share — stored in your own folder.",
6
6
  "license": "Apache-2.0",