Controls on a floating session

A session floated out into a window of its own now carries its own controls in
the title row, beside the close: hold it, reload it, end it — and start it
again once it has ended. In the terminal view the session bar is not drawn, so
until now a floating server could be watched but not touched.

RELOAD is new. It asks the program to read its configuration again without
losing what it holds — its port, its connections, its cache. It goes only to
the program running in the terminal, never to the shell, and when nothing is
running it says so instead of closing the session.

What an account has left

Over each terminal the account's own figures now appear — the session window
and the week, with the bars and when they come back — instead of "no reading
for this account yet". An account keeps its state either beside its directory
or inside it, and a stub file was winning over the one that had the figures.

They also follow the file now rather than a timer: when Claude Code writes a
new reading, it is on screen within a second. A window that has just reset is
never shown as full any more.

And the session's name is no longer repeated over its own terminal — the tab
and the bar above already say it.

0.99.0 — the sessions of a folder, current and counted once

• The sessions of a folder are answered by the service, with both paths resolved: the window was comparing a session's folder as text against the same folder with its links resolved, which on a Mac never matches — so a session started in that very folder could be missing from its list.
• The list stays current instead of being read once when the page was built.
• One row per conversation: a running session and the transcript it is writing are no longer listed twice. Six finished ones, the rest named as being in the archive.
• "orphaned" is gone as a word. A session whose process went with a restart of plxr is over, and says so.
• Buttons built to look like rows of text no longer carry the browser's grey button face — that affected every such row in the window.

0.98.2 — the first click really counts now

• The first click into the window from another application counts. The previous attempt answered for the wrong view: AppKit asks the innermost view the click lands on, which inside a web view belongs to WebKit.

0.98.1 — the first click counts, and the picture follows the screen

• The first click into the window from another application now counts, instead of only waking the window.
• The picture follows the screen again: moved to another display, the web view lays out and rasterises afresh — without a scale being written into its layers, which is what took the smoothing off the text last time.

0.98.0 — the right account, in a size you can read

• The account shown over a terminal is the one its Claude is really signed in as. plxr believed the account it had picked when it started the shell; an alias that sets CLAUDE_CONFIG_DIR for one command put the CLI somewhere else, and the usage shown belonged to the untouched account. The hook runs inside that process and now says which account it is.
• The usage over the terminal is readable: a row per window with a full-width bar, the share used in words and when it comes back — inside the pane, at the window's own type size. An account with no reading says so in one line instead of showing two empty bars.
• Menu rows line up: whenever a list holds switches or marks, every row keeps room for one. The views menu carries its marks.
• A button that is on is filled, not outlined.
• Clicking into the window from somewhere else puts the keyboard in the terminal, unless the click landed on something that wants it — a field, a button, a list, a tab.

0.97.0 — a beta beside it, and LCARS as a file you bring

• A build can run beside the one holding your work: PLXR_CHANNEL gives it its own home, and ./bundle-macos.sh <version> beta makes a "plxr beta.app" that macOS treats as its own application.
• LCARS ships as an example theme (docs/themes/lcars.json) — a whole visual language brought in as one file, not compiled into the application.
• Antonio, an ultra-compressed grotesque, ships with plxr for looks that ask for one.
• Every typeface plxr ships is now named on the licences page with its licence text, which is what those licences ask for. Four of them had travelled unnamed since the first build.
• The settings panel asks for the themes and skins again whenever the looks are opened, so one that arrived since can be found.

0.96.0 — bring your own look, for real this time

• A theme file may carry the stylesheet that makes it. On import it becomes a skin of its own, named, listed beside the four that ship, and worn at once — one file is a whole look.
• The window loads a brought stylesheet from the service. Every piece of that path existed already; the window had never once asked for it.
• The skin picker lists what the service reports instead of four hard-coded names.
• What a theme asks for beyond colours is finally read: the typeface, the two sizes, and the four effect switches.
• EXPORT writes the look that is on back out as one file, stylesheet and all. There was no way to produce a theme file at all before.
• A brought stylesheet may not fetch anything: no @import, and url() only to what the daemon itself serves.

0.95.1 — a folder clicked in a terminal opens as a folder

• A folder clicked in a terminal opens as a folder: it becomes the project and the tree comes up on it, instead of a panel saying "that is a directory".
• Folders whose names have spaces in them can be clicked as well.

0.95.0 — the sessions arrange themselves

• LAYOUTS can spread every open session into a place of its own: as a row of columns, or as a rectangle when a row would leave them too narrow to read.
• Over each terminal stands the account that session spends: its name, the five-hour window and the week, each with a bar.
• A dialog's field no longer selects itself half a second after it opens, so what is typed into a rename stays typed.
• An account renamed answers to its new name at once, on the status row and over the terminal.
• A link clicked in a terminal opens in the browser. In the window there is nothing for window.open to make a tab in, so the daemon hands the address to the machine — http, https and mailto only.