v1.0.3 — agent-side curation, un-archive, 404 for missing notes

v1.0.3 — agent-side curation, un-archive, and a 404 for missing notes.

Memory curation grows up: the agent can now curate, archives are reversible, and the curation API returns the right HTTP status. No inference-path change — decode is byte-identical, so there's nothing new to benchmark.

• The agent can archive — safely. It may archive only a note it recalled this session, and only behind an always-on confirmation that shows the note's real stored text (never the model's claim) plus a required reason. It's on the memory axis, so even --allow-shell doesn't auto-approve it; headless denies. forget (hard delete) stays user-only.
• Archiving is reversible — /unarchive <id>. Archive drops the note's vector but keeps the record; unarchive re-embeds the stored text (the embedder is deterministic, so the original vector comes back) and restores it to recall, node-id link intact. Idempotent, and it survives a restart. Like /forget, it's a user action — the agent has no un-archive tool.
• A missing id is a 404, not a 500. POST /memory/archive · /unarchive · /delete now answer 404 Not Found when the id doesn't exist — honestly distinguishing "your id was wrong" from "the server broke". Real faults still return 500.

Engine 1.0.2 → 1.0.3; vf-clide 0.3.1 → 0.3.2.

See CHANGELOG.md and the wiki's Memory / Memory Design pages.