v0.13.0

Scheduling a card ahead now actually parks it

Two things went wrong when a new card was dated into the future.

It joined the current sprint. No sprint covers a future day — sprints are daily and open as they start — so the card sat in a sprint it would never be worked in: dragged forward by every daily carry-over, its dates reading "current sprint" the whole time, its log collecting a sprint event a day while nobody touched it. aeman already had the right state for this — the "next sprint" create leaves a card sprint-less and the carry-over that reaches its day adopts it — and a future day now takes that path, on create and on reschedule. An explicit sprint still wins.

Its day counter counted from creation, so a card made today for next month arrived three weeks old and coloured as rotting. The counter means days on the board, and a parked card is not on the board: it now counts from whichever came later, the card's creation or the day it landed. Ordinary cards are unaffected — a card open for ten days still reads 10d.

Note for teams that lean on the counter as a nagging signal: a card deferred with +1 day / +1 week also moves its start day, so its age now restarts when it comes back. The defer history stays in the card's log.

This supersedes the documentation-only answer given in #82 — the reports were right, and the behaviour is fixed rather than described.