# Changelog
All notable changes to `mx` are documented here.
The format is loosely based on [Keep a Changelog](https://keepachangelog.com).
## [Unreleased]
### Added
- `mx memory list` and `mx memory search` now emit a best-effort **stderr**
hint when the caller's own private entries match the query but are hidden by
the public-only default (Issue #400). The hint reads
`note: N private entr(y|ies) of yours matched but ... hidden; use
--include-private to see them`. It fires only when `MX_CURRENT_AGENT` is set
and neither `--include-private` nor `--mine` was given. **No change** to
stdout, `--json` output, or exit codes — the hint is STDERR only and any
error computing it is swallowed silently. The hint is **suppressed under
`search --semantic`**: its count uses the BM25 `@@` text predicate, which does
not agree with vector similarity, so counting there would both under- and
over-report relative to what `--include-private --semantic` actually shows.
### Fixed
- Embedded schema application now retries transient SurrealDB
"read or write conflict … can be retried" errors with jittered backoff
(bounded, `IF NOT EXISTS`-idempotent). Fixes flaky failures when several `mx`
processes initialize a fresh store concurrently (surfaced by the integration
test suite under parallel load). No change on the happy path — retries only
run on a contended init.
### Changed
- Documented the `--min-resonance` basis divergence (Issue #404): `wake`
filters on **raw** stored resonance, while `list`/`search` filter on
time-decayed **effective** resonance. Behavior is unchanged; the flag help
text now states which basis each command uses until an explicit
`--resonance-basis raw|decayed` flag lands in #404.