theme edit copies the whole user library into the project config, and does not apply the change

What happened

Running from inside a project directory reported success:

Two things then turned out to be wrong.

1. The change was not applied. keyword: editorial type:
   palette: amber=#E8923B charcoal=#282A2C cream=#F2EAD8 teal=#14534F prompt: Editorial conceptual illustration, flat screen-print / risograph aesthetic: bold simplified shapes, clean confident linework, a light grainy overprint texture and subtle halftone shading, one strong central visual metaphor. Strict limited palette matching the publication: deep petrol-teal, warm amber-orange accent, soft cream background, dark charcoal lines and detail. Smart, a little wry, the feel of a quality magazine op-ed illustration. Flat 2D, absolutely no 3D rendering. Wide 16:9 banner, subject centred with generous negative space. No text, letters, numbers, logos or brand marks anywhere. card: mode=overlay style="Editorial conceptual illustration, flat screen-print / risograph aesthetic: bold simplified shapes, clean confident linework, light grainy overprint texture, one strong central visual metaphor. Strict palette: deep petrol-teal, warm amber-orange accent, soft cream, dark charcoal. Vertical 9:16, generous negative space in the lower half for an overlaid caption. Wordless: no text, letters, numbers, logos or brand marks anywhere." music: gain=0.16 prompt="restrained editorial bed, sober and understated" voice: id=MhaH9hcD2Ulcr80j28Z1 stability=0.6 similarity=0.92 still reported no aspect, and a subsequent still returned a square image.
2. It wrote the entire user theme library into the project config. gained 176 lines: all 13 themes from , copied in under an empty-string type key:

That file is committed to the repo, so the effect is a large unintended diff in version control, sourced from a users personal theme library. In a shared repo that is also a small privacy footgun.

Why it matters

The project config is tracked. A command that reports editing one field should not silently relocate an entire library into it, and certainly not while failing to make the edit that was asked for.

Expected

Editing a theme edits that theme, in whichever scope it already lives in, and says which scope it wrote to. If promoting a user theme into the project is a necessary side effect of editing it there, that is worth saying out loud before doing it.

Environment

keryx v0.9.0, theme catalogue migrated per spec 0047. Reverted locally with ; no lasting damage.