Skip to content

Nuzo 1.1.0

Latest
Latest

Choose a tag to compare

View all tags
@fabionfsc fabionfsc released this 14 Jul 17:42
v1.1.0
5e73798
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Added

  • A Registry-ready @nuzo/memory-mcp distribution now exposes one deterministic stdio entrypoint and canonical mcpName while reusing the shared MCP server implementation.
  • A version-aligned server.json, official publisher validation, staged npm continuity smoke, and maintainer publication runbook prepare Nuzo for the preview MCP Registry.

Changed

  • Public adoption guidance now includes a disposable 60-second demo, a decision guide for repository files and native memory, a dated comparison of adjacent agent-memory systems, focused installation feedback, and an executable launch playbook.
  • Dense capture-suggestion scopes now use an indexed exact-duplicate lookup and bounded SQLite FTS prefilter instead of materializing every active memory; non-exhaustive evidence continues to fail closed as uncertain.
  • Public presentation now uses a polished post-1.0 landing page, README, and package README narrative for clearer first-time evaluation.

Fixed

  • MCP challenge and relationship mutations now attribute audit events to the trusted server actor instead of accepting caller-supplied attribution, and read-only host hooks skip cleanly, staying fail-open for the host session, when they encounter a newer unsupported SQLite schema.
  • Codex and Claude Code plugin hooks now anchor published npm resolution at the plugin root, and the Codex MCP server uses its host-resolved plugin directory, preventing a user's npm workspace from shadowing the pinned Nuzo runtime.
  • Published host canaries now create and verify fixtures with the public CLI, avoiding false forward-schema failures after a newer SQLite migration lands on main.
  • GitHub Pages deploys now retry once inside the deploy job when the Pages backend returns a transient failure after accepting the artifact.
  • GitHub Pages deployments now use explicit Pages configuration and queue deploy attempts instead of canceling an in-progress Pages deployment.
  • Docker installer smoke tests now derive their pinned package version from the repository release instead of continuing to exercise the previous public version after a release bump.

The npm and MCP Registry release is bound to the retained dry-run artifact from workflow run 29312594381 at source commit 5e737986f28d09453d8fc012fc8eb1dd53e3583f.

Assets 2
Loading