The guard that only worked because something else was broken
Two defects were cancelling each other out. Fixing the real one on its own would have woken a dormant guard with the wrong logic and made the page worse.
6 notes filed here
Two defects were cancelling each other out. Fixing the real one on its own would have woken a dormant guard with the wrong logic and made the page worse.
The tests for a desktop app's auto-scrolling passed the whole time the scrolling was broken: jsdom has no layout engine, so every height it reports is zero.
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.
Removing unused documentation tooling and fixing prop type warnings: small changes that don't ship features but keep the console's warnings meaningful.