3 Commits

Include renames

Author	SHA1	Message	Date
mathiasandClaude Sonnet 5	fb69f4bf3d	fix(api): UpdateNote reserves updated_at/supersedes/supersede_reason from the caller's fragment ... hyperguild#125, found in #111's review as a non-blocking observation, decided now rather than left implicit: UpdateNote's merge loop applied every field from the caller's leading frontmatter fragment onto the restamped note, including updated_at/supersedes/supersede_reason. updated_at and supersedes were already safe -- both get unconditionally re-set right after the loop regardless of what the loop did with them -- but supersede_reason is only re-set when opts.Reason is non-empty, so a caller could set it via its own fragment and have it survive even with the Reason option left empty, bypassing the one intended entry point for that field. Decision: these three fields are this function's own output, not caller-settable, full stop -- skip all three in the merge loop rather than lean on the other two happening to be safe via call order. Makes the invariant explicit at the one place it could be silently broken by a future reordering, instead of implicit in which fm.set calls happen to run after the loop. Flip-tested: reverting the skip to just `l.key == ""` lets the caller's supersede_reason survive with Reason empty -- the new test catches it. Full module suite green. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-23 10:16:24 +02:00
mathias	5a5d938e8e	Brain-quality sweep, batch 1: brain_edit/brain_update correctness + close-session docs (#124) ... Co-authored-by: Mathias <mthbqv@gmail.com>	2026-09-22 21:27:11 +00:00
mathiasandClaude Opus 4.8	95a69fc2c1	feat(brain): add UpdateNote/ReadNote supersede primitives + frontmatter editor ... Implements the api-layer half of #45. UpdateNote supersedes a note in place (whole-note body replace, frontmatter re-stamp: updated_at, supersedes=prior content hash, supersede_reason), preserving created_at, wing, hall, and any custom fields. Never creates — a missing target is an error so callers fall back to brain_write. ReadNote is the read-after- write primitive (frontmatter + body + content_hash). ContentHash is the sha256 handle that round-trips write/update → get. Frontmatter is edited via a line-preserving ordered editor rather than a yaml.v3 round-trip, which would reorder keys and strip comments — the brain writes flat key:value frontmatter by hand. Embeddings are not refreshed here: the rewritten file's mtime advances, which the out-of-band vectorstore.Sync ticker uses to re-embed it — the same mechanism brain_write relies on. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-22 08:25:00 +02:00