The folder that stayed put
A code review turned up an invariant Greenhouse's adopt/import feature quietly broke, and the fix that made it boring again.
A code review turned up an invariant Greenhouse's adopt/import feature quietly broke, and the fix that made it boring again.
An import scanner that found the app's own scaffolding, then re-offered a folder it had just imported - two versions of the same missing conversation between layers.
A callback renamed to something generic kept its wizard-specific meaning, and the same signal meant two different things to two different listeners.
A self-hosted macOS build runner sharing a box with an NVR, a DMG bundler that drives Finder through AppleScript, and the env var that overrode my env var.
A spike into Tauri's asset protocol, a runtime-scoped grant for a user-chosen vault, a narrow CSP widening, and an autoplay bug the a11y tests caught first.
A null CSP, a config value joined onto a filesystem path unchecked, and a vault picker that would accept your home directory - none broken yet, all unlocked.
light-dark() made the CSS easy. Three test-tooling failures made the contrast gate hard. Then real screenshots proved the green gate wasn't the whole story.
The 7-day lock on active projects was idea-incubation logic pasted onto the wrong pipeline stage. Rotation already did the useful part of the job.
Vaulting now really moves your files, and a "Keep Vaulted" no-op that wasn't - re-vaulting would have reset the exact timestamp the daily review sorts on.
Does advancing a stage count as a touch, what happens at the last stage, and a cooldown-vs-rotation tangent that turned out to be one question, not two.
Page 1 of 2