Skip to content

v3.7.0

Latest
Latest

Choose a tag to compare

View all tags
@Magnifico4625 Magnifico4625 released this 10 Jun 10:40
· 1 commit to main since this release
v3.7.0
84fa294
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Locus v3.7.0 Release Notes

v3.7.0 is the Track D Codex memory reliability release.

It keeps the Track C richer recall work and adds stronger project isolation, date-aware recall, calendar discovery, freshness diagnostics, and current project-state summaries.

Added

  • Project-scoped recall/search/timeline over Codex conversation events, semantic memories, and durable memories.
  • Date-aware recall metadata: localDate, weekKey, monthKey, resolved ranges, and searched date buckets.
  • memory_calendar for day/week/month activity buckets before drilling into a broad period question.
  • memory_project_state for normalized project root/hash, package metadata, git state, latest project conversation timestamp, active durable counts, warnings, and active next steps.
  • Codex freshness diagnostics in memory_status and memory_doctor, including latest rollout timestamp versus latest imported event timestamp.
  • Codex surface diagnostics with LOCUS_CODEX_SURFACE=desktop|extension|cli as a diagnostic/debug override.
  • Same-topic durable lifecycle behavior where positive validation facts can supersede active Track D next steps.

Fixed

  • Existing legacy durable memories with NULL project_root can be used as a bounded fallback when strict scoped durable recall finds no current-project row.
  • Legacy V1 semantic memory tables without project_root remain writable before migration repair.
  • Hook subprocess tests now use an isolated test storage root instead of writing to the user's live Codex storage path.

Validation

  • Focused Track D gate: 32 files passed, 297 tests passed.
  • Full repository gate: npm run check passed with 122 files and 1343 tests.
  • Build gate: npm run build passed and regenerated dist/cli.js and dist/server.js.
  • Local npm package smoke:
    • npm pack produced locus-memory-3.7.0.tgz with 12 intended runtime files.
    • The tarball contains fresh dist, Codex README/config, canonical skill, plugin .mcp.json, plugin manifest, plugin skill, and these release notes.
    • Package and plugin manifest versions inside the tarball are both 3.7.0.
    • A clean temp install from the tarball reported locus-memory --version as 3.7.0.
    • Pre-publish install codex --yes passed with LOCUS_CODEX_RUNTIME_PACKAGE=<tgz> and a temp CODEX_HOME, configuring MCP through npm exec --package <tgz> -- locus-memory mcp.
  • Registry npm package smoke:
    • npm view locus-memory@3.7.0 version returned 3.7.0.
    • npm view locus-memory dist-tags --json returned "latest": "3.7.0".
    • A clean registry install from C:\tmp\locus-registry-smoke-3.7.0 reported npx --yes locus-memory@3.7.0 --version as 3.7.0.
    • npx --yes locus-memory@3.7.0 install codex --yes completed with an isolated CODEX_HOME.
    • codex mcp get locus showed command: npx.cmd and args: -y locus-memory@3.7.0 mcp.
  • Runtime smoke:
    • PATH Codex CLI reported codex-cli 0.138.0.
    • Codex Desktop-bundled CLI reported codex-cli 0.137.0-alpha.4.
    • With CODEX_HOME=C:\Users\Admin\.codex, codex mcp list and codex mcp get locus confirmed locus is enabled and points at this repo's dist/server.js.
    • The active Desktop MCP session answered memory_status, memory_doctor, and memory_recall, but still exposed the previous tool registry until reload; new live tools such as memory_calendar and memory_project_state require MCP/Desktop session reload before a live smoke can claim them.

Known Boundaries

  • Codex CLI remains the primary validated path.
  • Codex Desktop MCP marker behavior is covered by Track D tests and local MCP config smoke; live Desktop sessions may need a reload to expose new tool schemas.
  • Codex extension parity remains target-surface validation work.
  • LOCUS_CODEX_SURFACE is diagnostic/debug configuration, not normal user-facing setup.
  • Richer evidence-anchor display for commits, files, docs, command results, and timestamps remains a follow-up.
  • Topic keys are isolated by projectRoot; separate user-configurable topic namespace filters remain a follow-up unless project-root isolation proves insufficient.
  • LOCUS_CODEX_RUNTIME_PACKAGE is release-validation-only for local tarball smoke; published user installs should use the default pinned registry runtime.
Assets 2
Loading