claude-memory-admin 1.0.1 → 1.1.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/README.md CHANGED
@@ -122,7 +122,11 @@ session and, past the limit, silently stops loading.
122
122
  - **The cutoff, drawn where it falls**. Past the limit, the MEMORY.md tab rules a
123
123
  line across the file and dims everything below it, and Prune names the memories
124
124
  that stopped being loaded. Because the stripping shifts every line, the cutoff
125
- is mapped back to real line numbers rather than counted in the loaded text.
125
+ is mapped back to real line numbers rather than counted in the loaded text. The
126
+ tab reads the index either **rendered** — headings, lists and clickable entries,
127
+ with pointers to files that do not exist struck through — or as **source**, with
128
+ line numbers. Either way the cutoff is drawn in the same place. The choice is
129
+ remembered.
126
130
  - **Long hooks**. The hook is the text after the dash in `MEMORY.md`. A
127
131
  400-character hook can cost more than the memory it points at, and shortening
128
132
  it is the cheapest win available.
@@ -226,11 +230,17 @@ cd claude-memory-admin
226
230
  npm install
227
231
  npm start # or: node server.mjs
228
232
  npm test # runs on a throwaway copy of your real store
233
+ npm run dev:css # only when editing styles/app.css
229
234
  ```
230
235
 
231
- No bundler and no build step: the backend is `node:http` plus `node:fs`, and the
232
- frontend is plain ES modules the browser loads directly. Two runtime dependencies,
233
- `marked` and `dompurify`, both only for rendering memory bodies safely.
236
+ No bundler and no build step to run it: the backend is `node:http` plus `node:fs`,
237
+ and the frontend is plain ES modules the browser loads directly. Two runtime
238
+ dependencies, `marked` and `dompurify`, both only for rendering memory bodies safely.
239
+
240
+ Styling is the one thing that is compiled. `styles/app.css` is the Tailwind v4
241
+ source and `public/styles.css` is its committed output, so an installed copy is
242
+ ready to serve and never builds anything. After editing the source, run
243
+ `npm run build:css` and commit the result — CI rebuilds it and fails on drift.
234
244
 
235
245
  | Path | Purpose |
236
246
  | --- | --- |
@@ -246,6 +256,7 @@ frontend is plain ES modules the browser loads directly. Two runtime dependencie
246
256
  | `src/stats.mjs` | Load-limit accounting and overlap detection |
247
257
  | `src/search.mjs` | Full-text search across every store |
248
258
  | `src/mutate.mjs` | Delete / restore / unlink, the only code that writes |
259
+ | `styles/app.css` | Tailwind source, compiled to `public/styles.css` |
249
260
  | `public/` | Frontend |
250
261
 
251
262
  Tests run against committed fixtures under `test/fixtures/`: a projects store
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "claude-memory-admin",
3
- "version": "1.0.1",
3
+ "version": "1.1.0",
4
4
  "description": "Browse, audit and prune the auto memory Claude Code keeps under ~/.claude/projects",
5
5
  "keywords": [
6
6
  "claude",
@@ -54,10 +54,16 @@
54
54
  },
55
55
  "scripts": {
56
56
  "start": "node bin/claude-memory-admin.mjs",
57
- "test": "node --test test/*.test.mjs"
57
+ "test": "node --test test/*.test.mjs",
58
+ "build:css": "tailwindcss -i styles/app.css -o public/styles.css --minify",
59
+ "dev:css": "tailwindcss -i styles/app.css -o public/styles.css --watch",
60
+ "prepublishOnly": "npm run build:css"
58
61
  },
59
62
  "dependencies": {
60
63
  "dompurify": "^3.2.7",
61
64
  "marked": "^16.4.0"
65
+ },
66
+ "devDependencies": {
67
+ "@tailwindcss/cli": "^4.3.3"
62
68
  }
63
69
  }