claude-memory-admin 1.5.0 → 1.5.2

package/README.md

@@ -19,17 +19,26 @@ and this README were written by Claude Code, with a human directing the design
 and reviewing what landed. Fitting for a tool about what Claude writes for
 itself, and worth saying out loud.
 
-<sub>Brought to you by [BitSpire](https://bitspire.ch/).</sub>
-
 ---
 
 ### Prune: see what MEMORY.md actually costs you
 
 ![The Prune tab, showing how much of the MEMORY.md load limit a project uses and a sortable list of memories by age, size and inbound links](assets/prune.webp)
 
+### Health: every problem found, worst first
+
+![The Health tab in the light theme, listing checks ranked by severity: a broken wikilink, a memory no index entry points at, index hooks over 200 characters, hooks that only restate the file's own description, and an empty section](assets/health.webp)
+
 ### Graph: see how memories link to each other
 
-![The Graph tab, showing memories as nodes coloured by type with wikilinks as edges](assets/graph.webp)
+![The Graph tab, showing memories as nodes coloured by type with wikilinks as edges, orphans below a dashed line and a dashed outline where a link points at nothing](assets/graph.webp)
+
+### Context: what every session loads before a project is even chosen
+
+![The Global entry's Context tab, showing the estimated token cost of the user-scope instruction files, a file reached twice through both an import and the rules directory, and the order the files load in](assets/context.webp)
+
+There is a light theme and a dark one, toggled with `t`; the Health shot above is
+the light one and the rest are dark.
 
 ---
 
@@ -106,7 +115,11 @@ project is to the cliff, and makes it quick to get back under it.
   memory exists can no longer be traced from anything on disk.
 - **Sessions**: the transcripts beside a store, with the retention window drawn
   the way MEMORY.md's cutoff is - each session a tick, the sweep line where it
-  falls. Titles are the ones Claude Code generated, falling back to the session
+  falls. Under it, a tile per day shades how much work that day held, and
+  clicking one narrows the list to it; the grid spans the retention window
+  rather than a fixed year, because a year of empty tiles would read as *no
+  sessions* when it only means *already swept*. Titles are the ones Claude Code
+  generated, falling back to the session
   slug and then the opening prompt; a session that names itself nowhere in the
   part read is shown by id rather than given an invented name. Only the head of
   each file is ever read, so a 200MB store of transcripts costs a quarter of a

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-memory-admin",
-  "version": "1.5.0",
+  "version": "1.5.2",
   "description": "Browse, audit and prune the auto memory Claude Code keeps under ~/.claude/projects",
   "keywords": [
     "claude",

package/public/api.mjs

@@ -0,0 +1,26 @@
+import * as ui from '/ui.mjs';
+import { el, node } from '/dom.mjs';
+
+export async function api(path, options) {
+  const response = await fetch(path, {
+    headers: { 'content-type': 'application/json' },
+    ...options,
+  });
+  const data = await response.json().catch(() => ({ error: 'Bad response from server' }));
+  if (!response.ok) throw new Error(data.error || `Request failed (${response.status})`);
+  return data;
+}
+
+export function toast(message, { error = false, action } = {}) {
+  const element = node('div', { class: ui.toast(error) });
+  element.append(document.createTextNode(message));
+  if (action) {
+    element.append(node('button', {
+      class: ui.toastAction,
+      text: action.label,
+      onclick: () => { element.remove(); action.run(); },
+    }));
+  }
+  el('toast-root').append(element);
+  setTimeout(() => element.remove(), action ? 12000 : 4500);
+}