recap

After a fourteen-hour run the console tail is useless. Scrolling it is worse. This produces one page that a human can read in ninety seconds and an engineer can act on, bounded by a window it resolves rather than guesses.

The one rule

If a section could be written by reading git log, it is not the section anyone wanted.

The user's complaint, verbatim in spirit: "eight commit SHAs and 'story 1.8 is closed' is concise and comprehensive, and nowhere at all does it let me know what I can do now that I couldn't before. I'm a human — I can't remember the story numbers for the thirty projects I'm working on."

So a recap leads with capabilities in the user's own vocabulary, each with the literal thing to run, and treats commits as evidence in a footnote. pjangler fleet status --domain systemd now reports five observations per agent where it used to say unsupported is a recap sentence. Story 1.8 closed is not.

Run it out of band