v1.1.0

github-actions released this 02 Sep 20:56

· 64 commits to main since this release

d2fd9d6

Added

Versions. A comment on an element or a spot can ask for up to four answers
instead of one: the composer carries a 1× button beside Add that cycles to
4×. The agent builds every version at once, each guarded on an attribute
Tailr sets on <html>, and names it in a word or three. After the reload a
pill sits on the element with a tab per version — hover one and it widens to
the name while the page switches to that version live, so the comparison is
between the real things rather than between two descriptions of them.
Keeping a version is a mark like any other. It joins the batch, and sending it
is what makes that version permanent and takes the losing ones — and the
guards — out of the source. Turning the whole set down is the × on its row.
An unresolved set keeps the island awake, because the alternative is versions
sitting in someone's repository with nothing on screen that would remove them.
tailr variants <ref> <names…>, and the matching tailr_variants MCP tool,
for reporting what was built. The operating rules carry the whole contract:
where the switch lives, that version 1 must also be what renders without it,
and that a guard never outlives the choice that settles it.
A way out. End session sits under the island's panel, and it asks before
it acts: the card names what is being agreed to, one consequence per line —
the marks that go unsent, the versions that get cleaned up, the address the
application goes back to once Tailr stops proxying, and that the browser is
cleared. Until now the only way to end a session was a terminal the reviewer
does not have.
A cleanup pass on the way out, because ending is the last moment anything can
be done about what Tailr left behind. Versions nobody chose between go to the
agent as one final batch that takes them, and the switches guarding them, out
of the source; the switches come off the document; what Tailr kept in the
browser is cleared; the server stops and the overlay takes itself off the
page. If the agent never answers, End anyway leaves regardless and says
the cleanup did not finish rather than implying it did.

Fixed

A session was good for exactly one batch. The server keeps the last run
indefinitely, so a reviewer who reloaded was handed a finished run again and
the overlay re-entered its "Needs refresh" state — against changes they were
already looking at — with Send locked and no way back. A closed run now only
prompts the page that watched it close.

Assets 2