When your app can't take back a permission it already gave
Tauri's asset-protocol scope has an allow_directory and no revoke - so switching vaults became a restart, trading instant switching for a security property that actually holds.
Tauri's asset-protocol scope has an allow_directory and no revoke - so switching vaults became a restart, trading instant switching for a security property that actually holds.
Adding one status check to a Rust function meant it could no longer call another function the same way - and that constraint quietly opened a hole neither function had on its own.
Fixing one dashboard-refresh bug exposed a second hiding in the same shared component - and a third bug that turned out not to exist at all.
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 found the app's own scaffolding, then re-offered a folder it had just imported - two versions of one missing conversation.
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.
Page 2 of 4