daftari 1.11.0 → 1.12.1

package/CHANGELOG.md

@@ -7,6 +7,55 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [1.12.1] - 2026-05-26
+
+### Fixed
+
+- **MCPB now runs on Node 24 hosts.** The v1.12.0 `.mcpb` only shipped
+  `better-sqlite3` binaries built against Node 22 (ABI v127); on a Node
+  24 host (ABI v137) the loader failed with `NODE_MODULE_VERSION`
+  mismatch and the server never booted. `scripts/pack-mcpb.mjs` now
+  fetches both ABIs for both platforms (4 binaries total: darwin-arm64
+  × {v127, v137} + win32-x64 × {v127, v137}) and stages each under
+  `build/Release-${platform}-${arch}-${modules}/`. The loader patch in
+  `better-sqlite3`'s `lib/database.js` now includes
+  `process.versions.modules` in the path, so the right binary is
+  selected at runtime for the host's Node version. Sharp and
+  onnxruntime-node are NAPI-based (ABI-stable across Node versions)
+  and don't need this treatment.
+
+## [1.12.0] - 2026-05-26
+
+### Added
+
+- **Cross-platform MCPB packaging (#66).** The `.mcpb` artifact now
+  boots on both macOS (arm64) and Windows (x64). A single universal
+  package bundles platform-tagged native binaries for `better-sqlite3`
+  (under `build/Release-${platform}-${arch}/`) and `sharp`, and a
+  one-line loader patch in `better-sqlite3`'s `lib/database.js`
+  selects the right binary at runtime from `process.platform` /
+  `process.arch`. The manifest's `compatibility.platforms` is back
+  to `["darwin", "win32"]`. `npm run pack:mcpb` (new) builds the
+  universal artifact from a darwin-arm64 host.
+
+- **MCP tool annotations.** All 14 tools now carry a `title` and the
+  appropriate safety hint — `readOnlyHint` for read/search/analysis
+  tools, `destructiveHint` for write and curation tools. MCP clients
+  use these to label tools and to decide when to prompt for
+  confirmation before a call.
+
+### Fixed
+
+- **`vault_write` no longer rejects writes that omit `updated` /
+  `updated_by`.** The server stamps both fields on every write, so requiring
+  callers to also supply them was redundant — and a caller who omitted them
+  (reasonably) got `invalid frontmatter: updated: missing required field;
+  updated_by: missing required field`. The fields are now filled in before
+  built-in schema validation runs, then re-stamped post-validation by
+  `performWrite` as before. Callers that still supply them keep working — the
+  server-side stamp wins, identical to the previous behavior. The MCP input
+  schema description now flags both fields as server-managed.
+
 ## [1.11.0] - 2026-05-21
 
 ### Added