@ai-matrx/agents 0.21.9 → 0.21.11

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,17 +1,57 @@
1
1
  # Changelog
2
2
 
3
- ## 0.21.9
3
+ ## 0.21.11
4
4
 
5
5
  Automatic changed-only republish (docs/metadata drift since the last tag — see
6
- `git diff npm/matrx-agents/v0.21.8..npm/matrx-agents/v0.21.9 -- apps/shared/matrx-agents`).
6
+ `git diff npm/matrx-agents/v0.21.10..npm/matrx-agents/v0.21.11 -- apps/shared/matrx-agents`).
7
7
  No source changes intended and no consumer action required.
8
8
 
9
- ## 0.21.8
9
+ ## 0.21.10
10
10
 
11
11
  Automatic changed-only republish (docs/metadata drift since the last tag — see
12
- `git diff npm/matrx-agents/v0.21.7..npm/matrx-agents/v0.21.8 -- apps/shared/matrx-agents`).
12
+ `git diff npm/matrx-agents/v0.21.9..npm/matrx-agents/v0.21.10 -- apps/shared/matrx-agents`).
13
13
  No source changes intended and no consumer action required.
14
14
 
15
+ ## 0.21.9
16
+
17
+ ### Fixed
18
+
19
+ - `receiptRowToResolved` now rebuilds `layers` from what the server applied, so a read-only
20
+ table shows the applied limit (e.g. 12000, 2500) as the inherited Inline max instead of 200,
21
+ and the layer breakdown marks the layer that decided it (default → `default_max`, page →
22
+ `surface.max_inline_chars`, agent → declared `agent.max_inline_chars`; "you" stays on
23
+ `userRule`; page auto_context off and the agent kill switch / re-admit are rebuilt too).
24
+ - `ContextRulesTable` comfortable density (the chip's bottom sheet) at 375px: Item no longer
25
+ starves to one letter. Fixed columns are `2.75rem / 3.5rem / 6.75rem`, the per-row layer badge
26
+ is gone (the layer is in the row tooltip and the detail view), labels truncate with an ellipsis.
27
+
28
+ ### Consumer action
29
+
30
+ - matrx-frontend: delete the `layers.default_max` patch over `receiptRowToResolved`
31
+ (message-context-receipt) and the STOPGAP resource-ref pass-through in
32
+ `context-rules/request-context.ts` (fixed in 0.21.8).
33
+
34
+ ## 0.21.8
35
+
36
+ ### Fixed (in `./context`)
37
+
38
+ - `buildContextWire` wrapped a top-level resource reference (`{ __kind: "resource_ref", … }`, e.g.
39
+ an `attached_file_<id>` from `createResourceReference`) as `{ content: <ref>, label }`. The server
40
+ promotes only TOP-LEVEL references, so the attached document silently stopped resolving. A value
41
+ the server acts on by shape now ships exactly as-is (no label/type/description/limit added):
42
+ any `__kind: "resource_ref"` object, and a bare UUID under a `*_id` key (`file_id`,
43
+ `attached_file_id`, `current_note_id`, …).
44
+
45
+ ### Added
46
+
47
+ - `isWireDirective(key, value)`. Corpus `wire_passthrough_cases`, run here and by aidream pytest
48
+ against `normalize_resource_context` (promoted as-is, never promoted wrapped).
49
+
50
+ ### Consumer action
51
+
52
+ - matrx-frontend: none beyond upgrading — references built with `createResourceReference` resolve
53
+ again when sent through `buildContextWire`.
54
+
15
55
  ## 0.21.7
16
56
 
17
57
  Automatic changed-only republish (docs/metadata drift since the last tag — see