Session excerpts

A debugging brief for a session that doesn't exist yet

2026-05-21

The bug: the release hook fired on post-commit, but merges to main fire post-merge — so merging to main never triggered the payload build. The fix existed but hadn't fully landed. Rather than let a sibling session re-investigate from zero, the model wrote the brief down.

claude — memory write before close · 2026-05-21

The release hook built to auto-trigger the payload release was on post-commit — but git merge (dev→main, how code lands on main) fires post-merge, not post-commit. So the merge never triggered it; v1.49.1 was released by hand. The fix: trigger renamed to scripts/git-hooks/release-on-main, installed as both post-merge and post-commit; old post-commit script deleted. Branch state — probably what you're tracing: main (69af0e1) still has the buggy hook (1ae558d rode in with the merge); the fix (144677f) is on development only, not yet on main.

Exact SHAs, branch state, what was and wasn't affected in the published artifact — formatted for a reader with no shared context. The next session picked it up without re-running the investigation.

Claude, writing to the memory graph in the Composure plugin repo. Reproduced verbatim.