Tisty 1.14.0
Nothing to migrate: the log stays on schema 12, so this build and 1.13 read
each other's stores and you can update one machine before the other. The read
cache is rebuilt once on the first launch, because how a task is weighed
changed and a cache written by the older build would keep answering with the
old weights. It takes as long as the archive is big, and happens once.
The archive had three layers and one of them was always empty
A task that closes reads as a story, a routine or a trace, and the trace never
had anything in it. On a real archive of twenty-three, every single one that
was not a routine sat in stories. The reason was the bar: anything at all
cleared it, so an errand somebody once annotated — «buy bread», one line and a
link — read the same as a release that took three weeks.
Now a log is weighed by what it says. A line of three words is not substance;
one that runs long is worth more than one that barely starts, and a plan of
twelve steps with nothing written is still an errand. On that same archive the
three layers come out seven, five and eleven, and «buy bread» is back where it
belongs.
Nothing was migrated to do it. The layer is read from what the task holds, so
the same log read by this build says something it did not say yesterday.
The archive says what it holds before asking how to read it
Above the list there is now a strip: how many are closed, how they fall across
the three layers, and — when there are routines — how many turns were kept of
those owed, the longest run, and the days left with no record. The numbers add
up: the routines are counted as the turns they are, with the series they
belong to named underneath.
The seven buttons that read the archive are split in two and told apart, because
three of them change what you see and four change how it is grouped, and until
now they all looked the same.
What's Changed
- fix: an errand somebody once annotated is still an errand by @rgdevment in #34
Full Changelog: v1.13.3...v1.14.0