A task on a board and the commit that actually resolves it live in two completely different systems. Six weeks later, "which commit fixed this" costs a whole session of reading diffs to answer, unless something wrote the join down at the time.

One line, in the commit itself

Develosaur closes that gap with a trailer on the commit message:

Board: abc123 closed, def456 updated, ghi789 investigated

Full node ids, comma-separated, one line. Once it is in git history, git log --grep="Board:.*abc123" finds the exact commit that resolved a given task, forever, using a tool that already exists. No integration, no service to query, just text that was already going to be in the log.

The verb that writes it

handoff, called once at the end of a session, records the whole close-out: which ids were closed, which were advanced with a progress note, and it returns this trailer ready-made from exactly that. Nobody has to reconstruct it from memory at the end of a long session, which is exactly when a hand-written summary is least reliable.

The discipline that keeps it worth trusting

A trailer is only useful if it is honest, so the rules are strict on purpose: name a node only if you actually touched its subject matter this turn, say "closed" only for something you actually completed on the board, and write no trailer at all if the turn changed no code. An overclaiming trailer is worse than none, because the next person to read it believes it, and a false "closed" sends the next audit looking in the wrong place entirely.

Handoff finishes work, it does not plan the next session

The verb closes out what happened. It never reorders the pinned head, never pins anything for later, and never queues up "next steps" for the following session to inherit. The next session answers "what's next" by reading the live ranked list fresh, the same way described in how the priority order decides what is next, never by trusting instructions a previous session left lying around. Closing out and deciding what happens next stay two separate acts, on purpose.

This is the same close-out this blog's own posts have been landing with, described more generally in I shipped Develosaur using Develosaur. More on how the rest of the board works is on the how-it-works page, and more of these are on the blog.