A record may leave its lists some time after reaching a state: leaves_after
Test / test (pull_request) Successful in 1m20s

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GT37Z1Xtfd9pUuQtMTg6Yt
This commit is contained in:
Bendik Aagaard Lynghaug
2026-09-30 20:50:28 +02:00
co-authored by Claude Opus 5.5
parent 96c513d912
commit 0dc25b4023
8 changed files with 147 additions and 1 deletions
+5
View File
@@ -196,6 +196,11 @@ rest. Each is one line in the plan, and the builder does the wiring:
their own, which the form opens with and which sending again
replaces - a card on the front page they edit themselves. A picture
left unchosen stays as it was.
- **Let finished things go.** `leaves_after: { <stage>: { minutes: 10 } }`
takes a record out of every list that long after it reaches that
stage (days, hours and minutes add up). A card taken off the front
page need not stand greyed out on the desk for ever; the history
keeps it.
- **Pause what you cannot take on.** `paused: true` on a need keeps
its card on the page, saying what the business does and that it is
not taking new ones right now, with no form and a button that does