pastilhasandClaude Opus 5 701933d30d commit and push when it goes wrong too
The instruction was standing and nowhere in the repo, so every session started
by waiting to be asked. Written down because the reason is not obvious: a
branch held back because it is unfinished, untested or a dead end is exactly
the branch whose history is worth having. A reverted commit and its message
explain why an approach was abandoned; a quietly discarded attempt teaches the
next person nothing, and they will try it again.

The obligation that comes with it is saying what state the work is in — in the
message, and in COMMS/ when another agent will pick it up — rather than letting
a clean commit imply it is finished.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-11 21:32:21 +00:00
2026-02-16 19:34:35 +00:00
2026-02-16 19:34:35 +00:00
2026-02-16 19:34:35 +00:00
2026-02-22 03:35:26 +00:00
2026-02-16 19:34:35 +00:00
2026-02-16 19:34:35 +00:00
2026-08-11 15:15:09 +00:00
S
Description
No description provided
42 MiB
Languages
TypeScript 90.9%
Shell 4.7%
JavaScript 4.1%
CSS 0.2%
HTML 0.1%