nexusmem 0.10.2 → 0.10.4
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 +41 -2
- package/README.md +562 -550
- package/dist/cli/index.js +827 -169
- package/dist/cli/index.js.map +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -7,9 +7,48 @@ Tags were added retroactively on 2026-08-11 and point at the exact commits the n
|
|
|
7
7
|
built from, matched by publish timestamp: `v0.1.0` → `67a4776`, `v0.1.1` → `809e62c`,
|
|
8
8
|
`v0.1.2` → `b22a3b0`.
|
|
9
9
|
|
|
10
|
-
## [Unreleased]
|
|
10
|
+
## [Unreleased]
|
|
11
|
+
|
|
12
|
+
No unreleased changes yet.
|
|
13
|
+
|
|
14
|
+
## [0.10.4] — 2026-09-07
|
|
15
|
+
|
|
16
|
+
### Added
|
|
17
|
+
|
|
18
|
+
- Fresh-project syncs classify reconstructable Git commits and diffs, timestamped shell history,
|
|
19
|
+
and already-supported opt-in coding-agent history as `backfilled` only when a trustworthy source
|
|
20
|
+
timestamp predates NexusMem initialization. Trustworthily timestamped events between initialization
|
|
21
|
+
and sync time are `observed`. Tracked Markdown, untimestamped shell history, and other records that
|
|
22
|
+
cannot be classified remain `unknown`. Retrieval exposes this origin alongside the existing evidence
|
|
23
|
+
provenance.
|
|
24
|
+
|
|
25
|
+
### Changed
|
|
26
|
+
|
|
27
|
+
- Historical shell entries no longer receive timestamps inferred from history-file mtimes.
|
|
28
|
+
Missing timestamp, cwd, exit code, and duration metadata remain null, and incomplete shell
|
|
29
|
+
evidence is excluded from failure-to-fix correlation.
|
|
30
|
+
- Schema V13 adds `nodes.capture_mode` and nullable `nodes.source_ts`. Existing approximate
|
|
31
|
+
shell timestamps and document mtimes migrate to a null `source_ts`; other existing event timestamps are retained.
|
|
32
|
+
|
|
33
|
+
## [0.10.3] — 2026-08-31
|
|
11
34
|
|
|
12
|
-
|
|
35
|
+
### Added
|
|
36
|
+
|
|
37
|
+
- `hook git-post install|remove|status`: an opt-in git post-commit hook that runs a full
|
|
38
|
+
`nexusmem sync` (including embedding) in the background after every commit. Detached (`nohup ... &`),
|
|
39
|
+
so it never makes `git commit` itself wait; output goes to `.nexusmem/post-commit-sync.log` instead
|
|
40
|
+
of the terminal. `sync` gained a matching `--auto` flag (used only by this hook) that skips instead
|
|
41
|
+
of running if another `--auto` sync already holds an advisory lock over the project's workspace dir —
|
|
42
|
+
a burst of commits (e.g. a rebase) coalesces into one sync instead of piling up. The log file is
|
|
43
|
+
reset once it passes 2000 lines so it can't grow forever, and a skipped/coalesced run is always
|
|
44
|
+
reported there, even though the hook always passes `--quiet`.
|
|
45
|
+
|
|
46
|
+
### Known limitations
|
|
47
|
+
|
|
48
|
+
- A burst of commits fast enough to launch genuinely overlapping `sync --auto` processes can
|
|
49
|
+
interleave two runs' text mid-line in `.nexusmem/post-commit-sync.log` — the advisory lock
|
|
50
|
+
serializes the actual database writes (never at risk), not who gets to write to this diagnostic
|
|
51
|
+
log file. Cosmetic only; not planned to be fixed unless it turns out to matter in practice.
|
|
13
52
|
|
|
14
53
|
## [0.10.2] — 2026-08-30
|
|
15
54
|
|