nexusmem 0.10.3 → 0.10.4

package/CHANGELOG.md

@@ -7,9 +7,28 @@ Tags were added retroactively on 2026-08-11 and point at the exact commits the n
 built from, matched by publish timestamp: `v0.1.0` → `67a4776`, `v0.1.1` → `809e62c`,
 `v0.1.2` → `b22a3b0`.
 
-## [Unreleased]
-
-No unreleased changes yet.
+## [Unreleased]
+
+No unreleased changes yet.
+
+## [0.10.4] — 2026-09-07
+
+### Added
+
+- Fresh-project syncs classify reconstructable Git commits and diffs, timestamped shell history,
+  and already-supported opt-in coding-agent history as `backfilled` only when a trustworthy source
+  timestamp predates NexusMem initialization. Trustworthily timestamped events between initialization
+  and sync time are `observed`. Tracked Markdown, untimestamped shell history, and other records that
+  cannot be classified remain `unknown`. Retrieval exposes this origin alongside the existing evidence
+  provenance.
+
+### Changed
+
+- Historical shell entries no longer receive timestamps inferred from history-file mtimes.
+  Missing timestamp, cwd, exit code, and duration metadata remain null, and incomplete shell
+  evidence is excluded from failure-to-fix correlation.
+- Schema V13 adds `nodes.capture_mode` and nullable `nodes.source_ts`. Existing approximate
+  shell timestamps and document mtimes migrate to a null `source_ts`; other existing event timestamps are retained.
 
 ## [0.10.3] — 2026-08-31
 

package/README.md

@@ -23,6 +23,8 @@ The shell history is the part worth caring about. Git tells an agent what shippe
 tells it what was attempted, in what order, and which commands exited non-zero. That information
 exists nowhere else, and it disappears when your terminal scrollback rolls over.
 
+![How NexusMem works: git commits, shell commands with their real exit codes, docs, and GitHub threads flow into a local SQLite index, which returns a ranked, token-budgeted slice of that history so your coding agent answers with a real citation instead of a guess](docs/how-it-works.svg)
+
 **Contents:** [Try it](#try-it) · [Exact shell capture](#optional-exact-shell-capture) ·
 [Failure → fix chains](#failure--fix-chains-opt-in) · [How retrieval works](#how-retrieval-works) ·
 [Session summaries](#session-summaries-optional-local-model) ·
@@ -539,6 +541,11 @@ Tests are behavioral rather than snapshot-based, and several are regressions tie
 observed failures. `tests/git-errors.test.ts` injects a fake `spawn` to exercise the Windows
 process-spawn faults, which cannot be provoked on demand.
 
+Bug fixes, test coverage, and small focused features are welcome — see
+[CONTRIBUTING.md](CONTRIBUTING.md) for the workflow, or browse issues labeled
+[`good first issue`](https://github.com/yaminbkk/nexusmem/labels/good%20first%20issue)
+for something scoped and self-contained to start with.
+
 ## On how this was built
 
 This started as an experiment in whether a local context-memory engine for coding agents was viable,