build(deps): bump @mastra/evals from 1.6.0 to 1.7.0

[dependabot]

Bumps @mastra/evals from 1.6.0 to 1.7.0.

Release notes

Sourced from @​mastra/evals's releases.

February 24, 2026

Highlights

Background Process Management in Workspaces & Sandboxes

Workspaces now support spawning and managing long-running background processes (via SandboxProcessManager / ProcessHandle), with new tools like execute_command (background: true), get_process_output, and kill_process plus improved streaming terminal-style UI.

Runtime Tool Configuration Updates via Workspace.setToolsConfig()

You can dynamically enable/disable tools at runtime on an existing workspace instance (including re-enabling all tools by passing undefined), enabling safer modes like plan/read-only without recreating the workspace.

Observational Memory Reliability & Introspection Improvements

Core adds Harness.getObservationalMemoryRecord() for public access to the full OM record for the current thread, while @mastra/memory fixes major OM stability issues (shared tokenizer to prevent OOM/memory leaks, plus PostgreSQL deadlock fixes and clearer errors when threadId is missing).

Changelog

@​mastra/core@1.7.0

Minor Changes

• Added getObservationalMemoryRecord() method to the Harness class. Fixes #13392. (#13395)

  This provides public access to the full ObservationalMemoryRecord for the current thread, including activeObservations, generationCount, and observationTokenCount. Previously, accessing raw observation text required bypassing the Harness abstraction by reaching into private storage internals.

  const record = await harness.getObservationalMemoryRecord();
  if (record) {
    console.log(record.activeObservations);
  }

• Added Workspace.setToolsConfig() method for dynamically updating per-tool configuration at runtime without recreating the workspace instance. Passing undefined re-enables all tools. (#13439)

  const workspace = new Workspace({ filesystem, sandbox });
  // Disable write tools (e.g., in plan/read-only mode)
  workspace.setToolsConfig({
  mastra_workspace_write_file: { enabled: false },
  mastra_workspace_edit_file: { enabled: false },
  });
  // Re-enable all tools
  workspace.setToolsConfig(undefined);

• Added HarnessDisplayState so any UI can read a single state snapshot instead of handling 35+ individual events. (#13427)

  Why: Previously, every UI (TUI, web, desktop) had to subscribe to dozens of granular Harness events and independently reconstruct what to display. This led to duplicated state tracking and inconsistencies across UI implementations. Now the Harness maintains a single canonical display state that any UI can read.

  Before: UIs subscribed to raw events and built up display state locally:

... (truncated)

Changelog

Sourced from @​mastra/evals's changelog.

1.7.0

Minor Changes

• Added a summarization scorer to @mastra/evals. It grades a summary on two axes and returns the lower score, so a summary cannot pass by being faithful but empty, or thorough but wrong. (#20293)

  Alignment checks that every claim in the summary is supported by the source text. Coverage draws closed-ended questions from the source and answers them using the summary alone, in a separate call that never receives the source, so a missing fact cannot be answered from the source instead. The final score is min(alignment, coverage) × scale, and the reason names the axis that produced it.

  The source text defaults to the user message of the run input. Pass source or sourceExtractor when the text being summarized comes from somewhere else, such as a tool result. maxQuestions bounds the coverage questions so cost does not grow with document length.

  import { createSummarizationScorer } from '@mastra/evals/scorers/prebuilt';
  const scorer = createSummarizationScorer({
  model: 'openai/gpt-5.5',
  options: { maxQuestions: 10 },
  });
  const result = await scorer.run(run);
  result.score;

  This restores the summarization metric that was removed with the legacy evals system, rebuilt on the scorers pipeline.

Patch Changes

• Updated dependencies [4844167, c5e56ff, 594f7b2, 7f4e26d, 311f943, 322daa6, db4e6ff, 5faf93f, 82201f7, cadaa13, 0c89896, 6d19a65, 23b4238, 80ad891, fb18da5, fb18da5, e320a76, 03b4918, 14ef73a, b582f7f, 0a6598b, 06000d7, 1d677d5, 9e1dad8, 2f43145, 4e35a56, d94b8e1, 93e28ec, 729dab4, 484003d, 3de0188, 34d34d8, b582f7f, 933d291, a1cb98d, 598ad82, 1fd6aad]:
  • @​mastra/core@​1.56.0

1.7.0-alpha.0

Minor Changes

• Added a summarization scorer to @mastra/evals. It grades a summary on two axes and returns the lower score, so a summary cannot pass by being faithful but empty, or thorough but wrong. (#20293)

  Alignment checks that every claim in the summary is supported by the source text. Coverage draws closed-ended questions from the source and answers them using the summary alone, in a separate call that never receives the source, so a missing fact cannot be answered from the source instead. The final score is min(alignment, coverage) × scale, and the reason names the axis that produced it.

  The source text defaults to the user message of the run input. Pass source or sourceExtractor when the text being summarized comes from somewhere else, such as a tool result. maxQuestions bounds the coverage questions so cost does not grow with document length.

  import { createSummarizationScorer } from '@mastra/evals/scorers/prebuilt';
  const scorer = createSummarizationScorer({
  model: 'openai/gpt-5.5',
  options: { maxQuestions: 10 },
  });
  const result = await scorer.run(run);
  result.score;

... (truncated)

Commits

• b4c8440 chore: version - exit prerelease mode
• c5984b4 chore: version packages
• e7ae93a feat(evals): add summarization LLM scorer (#20293)
• d271d37 chore: migrate package builds to tsdown (#19829)
• bdeaef5 chore: migrate linting to oxlint (#20173)
• 3a507cb chore: migrate repository formatting to oxfmt (#19807)
• See full diff in compare view

[github-actions]

Coverage Report for server

Status	Category	Percentage	Covered / Total
🟢	Lines	98.38% (🎯 97%)	3173 / 3225
🟢	Statements	97.7% (🎯 96%)	3322 / 3400
🟢	Functions	98.74% (🎯 97%)	551 / 558
🟢	Branches	89.1% (🎯 87%)	1300 / 1459

File Coverage

No changed files found.

Generated in workflow #1928 for commit 684df28 by the Vitest Coverage Report Action

[github-actions]

Coverage Report for web

Status	Category	Percentage	Covered / Total
🟢	Lines	97.32% (🎯 96%)	1526 / 1568
🟢	Statements	96.24% (🎯 95%)	1613 / 1676
🟢	Functions	95.82% (🎯 95%)	643 / 671
🟢	Branches	90.77% (🎯 88%)	1013 / 1116

File Coverage

No changed files found.

Generated in workflow #1928 for commit 684df28 by the Vitest Coverage Report Action

[github-actions]

Coverage Report for shared

Status	Category	Percentage	Covered / Total
🟢	Lines	99.12% (🎯 98%)	226 / 228
🟢	Statements	81.2% (🎯 80%)	242 / 298
🟢	Functions	100% (🎯 98%)	76 / 76
🟢	Branches	63.52% (🎯 62%)	101 / 159

File Coverage

No changed files found.

Generated in workflow #1928 for commit 684df28 by the Vitest Coverage Report Action

[github-actions]

Coverage Report for widget

Status	Category	Percentage	Covered / Total
🟢	Lines	99.56% (🎯 98%)	229 / 230
🟢	Statements	99.19% (🎯 96%)	246 / 248
🟢	Functions	100% (🎯 98%)	45 / 45
🟢	Branches	95.96% (🎯 92%)	119 / 124

File Coverage

No changed files found.

Generated in workflow #1928 for commit 684df28 by the Vitest Coverage Report Action

[owk-owk130]

core 1.52.1 据え置きのまま上げられることを確認済み（バンドル・lint・テストとも緑）。同じ衛星グループの #1029 に検証内容をまとめてあります。同グループの @mastra/memory の workerd 実機確認が済んだらまとめてマージします。