v0.5.10: Exact Memory Writes and Bounded Automatic Review

v0.5.10 includes Runtime matching in #256, verified OpenViking writes in #234, and automatic-review limits and Agent Teams compatibility in #257.

#Runtime and OpenViking writes

Runtime replace and remove prefer a unique exact content match before trying a unique substring. An entry containing only X can therefore be edited or removed alongside EGO_LINUX_CHROME. Duplicate exact matches still require disambiguation, and refusal leaves existing data intact.

OpenViking creates a unique file containing the original text, verifies indexing and exact content readback, then returns the scoped file identity used by Host receipts and archive compensation. It no longer treats an extraction response as proof that the requested text was stored. Search and browse return full content. Account isolation, legacy owner-root resolution and deletion scope are validated; incomplete or uncertain writes return an error with the candidate URI. The original contributor's commit is preserved in the merged history. Servers lacking the required content write/read contract fail explicitly; no settings or stored content are migrated.

#Automatic review

Automatic review has an independent switch, a default five-minute minimum interval and a limit of 20 attempts per loaded parent Agent. The default spawn path bounds its context; fork remains explicit, with fallback or skip available before child startup. The per-response token limit is not a total usage cap. Attempt budgets reset when the Agent unloads or the Host restarts; existing session history is retained.

With the affected published Agent Teams service and tools enabled together, automatic review pauses before creating a child and explains the incompatible composition. This contains the automatic-review failure; it does not repair upstream Team policy or manual delegation. A failed review can expose receipts for writes it already committed so users can reconcile them without replaying the run.

#Packages and upgrade

The Starter pins the complete sixteen-plugin composition. The other thirteen plugins retain their versions. Mnemon CLI remains independently maintained.

dsh plugin --profile web add dsh-mnemon@0.5.10

Restart DSH and reload the browser. Substitute headless for that Profile. The full DSH profile requires Node ^22.19.0 || >=24.0.0.

#Verification

The combined implementation passed 1,162 root tests with five opt-in skips, plugin suites, actual Mnemon 0.2.8 CLI checks, Headless activation/restart, deterministic builds and public package checks. Sixteen independent plugins and seventeen artifacts passed installation and composition verification, including all three optional Strategy extensions together. Real OpenViking 0.4.20 passed create/read/search/delete checks; the published DSH 0.1.5-rc.2 and Agent Teams 0.1.5-alpha.2 matrix verified the compatibility pause.

Real WebUI before/after screenshots and exact tested revisions are retained in the Runtime report, OpenViking report and automatic-review report. Model replies and embeddings use deterministic local fixtures; these checks do not measure live model judgment or semantic recall quality.

The release workflow verifies the versioned workspace and independent artifacts, publishes the three changed plugins before the Starter, checks the complete Registry composition and a real upgrade from v0.4.7, then creates the GitHub Release.

Previous release: v0.5.9.