Harvest shelf: giving Greenhouse's released items somewhere to land
Releasing a project was write-only: the database stamped a timestamp, a badge branch could never render, and the entire payoff of the pipeline was invisible.
Releasing a project was write-only: the database stamped a timestamp, a badge branch could never render, and the entire payoff of the pipeline was invisible.
Greenhouse saved a capture note and a handoff note faithfully, but showed neither: one had no field in the wire type, the other's command was never called.
A 'don't build this' recommendation built on two unverified assumptions, and the one-line Tauri activation-policy fix that was sitting there the whole time.
Stage names serialized into every config.yaml at creation time made translation and templates a per-vault migration - until the words stopped being data.
The streak and the badge computed the same concept two different ways, and imports were quietly crediting six-month-old ideas as today's creative act.
An untracked PRD commitment with zero CI, zero path-handling audit, and zero pressure behind it - resolved in fifteen minutes by actually making the call.
SQLite treats a zero-byte file as a valid fresh database, so every corruption check passed - and the backup pruning would have deleted the good copies within a week.
"Keep" set a client-side flag, and a comment promised the pick would change tomorrow. It never did. The fix: one nullable column and distrust of comments.
A monotonic counter for out-of-order refreshes, a cancelable Esc-key dialog event, and a duplicate-key crash from a timestamp that collides within a second.
A kanban board rendered a prop that went stale the moment other data changed, and every mocked test passed because a mock can't express staleness.
Page 1 of 4