Skip to content

fix: restore CI and Rust recall parity#19

Merged
rebel0789 merged 1 commit into
mainfrom
agent/fix-ci-rust-parity
Jul 13, 2026
Merged

fix: restore CI and Rust recall parity#19
rebel0789 merged 1 commit into
mainfrom
agent/fix-ci-rust-parity

Conversation

@rebel0789

Copy link
Copy Markdown
Owner

What changed

  • Restore the missing @memory-recall/semantic-setup workspace entry in package-lock.json, so clean installs succeed.
  • Bring the Rust memory implementation back into contract parity with Node:
    • add fact fingerprints,
    • keep explicit-ID proposals out of bulk approval,
    • report skipped explicit proposals,
    • align MCP identity and input schemas.
  • Refresh release provenance for the regenerated lockfile.

Root cause

The lockfile no longer represented the declared workspace, which made npm ci fail. The Rust implementation had drifted from the Node contract used by the recall conformance checks.

Validation

  • npm run ci — 655 tests passed, 144 evaluation gates passed.
  • cargo fmt --check
  • cargo test
  • cargo build --release
  • node scripts/rust-recall-conformance.mjs
  • Rust ingest, graph/query, distribution, intelligence, and evaluation quality gates.

@rebel0789 rebel0789 marked this pull request as ready for review July 13, 2026 09:40
@rebel0789 rebel0789 merged commit 40e0aae into main Jul 13, 2026
3 checks passed
@rebel0789 rebel0789 deleted the agent/fix-ci-rust-parity branch July 15, 2026 09:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant