v0.35.0

A specialist for every language you name

Summo could pair one specialist model with the language you named
first. Name Vietnamese, English and Japanese and the Japanese half of
your meeting had no specialist at all — it was whatever the multilingual
model happened to hear. On the published figures that is 8.4 %
character error against 39.8 %: most of the accuracy of every Japanese
sentence anybody said.

Now each language you name gets its own model, and each utterance goes to
the model that names its language rather than to one that claims all of
them. A model brought in for one language no longer waits behind a
sentence in another — they are different models and there was never a
reason beyond a single counter for them to queue.

If you name a language whose model is not installed, Summo says so and
offers the download, instead of showing a chip that bought nothing.

Việc cần làm is a board you can actually use

Every way into it needed a meeting behind it, so a task nobody had
recorded could not be written down at all. And a task could be dragged
between columns and nothing else: no fixing the half-sentence a model
pulled out of a summary, and no removing a line that was never a task —
which could only be dragged to Xong, a lie in the one place you look
to find out what you finished.

• Write one down — a task, who it is for, when it is due.
• Reword it, without opening the Markdown file.
• Delete it. An agent's plan goes with it.
• A list as well as a board, because four columns are good for moving
  work along and bad for reading it in order.

Loose tasks live on an ordinary note, so they are still a list you can
open in Obsidian or anything else that reads Markdown.

Thư viện: sort, a flat list, and old recordings that play

There was no sort — filters, yes, but the order was fixed. There is one
now, newest first by default, plus the flat list that makes sorting by
title or by length mean anything at all: inside a day heading it could
only ever reorder that day.

And the detail pane has always counted your recordings — "· 2 bản
ghi" under the date — while offering no way to hear one. The player and
the route both existed. The only screen that lists old meetings could
reach neither. Now it can.

The readout left the chrome of every screen

The RAM and RTF numbers were in the footer of every page. They are behind
the performance switch now, and still on screen for anyone who wants
them, under Cài đặt → Giao diện, beside the switch that decides it.

This was attempted last release and pulled, because hiding a number is
only acceptable if it is still somewhere and that could not be shown. It
can now: one browser test asserts the number is readable where it moved
to, another asserts it has not come back to the footer.

A recording falling behind is not behind that switch. That is the
recording going wrong, not a statistic you opted into.

Measured, not fixed

Pressing record takes 2977 ms before the meeting is running. That is
printed on every test run now, and the run fails above eight seconds — so
a change that makes it worse shows up in the log of the run that made it
worse. It is slower than it should be: Summo prepares the model ahead of
time and the press is beating it. That is the next thing to fix, and
saying so is better than a release note that does not mention it.