Windows support: not now, maybe never
Greenhouse’s PRD has quietly committed to macOS + Windows since early on, mostly because I liked the idea of one day handing Mike Monday’s students a friendly cross-platform build. But an earlier issue deferred the actual Windows CI job to “later,” and later never got filed as its own issue. So the commitment sat there, untracked, doing nothing.
I finally made myself pick: drop it from v1. Tauri still supports Windows architecturally, nothing in the current code choices forecloses it, so if a Windows build actually becomes worth building later (real demand, or the teaching-template idea turning into a real next step instead of a maybe) it’s still on the table. But right now it was unscoped work sitting in the PRD as an implicit promise, with zero path-handling audit, zero CI, and zero pressure to actually build it.
Updated the PRD to say macOS-only for v1, with a one-line pointer back to the decision. Fifteen minutes of work, mostly documentation, and one fewer piece of untracked scope hanging over the release pipeline.
The general shape is worth naming: a commitment that lives only in a planning doc, with no issue tracking it and no work scheduled against it, isn’t a plan. It’s a liability that makes every estimate quietly wrong. Deciding “not now, maybe never” out loud costs almost nothing and returns the scope to reality.
Related reading
Two notes nobody ever saw
Greenhouse saved a capture note and a handoff note faithfully, and showed neither: one had no field in the wire type, the other had a working command nobody called.
The scan that offered to import itself
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.
Navigation redesign: topbar tabs and a Settings dialog
Eight footer controls at identical visual weight, an i18n key doing double duty, and the ARIA pattern the project's own a11y test refused to let me half-build.