v0.5.24: Complete Entity Counts and Related Memories on Demand

This patch release publishes PR #332. On Memory System → Memory Spaces → Entities, the number next to an entity did not match what selecting it listed: an entity counted 22 could list 5, and another counted 5 could list 9.

• Counts from every memory. The list of entities added up each space's 20 most frequent entities from the Provider's status, so most entities were missing and some counts were short. Each space now builds one entity index from the memories its Provider lists. An entity's count is the number of memories that carry it, and the list holds every entity. Spellings merge the way the Overview graph merges them, so the two agree.
• A selection lists exactly those memories. Selecting an entity ran Agent recall. Its quality policy keeps at most four medium matches, and memories that do not carry the entity filled the free places. Now every memory that carries the entity is listed as soon as it is selected, most important first, a page at a time.
• Related memories on demand. Below the list, Find related memories runs recall for the entity among memories that do not carry it. Recall takes about half a second per space, so it runs only when asked for. Once opened, related memories stay open for the next entities until you hide them, for the rest of the browser session. When no memory carries a name you entered, related memories show by themselves.
• Steadier loading. The spaces show before their indexes are read. A placeholder appears only for a read that takes a while, and a late answer for an earlier selection is dropped. A forgotten memory leaves the lists at once.
• Providers. A Provider whose list() stops short of a space can implement the optional entityIndex(body); see Extensions. The first-party Providers need no change.

#Measurements

On synthetic Mnemon Native spaces in the WebUI, on DSH 0.2.0-rc.2 and 0.1.7-rc.2:

With four spaces of 500 memories each, a selection used to show 20 results after 1.5–1.7 s. It now shows every memory that carries the entity (855, 211 and 86 in the runs) after 7–10 ms, and related memories, when asked for, after 1.5–1.8 s. The Entities page record has every run, including a copy of the export behind the report.

#Upgrade and compatibility

From v0.5.22, use Memory System → Status → Check versions → Update, then restart DSH. To install or update to the exact version from the CLI:

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

Restart an existing DSH process after installation; a new installation can choose Enable now on the Plugins page. An explicit version keeps pnpm's 24-hour release window from picking an earlier one. For older desktop installations, see Compatibility and upgrades.

Supported hosts stay DSH 0.2.0-rc.2 (npm latest and next) and DSH 0.1.7-rc.2; complete profiles use Node ^22.19.0 || >=24.0.0. Storage formats and configuration are unchanged, and existing memory needs no migration. The entity index is held in memory and rebuilt when a space changes. No new Starter SDK export is required, so plugin peer floors stay unchanged.

#Changed packages

The Starter pins the new Memory Spaces version. Its other 16 component versions are unchanged, as are all locked external dependency versions.

#Verification

The versioned release acceptance installs the release packages through Add plugin on both supported hosts and checks the Entities page. The fix has its own before-and-after record.

Publication verifies the complete pinned composition, the Registry installation and a real upgrade before creating the GitHub release.

Previous release: v0.5.23.