ur-agent 1.59.0 → 1.60.0
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,5 +1,32 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 1.60.0
|
|
4
|
+
|
|
5
|
+
- Added `ur memory-integrity`, tamper-evidence for the file-backed memory
|
|
6
|
+
stores. Project task memory was hash-chained and could prove tampering; the
|
|
7
|
+
auto-memory and team-memory directories had nothing, and their contents are
|
|
8
|
+
injected straight into context. A chain over append-only lines does not
|
|
9
|
+
describe a mutable file tree, so this is a digest manifest: it detects files
|
|
10
|
+
modified, deleted outside UR, and — the case that matters most — dropped in
|
|
11
|
+
by something else, which is an injection vector with a direct path to the
|
|
12
|
+
model. `quarantine` moves suspect files aside rather than deleting them, and
|
|
13
|
+
`verify` exits non-zero so it can gate.
|
|
14
|
+
- Deletion is now provable: removing an entry rewrites the manifest, so a
|
|
15
|
+
previously-deleted memory that reappears is reported as untracked instead of
|
|
16
|
+
being quietly reloaded.
|
|
17
|
+
- The release gate now grades recorded eval trajectories and writes versioned
|
|
18
|
+
per-category scores to `dist-release/trajectory-scores.json`. A run that
|
|
19
|
+
edited files without verifying, issued a destructive command, or looped on an
|
|
20
|
+
identical failure fails the gate even when its conclusion was correct.
|
|
21
|
+
- Added `test/settingsDocCoverage.test.ts`: every `SettingsSchema` key must
|
|
22
|
+
appear in `technical/06-configuration.md`. It found six undocumented settings
|
|
23
|
+
(`worktree`, `channelsEnabled`, `allowedChannelPlugins`, `urMdExcludes`,
|
|
24
|
+
`pluginTrustMessage`, `$schema`), now documented. Command coverage was
|
|
25
|
+
already enforced; settings coverage was not, which is how they slipped.
|
|
26
|
+
- Refreshed `ur agent-trends`, which still listed the claim-to-source ledger,
|
|
27
|
+
trajectory grading and multimodal capability warnings as future work after
|
|
28
|
+
they shipped — leaving UR misreporting its own coverage.
|
|
29
|
+
|
|
3
30
|
## 1.59.0
|
|
4
31
|
|
|
5
32
|
- Added `ur sources`, a claim-to-source ledger. `wrapUntrusted` already stamped
|