v3.2.11

v3.2.11 - Mem0 smoke-test + release boundary + focused QA hardening

This release updates shared Mem0 onboarding and inspector behavior, and makes
release preparation checks cleaner and safer.

Fixed

• Mem0 shared/provider QA now distinguishes process exit success from semantic
  JSON success and proves useful live add/search/recall/list results.
• OpenAI embedding setup and health are reported separately from live recall;
  quota-blocked recall is no longer counted as a pass.
• Shared provider root metadata is kept consistent across configure/setup/status,
  and project-local Unicode paths use an ASCII-safe UTF-8 Node/Python bridge.
• Agent-facing Mem0 setup output no longer contains mojibake.
• Release/evaluation checks reject ok: false, failure statuses, and unexpected
  nested semantic failures even when the command exits 0.
• Flow and update verification now reject a semantically broken doctor or
  nested command result even when the child process exits 0.
• Update verification compares installed system files with the selected source
  by SHA-256, proves preservation of pre-existing protected curated files after
  all post-checks, and records whether the local rollback backup is safe to
  remove.
• Updates from an installed but not yet initialized artifact now select one
  non-interactive import before final release verification; initialized
  projects keep the direct release refresh path.
• Routing bundle generation accepts current and legacy external-memory provider
  metadata shapes during the first migration pass.
• Verified update backups can be pruned explicitly; unverified backups are
  retained, while legacy project-root backups and generated QA/baseline folders
  are excluded from knowledge discovery.
• Release artifacts require the current release note and reject notes newer
  than the artifact version.
• Runtime-generated reports now take their schema version from the installed
  system version, and focused schema hygiene rejects stale/future schemas.
• The public benchmark runner packages its evidence with the public ZIP helper
  and no longer depends on maintainer-only release tooling.
• Quick release checks fail closed when the git comparison baseline is
  incomplete and direct the maintainer to the required full/conformance path.
• Public artifact packaging no longer ships maintainer-only release tooling and runtime
  metadata state files.
• Inspector auto-update UI is now single-action by default and surfaces explicit
  on-session state.
• Release validation now enforces release-policy required/forbidden lists in packaging
  checks for user-facing artifacts.
• Memory smoke tests and focused checks now validate shared provider behavior and local
  defaults more deterministically.
• Free-core graph diagnostics validate structural trust invariants instead of a
  project-size-dependent node threshold.
• Team-mode doctor flow now regenerates the workspace health state before
  evaluation and validates append-only events in the shared repository event
  store, so semantic checks no longer hide or misclassify an uninitialized
  workspace.

Notes

• self-test-install-policy expects this release note file to exist as
  .release-notes/v3.2.11.md; it is now present for deterministic bootstrap/update
  coverage.
• Full release gate status is reported separately from focused preparation
  checks and must not be inferred from process exit codes alone.

v3.2.10

v3.2.10 - Mem0 storage diagnostics patch

v3.2.10 tightens Mem0 shared/project-local storage reporting after real-world
Qdrant lock recovery testing.

Fixed

• Status now follows the actual configured Qdrant path when config.meta.json
  has stale provider_scope metadata.
• Stale shared/project-local metadata is reported through
  metadata_scope_mismatch, metadata_provider_scope, and
  path_inferred_provider_scope.
• Qdrant lock and permission failures are classified as storage availability
  problems instead of missing Mem0/Python runtime installs.
• Mem0 runtime/package availability stays cached when the Python runtime works
  but the configured Qdrant storage is locked or not writable.
• Next commands for Qdrant lock/permission failures no longer suggest generic
  setup as the repair path.
• Inspector update status now shows a single Update action plus an
  Auto-check: On/Off mode for launch-time update checks.
• Inspector update status responses explicitly report that automatic apply is
  disabled and manual confirmation is required.
• Inspector Turn off now gives immediate in-page feedback while the local
  server shuts down.
• Inspector generated HTML no longer includes stale mojibake UI text.
• Public release packaging now excludes maintainer-only self-tests that depend
  on internal release packaging/validation tools.

Guidance

• Shared per-user Mem0 provider storage remains the default.
• Project-local provider storage remains an explicit user choice via
  --provider-scope project.
• Agents must repair a shared Qdrant lock or permission issue directly before
  changing provider scope.

Verification

• node .knowledge/tools/self-test-memory-providers.js
• node .knowledge/tools/self-test-memory-providers.js --recipe-quality-only
• node .knowledge/tools/doctor.js --json
• node .knowledge/tools/self-test-inspector-ui.js --json
• node .knowledge/tools/self-test-inspector-update-e2e.js
• node .knowledge/tools/self-test-inspector-actions.js --json
• node .knowledge/tools/self-test-inspector-launcher.js --json
• node .knowledge/tools/self-test-inspector-next-actions.js
• node .knowledge/tools/self-test-free-core-graph.js

Full release gate was not run for this patch preparation.

v3.2.9

v3.2.9 - Inspector update polish and Local FastEmbed hardening

v3.2.9 improves the local Inspector update experience and tightens Mem0 Local
FastEmbed runtime behavior for agent-guided installs.

Changed

• Simplified the live Inspector update panel to one Update action backed by the
  existing launch-time release check.
• Refreshed the live Inspector update state in the current session after apply,
  including the topbar chip, banner state, current version, and action button.
• Clarified Mem0 status semantics across offline status, live runtime health,
  and operational list/add/search/recall smoke checks.
• Added fastembed_onnx_external_data_path_error for Local FastEmbed ONNX
  model-cache failures and kept cached Mem0 runtime status available when that
  operational layer fails.
• Added fastembed_model_download_timeout for first-run Local FastEmbed model
  warmup/download timeouts, with long-timeout retry guidance and cached Python
  runtime reuse.
• Added docs/cookbook/12-mem0-shared-provider-storage.md for existing
  projects that need to adopt the shared per-user provider storage default with
  explicit --provider-scope shared.
• Live Mem0 Python selection now prefers the configured runtime from
  config.meta.json over stale runtime-status cache entries.
• Mem0 provider status now reports configured=true when config.json exists,
  even if there is no install approval receipt.

Safety

• Live Mem0 add/search/recall/list require explicit provider config before
  storage startup, preventing an accidental fallback to default /tmp/qdrant.
• Public artifacts continue to exclude runtime Mem0 config/state, local paths,
  private notes, and maintainer-only release/QA tooling.

Verification

• Full local release gate passed.
• Public artifact validation passed with 319 entries and 0 violations.
• Inspector next-action, launcher, UI, action, and update e2e checks passed.
• Mem0 focused checks passed, including provider choice, shared storage,
  unsupported FastEmbed runtime guard, cache diagnostics, and status semantics.
• Live Mem0 Local FastEmbed health/add/search/recall/list passed using
  intfloat/multilingual-e5-large at 1024 dimensions.
• Docker/Linux release gate passed during release preparation.

Compatibility Note

• Native macOS/iOS runtime testing was not run for this release. macOS
  compatibility is covered only indirectly through POSIX/Linux Docker checks.

v3.2.8

v3.2.8 - Mem0 shared provider onboarding

v3.2.8 tightens Mem0 onboarding so agents must ask which embedding backend to
use and makes shared per-user provider storage the default.

Changed

• setup mem0-oss --live --json now stops with
  setup_status: needs_embedding_provider_choice when no embedding backend is
  configured.
• Setup no longer silently writes an OpenAI embedding config.
• write-recipe mem0-oss --json no longer creates Mem0 config as a side
  effect.
• Default Mem0 provider storage is shared per OS user, with project-keyed
  Qdrant/history/runtime directories.

Added

• Explicit project-local provider storage with --provider-scope project.
• docs/cookbook/11-mem0-project-local-provider.md for the rare project-local
  path.
• Mem0 status/config metadata for provider scope, shared provider root, project
  storage key, Qdrant path, and history DB path.

Safety

• OpenAI API and Local FastEmbed remain explicit guided choices.
• Runtime/user state stays outside public release artifacts.
• Mem0 remains advisory-only external memory.

v3.2.7

v3.2.7 - Mem0 embedding backend choice and Inspector file links

v3.2.7 makes Mem0 embedding backend selection an explicit guided install choice
and fixes live Inspector next-action links in the Trust Graph.

Added

• configure-embeddings for mem0-oss, with separate OpenAI and FastEmbed
  embedding backend configuration.
• OpenAI embedding setup for text-embedding-3-small without storing API keys
  in repository files.
• Local FastEmbed setup guidance with pinned fastembed==0.5.1, runtime
  compatibility guard, model dimension detection, and separate Qdrant
  collection creation.
• Mem0 cookbook coverage that distinguishes LLM provider, embedding provider,
  vector store, and history store.
• Automated Inspector next-action smoke coverage for live /api/files/open
  behavior.

Fixed

• FastEmbed configuration blocks reuse of an OpenAI 1536-dimension Qdrant
  collection.
• Visual Inspector Trust Graph next actions open module cards and referenced
  files through token-protected local file APIs.
• Public release packaging excludes maintainer-only release, QA, CI, and
  validation tooling.
• Public release validation blocks maintainer-only files if they leak into the
  user-facing ZIP.
• Mem0 docs use safe API-key placeholders instead of secret-like assignments.

v3.2.6

v3.2.6 - Mem0 guided setup and recipe gate

v3.2.6 turns Mem0 OSS onboarding into a guided product flow. Agents now have one
recommended setup command, deterministic cookbook generation, validation, and an
Inspector onboarding card instead of hand-assembled memory commands.

Added

• node .knowledge/tools/memory-provider.js setup mem0-oss --live --json.
• write-recipe and validate-recipe for the Mem0 cookbook page.
• Repo-local Mem0 config and runtime status cache under
  .knowledge/external_memory/mem0.
• Inspector Mem0 onboarding card with copy actions for install, setup, health,
  add, search, and recall.
• Release gate coverage for Mem0 recipe quality.

Fixed

• Status and status-all remain offline-safe while reflecting cached live health.
• Receipt, runtime availability, and package install state are reported
  separately.
• Live Mem0 search/list use Mem0 2.0.4 filter-based calls.
• Live setup rejects mismatched or unreported Mem0 runtime versions and returns
  one exact pinned install command.
• Offline status and Inspector show cached Mem0 runtime version and pin match.
• Live operation output labels embedding-provider behavior for add, search, and
  recall.

v3.2.5 - Inspector first-run, updater, graph shelf, and shutdown

v3.2.5 - Inspector first-run, updater, graph shelf, and shutdown

v3.2.5 focuses on making the local Inspector feel like the real control surface
after install: it opens for First-run setup, shows update status clearly, can
apply verified system updates with confirmation, and can shut itself down from
the UI.

Added

• Live Inspector Turn off button that closes the local server and releases the
  port.
• Collapsible Free Core Trust Graph shelf directly under Knowledge Trust metrics.
• In-page graph node drilldown instead of raw links to broken local pages.
• Inspector update dry-run/apply APIs backed by the existing safe
  update-system-files.js path.
• Deterministic updater e2e test that simulates a future release zip.

Fixed

• Inspector launcher normalizes project roots to .knowledge before writing
  logs, preventing stray root-level maintenance/ folders.
• Install/import flow now returns explicit chat copy that .knowledge already
  works and Inspector is open for First-run setup.

v3.2.4 - Install source and integration selection hotfix

v3.2.4 - Install source and integration selection hotfix

v3.2.4 tightens the public install path so agents select the current curated
release asset instead of old generic assets, GitHub source archives, or source
checkouts copied into target repositories.

Install note: For new installs, always start from
https://github.com/pro2pilot/knowledge/releases/latest and download the
attached asset named knowledge-vX.Y.Z.zip that matches the latest release
tag. Do not use GitHub "Source code" archives, GitHub "Download ZIP",
default.knowledge.zip, .knowledge.zip, knowledge.zip, or git clone as
an install package.

Fixed

• Update checks now accept only the exact knowledge-v<tag>.zip asset from the
  latest GitHub release and no longer fall back to generic or older ZIP assets.
• First-run integration install no longer treats --all as a normal setup path;
  installing every agent bridge now requires explicit --all --confirm-all.
• A no-runtime integration run now returns runtime_required without creating
  AGENTS.md, CLAUDE.md, .agents/, .claude/, .opencode/, or other
  vendor bridge folders.

Added

• Agent-facing docs for connecting another agent later to the same already
  installed .knowledge/ repository.
• A focused update-selection self-test that proves old/generic assets are not
  selected when a current exact release asset exists.

Upgrade Note

Existing installs do not need to reinstall the whole system. To add another
agent to an already installed repo, keep the existing .knowledge/ folder and
run only that agent's bridge command:

node .knowledge/tools/install-check.js --json
node .knowledge/tools/install-agent-integrations.js --runtime <new-agent>
node .knowledge/tools/flow.js doctor

v3.2.3 - Install source-checkout hotfix

Warning

Archived release. Do not use this page for new installs.
For new installs, always use the current latest GitHub release:
https://github.com/pro2pilot/knowledge/releases/latest

Download only the attached asset named knowledge-vX.Y.Z.zip that matches the latest release tag. Do not use GitHub "Source code" archives, GitHub "Download ZIP", default.knowledge.zip, .knowledge.zip, knowledge.zip, or git clone as an install package.

v3.2.3 - Install source-checkout hotfix

v3.2.3 closes an install footgun where an agent could clone this repository
into a target project, leave it as knowledge-src/, and then import that
source checkout as if it were project code.

Install note: For new installs, always start from https://github.com/pro2pilot/knowledge/releases/latest and download the attached asset named knowledge-vX.Y.Z.zip that matches the latest release tag. Do not use GitHub "Source code" archives, GitHub "Download ZIP", default.knowledge.zip, .knowledge.zip, knowledge.zip, or git clone as an install package.

Added

• Root INSTALL.md with an agent-focused install contract.
• Machine-readable install-policy.json for agents and tooling.
• install-check detection for source checkouts in the target root, including knowledge-src/.
• Release self-tests that prove source checkouts are blocked before import and ignored by direct ingest/sync fallbacks.

Changed

• flow import now runs install-check before ingest.
• ingest-existing-project.js ignores detected .knowledge source checkouts instead of registering them as project modules.
• sync-tracked.js --scan --discover ignores detected .knowledge source checkouts.
• README keeps the install warning visible while moving detailed agent-only instructions into a collapsed contract.

Fixed

• A fresh install can no longer silently produce knowledge_src modules and large repair queues from installer source files left in the target project.

v3.2.2

Warning

Archived release. Do not use this page for new installs.
For new installs, always use the current latest GitHub release:
https://github.com/pro2pilot/knowledge/releases/latest

Download only the attached asset named knowledge-vX.Y.Z.zip that matches the latest release tag. Do not use GitHub "Source code" archives, GitHub "Download ZIP", default.knowledge.zip, .knowledge.zip, knowledge.zip, or git clone as an install package.

v3.2.2 - Release cleanup and bridge integrations

v3.2.2 cleans the public install surface and adds explicit bridge support for OpenClaw and Hermes.

Install note: Do not use GitHub "Download ZIP" as the install package. Use the release asset only.

Added

• --runtime openclaw installs AGENTS.md plus .agents/skills/.
• --runtime hermes installs the generic AGENTS.md bridge without creating an unconfirmed vendor folder.
• Quick-Start and integration docs now list OpenClaw and Hermes directly while Pi remains a manual bridge target.

Changed

• Active version and schema markers are updated to 3.2.2.
• Release artifact commands and validation examples now point to dist/knowledge-v3.2.2.zip.
• Graphiti and Zep are described as not bundled in the free/core install asset.

Removed

• Stale debug/pro export commands and marketing-pack generation from the public release line.
• Source runtime proof folders that are not part of the install asset.