@ai-matrx/agents 0.21.16 → 0.21.18

package/CHANGELOG.md

@@ -1,5 +1,32 @@
 # Changelog
 
+## 0.21.18
+
+Automatic changed-only republish (docs/metadata drift since the last tag — see
+`git diff npm/matrx-agents/v0.21.17..npm/matrx-agents/v0.21.18 -- apps/shared/matrx-agents`).
+No source changes intended and no consumer action required.
+
+## 0.21.17
+
+### Fixed (in `./context`) — a saved rule lands the same whichever side "declares" the key
+
+Live drift: `current_note_published_to_web` is declared on `matrx-user/notes` by the client's
+code manifest but not by the server's DB manifest, so the client filed it under the page and the
+server under `_default`; a rule the person saved never reached the server.
+
+### Added
+
+- `lookupSavedRuleFor(rows, primarySurface, surfaceKey, key)`: while a primary surface P is in
+  play, a key filed under `_default` or P resolves to the per-field merge `_default[K]` then
+  `rows[P][K]` (P wins); a surroundings key keeps its own surface; no P = `lookupSavedRule`.
+- `resolveContextRow(source, savedRows, cap?, primarySurface?)` uses it.
+- Corpus `effective_lookup_cases` (the server's `lookup_user_rule_for` runs the same cases).
+
+### Consumer action
+
+- matrx-frontend: pass the page's primary surface key as `resolveContextRow`'s 4th argument.
+  Saving is unchanged (page values to P, everything else to `_default`).
+
 ## 0.21.16
 
 Automatic changed-only republish (docs/metadata drift since the last tag — see