v1.12.0

Tisty 1.12.0

Nothing to migrate: the log stays on schema 12, so this build and 1.11 read each
other's stores and you can update one machine before the other. The first search
after updating may take a moment longer while Tisty reads what each document
holds; after that it is faster than it was.

The page stops moving while you write

Opening a document returns the view to where you left it, and a long one keeps
changing height while it draws itself - code blocks picking up their colours,
pictures arriving - so it kept reaching for that spot again, for up to ten
seconds. Scrolling called it off. Typing did not, so writing into a long
document could drop the page out from under you in the middle of a sentence. A
key press now ends it: the view belongs to whoever is writing, and where you
were last time stops mattering the moment you say something new.

An assistant reads what it needs, not the whole thing

Tisty keeps a small card for each document - its headings and where they start,
how long it is, how many pictures it holds, the words it leans on - worked out
from the text itself, on this machine, and it never leaves. An assistant reads
that to pick which document it needs, then asks for the part it wants, or
changes that part without having read the rest. A long document is no longer
poured into somebody's model because an assistant wanted one paragraph of it.

Having read one, it can leave a summary and notes for the next one. That stays
here too: it never syncs, it is not part of the document, and you do not see it
in your window - it is the assistants' own margin. It is kept against the text
as it read at the time, so if you write in the document afterwards, whoever
reads that summary is told it describes an older version rather than trusting
it.

Searching asks the index instead of opening every document, so it no longer
walks the whole shelf to answer one word.

What an assistant may do, and what it still may not

It can now move the day of a task it filed itself, when what it learnt moves it -
the meeting slipped a week, the paper came early. A day you set is still yours:
naming one of your tasks is refused with the reason. It can add under a heading
rather than only at the end, correct a passage by where it sits rather than only
by quoting it, and file several tasks in one go. It still cannot close, delete,
or touch what you wrote.

Nothing is written over until what it said is kept

Correcting a passage copies the old text aside first, inside the same lock, and
if that copy cannot be made the edit is refused rather than made. Keeping the
copy afterwards meant a failure there left you with no way back. An import that
is turned away no longer leaves the files beside it copied onto your disk.

A log worth sending

The log a person can export now says what actually happened: a sync round names
what it sent and brought and what it could not settle, a refusal that means
something is marked apart from one that is ordinary, and the notes that explain
a ghost document are written rather than dropped. Being told no is not the same
as something breaking, and the log no longer says both the same way.

What's Changed

• Feat: mcp for agents by @rgdevment in #28
• Feat: what an agent remembers by @rgdevment in #29

Full Changelog: v1.11.0...v1.12.0