Two background jobs that marked themselves done too early
Two background jobs stopped early and recorded themselves as complete, and once recorded, nothing in the system could reopen them.
5 notes filed here
Two background jobs stopped early and recorded themselves as complete, and once recorded, nothing in the system could reopen them.
An agent that plans feature flag removals is useful. The rule about which flags it may never touch is what makes it safe to leave running, and what let the job move to the person who actually wants it done.
A tooling migration, some dependency bumps and a telemetry schema: none of it on a roadmap, and all of it about keeping several frontend services easy to work in.
Merged pull requests already record what you did. Turning them into a work log with an LLM is easy; the hard part is the defensive rules that stop it corrupting the vault.
Time spent fixing a flaky release pipeline sounds like infrastructure work. Its effect on how a team works is easy to undercount.