chore: version packages - #104
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/master
branch
from
July 22, 2026 20:35
b4311ec to
70f6a82
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
agentsmesh@0.32.0
Minor Changes
9efbab1: Detect stale files in managed generated-output locations during
agentsmesh check, and exposecanonicalDrift,outputDrift, andoutputsStaleacross CLI, programmatic, and MCP results.a722921: Lessons recall now escalates on repeat failures. When
agentsmesh lessons hookruns as aPreToolUsefirst-touch guard and the exact action about to run has already failed twice or more (per the opt-in outcome log) with a captured lesson covering it, the covering rule is re-injected above the normal recall bullets as aRECURRENT FAILUREescalation — and it cuts through per-session dedup, since a rule the agent saw but did not apply must be shown again. Advisory context only, once per action per session; the covering rule is shown exactly once (the escalation is its delivery), and the default telemetry-off path is unaffected.Effectiveness telemetry is now attributed per harness session. The hook stamps the harness
session_id(and a per-batch relevancerank) onto thedelivered/failurerows of.agentsmesh/lessons/outcome-log.jsonland onto recall telemetry, soagentsmesh lessons statsgroups by real sessions and a failure only impeaches deliveries from its own session — noAGENTSMESH_SESSION_IDexport needed on hook-driven recalls.Added an opt-in
repairTriggersflag (defaultfalse) in.agentsmesh/lessons/config.jsonthat repairs degraded triggers at capture time: a broad or widefile_globis narrowed toward the evidence file's directory class, a stopworded or over-long keyword gets a matchable variant added beside it, and a keyword that tokenizes to nothing is dropped — each surfaced as aNARROWED_GLOB/KEYWORD_VARIANT_ADDED/DROPPED_KEYWORDwarning on the capture result. It never blocks a capture, never rewrites a glob without covering evidence, and never leaves a lesson with zero triggers.