Python
Merge main into fix/migration-chroma-settings
alvinfei3064515b4308
diff --cc CHANGELOG.mdindex 2ab98dd,0df9bb4..812e70a--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -4,17 -4,15 +4,26 @@@ Hy Memory and MemHub are versioned and## Unreleased+- SDK: `list_memories(scene="chat" | "coding" | "working")` lists one kind of+ memory. `coding` and `working` list that scene's whole store, newest update+ first (`workspace_id` still narrows it), and `total` is now the real count+ rather than the page size. The new `memory_stats()` returns the count and the+ latest created/updated time for each scene and their total, without reading+ any memory text. Previously coding and working memories could not be listed+ or counted without a workspace, so a library of 45 memories listed 22.+- The SDK migration no longer fails its first run on a home with legacy+ vectors: reattaching them left a Chroma instance open with its own settings,+ and the readback that followed could not open the same store+ ("An instance of Chroma already exists ... with different settings").+ - MemHub "添加记忆" (add a memory) no longer waits behind unprocessed history.+ Notes are claimed ahead of the event-time window that keeps history strictly+ old to new; they still run one at a time and in order within their session.+ - SDK reconcile keeps time order. Both reconcile prompts now state that only+ `memory_at` decides which memory is newer, that an older memory must never+ supersede or overwrite a newer one, and that an unknown time is not newer;+ the Chinese prompt now lists `memory_at` among the new-memory fields. The+ reconciler also enforces this in code: a SUPERSEDE or UPDATE aimed at a memory+ with a later `memory_at` becomes an ADD, so the newer memory stays current.- The SDK memory page now reads its list, count, source and time labels andgraph from one page response for one source filter, so rows, totals and themap no longer disagree. Memories with no recorded source are shown and