fix(store): split sibling fields back out when they leak into content

[MXAntian]

Why

A long store_memory argument closed with the wrong tag — </content> instead of </parameter>, or a bare <summary> — makes the tool-call parser keep reading. The sibling fields end up inside content (or summary) as raw XML:

…body text.</content>
<parameter name="summary">the summary</parameter>
<parameter name="importance">9</parameter>

and the real summary / importance / category arrive empty, so zod fills in its defaults. The write succeeds, the row has no summary line, and an importance-9 decision is stored as a 6. Nothing reports it.

A full scan of one production store turned up 47 live rows like this, spread over five months — despite an agent-side instruction to close tags carefully that was in place the whole time. Some were on the summary side (…</summary><parameter name="importance">7), and three followed a correct </parameter>, so "be careful with tags" was never going to be enough.

What

tag-leak-repair.mjs — a pure function run at the top of the store_memory handler, before quarantine routing or the write.

Detection is structural, not substring: a wrong closer immediately followed by a field tag, and the whole tail has to parse as field tags to the end of the string. That distinction matters because the rows most likely to contain these strings are the ones describing the bug:

input	result
body</content><parameter name="summary">S	repaired — content body, summary S
…a tail like `</content><parameter name="summary">…` then more prose	untouched (backticked, and prose follows)
…</content>, which then corrupts importance	untouched (no field tag follows)
x</content><parameter name="summary">S</parameter> and more text	untouched, reported as ⚠️ possible leak

Merge rule. For fields zod defaults when they're absent (importance, category, memory_type, memory_level), the passed value is the default standing in for the one that leaked, so the leaked value wins. Fields with no default (summary, tags, supersedes, …) keep a non-empty passed value. Invalid values (unknown category, importance 42) are dropped rather than applied.

Feedback. The response gains one line:

Stored memory (id: 1, importance: 9, type: long_term, level: semi_abstract)
🩹 close-tag leak repaired: summary, importance, category moved back out of content — a field was closed with the wrong tag; each <parameter> must end with </parameter>

Tests

• tag-leak-repair.test.mjs: the parser against leak shapes taken from real corrupted rows, plus prose that must pass untouched
• tag-leak.integration.test.mjs: spins up the HTTP server on a temp DB, sends a leaked write and a prose write through store_memory, and checks the stored rows
• Both are wired into CI

Existing rows aren't migrated here. The same function can be run over a store as a one-off (dry-run first, and clear content_vector on rows whose content changed so they get re-embedded).

🤖 Generated with Claude Code