v0.0.9 — JSON envelopes out of memory bodies, plus store inspection

Found by running the new npm run inspect on a live brain within an hour of publishing 0.0.8, which is the whole argument for the command existing.

The defect 0.0.8 missed

0.0.8 fixed titles and facts but still appended raw tool output verbatim:

Wrote inspect-store.ts. {"type":"create","filePath":"…","content":"//\n…"

An entire written file, stored inside its own memory. Output is now mined for the one field a human would read (stdout, output, stderr, message) and everything else is dropped. content/file-body fields are deliberately never harvested — they are the payload we are trying not to keep.

New: npm run inspect

Grades the live brain against the same rules the capture path enforces — bare-tool-name titles, JSON in bodies, records with no facts and no concepts, whether importance has any spread — then prints the most recent captures to read, because no aggregate tells you whether the knowledge is worth having.

It exists because 761 passing tests and a 100% firewall eval both reported "healthy" while the store was full of tool logs. Reading the rows is the only check that catches this class of defect. Reads a snapshot, never the live file; mutates nothing.

Two bugs the inspector found in itself

• Its JSON check only looked at the start of a body, so Wrote foo.ts. {…} read as clean.
• Its bare-tool-name check was case-sensitive while hosts disagree on casing (Read vs read).

Upgrading

npm install -g memwarden@0.0.9
memwarden down && memwarden up
npm run inspect          # from a clone, to grade your own store

Records captured before 0.0.8 keep their old shape and age out through retention.

763 tests · firewall eval 8/8 · published with SLSA provenance.